Arguable. Emunie doesn't have the delegates system you have, but is truly and fully decentralized.
It's depends from that you mean under
fully decentralized, Bitcoin also was designed to be fully decentralized but today you have 3 pools which have more that 50% hashing power.
Today BitShares has 101 block signers (delegates) in 2.0 it's will be configurable without hard fork, so if shareholders will decide to have more decentralization they can vote to 1001 delegate.
Bitcoin has 3+ block signers, Ripple has 7, BitShares has 101, Nxt has 700+, eMunie - potentially unlimited like Bitcoin?
I guess fuserleer meant as in fully decentralized, like when Bitcoin was still at the CPU mining stage of its development. But let's wait for him to drop by and explain.
Correct, there are no super-nodes, delegates or anything of the sort and never will be. There are no blocks and there is no mining so supply distribution is 100% fair. Consensus is achieved via a different algorithm which I posted about here a while ago.
Bitshares doesn't count, as its not a fully decentralized transactional system
by design, and even if it was I doubt those claims are anywhere near possible in the real world.
In these videos that everyone keeps posting he says "to keep everything in memory". How much memory do you think you need to keep pace with a days worth of 100,000 transactions per second in there?
He claims that the minimum tx size is something like 120 bytes so thats 120*100000*86400 bytes of transactional data per day, if you are keeping that in memory then it's near as damn it 1TB of RAM.
Now you probably dont need *that* much, but if you are order matching, then you need to have at least a large portion of recent transactions, a couple of hours worth maybe so that you can successfully match old buys/sells that haven't been matched yet to new ones.
What happens if you need to go to disc for a few 100,000 that arent in RAM......dead......that 100,000 tps turns into 1000 tps as soon as you start hitting discs.
In another video he says they made a 1M tx ledger, loaded it to RAM and processed it in 10 secs. I could load a 1M eMunie ledger to RAM and re-process it in rapid time too. The problem is constantly getting it into RAM and getting it back out again.
Whats the best write speed on PCI SSDs atm, about a gig per sec? so it takes 1000 seconds to get a days worth of data that might be in RAM to/from disc best case. If you do it on demand then that 100,000 tps disappears.
What about ACID compliance too, if everything is in RAM what if that machine suddenly crashes, or has a power outage? What if it was the only machine in the delegate list that had some of the very most recent transactions and hadn't forwarded them yet?
Furthermore I am suspicious that this 100,000 tps only applies to its order matching and not general transactions. How can 120 bytes store TXID, sender/receiver, signature, value, asset type and the inputs, it doesn't fit.
For the record I'm not well versed in how Bitshares works, nor am I going to spend the precious time to learn its innards, I'm just going on what I've casually read here and common sense.