11–20 of 28 posts
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 doesn't prevent a flood attack. The challenge in this approach does not lie in "preventing it" but in "dealing with it".
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.
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!
> Transactions are FREE (the fee is always zero) How would you deal with DDoS attacks? Taking down a ledger like this could be easy...
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!
What do you like about Stellar? It's not decentralized at all. Being premined is just the icing on the cake.
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?
I'm using upserts... The reason I'm using upserts is basically just lazyness because I didn't feel like refactoring the source code to work around requiring upserts. Also, I'm not very confident in C++ so I did not want to take on that task.
IF record EXISTS then UPDATE else INSERT