So if a full-fledged system is to be made from the instructions you have given here, how much time would it take for it to be made available to the public and what about the security of the chain?
You are viewing a single comment's thread from:
So if a full-fledged system is to be made from the instructions you have given here, how much time would it take for it to be made available to the public and what about the security of the chain?
In this configuration node will not be available to the public in other means than just being a part of Steem p2p network. It's a consensus node. In this configuration it can serve you as a simple API node (with subset of supported API calls), you can use it for example to broadcast transactions to the network.
To turn it into a public seed node, you need to add:
p2p-endpoint = 0.0.0.0:2001which will make it to listen on all interfaces on port 2001 (default p2p port for Steem)
and then let people know on a steem.chat's #seed-nodes channel that a new seed-node is in town ;-)
Static IP is required and some reliable hostname is obviously good to have.
It will take about 72 hours using that example hardware/software configuration to reach the head block.
When it finish replaying, its API endpoint will be available. You can use some proxy with SSL termination to make it available to the public too, but keep in mind that API is limited.
Such node might improve distribution of the system but it doesn't play the same role as in PoW networks.
Hoping this to change a bit on the next SMT model...
its not a standard thing...everyone will have its "crazy" things... I for example, would be more enterprise model... if I had the money to support it. Not that I could not do it with what I have (which I have done in the past)...
Everything depends... ask something more specific, and I might be able to shed some more light. If that's where you want to go.