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

Hacking Double-spending #2582

Closed
ghost opened this issue Feb 15, 2019 · 2 comments
Closed

Hacking Double-spending #2582

ghost opened this issue Feb 15, 2019 · 2 comments

Comments

@ghost
Copy link

ghost commented Feb 15, 2019

I'm wondering how did you get around the problem with double spending?

If I rewrite your wallet source code and compile a unique version, can I spend my coins more than once?

https://www.reddit.com/r/Mimblewimble/comments/56heys/can_mimblewimble_prevent_double_spends/

@rsoltanzadeh
Copy link
Contributor

Cut-through can be done on-chain as well. This is a 0-conf issue rather than a cut-through one.

@antiochp
Copy link
Member

Agreed. I think the issue described in that reddit post is around 0-conf.
We handle this at the wallet level by requiring (by default, but configurable) a minimum of 10 confirmations (taking approx 10 minutes) before coins are treated as "confirmed" and spendable.

can I spend my coins more than once?

No. You can make two conflicting txs that both attempt to spend the coins. But only one will make it onto the chain with enough confirmations to be treated as "confirmed" by other wallets.

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

2 participants