The following email is notable because Satoshi responds to a question from Mike Hearn about micropayments.
Date: Sun, Apr 19, 2009 at 2:14 AM
To: Mike Hearn <email@example.com>
The list is:
I’ll always announce new versions there. Automatic update, or at least notification of new versions, is definitely on the list. There could potentially be necessary changes in the future where nobody will want to talk to you until you upgrade, and there needs to be code in the older version to convey that to the user. This is all the harder in the context of not trusting anyone.
Your approach to micropayments sounds right. At first, it might be a good idea to default to asking permission until the user gets comfortable and is ready to set it to automatic. The end goal though should get to something like you describe, where it’s similar to using your cell phone without really having to think about the per minute charges.
I looked at Google protocol buffers when they were released last year, but I had already written everything by then. What I did was something similar to Boost Serialisation. For this application, where I was parsing messages from strangers who might have extreme incentive to hack the protocol, it was necessary to make it as basic as possible so I could crawl over every line of code to convince myself it was airtight. It became clear that any unnecessary degrees of freedom in the binary format multiplied the potential angles of attack. You guys are so right though to standardize across the company on protocol buffers. I think you’ve got the optimal solution in the general case.
Your approach to micropayments sounds right…The end goal though should get to something like you describe, where it’s similar to using your cell phone without really having to think about the per minute charges.
- Bitcoin open source implementation of P2P currency (2009-02-11 22:27:00 UTC)