From: jl2012@xbt.hk
To: jyellen@toothandmail.com
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Annoucing Not-BitcoinXT
Date: Sun, 16 Aug 2015 23:10:48 -0400 [thread overview]
Message-ID: <259b2961959104a03bbb4e6645aecfa5@xbt.hk> (raw)
In-Reply-To: <20150816173433.Horde.qKtgfc1SFgXRd026yTjnmg1@www.vfemail.net>
Thanks to mining centralization, such attempts won't be successful.
Asking mining pools to mine spoofing blocks in their real name is even
harder than asking them to run the real BitcoinXT
Node count is always manipulable, there is nothing new. People running
this will only be interpreted as XT-supporters.
Julie via bitcoin-dev 於 2015-08-16 18:34 寫到:
> 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
next prev parent reply other threads:[~2015-08-17 3:10 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 [this message]
2015-08-17 7:04 ` Peter Todd
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=259b2961959104a03bbb4e6645aecfa5@xbt.hk \
--to=jl2012@xbt.hk \
--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