New answers tagged

1

Let's go over this step by step. Suppose say you want to lock some bitcoins in a 2-of-3 multi-sig. Locking steps Create a multi-sig script: OP_2 <pub_key 1> <pub_key2> <pub_key3> OP_3 OP_CHECKMULTISIG. Hash the multi-sig script with HASH160 which gives you multi-sig_scripthash. Base58Check the multi-sig_scripthash with version 0x05 ...


4

Let's run through the program. The stack starts as <A sig> <A pubkey>. You run OP_DUP. The stack is now <A sig> <A pubkey> <A pubkey>. You run OP_HASH160. The stack is now <A sig> <A pubkey> <A pubkeyhash>. You push (A expected pubkeyhash). The stack is now <A sig> <A pubkey> <A pubkeyhash> &...


0

Your question is a nice thought experiment. Your example would not itself work: as CHECKSEQUENCEVERIFY is relative to the mining date or height, so in week 3, all three parties could sign at the same time. On day 1 things work as you intend. On day 8 'X' can now sign at any point without delay but must wait a week for Y and two for Z. On day 15, 'X' and '...


3

It has always been the case that the full Bit Machine would be "exposed"[1] by allowing arbitrary Simplicity. This is because the combinators that let you compose the high-level jets are exactly the same combinators that define low-level Simplicity. Thus even if only a few high-level jets are chosen to be exposed, it would still be the case that the low-...


Top 50 recent answers are included