@whotheff answers to your questions:
1. The jsecoin.com domain is currently a single point of failure. All the publisher traffic goes through it and it's used for the platform miners as well, all be it a subdomain and separate nodes. The vast majority of traffic goes through the Google load balancer that handles that domain name and then splits it off in different directions. If the website died then this wouldn't affect the publisher or platform system because they are separate. If that domain got hacked/stolen etc. then we would have to either figure out how to get it back or register a new domain and rebrand or something along those lines. It wouldn't be a good scenario. We will always need a point of discovery for the network, to mitigate risk however at a later stage it would be beneficial to divide this into multiple access points around the globe, perhaps even owned and managed by partners.
2. If you believe that Ethereum is real decentralzation or decentralized enough to meet your criteria then we will be fully integrating the ERC20 functionality in October so users can hold tokens in 3rd party wallets on Ethereums blockchain, transfer between wallets, deposit/withdraw to and from the platform. With the JSE network we need more volume before we open up the client-side consensus (end goal). We currently have around 20,000 concurrent active connections at any one time which wouldn't be enough to prevent a 51% attack from a large bot net. We could use the interim solution at any point which is actually coded and ready to go. Currently the nodes use trusted ECDSA signatures to prevent attacks but we could turn this off by changing one variable in the code base which would enable a standard consensus system using the node servers. We would need some incentive to 3rd parties to run the nodes and at enough scale to prevent abuse, PoS or something like that. Ideally I'd like to see the network get a huge influx of publisher traffic when we list on exchange and tokens become tradeable and hold a USD value. Then we can start work on rolling out the webRTC network in stages. It'll be a slow process and something we need to do lots of testing with. We have already run tests it in a local environment but this is very different to a real world scenario where funds are at stake. The client-side consensus algorithm will be up and running securely throughout the network in 2019, exact date I wouldn't like to say until we are closer to a finished product.
1. The jsecoin.com domain is currently a single point of failure. All the publisher traffic goes through it and it's used for the platform miners as well, all be it a subdomain and separate nodes. The vast majority of traffic goes through the Google load balancer that handles that domain name and then splits it off in different directions. If the website died then this wouldn't affect the publisher or platform system because they are separate. If that domain got hacked/stolen etc. then we would have to either figure out how to get it back or register a new domain and rebrand or something along those lines. It wouldn't be a good scenario. We will always need a point of discovery for the network, to mitigate risk however at a later stage it would be beneficial to divide this into multiple access points around the globe, perhaps even owned and managed by partners.
2. If you believe that Ethereum is real decentralzation or decentralized enough to meet your criteria then we will be fully integrating the ERC20 functionality in October so users can hold tokens in 3rd party wallets on Ethereums blockchain, transfer between wallets, deposit/withdraw to and from the platform. With the JSE network we need more volume before we open up the client-side consensus (end goal). We currently have around 20,000 concurrent active connections at any one time which wouldn't be enough to prevent a 51% attack from a large bot net. We could use the interim solution at any point which is actually coded and ready to go. Currently the nodes use trusted ECDSA signatures to prevent attacks but we could turn this off by changing one variable in the code base which would enable a standard consensus system using the node servers. We would need some incentive to 3rd parties to run the nodes and at enough scale to prevent abuse, PoS or something like that. Ideally I'd like to see the network get a huge influx of publisher traffic when we list on exchange and tokens become tradeable and hold a USD value. Then we can start work on rolling out the webRTC network in stages. It'll be a slow process and something we need to do lots of testing with. We have already run tests it in a local environment but this is very different to a real world scenario where funds are at stake. The client-side consensus algorithm will be up and running securely throughout the network in 2019, exact date I wouldn't like to say until we are closer to a finished product.
Thanks for the thorough reply! When I try to question a coin's fundamentals, they usualy delete my post.
While with JSEcoin, I even get a detailed explanation!
Which is why I'm certain I did the right choice with you guys!
The attitude of developers JSEcoin to users is respect. This was the first reason why I considered this project promising a year ago.
Now I'm most worried about the lack of interest in ICO. As if the lack of money did not affect the implementation of ambitious project plans.
