Re: [bitcoin-dev] Combined CTV+APO to minimal TXHASH+CSFS

2023-08-23 Thread Brandon Black via bitcoin-dev
> > * If the top item on the stack is not a minimally encoded `OP_0`, `OP_1`, > or > `OP_2`; succeed immediately[^2]. > > I presume this was supposed to go to OP_4 now. Fixed, thanks! > > ### How does the efficiency compare to [bip118][]? > > Just noting BIP118 also allows pubkey of "1" to

Re: [bitcoin-dev] Combined CTV+APO to minimal TXHASH+CSFS

2023-08-23 Thread Brandon Black via bitcoin-dev
Quick update to the proposal thanks to James O'Beirne: CTV is 2-bytes less expensive than I thought when used alone. I thought that script success required exactly OP_TRUE not just a CastToBool()=true value on the stack. This means that my proposal is 2 weight units (0.5vBytes) larger than CTV

Re: [bitcoin-dev] Combined CTV+APO to minimal TXHASH+CSFS

2023-08-22 Thread Greg Sanders via bitcoin-dev
Hi Brandon, Not going to dive too deep here, just adding a bit of color. > * If the top item on the stack is not a minimally encoded `OP_0`, `OP_1`, or `OP_2`; succeed immediately[^2]. I presume this was supposed to go to OP_4 now. > ### How does the efficiency compare to [bip118][]? Just

[bitcoin-dev] Combined CTV+APO to minimal TXHASH+CSFS

2023-08-22 Thread Brandon Black via bitcoin-dev
Hi list, https://gist.github.com/reardencode/2aa98700b720174598d21989dd46e781 I'm seeking feedback on this proposal to provide the functionality requested by those advocating for bip118 and bip119 in a combined way that retains the low risk associated with each of those separate proposals. At