Well, it is called Delegated Byzantine Fault Tolerant (dBFT) consensus mechanism .. it is similar to the EOS / STEEM / Bitshares proxy voting for bookkeepers (ie. witnesses) - the selected group reach consensus and produce blocks ..
Gas (or NeoGas) is earned by anyone who holds Neo, and this gas is used to utilize functions on the blockchain .. there is also a Council for strategic guidance .. answerable to the community, not dictating to it.
The thing that I feel differentiates is the clarity and purposefulness in implementation, that participants are welcomed and rewarded, and there is a degree of openness to potential developers, and facilitation that I have not seen with the other platforms.
I also excited about it, because I have some skills with C# from game creation that I am eager to use with this blockchain .. despite the benefits offered by webassembly in EOS, I have no desire to stumble around with C++ ..
So what kind of governance does NEO have compared to EOS?
Hello!
Well, it is called Delegated Byzantine Fault Tolerant (dBFT) consensus mechanism .. it is similar to the EOS / STEEM / Bitshares proxy voting for bookkeepers (ie. witnesses) - the selected group reach consensus and produce blocks ..
Gas (or NeoGas) is earned by anyone who holds Neo, and this gas is used to utilize functions on the blockchain .. there is also a Council for strategic guidance .. answerable to the community, not dictating to it.
The thing that I feel differentiates is the clarity and purposefulness in implementation, that participants are welcomed and rewarded, and there is a degree of openness to potential developers, and facilitation that I have not seen with the other platforms.
I also excited about it, because I have some skills with C# from game creation that I am eager to use with this blockchain .. despite the benefits offered by webassembly in EOS, I have no desire to stumble around with C++ ..
Good news for you ... Ruby will be supported! :-)