-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Sending transaction with mineNow = false. #32
Comments
Also this case creates block with 2 transactions (after I fixed Hash() function), but the second one didnt change Sender output Value. |
I'm stuck at this problem too. |
@fe1t Yes, I will investigate the core of this problem. I did not fork this repo, I created my own repo based on this tutorial with my features. So perhaps, I will fork this repo and create PRs. |
@fe1t I will add Timestamp field to Transaction. Then I will fix handleTx() in case if len(mempool) >= 2. I think that we should recheck transactions (txs) that were created before by some algorithm. |
@fe1t Unfortunately this bug is huge, we should also fix Sign/Verify when rechecking transactions, also we cant Find or Verify transaction before adding block with them, because they are not present in the blockchain. So now I just fix len(mempool) >= 1, but it is workaround just for simple testing. |
If you try to send transaction with mineNow = false from same wallet (address) 2 times, you got 2 transactions with same transaction hash, because NewUTXOTransaction will create identical Transaction structs.
My solution works with adding some salt:
The text was updated successfully, but these errors were encountered: