Skip to content
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

Compensate for conflicting transactions? #16

Open
amiller opened this issue Jul 13, 2017 · 0 comments
Open

Compensate for conflicting transactions? #16

amiller opened this issue Jul 13, 2017 · 0 comments

Comments

@amiller
Copy link
Owner

amiller commented Jul 13, 2017

If a client creates an N-way doublespend, but each node only sees one of them, then it is possible that this will not be noticed until all of them are committed.

The simplest thing to do is just reject all but the first transaction. That is, the transaction will be "committed" in the blockchain, but discarded after processing with no effect. However, this introduces a DoS vector because double-spends use up space, but are cheap. This could be related to #8 on variable size transactions.

One approach may be to require parties to reserve some "double spend insurance", which is collateral that can be taken in compensation in the case of a double-spend.

Unfortunately requiring this much collateral could require a lot of money. Is there a tradeoff here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant