📅 Original date posted:2014-07-18
📝 Original message:On Fri, Jul 18, 2014 at 5:54 PM, Emin Gün Sirer <el33th4x0r at gmail.com> wrote:
> The problem being tackled here is very similar to "set reconciliation,"
> where
> peer A thinks that the set of transactions that should be in the block is
> S_A,
Most things I've seen working in this space are attempting to minimize
the data transfered. At least for the miner-interested case the round
complexity is much more important because a single RTT is enough to
basically send the whole block on a lot of very relevant paths.
I know much better is possible (see up-thread where I linked to an old
proposal to use forward error correction to transfer with low data
transfer (but not optimal) and negligible probability of needing a
round-trip, with a tradeoff for more overhead for lower roundtrip
probability).
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 15:24:10
in reply to nevent1q…zqrl
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetPublished at
2023-06-07 15:24:10Event JSON
{
"id": "bcd9fcc984e53fb42cce5c73dae1d8baf42d8be032f6f73e2238c641623b7a60",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686151450,
"kind": 1,
"tags": [
[
"e",
"3507527acf6651445fc18e718512a320c7c5edde322b321b00914bf719d85722",
"",
"root"
],
[
"e",
"0d05ccbf908bb93acd29eacb0761550f4033a7c6e15b8543925a3b049df113f1",
"",
"reply"
],
[
"p",
"b68afd106d166cdb4d51d8e16c275c09e0a49020fb6f311509c56b6743b37a84"
]
],
"content": "📅 Original date posted:2014-07-18\n📝 Original message:On Fri, Jul 18, 2014 at 5:54 PM, Emin Gün Sirer \u003cel33th4x0r at gmail.com\u003e wrote:\n\u003e The problem being tackled here is very similar to \"set reconciliation,\"\n\u003e where\n\u003e peer A thinks that the set of transactions that should be in the block is\n\u003e S_A,\n\nMost things I've seen working in this space are attempting to minimize\nthe data transfered. At least for the miner-interested case the round\ncomplexity is much more important because a single RTT is enough to\nbasically send the whole block on a lot of very relevant paths.\n\nI know much better is possible (see up-thread where I linked to an old\nproposal to use forward error correction to transfer with low data\ntransfer (but not optimal) and negligible probability of needing a\nround-trip, with a tradeoff for more overhead for lower roundtrip\nprobability).",
"sig": "75724d624586f2be6727135722a1a5fabcc52c8a5bcc42a3e04162e7adaf06c6391cf23418c645ba04aa3f7358047cfc6ab6df37044d35b53d0a877ef5750dfa"
}