From: gladoscc <admin@glados.cc>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Uniquely identifying forked chains
Date: Sat, 29 Aug 2015 01:27:01 +1000 [thread overview]
Message-ID: <CAL7-sS1aMqrUzMEbiQUWuxFtVHGv+-is7-BeAuje3rfQs_-JeQ@mail.gmail.com> (raw)
In-Reply-To: <CAL7-sS3CaHvZxUb-Q6HagHYufYnko_T4TBoFhd31rr5OxaiAEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
There has been discussion of using the genesis block hash to identify
chains in BIP 21 (bitcoin:// URI scheme). However, this does not allow
identification between blockchain forks building upon the same genesis
block. While many see this as undesirable, I think it is inevitable that
this will eventually happen at some point, and think it is best to build
systems redundantly.
I propose identifying blockchains for BIP 21 and any other relevant needs
through:
1) the genesis block hash for a new chain, or
2) a hash of the genesis block hash, concatenated with block hash(es) of
fork point(s) for a fork chain
This would support forks, forks of forks, forks of forks of forks, etc
while preserving a fixed length chain identifier.
If a user wants to specify "whatever chain is the longest with PoW", they
would use (1). In times where multiple chains are coexisting and being
actively mined, a user can use (2) to specifically identify a chain.
Thoughts?
[-- Attachment #2: Type: text/html, Size: 1085 bytes --]
next parent reply other threads:[~2015-08-28 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL7-sS2mrBqM7w5T8mRBFvVrCaHy1zT1YsgrHUxRBqdTFqczow@mail.gmail.com>
[not found] ` <CAL7-sS3CaHvZxUb-Q6HagHYufYnko_T4TBoFhd31rr5OxaiAEw@mail.gmail.com>
2015-08-28 15:27 ` gladoscc [this message]
2015-08-28 20:15 ` [bitcoin-dev] Uniquely identifying forked chains Matt Whitlock
2015-08-28 20:45 ` Jorge Timón
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=CAL7-sS1aMqrUzMEbiQUWuxFtVHGv+-is7-BeAuje3rfQs_-JeQ@mail.gmail.com \
--to=admin@glados.cc \
--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