Re: [bitcoin-dev] [PROPOSAL] OP_TX: generalized covenants reduced to OP_CHECKTEMPLATEVERIFY

2022-06-23 Thread Anthony Towns via bitcoin-dev
On Tue, May 10, 2022 at 08:05:54PM +0930, Rusty Russell via bitcoin-dev wrote: > OPTX_SEPARATELY: treat fields separately (vs concatenating) > OPTX_UNHASHED: push on the stack without hashing (vs SHA256 before push) > OPTX_SELECT_OUTPUT_AMOUNT32x2*: sats out, as a high-low u31 pair > OPTX_SELECT_

Re: [bitcoin-dev] Bitcoin covenants are inevitable

2022-06-23 Thread Peter Todd via bitcoin-dev
On Tue, Jun 21, 2022 at 01:00:07PM -0600, Keagan McClelland via bitcoin-dev wrote: > > The PoW security of Bitcoin benefits all Bitcoin users, proportional to > the > value of BTC they hold; if Bitcoin blocks aren't reliably created the value > of > *all* BTC goes down. It doesn't make sense for t

Re: [bitcoin-dev] Playing with full-rbf peers for fun and L2s security

2022-06-23 Thread Peter Todd via bitcoin-dev
On Tue, Jun 21, 2022 at 07:45:48PM -0400, Antoine Riard wrote: > > BTW I changed one of my OTS calendars to issue fee-bumping txs without the > > opt-in RBF flag set as an experiment. I also made sure txs would > propagate to > > the above node. As of right now, it's up to 32 replacements (once per