Create account

replied 2328d
Simon Van Gelder
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.
2 / 6
Simon Van Gelder
replied 2328d
They are complimentary technologies, not in competition.
Simon Van Gelder
replied 2328d
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 2328d
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 2328d
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 2328d
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 2328d
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