This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0073 [2021/08/06 13:08] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0073 [2021/08/17 13:33] (current) murphy |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| === Abstract === | === Abstract === | ||
| - | : //This BIP describes an enhancement to the payment protocol ([[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070| BIP 70]]) that addresses the need for short URLs when scanning from QR codes. It generalizes the specification for the behavior of a payment request URL in a way that allows the [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] and server to negotiate the content of the response using the HTTP Accept: header field. Specifically, the client can indicate to the server whether it prefers to receive a bitcoin URI or a payment request.// | + | : //This BIP describes an enhancement to the payment protocol ([[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070| BIP 70]]) that addresses the need for short URLs when scanning from QR codes. It generalizes the specification for the behavior of a payment request URL in a way that allows the [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] and [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]] to negotiate the content of the response using the HTTP Accept: header field. Specifically, the client can indicate to the server whether it prefers to receive a bitcoin URI or a payment request.// |
| : //Implementation of this BIP does not require full payment request ([[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070| BIP 70]]) support.// | : //Implementation of this BIP does not require full payment request ([[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0070| BIP 70]]) support.// | ||