How would this prevent a flood attack ? What I mean is in Bitcoin and presumably Stellar, you need coins to create transactions. There is therefore a cost to spamming the system.
It's interesting that it says that "Warning: Requires Postgres 9.5. You WILL lose sync if you run against an earlier version. YOU HAVE BEEN WARNED."
Which PostgreSQL features new in 9.5 are being used that cause that? Or are earlier versions somehow buggy?
> Transactions are FREE (the fee is always zero)
How would you deal with DDoS attacks? Taking down a ledger like this could be easy...
How is it protected from Sybil attacks on consensus algo? The algo description is definitely needed.
Is there any interesting lecture that got you this far or did you study source code?
Check out https://morph.is/v0.8/ if you haven't seen it, decentralized encrypted file storage and email, exciting stuff.
Cool. I really liked the idea of Stellar, but I just cant get over the premined coin distribution. Nice to have a truly decentralized alternative!
Basically, `Bitcoin - Politics`. A nice idea.
Needs a brief documentation "how it works" or something... I really don't understand the concept, I'm very familiar with bitcoin and somewhat familiar with ripple/stellar. How is the ledger maintained? How do we form the consensus on the valid ledger? What are the incentives for running nodes? etc.