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
-- 
_______________________________________________
bitcoin-dev mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Reply via email to