From: Jonas Nick <jonasd.nick@gmail.com>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] P2QRH / BIP-360 Update
Date: Wed, 26 Feb 2025 08:08:50 +0000 [thread overview]
Message-ID: <69ab395f-acba-4d11-87ee-9da6327509c6@gmail.com> (raw)
In-Reply-To: <8e1cf1b5-27d1-4510-afec-52fb28959189n@googlegroups.com>
> it would require an extraordinary amount of computation to wind up with enough
> to store arbitrary data.
I have no idea why this would require extraordinary amount of computation. In
the example I provided, arbitrary data can be included in the attestation
structure with zero additional computational cost, no elliptic curve grinding or
hash collisions required.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/69ab395f-acba-4d11-87ee-9da6327509c6%40gmail.com.
next prev parent reply other threads:[~2025-02-26 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 15:40 [bitcoindev] P2QRH / BIP-360 Update Hunter Beast
2025-02-19 17:23 ` Dustin Ray
2025-02-19 22:57 ` Hunter Beast
2025-02-20 22:11 ` Matt Corallo
2025-02-23 20:33 ` Hunter Beast
2025-02-26 19:02 ` Matt Corallo
2025-02-28 4:19 ` Dustin Ray
2025-02-21 8:54 ` Jonas Nick
2025-02-23 20:58 ` Hunter Beast
2025-02-24 13:17 ` Jonas Nick
2025-02-25 18:03 ` Hunter Beast
2025-02-26 8:08 ` Jonas Nick [this message]
2025-02-24 16:12 ` Ian Quantum
2025-02-26 0:03 ` Tim Bratton
[not found] ` <CABfMNdKy6U+nLbq-nwK53_yiguxqanF1jexYHLGLMyef9cG1mw@mail.gmail.com>
2025-02-25 16:54 ` Hunter Beast
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=69ab395f-acba-4d11-87ee-9da6327509c6@gmail.com \
--to=jonasd.nick@gmail.com \
--cc=bitcoindev@googlegroups.com \
/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