📅 Original date posted:2015-07-24
📝 Original message:They do not run anything but BitcoinJ (evidenced by them blindly following invalid chains), so no proper consensus checking going on here at all. Connected to my nodes is a bad peer (doesn’t relay inventory but downloads everything) from 37.187.136.15, with the user agent /BitcoinJ:0.12SNAPHOT/Satoshi:0.2.0/ which is owned by blockchain.info. You can also submit an invalid transaction through their /pushtx interface and get a mixture of noise and BitcoinJ error messages out of it as well.
If even the people who have to their claim hundreds of thousands of wallets are relying on their security don’t bother running even a single node to sanity check against, who are we really going to expect people to in the future if the load goes 8x, 16x, 32x higher? Like CoinBase and others, these are the companies which are claimed will be the ones supporting the network with ludicrous sized blocks because they have a financial incentive to.
Well, they don't even do it now when it could be achieved with a $5 VPS.
> Sent: Friday, July 24, 2015 at 8:43 PM
> From: "Peter Todd via bitcoin-dev" <bitcoin-dev at lists.linuxfoundation.org>
> To: "Thomas Zander" <thomas at thomaszander.se>
> Cc: bitcoin-dev at lists.linuxfoundation.org
> Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis
> We can test the fact that blockchain.info's wallet and block explorer
> has behaved in a way consistent with not running a full node - they have
> shown invalid data that any full node would reject on multiple
> occasions, most recently invalid confirmations during the BIP66 fork.
Slurms MacKenzie [ARCHIVE] /
npub168…hhm7q
2023-06-07 17:43:35
in reply to nevent1q…7730
Author Public Key
npub168j7xscxgv5tup3uxm0tpkktvc9ctzwuhj5szyhec3y4qwmrawaq9hhm7qPublished at
2023-06-07 17:43:35Event JSON
{
"id": "6cc5bd54f8dfa8c23c7b8f87e42990a33900e7da60b9606b92f6b02ae7b432c0",
"pubkey": "d1e5e343064328be063c36deb0dacb660b8589dcbca90112f9c449503b63ebba",
"created_at": 1686152615,
"kind": 1,
"tags": [
[
"e",
"fad7a9dfe8ad03505fa882cfc142cd53cfb83fa310033743eaad5169b0befe94",
"",
"root"
],
[
"e",
"fa54d5032e0535cc7b35cc399b9aa48a3690411eee6bc7152ba3e651c71461b0",
"",
"reply"
],
[
"p",
"e899768d254f3537af7e26455968583632d0ab0bd4c780445eacfa087ac80d8f"
]
],
"content": "📅 Original date posted:2015-07-24\n📝 Original message:They do not run anything but BitcoinJ (evidenced by them blindly following invalid chains), so no proper consensus checking going on here at all. Connected to my nodes is a bad peer (doesn’t relay inventory but downloads everything) from 37.187.136.15, with the user agent /BitcoinJ:0.12SNAPHOT/Satoshi:0.2.0/ which is owned by blockchain.info. You can also submit an invalid transaction through their /pushtx interface and get a mixture of noise and BitcoinJ error messages out of it as well. \n\nIf even the people who have to their claim hundreds of thousands of wallets are relying on their security don’t bother running even a single node to sanity check against, who are we really going to expect people to in the future if the load goes 8x, 16x, 32x higher? Like CoinBase and others, these are the companies which are claimed will be the ones supporting the network with ludicrous sized blocks because they have a financial incentive to. \n\nWell, they don't even do it now when it could be achieved with a $5 VPS. \n\n\n\u003e Sent: Friday, July 24, 2015 at 8:43 PM\n\u003e From: \"Peter Todd via bitcoin-dev\" \u003cbitcoin-dev at lists.linuxfoundation.org\u003e\n\u003e To: \"Thomas Zander\" \u003cthomas at thomaszander.se\u003e\n\u003e Cc: bitcoin-dev at lists.linuxfoundation.org\n\u003e Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or \"If We Do Nothing\" Analysis\n\u003e We can test the fact that blockchain.info's wallet and block explorer\n\u003e has behaved in a way consistent with not running a full node - they have\n\u003e shown invalid data that any full node would reject on multiple\n\u003e occasions, most recently invalid confirmations during the BIP66 fork.",
"sig": "168afa8fbfd6ae688f599ecc544726286969da39625c64711725f26eaa4439d508a75dab6523fab5f7f587418150277aa5b6a0c2914a18045580013da680ce97"
}