Create account

Simon Van Gelder
replied 2374d
Still waiting for HTTP Error Code 402 (Payment Required) to enter general usage.
1 / 10 1
replied 2374d
Difference between HTTP 402 and Bitcoin is that Bitcoin actually made progress in that area ;)
Simon Van Gelder
replied 2374d
I would image the majority of these types of payments will be of the the mico-type. If a single chain is to become the default, it will need to be able to handle these transactions.
Simon Van Gelder
replied 2374d
Again, a fundamental misunderstanding: this time of my point. 402 says "use something to pay us", crypto is only one way to pay.
replied 2374d
402 is then obviously obsolete, since it has gained no traction, and crypto has.

I don't really understand where HTTP 402 comes into play when regarding crypto micropayments.
Simon Van Gelder
replied 2374d
They are complimentary technologies, not in competition.
Simon Van Gelder
replied 2374d
402 Errors are returned by a website when you need to make a payment for access. Access could be a snail-mailed OAuth token, but crypto now makes this feasible.That's why I'm waiting.
replied 2374d
Ahhh. 402 initiates payment, then crypto is used for that payment. Yeah, I see your point now. I guess BIP70 supercedes the HTTP402 in this case
Simon Van Gelder
replied 2374d
402s been around for a long time, but "Reserved for future use": Already part of the HTTP protocol, and would just take BIP70 on top as a data format. BIP70 is new to me, will read up.
1
replied 2374d
I don't dispute that. Personally I will use what works reliably and securely, whichever becomes commonplace is fine by me, so long as crypto is the underlying asset used for payments
Simon Van Gelder
replied 2374d
Here's an example implementation combining the two (not mine, not tested): https://github.com/bumi/api-payments-example/blob/master/README.md


About Privacy Terms Stats