-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRDT & blockchain comments #3
Comments
Thanks @gritzko -- i will read the thread more and write out my thoughts. But more importantly, i will read your paper. It sounds very exciting 😄 |
I gave this a quick once over, this doesn't provide Byzantine Agreement. Nor does the punishment model provide any sort of Sybil resistance. This model was interesting to think about, but it doesn't seem to provide any protection in an adversarial environment. |
@AFDudley that is exactly the point. This is exactly the point with everything eventually consistent, e.g. Amazon Dynamo: it is already good enough. Making it perfect is so insanely expensive that it makes it actually much worse in price/performance terms. The idea is: make coin splits a possibility which is less than the rounding error. There are much more significant real-world risk factors which can not be physically eliminated anyway. |
If the point of this is to run it in a federated context, that's cool it's a lot more interesting in that regard, I still don't like the blame model though. |
I like the approach, but the challenge is to assure economic security against double spends, especially given a globally active network adversary. Pushing all the validation to the edges is reminiscent of what Eg Peter Todd has been advocating for in a scalability context, but it remains to be seen how the economic security guarantees can be preserved. Perhaps some mix of an atomic broadcast backbone which can manage and slash security deposits combined with this sort of coin-consistency-only-at-the-edges could work. Punishment in IP space alone (ie evicting peers) is almost certainly not enuf to secure a real coin. Entanglement matrix only seems to work if peers reliably sign everything and pass it on . But byzantine peers can't be relied on to do that. |
Sorry for slow responses, I am vacationing right now. I mentioned Hawala as an inspiration for the proposal. Hawala is honor-based: you have your life's business and income (and your children are likely to inherit that), iff you behave well. Mandatory signing is a purely technical thing, it can be mandated at the protocol level (ops are not accepted unless signed). Thanks for the questions, I do my best to extend the docs based on the feedback. |
@AFDudley I added a discussion on the general approach https://gritzko.gitbooks.io/swarm-the-protocol/content/coin.html#the-general-approach |
@gritzko Quite surprised IOTA (https://www.iotatoken.com) never popped in the discussion. Their approach look extremely similar to what Swarm split-coin proposes. @AFDudley Could your comment on peer identity and sybil resistance be applied to IOTA as well, by the way? |
@ukstv It popped in another discussion I recently had. IOTA is DAG-based, but it relies on "truth as the longest history branch", i.e. implicit voting. "Swarm coin" has no voting. Also, S.Popov is a mathematician, so their whitepaper is rather light on logistical details. That's all I can say at the moment. |
Migration of this thread:
https://twitter.com/juanbenet/status/748991617495859201
The text was updated successfully, but these errors were encountered: