From: AdamISZ <AdamISZ@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] PathCoin
Date: Mon, 24 Jan 2022 14:43:53 +0000 [thread overview]
Message-ID: <jMANAdspMdPb1ZCFttQ3tGmkZ0oYojLY5Oz1d8ZSNl3JhZeDuT1xK0vxTu8uyHcgPXWsM_6XNb3R9tVD3_Yez88pviFrCaNt7LPqdWVBWus=@protonmail.com> (raw)
Hello list,
I took the time to write up this rather out-there idea:
Imagine you wanted to send a coin just like email, i.e. just transfer data to the counterparty.
Clearly this is in general entirely impossible; but with what restrictions and assumptions could you create a toy version of it?
See this gist for a detailed build up of the idea:
https://gist.github.com/AdamISZ/b462838cbc8cc06aae0c15610502e4da
Basically: using signature adaptors and CTV or a similar covenant, you could create a fully trustless transfer of control of a utxo from one party to another with no interaction with the rest of the group, at the time of transfer (modulo of course lots and lots of one-time setup).
The limitations are extreme and as you'd imagine. In the gist I feel like I got round one of them, but not the others.
(I very briefly mention comparison to e.g. statechains or payment pools; they are making other tradeoffs against the 'digital cash' type of goal. There is no claim that this 'pathcoin' idea is even viable yet, let alone better than those ideas).
Publishing this because I feel like it's the kind of thing imaginative minds like the ones here, may be able to develop further. Possibly!
waxwing / AdamISZ
next reply other threads:[~2022-01-24 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 14:43 AdamISZ [this message]
2022-01-25 11:53 ` Billy Tetrud
2022-01-25 12:50 ` AdamISZ
2022-01-28 15:27 ` Billy Tetrud
2022-01-29 17:16 ` AdamISZ
2022-01-30 15:39 ` Billy Tetrud
2022-02-20 18:26 ` AdamISZ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jMANAdspMdPb1ZCFttQ3tGmkZ0oYojLY5Oz1d8ZSNl3JhZeDuT1xK0vxTu8uyHcgPXWsM_6XNb3R9tVD3_Yez88pviFrCaNt7LPqdWVBWus=@protonmail.com' \
--to=adamisz@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox