{
"subject": "Bitcoin P2P e-cash paper",
"content": {
"format": "email",
"body": "James A. Donald wrote:\n> > Fortunately, it's only necessary to keep a\n> > pending-transaction pool for the current best branch.\n> \n> This requires that we know, that is to say an honest\n> well behaved peer whose communications and data storage\n> is working well knows, what the current best branch is -\n\nI mean a node only needs the pending-tx pool for the best branch it\nhas. The branch that it currently thinks is the best branch.\nThat's the branch it'll be trying to make a block out of, which is\nall it needs the pool for.\n\n\n> > Broadcasts will probably be almost completely\n> > reliable.\n> \n> Rather than assuming that each message arrives at least\n> once, we have to make a mechanism such that the\n> information arrives even though conveyed by messages\n> that frequently fail to arrive.\n\nI think I've got the peer networking broadcast mechanism covered. \n\nEach node sends its neighbours an inventory list of hashes of the\nnew blocks and transactions it has. The neighbours request the\nitems they don't have yet. If the item never comes through after a\ntimeout, they request it from another neighbour that had it. Since\nall or most of the neighbours should eventually have each item,\neven if the coms get fumbled up with one, they can get it from any\nof the others, trying one at a time.\n\nThe inventory-request-data scheme introduces a little latency, but\nit ultimately helps speed more by keeping extra data blocks off the\ntransmit queues and conserving bandwidth.\n\n\n> You have an outline\n> and proposal for such a design, which is a big step\n> forward, but the devil is in the little details.\n\nI believe I've worked through all those little details over the\nlast year and a half while coding it, and there were a lot of them.\nThe functional details are not covered in the paper, but the\nsourcecode is coming soon. I sent you the main files.\n(available by request at the moment, full release soon)\n\nSatoshi Nakamoto\n\n\n---------------------------------------------------------------------\nThe Cryptography Mailing List\nUnsubscribe by sending \"unsubscribe cryptography\" to majordomo at metzdowd.com\n\n"
},
"source": {
"name": "cryptography",
"url": "http://www.metzdowd.com/pipermail/cryptography/2008-November/014863.html"
},
"date": "2008-11-17T17:24:43Z"
}