From: Adam Back <adam@cypherspace•org>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] one-show signatures (Re: The relationship between Proof-of-Publication and Anti-Replay Oracles)
Date: Sun, 21 Dec 2014 18:10:47 +0000 [thread overview]
Message-ID: <CALqxMTFK_sxdFjVi0qAC0JMdXa=tVBBNp0VrveRUfwa3b1UYhw@mail.gmail.com> (raw)
Yes you could for example define a new rule that two signatures
(double-spend) authorises something - eg miners to take funds. (And
this would work with existing ECDSA addresses & unrestricted R-value
choices).
I wasnt really making a point other than an aside that it maybe is
sort-of possible to do with math what you said was not possible where
you said "This [preventing signing more than one message] is
impossible to implement with math alone".
Adam
On 21 December 2014 at 15:29, Peter Todd <pete@petertodd•org>
> There's no need to get into the specifics of crypto math so early; you
> can just as easily and only slightly less efficiently obtain the same
> result with a few extensions to the Bitcoin scripting system to verify
> ECDSA signatures directly.
next reply other threads:[~2014-12-21 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 18:10 Adam Back [this message]
2014-12-21 18:51 ` Peter Todd
2014-12-22 0:56 ` paul snow
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='CALqxMTFK_sxdFjVi0qAC0JMdXa=tVBBNp0VrveRUfwa3b1UYhw@mail.gmail.com' \
--to=adam@cypherspace$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pete@petertodd$(echo .)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