http-micropayments
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revisionNext revision | |||
— | http-micropayments [2015/10/24 17:35] – donpdonp | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ## Cryptocoin HTTP Micropayments | ||
+ | |||
+ | |||
+ | #### Retrieving payment data for a resource/ | ||
+ | * GET <URI> | ||
+ | * 200 or 402: receives txout in headers. computes signed tx. | ||
+ | * OR second request with content-type: | ||
+ | * POST <URI> | ||
+ | * content-type: | ||
+ | |||
+ | #### HTTP Header | ||
+ | more featureful to use txout | ||
+ | ``` | ||
+ | X-micropayment: | ||
+ | ``` | ||
+ | or simply list receiving address | ||
+ | ``` | ||
+ | X-micropayment: | ||
+ | ``` | ||
+ | |||
+ | (from https:// | ||
+ | * " | ||
+ | * " | ||
+ | |||
+ | |||
+ | #### processing payment | ||
+ | Fastest: client signs TX, hands to server (no bitcoin network involved). Server can selectively run various checks, including submitting to the bitcoin network and waiting, or trusting valid signature and recent balance. | ||
+ | |||
+ | Post of signed TX is optional. If donation/ | ||
+ | |||
+ | #### Cons | ||
+ | * payment info in http headers is likely to be lost when content is re-uploaded (eg, uploaded to IPFS). | ||
+ | * Better to embed in HTML doc | ||
+ | * other mime types? png/ | ||
http-micropayments.txt · Last modified: 2024/01/31 04:08 by 127.0.0.1