Mar 19, 2018

Hmm, this is new to me: I am now looking at https://github.com/libbitcoin/libbitcoin/blob/master/include/bitcoin/bitcoin/impl/machine/operation.ipp#L212-L219 So data lengths beyond 0x4b will require a preceding opcode OP_PUSHDATA1 , OP_PUSHDATA2 depending on the data size? I will have a closer look to better understand the multiple possible mappings you mentioned. But there are still 2 observations I cannot explain: 1) Looking at a P2SH(P2WSH) example from the BIP143 proposal, I noticed the [witnessScript] data in the witnessScript simply has a preceding cf to indicate the number of following data bytes, but no OP_PUSHDATA. I noticed cf>4b. 2) When I try to pass the script object /w the data operation OP_PUSHDATA1 to the witness object: witness my_witness(script.to_data(false), false);, it remains empty. Witness objects constructed from scripts with simple data pushes, such as [number of bytes][data bytes], work fine. Based on the BIP143 example and my troubles with the above witness object, I am guessing the witness doesn't work with the OP_PUSHDATA opcode. Could that be? Thanks in advance!