From: Ben Dewaal <b.dewaal@northernbitcoin.com>
To: "ee@cypherpunk.org" <ee@cypherpunk.org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Towards a singular payment protocol
Date: Wed, 13 Nov 2019 08:52:19 +0000 [thread overview]
Message-ID: <FRXPR01MB04543D16EA2749E6900E8C5B81760@FRXPR01MB0454.DEUPRD01.PROD.OUTLOOK.DE> (raw)
In-Reply-To: <D5859AF5-CA49-42DF-8FAE-5BBBE2DF6699@cypherpunk.org>
I really don't see any merit to this idea. To keep the reply brief, here's three of the larger problems I see with it:
1. Other schemes will still exist and aren't likely to be deprecated. All this proposal is doing is adding one /more/ scheme for wallet developers to support. It doesn't make their lives any easier.
2. Beyond basic payments, these kinds of simple URI scheme aren't going to be enough anyway. As we build more complex payment systems with more advanced features, we'll find these kinds of schemes less and less suitable as they grow in the number and complexity of attributes we need to include. It's just not future-proof, even in the short term.
3. I don't see any reasonable way to define the attributes and what developers should do when their software encounters something it doesn't understand. It'd either be too strict so that no one implements it, or become a nightmare of incompatible and misunderstood implementations that you never trust your wallet is going to interpret how the URI creator intended.
Regards,
Ben
--
next prev parent reply other threads:[~2019-11-13 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 15:02 [bitcoin-dev] Towards a singular payment protocol ee
2019-11-13 8:52 ` Ben Dewaal [this message]
2019-11-13 17:49 ` EE
2019-11-14 12:31 ` Ben Dewaal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FRXPR01MB04543D16EA2749E6900E8C5B81760@FRXPR01MB0454.DEUPRD01.PROD.OUTLOOK.DE \
--to=b.dewaal@northernbitcoin.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=ee@cypherpunk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox