public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: jyellen@toothandmail.com,
	Julie via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>,
	bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Annoucing Not-BitcoinXT
Date: Mon, 17 Aug 2015 07:04:18 +0000	[thread overview]
Message-ID: <71D526DA-6249-4119-B2A2-40960622D65E@petertodd.org> (raw)
In-Reply-To: <20150816173433.Horde.qKtgfc1SFgXRd026yTjnmg1@www.vfemail.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

The fun thing about this, is you only need >25% of hashing power running Not-BitcoinXT to screw over the miners running XT, as XT blocks are valid Bitcoin blocks if they're on a valid Bitcoin chain.

75% upgrade thresholds have a lot of issues...


On 16 August 2015 15:34:33 GMT-07:00, Julie via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>Announcing Not-BitcoinXT
>
>https://github.com/xtbit/notbitcoinxt#not-bitcoin-xt
>
>
>
>
>-------------------------------------------------
>
>ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of
>the NSA's hands!
>$24.95 ONETIME Lifetime accounts with Privacy Features!
>15GB disk! No bandwidth quotas!
>Commercial and Bulk Mail Options!
>_______________________________________________
>bitcoin-dev mailing list
>bitcoin-dev@lists.linuxfoundation.org
>https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
-----BEGIN PGP SIGNATURE-----

iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV0YdD
AAoJEMCF8hzn9Lnc47AH/1xFeDBejXmWjYlloDIq4OY8DypXypWk+J6BI2s5htm/
zBEQ/109u2T+7UYV5hSfh9GUj67NJ5HPbsPOpqoMqGO/yoJglM7ZEypNTKnOUlUf
3Ax+sgx5h5z2a51cshG0ups2liYgT926jzIyoz+Cs/O0g0mp+1Xu2rWm3qfnueXU
eqeqZ5SgnVT2JmnHubaYOl3IJvYs0B68TeSzFD0UFQzr7W7bzSFno4dIgpUhr5nP
Rd5ZFdYeotiGiPGStPmYshljuy0sbDydKBN29qViGRqXCUDA5QBAFGc/yfOm+82E
9LznXUfeJmsPztS1Wv8OzB7lpHVISKxrNKTCCt9U3oM=
=ZaI2
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2015-08-17  7:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 22:34 [bitcoin-dev] Annoucing Not-BitcoinXT jyellen
2015-08-17  3:10 ` jl2012
2015-08-17  7:04 ` Peter Todd [this message]
2015-08-17 10:09 ` NxtChg
2015-08-17 12:40   ` Vali Zero
2015-08-17 13:34     ` NxtChg
2015-08-17 14:03       ` Eric Lombrozo
2015-08-17 14:09         ` Levin Keller
2015-08-17 14:30           ` Eric Lombrozo
2015-08-17 14:36         ` Adam Back
2015-08-17 14:58           ` GC
2015-08-17 15:03           ` Levin Keller
2015-08-17 15:07             ` Eric Lombrozo
2015-08-19  3:49           ` odinn
2015-08-17 15:10         ` NxtChg
2015-08-17 16:37       ` Eric Lombrozo
2015-08-17 16:55         ` Eric Lombrozo
2015-08-18  4:37           ` Dave Scotese
2015-08-18  5:13             ` GC
2015-08-18  5:33               ` Dave Scotese
2015-08-18  9:46         ` NxtChg
2015-08-19  9:47           ` 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=71D526DA-6249-4119-B2A2-40960622D65E@petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=jyellen@toothandmail.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