miniscript
miniscript copied to clipboard
sipa
Miniscript site and implementation
`pk()()` is considered a valid policy because it identifies `)(` as the name. Found via: [bitcoinfuzz](https://github.com/brunoerg/bitcoinfuzz)
The second policy example at https://bitcoin.sipa.be/miniscript/ "One of two keys (equally likely)" - `or(pk(key_1),pk(key_2)))` - compiles to `or_b(pk(key_1),s:pk(key_2))`. Should it not compile to `multi(1,key_1,key_2)` instead, which has the same witness...
The site currently says: "Fragments that do not change the semantics of their subexpressions are called wrappers." and a bit below it says "t:, l:, and u: wrappers are syntactic...
Fixes #126 When passing hex values to `ripemd160` and `hash160` as in: `hash160(aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa)` it will generate correct ASM: `OP_SIZE OP_EQUALVERIFY OP_RIPEMD160 OP_EQUAL` Not omitting the `` When using the special...
At https://bitcoin.sipa.be/miniscript/, if I enter this miniscript: `sha256(aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa)` I receive the expected script structure: ``` OP_SIZE OP_EQUALVERIFY OP_SHA256 OP_EQUAL ``` For hash160/ripemd160 however, the hash is missing in the script....
Should this link here: https://github.com/sipa/miniscript/blob/master/index.html#L114 Be pointing to: https://github.com/apoelstra/rust-miniscript Or this: https://github.com/rust-bitcoin/rust-miniscript The latter seems more appropriate, since the former is fork and hasn't been updated in ~2 years. Happy...
The maximum number of pubkeys allowed in a multisig are 20 as per consensus rules. The impementation performs this check, but the requirement was not documented in the table.
Not sure if it's worth trying to have an exhaustive list at the cost of missing some rules.
The malleability type properties for `thresh` on the website state: > s=at most k-1 are non-s; e=all are s for `e` it should say `e=all are e and all are...