From: Robin Linus <robin@zerosync•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Some Day Peg: A crazy two-way peg bridging BTC to other chains Raw
Date: Thu, 22 Jun 2023 13:49:41 +0200 [thread overview]
Message-ID: <F24818BB-2D29-44FE-9020-EA2EFDD2E55A@zerosync.org> (raw)
In-Reply-To: <A291D224-2C72-4A30-AB95-56DB79221E3A@zerosync.org>
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
Hi all,
Here's an interesting but not-so-serious attempt to implement a two-way peg in Bitcoin Script.
https://gist.github.com/RobinLinus/1102fce176f3b5466180addac5d26313 <https://gist.github.com/RobinLinus/1102fce176f3b5466180addac5d26313>
-Robin
[-- Attachment #2: Type: text/html, Size: 1505 bytes --]
parent reply other threads:[~2023-06-22 11:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <A291D224-2C72-4A30-AB95-56DB79221E3A@zerosync.org>]
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=F24818BB-2D29-44FE-9020-EA2EFDD2E55A@zerosync.org \
--to=robin@zerosync$(echo .)org \
--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