From: Karl-Johan Alm <karljohan-alm@garage•co.jp>
To: Gregory Maxwell <greg@xiph•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: shiva@blockonomics•co
Subject: Re: [bitcoin-dev] Testnet3 Reest
Date: Wed, 5 Sep 2018 12:00:39 +0900 [thread overview]
Message-ID: <CALJw2w6a2YMS=nso5_6Rsom8qgNt93me3sv7Gr1vrHNcrZOVHQ@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgSF=hx581aGUBVv6zardKG4gex43B-jZbAu0a9Rupg1WQ@mail.gmail.com>
On Fri, Aug 31, 2018 at 9:43 PM Gregory Maxwell via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> We looked at doing this previously in Bitcoin core and jtimon had some
> patches, but the existing approach increased the size of the
> blockindex objects in memory while not in signed testnet mode. This
> could probably have been fixed by turning one of the fields like the
> merkel root into a union of it's normal value and a pointer a
> look-aside block index that is used only in signed block testnet mode.
I am currently working on an implementation that simply puts a global
mapping of block hash to signature that is transparently
(de)serialized in the block header.
We were looking into various ways to stuff the signature into the
actual header itself without changing its size, but this looked like
it required truncating the prevblock/merkleroots and such, which
seemed a bit too invasive.
I don't think my approach with a global mapping to sig differs in any
meaningful way from your suggested union, but corrections welcome.
The code is here: https://github.com/kallewoof/bitcoin/tree/signet
I believe jtimon is interested in helping out, and Jeremy Rubin has
also said he wants to help.
prev parent reply other threads:[~2018-09-05 3:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 7:28 shiva sitamraju
2018-08-30 20:02 ` Peter Todd
2018-08-30 20:36 ` Jimmy Song
2018-08-30 20:44 ` Johnson Lau
2018-08-31 0:06 ` Gregory Maxwell
2018-09-01 14:47 ` rhavar
2018-09-05 3:00 ` Karl-Johan Alm [this message]
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='CALJw2w6a2YMS=nso5_6Rsom8qgNt93me3sv7Gr1vrHNcrZOVHQ@mail.gmail.com' \
--to=karljohan-alm@garage$(echo .)co.jp \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)org \
--cc=shiva@blockonomics$(echo .)co \
/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