-
Discussion group 6 agreed largely with these notes I'd made about this section of the BIP; I would PR but I don't think that's appropriate, since it's kind of central to what the author(s) are writing…
-
Review comment by @gmaxwell.
The text is clear about it having precedence over the 520 byte limit, but not that it also overrides the 1000 stack element limit and other things.
-
A few observations on things that confused workshop particiapnts:
- `OP_RIPEMD160` is an unusual opcode. I think `OP_HASH160` is more commonly used (eg lightning HTLCs use `OP_HASH160`). We should …
-
Review comment by @gmaxwell:
Even without MuSig, due to the signature hash committing to the tapleaf hash, signers must commit up front to the exact subset that will be signing. That means you can't …
-
Review comment by @gmaxwell.
I believe the reason is that turning them into success would complicate some forms of debugging. Script disassembles will likely continue to disassemble these opcodes as …
-
Review comment by @gmaxwell.
-
Review comment by @gmaxwell.
-
**problem**: files tracked by the VCS should not be overwritten or changed by tests or tools if not explicitly called by the user. This is confusing users and means that the change needs to be ignored…
okurz updated
7 years ago