Good morning kim,
An issue with covenants is that the only "good" use case so far is vaults.
Indeed, what you originally gave as a usecase in your first email is in fact a
vault.
Here is gmax original bitcointalk post:
https://bitcointalk.org/index.php?topic=278122.0
Since covenants
Hi ZmnSCPxj,
Thanks for the heads up and suggestions.
Found my way to the bitcoin-covenant article. That is indeed generalized
and flexible, hence more powerful than this dumbed-down plain comparison of
output bytes-to-bytes.
Interestingly, the vault described in bitcoin covenant, which can
Good morning kim,
This seems to be a specific instance of "covenants". I believe, that there are
vague plans to possibly include OP_CHECKSIGFROMSTACK, which would allow
covenants much more generally, but with more complex (clever) SCRIPT.
The specification of the behavior of the opcode is
Discussing the possibility of a new opcode (OP_CHECKTXOUTSCRIPTHASHVERIFY)
for the Bitcoin scripting system that allows a transaction output to be
only spendable in a predefined manner.
*Brief Description*
Bitcoin transactions have a txoutScript (scriptPubKey) field for each
output.
