From: Gregory Maxwell <greg@xiph•org>
To: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] The first successful Zero-Knowledge Contingent Payment
Date: Fri, 26 Feb 2016 23:45:03 +0000 [thread overview]
Message-ID: <CAAS2fgRTMoeC2sa-Hzr44amqZ16tyNUcLXxbN0W4tSfzr7Z0pw@mail.gmail.com> (raw)
In-Reply-To: <CAE-z3OVpd99Xyd9xenJir=7qfr4KOx=_hDpKtEKzAqtzteNMyQ@mail.gmail.com>
On Fri, Feb 26, 2016 at 11:33 PM, Tier Nolan via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> That is very interesting.
>
> There has been some recent discussion about atomic cross chain transfers
> between Bitcoin and legacy altcoins. For this purpose a legacy altcoin is
> one that has strict IsStandard() rules and none of the advanced script
> opcodes.
One might wonder why anyone would want to own coins that couldn't keep
up technologically, but to each his own. (especially one defunct
enough that it can't even update IsStandard rules...)
I don't think it's infeasible to do the EC multiply in a snark, but an
efficient implementation would be a lot of work. You'd probably want
to build a circuit for the field operations using 128 bit operations.
Fortunately the overall operation is pretty easy to directly convert
into a circuit (e.g. no branching).
Why not use the single-show-signature scheme I came up with a while
back on the Bitcoin side to force the bitcoin side to reveal a private
key?
http://lists.linuxfoundation.org/pipermail/lightning-dev/2015-November/000344.html
next prev parent reply other threads:[~2016-02-26 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 21:42 Gregory Maxwell
2016-02-26 23:06 ` Sergio Demian Lerner
[not found] ` <CAAS2fgT8RE7w87Yv9Be7arH-xGCtwcq0Ynbk21ZVpqJZrEN5EQ@mail.gmail.com>
2016-02-26 23:23 ` [bitcoin-dev] Fwd: " Gregory Maxwell
2016-02-26 23:33 ` [bitcoin-dev] " Tier Nolan
2016-02-26 23:45 ` Gregory Maxwell [this message]
2016-02-26 23:56 ` Tier Nolan
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=CAAS2fgRTMoeC2sa-Hzr44amqZ16tyNUcLXxbN0W4tSfzr7Z0pw@mail.gmail.com \
--to=greg@xiph$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tier.nolan@gmail$(echo .)com \
/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