You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we have to build valid SingleProofs everytime we build a transaction that goes into a block, tests of this logic are either inflexible, as proof have to be stored on a proof server, or they're very slow.
The function mine_block_to_wallet_invalid_block_proof should not just make invalid block proofs but also invalid transaction proofs, for both merged transactions and for coinbase transactions.
The text was updated successfully, but these errors were encountered:
Allow caller to specify proof quality of coinbase transaction. This
change has the benefit of allowing tests that do need coinbase
transactions but not necessarily with valid proofs.
This closes#242.
Co-authored-by: Thorkil Schmidiger <thor@neptune.cash>
Allow caller to specify proof quality of coinbase transaction. This
change has the benefit of allowing tests that do need coinbase
transactions but not necessarily with valid proofs.
This closes#242.
Co-authored-by: Thorkil Schmidiger <thor@neptune.cash>
Since we have to build valid
SingleProof
s everytime we build a transaction that goes into a block, tests of this logic are either inflexible, as proof have to be stored on a proof server, or they're very slow.The function
mine_block_to_wallet_invalid_block_proof
should not just make invalid block proofs but also invalid transaction proofs, for both merged transactions and for coinbase transactions.The text was updated successfully, but these errors were encountered: