📅 Original date posted:2022-07-24
📝 Original message:On Wed, Jul 20, 2022 at 2:46 PM Antoine Riard via bitcoin-dev <
bitcoin-dev at 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 following use-cases: multi-party
> stateful contracts [11], congestion trees [12], payment pools [13], "eltoo"
> layered commitments [14], programmable vaults [15], multi-events contracts
> [16], blockchain-as-oracle bets [17], spacechains [18], trustless
> collateral lending [19], ...
>
The big question you missed is whether capabilities are in scope for a
covenants proposal. In particular, vaults work a lot better when payments
to them are immediately locked up in the vault rather than it having to do
a step to accept them first.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220724/37c519d3/attachment.html>;
Bram Cohen [ARCHIVE] /
npub1ld…t8ur6
2023-06-07 23:12:06
in reply to nevent1q…pu5j
Author Public Key
npub1ldcq03p2qe58u0xnlwa35wchjuhz49y6ueu5ghmtjetez9xstnvsmt8ur6Published at
2023-06-07 23:12:06Event JSON
{
"id": "f59c01d08573f77e4ad07a8bbefdefe4ae6854b2ae6a3300ca6491ae7177e1fc",
"pubkey": "fb7007c42a06687e3cd3fbbb1a3b17972e2a949ae679445f6b96579114d05cd9",
"created_at": 1686179526,
"kind": 1,
"tags": [
[
"e",
"32278431461b2aef74d3e0bd3f2c67c0cb2a1196ed72c760c4d2cf2b42931ee2",
"",
"root"
],
[
"e",
"70aa11ebcb12a4f14a5877e17dff39c8ab08377d7b4e591333e4c31229f49b5b",
"",
"reply"
],
[
"p",
"6485bc56963b51c9043d0855cca9f78fcbd0ce135a195c3f969e18ca54a0d551"
]
],
"content": "📅 Original date posted:2022-07-24\n📝 Original message:On Wed, Jul 20, 2022 at 2:46 PM Antoine Riard via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Indeed this range has grown wild. Without aiming to be exhaustive (I'm\n\u003e certainly missing some interesting proposals lost in the abyss of\n\u003e bitcointalk.org), we can mention the following use-cases: multi-party\n\u003e stateful contracts [11], congestion trees [12], payment pools [13], \"eltoo\"\n\u003e layered commitments [14], programmable vaults [15], multi-events contracts\n\u003e [16], blockchain-as-oracle bets [17], spacechains [18], trustless\n\u003e collateral lending [19], ...\n\u003e\n\nThe big question you missed is whether capabilities are in scope for a\ncovenants proposal. In particular, vaults work a lot better when payments\nto them are immediately locked up in the vault rather than it having to do\na step to accept them first.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20220724/37c519d3/attachment.html\u003e",
"sig": "3edd75d449f672eebb84d81254332375d4ffe7f3195ee2012db28ed3b7b185d6db8c1ff1795bbd8deb0a7c76c2ee2a0c229e1921467113fb47a1e5f7921521b8"
}