π
Original date posted:2015-08-15
π Original message:I posted this to /r/BitcoinMarkets but I thought I might post it here as
well.
---
Currently 0 mined blocks have voted for XT.
If it ever gets close to even 50%, many things can happen that would
reshape the game completely.
For instance:
- Core could start boycotting XT by not relying to them and/or not relying
from them.
- Core could appropriate the version string of XT, making it impossible to
know how much they are progressing and a losing bet to actually execute the
fork.
This kind of node war if the factions were sizeable would make it very
risky to transact at all - balances in new addresses could end up
vanishing. Usability of the system would plummet.
Note that any disagreement between the network and the biggest economic
actors - mainly the exchanges at this point, "wallet services" maybe -
would mean BTC plummets. Hard. And so would confidence.
It's a risky game to play.
---
PS: I consider this attempt at takeover about as foul as it gets. The
equivalent of repeating a referendum until a yes is obtained: the
reasonable reaction to this is actively blocking said "referendum". There
was a fair play alternative which is voting through coinbase scriptSig like
plain 8MBers are doing, or like BIP 100 proposes for dynamic adjustment.
Once a majority is obtained in this way, devs have to react or if they
don't then this sort of foul play would be justified. But this wasn't the
case.
-----
ηΊγγ°ζγ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150815/8ba538ee/attachment.html>;
muyuubyou [ARCHIVE] /
npub14hβ¦dkmle
2023-06-07 17:35:27
in reply to nevent1qβ¦wwuw
Author Public Key
npub14hzxhtcevdfs320qwvywn2pgak5fs72saazgx3cu323m7ejs4ltqjdkmlePublished at
2023-06-07 17:35:27Event JSON
{
"id": "6cbe57e5a426f06749b6ccfb12f73aaa5a38c54efdf60fec772f7126b6ddc81a",
"pubkey": "adc46baf19635308a9e07308e9a828eda8987950ef4483471c8aa3bf6650afd6",
"created_at": 1686159327,
"kind": 1,
"tags": [
[
"e",
"c8deaa0aeee1e5d915e04ef7baf8b8074172a310b656820cd8767442ca514e56",
"",
"root"
],
[
"e",
"5a8de15ecb3d685eee766bc2ab02f18c86a83c4df4c62dd46d6078be591317ce",
"",
"reply"
],
[
"p",
"82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e"
]
],
"content": "π
Original date posted:2015-08-15\nπ Original message:I posted this to /r/BitcoinMarkets but I thought I might post it here as\nwell.\n\n---\nCurrently 0 mined blocks have voted for XT.\n\nIf it ever gets close to even 50%, many things can happen that would\nreshape the game completely.\n\nFor instance:\n\n- Core could start boycotting XT by not relying to them and/or not relying\nfrom them.\n\n- Core could appropriate the version string of XT, making it impossible to\nknow how much they are progressing and a losing bet to actually execute the\nfork.\n\nThis kind of node war if the factions were sizeable would make it very\nrisky to transact at all - balances in new addresses could end up\nvanishing. Usability of the system would plummet.\n\nNote that any disagreement between the network and the biggest economic\nactors - mainly the exchanges at this point, \"wallet services\" maybe -\nwould mean BTC plummets. Hard. And so would confidence.\n\nIt's a risky game to play.\n---\n\nPS: I consider this attempt at takeover about as foul as it gets. The\nequivalent of repeating a referendum until a yes is obtained: the\nreasonable reaction to this is actively blocking said \"referendum\". There\nwas a fair play alternative which is voting through coinbase scriptSig like\nplain 8MBers are doing, or like BIP 100 proposes for dynamic adjustment.\nOnce a majority is obtained in this way, devs have to react or if they\ndon't then this sort of foul play would be justified. But this wasn't the\ncase.\n\n-----\nηΊγγ°ζγ\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150815/8ba538ee/attachment.html\u003e",
"sig": "2c3d696bc48d702aa0b91fd9133082850f639fd6674fa0dfac45ea06235a0b82ce451103d1d4646f3f6adc9a1fe6e75b0c5173655b6fe3908b84af4d7fe3b2e1"
}