Hey all,
A good first step might be to express this as a research problem on
bitcoinproblems.org! I've had in mind creating a problem page on how to
design a PQ TR commitment in each key so that if QC were to become a
reality we could softfork to enable that spend (and disable normal key path
Hi Bitcoin Developers,
Since some emails get moderated, I wanted to share one python script that I
found useful.
Download eml file from moderated archives:
https://lists.ozlabs.org/pipermail/bitcoin-dev-moderation/
Install fast_mail_parser and use this python script:
As expected, I sent some wrong explanations regarding input selection.
The coin grouping and consolidation penalty seems to be correct, but I
was wrong about the final best group selection. Let me try to correct this.
There are often many groups which have the same consolidation penalty.
In
On Fri, Apr 8, 2022 at 4:33 PM Christopher Allen <
christoph...@lifewithalacrity.com> wrote:
> That being said, it is interesting research. Here is the best link about
> this particular approach:
>
> https://ntruprime.cr.yp.to/software.html
>
Also I think this is the original academic paper:
On Fri, Apr 8, 2022 at 2:36 PM Erik Aronesty via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> I'm not saying I endorse any action at all. Personally I think this is
> putting the cart like six and a half miles in front of the horse.
>
I have to agree that practical
