From: Daniel Edgecumbe <esotericnonsense@esotericnonsense.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Graftroot: Private and efficient surrogate scripts under the taproot assumption
Date: Thu, 22 Feb 2018 11:44:21 -0800 [thread overview]
Message-ID: <1519328661.898070.1280084352.71F1C1C3@webmail.messagingengine.com> (raw)
In-Reply-To: <CAMnpzfo3pL0EB1HyzHO1sEiauGarRUHaWOG-pzMe40wBsGiN3g@mail.gmail.com>
> However, the non-interactive schnorr aggregation trick[1] can be
applied to merge the S values of all graftroots and signatures in a
transaction into a single aggregate. With this approach only a single
R value for each graftroot need be published, lowering the overhead to
~32 bytes-- the same as taproot. This has a side benefit of binding
the published grafts to a particular transaction, which might help
avoid some screwups.
I don't think that binding grafts to a particular transaction requires this aggregation.
It seems to me that you could just sign H(txid, script) rather than H(script).
I'm not aware of whether this would break aggregation.
---
Daniel Edgecumbe / esotericnonsense
esotericnonsense@esotericnonsense.com
https://esotericnonsense.com
https://danedgecumbe.com
next prev parent reply other threads:[~2018-02-22 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 5:58 [bitcoin-dev] Graftroot: Private and efficient surrogate scripts under the taproot assumption Gregory Maxwell
2018-02-05 15:56 ` Ryan Grant
2018-02-05 19:58 ` Gregory Maxwell
2018-02-09 7:29 ` Jeremy
2018-02-09 7:42 ` Jeremy
2018-02-22 12:19 ` Ryan Grant
2018-02-22 19:44 ` Daniel Edgecumbe [this message]
2018-02-24 18:58 ` Gregory Maxwell
2018-06-30 11:49 ` Sjors Provoost
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=1519328661.898070.1280084352.71F1C1C3@webmail.messagingengine.com \
--to=esotericnonsense@esotericnonsense.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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