Natanael [ARCHIVE] on Nostr: 📅 Original date posted:2017-05-03 📝 Original message:Den 3 maj 2017 16:05 skrev ...
📅 Original date posted:2017-05-03
📝 Original message:Den 3 maj 2017 16:05 skrev "Erik Aronesty via bitcoin-dev" <
bitcoin-dev at lists.linuxfoundation.org>:
> But as you've observed, the failure probabilities are rather high,
> especially if an active attacker targets nodes carrying less commonly
> available blocks.
Wouldn't the solution be for nodes to use whatever mechanism an attacker
uses to determine less commonly available blocks and choose to store a
random percentage of them as well as their deterministic random set?
IE X blocks end of chain (spv bootstrap), Y% deterministic random set, Z%
patch/fill set to deter attacks
Then he uses Sybil attacks to obscure what's actually rare and not. Even
proof of storage isn't enough, you need proof of INDEPENDENT storage, which
is essentially impossible, as well as a way of determining which nodes are
run by the same people (all the AWS nodes should essentially count as one).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170503/c4844326/attachment.html>
Published at
2023-06-07 18:00:42Event JSON
{
"id": "4436a33e5142ce84f655d0aa755678c87ebb4542640ce41572c1a8fd4fc04a5c",
"pubkey": "f14f3c71a4e63a12c842e4a50471263ada4b6cfde093fcb6588693a726b9b018",
"created_at": 1686160842,
"kind": 1,
"tags": [
[
"e",
"ed0c62c21bb2ab4b55b256850bcf0104c3d65cbd2c153f5d46266849b3c6bec4",
"",
"root"
],
[
"e",
"e2a44b3cd157fe46becdcce2017f7d8c86472e27aa803cc95b88972c7c79f629",
"",
"reply"
],
[
"p",
"22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa"
]
],
"content": "📅 Original date posted:2017-05-03\n📝 Original message:Den 3 maj 2017 16:05 skrev \"Erik Aronesty via bitcoin-dev\" \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e:\n\n\u003e But as you've observed, the failure probabilities are rather high,\n\u003e especially if an active attacker targets nodes carrying less commonly\n\u003e available blocks.\n\nWouldn't the solution be for nodes to use whatever mechanism an attacker\nuses to determine less commonly available blocks and choose to store a\nrandom percentage of them as well as their deterministic random set?\n\nIE X blocks end of chain (spv bootstrap), Y% deterministic random set, Z%\npatch/fill set to deter attacks\n\n\nThen he uses Sybil attacks to obscure what's actually rare and not. Even\nproof of storage isn't enough, you need proof of INDEPENDENT storage, which\nis essentially impossible, as well as a way of determining which nodes are\nrun by the same people (all the AWS nodes should essentially count as one).\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170503/c4844326/attachment.html\u003e",
"sig": "e50bca5ac289efb18469585c004252c095d77819d797bac751b4d3bae58e1f352e2a0a35406ca6e55d8b08f48d6c37d0da50ad85cd613321e9b7a6d58c374e4a"
}