-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Double spending ? #23
Comments
Same issue as you, I think it's a bug. |
Okay, but do you have any solution for the case? |
Sorry, I only treat it as a tutorial and give it up... |
It's just a tutorial. In real bitcoin, there need 6 more confirms to write blocks to chain. |
As you can see, transaction input (598b4e12b0bd16e87f7cdd108a4361c27c147e943fe7742a807dd3d8d0a7f2db) was used 2 times.
Assume I have 3 wallets: A(10 coins), B(0 coins), C(0 coins). then i'm trying to send from A -> B(1 coins) and A -> C(2 coins).
first transaction: A -> B (1 coins) and A -> A (9 coins)
second transaction: A -> C (2 coins) and A -> A (8 coins)
that will result A will have 17 coins instead of having only 7 coins left.
A(17 coins), B(1 coin), C(2 coins) ??
P.S. both transactions happened in NODE_ID=3001
P.S.2 NODE_ID=3002 was miner node.
The text was updated successfully, but these errors were encountered: