New answers tagged transaction-malleability
0
One of the standardness rules (relay rules) in Bitcoin Core is that the scriptSig must contain only operations that push data to the stack. Since you have actual opcodes that do non-push things, this transaction is non-standard so your node is not accepting it.
On regtest, you can disable standardness checks by adding -acceptnonstdtxn to your startup ...
2
What malleability means is that you can create a transaction that is identical in its meaning (same inputs, same outputs) but with a different TXID. That is problematic for 2nd layer protocols where transactions build onto each other but aren't necessarily published to chain.
But a "malleated" transaction is still a double spend. And it appears newer ...
Top 50 recent answers are included
