I've been thinking about the requirements for a payment protocol
lately. It seems we have consensus that we need one of these. Pieter
has a gist on the topic here: https://gist.github.com/1237788
IMHO we'll want to move away from send X BTC to address Y and more
towards upload to me transactions
I agree we need a payment protocol, but instead of thinking of all of the
things we might possibly want I would like to solve a few boring problems
that we have right now.
Absolutely critical:
+ Bitcoin addresses by themselves are insecure against man-in-the-middle
attacks. We need a payment
On Tue, Oct 2, 2012 at 1:52 PM, Peter Vessenes pe...@coinlab.com wrote:
This is small, but an interesting tidbit from BTC Foundation payments;
roughly 3-5% of our initial members double-spent. WOW, that's terrible.
To be specific, do you mean
a) paid twice
or
b) sent BF coins, then sent
I meant sent twice, a.
No double-spends that I'm aware of. Sorry for the loose verbiage!
Peter
On Tue, Oct 2, 2012 at 11:07 AM, Jeff Garzik jgar...@exmulti.com wrote:
On Tue, Oct 2, 2012 at 1:52 PM, Peter Vessenes pe...@coinlab.com wrote:
This is small, but an interesting tidbit from BTC
I think it's worth pondering the different things we may want in
future, even if that future is quite far out, just to ensure we have a
robust design that won't box us in later. Brainstorming feature ideas
now doesn't commit anyone to implementing them, but it may help
improve the final v1 design.
5 matches
Mail list logo
