📅 Original date posted:2014-07-19
📝 Original message:On Fri, Jul 18, 2014 at 4:53 PM, Gavin Andresen <gavinandresen at gmail.com> wrote:
> Two more half-baked thoughts:
>
> We should be able to assume that the majority of transaction data (except
> for coinbase) has already been propagated. As Jeff said, incentivizing nodes
> to propagate transactions is a very good thing (the signature cache already
> gives a small incentive to miners to propagate and not 'hoard'
> transactions).
Maybe a stupid idea - but couldn't we make that assumption a surety by
starting the 'set synchronization process' as soon as the miner starts
crunching on a certain block, instead of when it broadcasts it? So the
peers are prepared, and the actual block broadcast is just the header
+ coinbase tx.
Wladimir
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 15:24:11
in reply to nevent1q…mwnx
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pPublished at
2023-06-07 15:24:11Event JSON
{
"id": "6c45409bf4b66ddcbd66ca344b0ae77ee14004458e44c08a984e9ef7f07d08ce",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686151451,
"kind": 1,
"tags": [
[
"e",
"3507527acf6651445fc18e718512a320c7c5edde322b321b00914bf719d85722",
"",
"root"
],
[
"e",
"d56a9f852515b41770615d9904b21cd59499be311047bdd39b9f7dee7b42c9ff",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2014-07-19\n📝 Original message:On Fri, Jul 18, 2014 at 4:53 PM, Gavin Andresen \u003cgavinandresen at gmail.com\u003e wrote:\n\u003e Two more half-baked thoughts:\n\u003e\n\u003e We should be able to assume that the majority of transaction data (except\n\u003e for coinbase) has already been propagated. As Jeff said, incentivizing nodes\n\u003e to propagate transactions is a very good thing (the signature cache already\n\u003e gives a small incentive to miners to propagate and not 'hoard'\n\u003e transactions).\n\nMaybe a stupid idea - but couldn't we make that assumption a surety by\nstarting the 'set synchronization process' as soon as the miner starts\ncrunching on a certain block, instead of when it broadcasts it? So the\npeers are prepared, and the actual block broadcast is just the header\n+ coinbase tx.\n\nWladimir",
"sig": "739fc46489a4b9c790c6e21d038d53951670b269a1f8a05817f3eaae8cffda518c21df60bb895ddb48f0332aa89a763c19fb6a443ee9ff7ba2ecb1aed732e4ea"
}