{
"subject": "Re: [bitcoin-list] Bitcoin v0.1.5 released",
"content": {
"format": "email",
"body": "Hal Finney wrote:\n> That sounds good. I'd also like to be able to run multiple coin/block\n> generators on multiple machines, all behind a single NAT address. I\n> haven't tried this yet so I don't know if it works on the current\n> software.\n\nThe current version will work fine. They'll each connect over the\nInternet, while incoming connections only come to the host that\nport 8333 is routed to. \n\nAs an optimisation, I'll make a switch \"-connect=1.2.3.4\" to make\nit only connect to a specific address. You could make your extra\nnodes connect to your primary, and only the primary connects over\nthe Internet. It doesn't really matter for now, since the network\nwould have to get huge before the bandwidth is anything more than\ntrivial.\n\n\n> BTW I don't remember if we talked about this, but the other day some\n> people were mentioning secure timestamping. You want to be able to\n> prove that a certain document existed at a certain time in the past.\n> Seems to me that bitcoin's stack of blocks would be perfect for this.\n\nIndeed, Bitcoin is a distributed secure timestamp server for\ntransactions. A few lines of code could create a transaction with\nan extra hash in it of anything that needs to be timestamped. \nI should add a command to timestamp a file that way.\n\n\n> > > Later I want to add interfaces to make it really easy to integrate\n> > > into websites from any server side language.\n>\n> Right, and I'd like to see more of a library interface that could be\n> called from programming or scripting languages, on the client side as\n> well.\n \nExactly.\n\n \nSatoshi Nakamoto\n\nhttp://www.bitcoin.org\n\n\n\n"
},
"source": {
"name": "bitcoin-list",
"url": "https://sourceforge.net/p/bitcoin/mailman/message/21740046/"
},
"date": "2009-03-04T16:59:12Z"
}