From: "Jorge Timón" <jtimon@jtimon•cc>
To: Chun Wang <1240902@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] RFC - BIP: URI scheme for Blockchain exploration
Date: Sun, 30 Aug 2015 04:20:17 +0200 [thread overview]
Message-ID: <CABm2gDqNQEcm5CWE8Rb0p1NGk=9bzjeSh6DD84=qvJ9kk+uFYw@mail.gmail.com> (raw)
In-Reply-To: <CAFzgq-xvwZ+O0iLLAZoTWKMSaHAt+ZRyBe6dBdnLFEQYj=xVDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On Aug 29, 2015 7:02 PM, "Chun Wang via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> On Sun, Aug 30, 2015 at 4:10 AM, Jorge Timón
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
/tx/3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a?chain=000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943
> >
> > (a tx in testnet)
> >
> >
/block/00000000000000000b0d504d142ac8bdd1a2721d19f423a8146d0d6de882167b?chain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
>
> Some altcoins (LTC and FTC for example) have the same genesis block hash.
That's obviously a design mistake in FTC, but it's not unsolvable. FTC
could move their genesis block to the next block (or the first one that is
not identical to LTC's).
Bitcoin and all its test chains have different genesis blocks, so I'm not
sure FTC should be a concern for a BIP anyway...
[-- Attachment #2: Type: text/html, Size: 1204 bytes --]
next prev parent reply other threads:[~2015-08-30 2:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 11:48 Marco Pontello
2015-08-29 16:31 ` Richard Moore
2015-08-29 17:19 ` Matt Whitlock
2015-08-29 19:24 ` Richard Moore
2015-08-29 18:07 ` Andreas Schildbach
2015-09-01 14:33 ` Marco Pontello
2015-08-29 18:58 ` Btc Drak
2015-08-29 19:01 ` Matt Whitlock
2015-08-29 20:10 ` Jorge Timón
2015-08-30 2:02 ` Chun Wang
2015-08-30 2:20 ` Jorge Timón [this message]
2015-09-01 22:56 ` Btc Drak
2015-09-01 14:49 ` Marco Pontello
2015-09-01 21:16 ` Matt Whitlock
2015-09-01 21:25 ` Esteban Ordano
2015-09-01 21:38 ` Marco Pontello
2015-09-01 21:42 ` Matt Whitlock
2015-09-01 21:43 ` Marco Pontello
2015-09-01 22:46 ` Jorge Timón
2015-09-01 23:25 ` Matt Whitlock
2015-09-01 16:12 ` Danny Thorpe
2015-09-01 22:59 ` Btc Drak
2015-09-01 23:57 ` Jorge Timón
2015-08-29 19:28 ` Richard Moore
2015-09-01 14:51 ` Marco Pontello
2015-11-15 2:14 ` Marco Pontello
2015-11-15 11:42 ` Jorge Timón
2015-11-16 0:59 ` Marco Pontello
2015-11-16 14:43 ` Jorge Timón
2015-11-16 22:10 ` Marco Pontello
2015-11-18 11:29 ` Jorge Timón
2015-11-18 12:31 ` Marco Pontello
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='CABm2gDqNQEcm5CWE8Rb0p1NGk=9bzjeSh6DD84=qvJ9kk+uFYw@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--cc=1240902@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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