📅 Original date posted:2013-07-31
📝 Original message:I think it's important to expect PaymentRequest-only bitcoin URIs in the
future. Some types of payments (exotic transactions) may not make sense to
have a single fallback address. Or, a page with a bitcoin URI link may be
relying on a separate service provider to assemble the transaction.
On Wed, Jul 31, 2013 at 5:33 AM, Gavin Andresen <gavinandresen at gmail.com>wrote:
> On Wed, Jul 31, 2013 at 6:45 PM, Roy Badami <roy at gnomon.org.uk> wrote:
> >
> > Is it envisaged to be possible/sensible to have a URI that is *only* a
> > payment request? i.e. something like the following (although I'm not
> > sure this is a valid URI):
> >
> > bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
>
> I think we'll want a bitcoin address in there for a long time for
> backwards compatibility.
>
> If web browser support for arbitrary MIME types is strong enough (I
> haven't tested), then a payment request can be initiated with just an
> anchor tag:
> <a href="https://merchant.com/pay.php?3D2a8628fc2fbe";
> type="application/bitcoin-paymentrequest">
>
> Doing it that way saves a http round-trip.
>
> --
> --
> Gavin Andresen
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130731/a5fc54fa/attachment.html>;
E willbefull [ARCHIVE] /
npub1le…nwldf
2023-06-07 15:05:26
in reply to nevent1q…dq45
Author Public Key
npub1lepsynjuh6hvdlsyxjaefyg9n3g67fcc5r2cjkasm85q8cx9wnwqnnwldfPublished at
2023-06-07 15:05:26Event JSON
{
"id": "2b48fba3bfd6f7aa59da6cab7ef7895afeb9f15cad831106dee49bdad361a531",
"pubkey": "fe43024e5cbeaec6fe0434bb9491059c51af2718a0d5895bb0d9e803e0c574dc",
"created_at": 1686150326,
"kind": 1,
"tags": [
[
"e",
"acb519b4f9bdad686b6843b54b930bf9807cd870096d61003ce465cbbdec8f90",
"",
"root"
],
[
"e",
"1bd807d0acdfc3930f25929476b3e4beb734aa730f429f612d2007c668e8b0da",
"",
"reply"
],
[
"p",
"e316966328c4cb66c34719ef9a7b3bc54ef601663ad4ab06185991237735aa19"
]
],
"content": "📅 Original date posted:2013-07-31\n📝 Original message:I think it's important to expect PaymentRequest-only bitcoin URIs in the\nfuture. Some types of payments (exotic transactions) may not make sense to\nhave a single fallback address. Or, a page with a bitcoin URI link may be\nrelying on a separate service provider to assemble the transaction.\n\n\nOn Wed, Jul 31, 2013 at 5:33 AM, Gavin Andresen \u003cgavinandresen at gmail.com\u003ewrote:\n\n\u003e On Wed, Jul 31, 2013 at 6:45 PM, Roy Badami \u003croy at gnomon.org.uk\u003e wrote:\n\u003e \u003e\n\u003e \u003e Is it envisaged to be possible/sensible to have a URI that is *only* a\n\u003e \u003e payment request? i.e. something like the following (although I'm not\n\u003e \u003e sure this is a valid URI):\n\u003e \u003e\n\u003e \u003e bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe\n\u003e\n\u003e I think we'll want a bitcoin address in there for a long time for\n\u003e backwards compatibility.\n\u003e\n\u003e If web browser support for arbitrary MIME types is strong enough (I\n\u003e haven't tested), then a payment request can be initiated with just an\n\u003e anchor tag:\n\u003e \u003ca href=\"https://merchant.com/pay.php?3D2a8628fc2fbe\"\n\u003e type=\"application/bitcoin-paymentrequest\"\u003e\n\u003e\n\u003e Doing it that way saves a http round-trip.\n\u003e\n\u003e --\n\u003e --\n\u003e Gavin Andresen\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Get your SQL database under version control now!\n\u003e Version control is standard for application code, but databases havent\n\u003e caught up. So what steps can you take to put your SQL databases under\n\u003e version control? Why should you start doing it? Read more to find out.\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=49501711\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130731/a5fc54fa/attachment.html\u003e",
"sig": "26416802945f0451d34ca27d185b0f2a0bbb077d54ab83197333497a839a1874e578e48b985b6aef7c9b4341a219985117835c0f5bb285a8d2f8c8977222e442"
}