bip-0325: clarify the OP_TRUE challenge special case
While `OP_TRUE` challenges have been implicitly accepted until now, it was never defined exactly how these should be solved. This adds an exception for the case where the challenge is `OP_TRUE`, that the solution must be *absent*. I.e. not even an empty signet commitment may be present, or the block should be considered invalid. Pros: this means a signet node with challenge `OP_TRUE` works *exactly the same* as testnet/mainnet, in terms of block generation (i.e. `generate*` RPC functions in Bit
No reviewsSpecification
While OP_TRUE challenges have been implicitly accepted until now, it was never defined exactly how these should be solved. This adds an exception for the case where the challenge is OP_TRUE, that the solution must be absent. I.e. not even an empty signet commitment may be present, or the block should be considered invalid.
Pros: this means a signet node with challenge OP_TRUE works exactly the same as testnet/mainnet, in terms of block generation (i.e. generate* RPC functions in Bitcoin Core can be used out of the box).
Discussion (0 threads)
Loading discussions...