[Bitcoin-ml] Proposal to deploy cashaddr January, 14

[Simon Liu]

Hi,

Yes, expanding the version field works.

Currently the spec only reserves 4 bits for address types.

How about something like this?

Version field (4 bytes)
msb - reserved as zero
28 bits - address type
3 bits - size of hash

Regards,
Simon




On 11/18/2017 09:13 AM, Jason Dreyzehner wrote:
> Is it possible that your use case is handled by the version byte? If you
> want to encode more data in the payload, you can define a new version
> and get implementors to adopt it. 
> 
> If the data you want to encode doesn’t need wide ecosystem support,
> maybe it’s a good candidate for the Payment Protocol (BIPS 70-73)?
> 
> eg. In a URI:
> bitcoincash:qpzry9x8gf2tvdw0s3jn54khce6mua7lcw20ayyn?mycustomkey=mycustomvalue
> 
> In your case of out-of-band messaging – BitPay payment requests
> currently include a short memo for wallets to automatically add when
> paying a merchant. Many wallets save it as a memo in the user's
> transaction history. (e.g. “Payment request for BitPay invoice #### for
> merchant Valve Corporation”)
> 
> Jason
>