Good morning alia, Antoine, and list,
> Hi Antoine,
> Claiming Taproot history, as best practice or a standard methodology in
> bitcoin development, is just too much. Bitcoin development methodology is an
> open problem, given the contemporary escalation/emergence of challenges,
> history is no
I suppose it is more about spending from vaults, rather than locking in. A
covenant would impose rules for spending tx.e.g. :Don't spend this output
unless it is claimed by a tx which
1) Spends it as a whole in the very first output.
2) This output is P2SH with specified script pattern ( a TLC sc
On Wed, Jul 20, 2022 at 2:46 PM Antoine Riard via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Indeed this range has grown wild. Without aiming to be exhaustive (I'm
> certainly missing some interesting proposals lost in the abyss of
> bitcointalk.org), we can mention the followin
--- Original Message ---
On Saturday, July 23rd, 2022 at 9:11 PM, Antoine Riard via bitcoin-dev
wrote:
> Hi Michael,
>
> I'm thinking such a covenant effort would be more a technical process aiming
> to advance the state of covenant & contracting knowledge, collect and
> document the u
Hi Michael,
> One cautionary word from someone who is probably still feeling the
effects of burn out from the activation drama earlier in the year. No
process can guarantee community > consensus at the end of it especially if
some of those who we consider experts in this area only tentatively
part
