From: Sjors Provoost <sjors@sprovoost•nl>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>,
CryptAxe <cryptaxe@gmail•com>, Luke Dashjr <luke@dashjr•org>
Cc: Matt Corallo <matt@chaincode•com>
Subject: Re: [bitcoin-dev] BIP-21 amendment proposal: -no125
Date: Tue, 5 Dec 2017 21:00:01 +0100 [thread overview]
Message-ID: <FD79573C-4771-464B-A570-E2868BBA0CA5@sprovoost.nl> (raw)
In-Reply-To: <201712051939.33238.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
CryptAxe wrote:
> Perhaps instead of a flag that can be used to disable a specific operation, there should be a "-ignoredflags=x,y,z" section of the URI that can be used to ignore whatever BIP this might also be useful for in the future?
I don't think all BIPs lend themselves to this pattern. Can you think of another example? I also suspect each ignored flag requires carefully defined behavior, so it's probably better to spell that out in the BIP.
I also wouldn't be surprised if this BIP will get superseded in its entirety in the not too distant future; I believe there's some earlier discussion on this list about variations on BIP-71. So I don't think there will be many additional params in the future that warrant abstraction.
Luke Dashjr wrote:
>> P.S. I'd similarly suggest adding a bech32 param, but that's for another
>> discussion
>
> Bech32 addresses are just normal addresses. What need is there for a param?
>
> Luke
Most wallets consider bech32 addresses to be invalid. This would allow merchants to display a backwards compatible P2SH address and allow modern wallets to use bech32. In fact, this should be encouraged because it's slightly cheaper for the recipient to spend these funds (but not worth even a tiny increase in shopping cart abandonment).
Once the new format has sufficient adoption, merchants can simply drop support for old wallets and not use this parameter.
Sjors
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-05 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 19:24 Sjors Provoost
2017-12-05 19:39 ` Luke Dashjr
2017-12-05 20:00 ` Sjors Provoost [this message]
2017-12-05 20:06 ` CryptAxe
2017-12-11 18:19 ` Peter Todd
2017-12-23 16:25 ` Matt Corallo
2017-12-23 18:33 ` Paul Iverson
2017-12-05 19:40 ` CryptAxe
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=FD79573C-4771-464B-A570-E2868BBA0CA5@sprovoost.nl \
--to=sjors@sprovoost$(echo .)nl \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=cryptaxe@gmail$(echo .)com \
--cc=luke@dashjr$(echo .)org \
--cc=matt@chaincode$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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