[Bitcoin-development] BIP 21 (modification BIP 20)

Andreas Schildbach andreas at schildbach.de
Tue Jan 31 11:55:01 UTC 2012


On 01/31/2012 11:22 AM, Wladimir wrote:

> To ensure forward compatibility with optional fields, we need to define
> how a client handles fields that it doesn't know about.
> 
> When should it display an error message, and when should it silently
> accept and ignore the extraneous fields?

IMHO its standard that unknown URL parameters are simply ignored. I
think we should not change this principle.

> (For example, if something that restricts the validity, such
> as "expires" is added later on, it is pretty important not to ignore it.
> Older clients should refuse to comply.)

In this case, you'd need to refuse *all* parameters you don't know
about. In consequence, all extensions would break older clients.





More information about the bitcoin-dev mailing list