📅 Original date posted:2011-09-08
🗒️ Summary of this message: Keeping the discussion on one mailing list is less confusing. A simple approach to scalability is suggested, with the option to improve later.
📝 Original message:It's probably best to keep this discussion on just one mailing list. It's
confusing to have duplicate threads in different places. People will end up
making the same points.
To repeat what I posted elsewhere, for now I'd just start with the simplest
possible approach:
- Ignore version skew for now (disconnect older clients)
- Don't send received transactions/blocks to the bitcoind. Let it hear about
them from its own p2p connections. That way you will always receive all
valid transactions/blocks which you can then relay/cache/drop inbound
duplicates.
- Parse/handle inv/getblocks/getheaders requests so clients that connect and
catch up with the chain don't place any load on the bitcoind. If a client
requests data the proxy doesn't have in RAM, it can go fetch it from the
underlying bitcoind.
If you can make v1 work and demonstrate actual scalability improvements,
then you can always go back and make it smarter in v2.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110908/4ae500f3/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 02:23:08
in reply to nevent1q…nn9l
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 02:23:08Event JSON
{
"id": "c152c3a758e5c84df20ef74b01c17202f34ffefc9033625dd6594c0b8013ade3",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686104588,
"kind": 1,
"tags": [
[
"e",
"84f886c581f79ae0e62167f62ed88aefa7cda08705a70faadd465e3524d4e5cf",
"",
"root"
],
[
"e",
"7fec3d2b3adaa561630ab1a7b4b3b3be86149c70d1b29991dd65d1c12afdb83b",
"",
"reply"
],
[
"p",
"fec9b86ad53f610a8cab1b299acd9dc48a0c018163c9a3ac28bfef2117de2ae6"
]
],
"content": "📅 Original date posted:2011-09-08\n🗒️ Summary of this message: Keeping the discussion on one mailing list is less confusing. A simple approach to scalability is suggested, with the option to improve later.\n📝 Original message:It's probably best to keep this discussion on just one mailing list. It's\nconfusing to have duplicate threads in different places. People will end up\nmaking the same points.\n\nTo repeat what I posted elsewhere, for now I'd just start with the simplest\npossible approach:\n\n- Ignore version skew for now (disconnect older clients)\n\n- Don't send received transactions/blocks to the bitcoind. Let it hear about\nthem from its own p2p connections. That way you will always receive all\nvalid transactions/blocks which you can then relay/cache/drop inbound\nduplicates.\n\n- Parse/handle inv/getblocks/getheaders requests so clients that connect and\ncatch up with the chain don't place any load on the bitcoind. If a client\nrequests data the proxy doesn't have in RAM, it can go fetch it from the\nunderlying bitcoind.\n\nIf you can make v1 work and demonstrate actual scalability improvements,\nthen you can always go back and make it smarter in v2.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110908/4ae500f3/attachment.html\u003e",
"sig": "f275b1c349642af654035b479d738fd96fe1f01267359e6e31fef9ba26236fb8a39afc74170c61c24139012a96bf2dd4ddb43e75f468f6984c92deb96e3ff5ca"
}