Olaoluwa Osuntokun
Olaoluwa Osuntokun
Optimizations are certainly possible to speed things up or even modify the way we export data in general. Right now we just read everything then export over, things could be...
> Anyway, "as normal" is very ambiguous. Agree, just trying to capture that the pop still happens, will think of some better phrasing that better captures the semantics. When working...
> Anyway, "as normal" is very ambiguous. Updated to explicitly note that an element is popped from the stack. This matches the `OP_CHECKSIG` behavior that details what happens to the...
> I can see that it's possible to be confused if one is primed by the legacy implementation of CHECKSIGVERIFY in Core (which is presumably similar to btcd's). Here's my...
Discussed this on IRC w/ `sipa`, and I understand your PoV now @jonasnick: if you made an impl of `OP_CHECKSIGVERIFY` from scratch based on this spec, you'd implement things properly...
Transferred from the old `btcutil` repo.
Transferred from the old `btcutil` repo.
Transferred from the old `btcutil` repo.
Transferred from the old `btcutil` repo.
There's a bug here in that it doesn't detect mutations in the underlying `*wire.MsgTx` so if the value is changed at all, then we don't update the serialization. In the...