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

Vuln- Halt block production #390

Closed
hans-schmidt opened this issue Oct 18, 2018 · 0 comments
Closed

Vuln- Halt block production #390

hans-schmidt opened this issue Oct 18, 2018 · 0 comments
Assignees
Labels

Comments

@hans-schmidt
Copy link
Contributor

I have verified (the hard way- sorry) that on testnet6 I am able to crash mining and bring block production to a stop by issuing a single transaction.

Detailed analysis is inconvenient because I am unable to restart block production after I stop the chain.

Please see the following transaction which was issued immediately after Block 35441 on testnet6

Transaction ID:
62b06f969a9fb37d3ed69016229b5ef8d472521df2f9470cea3049148906e1ec

Raw Transaction:
0200000002cb32ecb6c826d89689e6a4d85996ef8ad8f5a626f659c69476f68d70aa9273c4000000006a473044022018f13d08d16a258c7d9f8b97985d6315162ef32971fa966f45474e7f4a53bff602203fa5f5506fcbb46b67e7d770a27545a0996f39d5b39d8734823c45803d907e230121024953231de4abe8f9fd7e0ed22e5ae935e2cbfba808470bd8accf4c6a5679af30ffffffffdcb98cb7aa71b1fc9a7399bbf8bcda051f23cbf131650151e07dceb7bad3c6f0010000006a47304402203585b3f0a8af6da2308d85d75b713982bbb0ffa57eaf4c14eb39b41a4162513d022006a994a042ba9f6b4ffef4252242bf3d095be0d81f0d6c18d087e2bc5923467a012103642b269e679909cb11129e1396dd447999a2e5847161bed5cbb9e5bc4a6b4e5fffffffff040065cd1d000000001976a914dda3d21797ff26cb8ae9a769bdc68cf4567f5bba88ace0c3c51d000000001976a914f268a63f4206864e8e8942a0bc0d6b1974ea021988ac00000000000000003476a9147f063ede633579e9adfcda985d70b735acfab97888acc01872766e740b524f4f545f4155544f312100e1f505000000007500000000000000004376a914129519f1af0d2a22ce827ee79786962edef66bbd88acc02772766e7116524f4f545f4155544f3123756e697175655f6d616e3100e1f50500000000000000007500000000

A mining crash occurred earlier in the day which required manual intervention to restart. Community members on Discord appeared to conclude that it was a different issue, but I believe that it was triggered by my Transaction ID 07b21adf9262410a68b08a6ba05377a61e7bd54b7f0c9ed370f8d4312836d6ad, which is equivalent to the transaction detailed above.

blondfrogs added a commit that referenced this issue Oct 18, 2018
@blondfrogs blondfrogs added the bug label Oct 18, 2018
@blondfrogs blondfrogs self-assigned this Oct 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants