You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is 5 like in Bitcoin making the P2SH addresses look the same (they start with 3). This is confusing for new people and will lead to coin loss. Lots of services use Segwit-in-P2SH as default, which is making the whole issue even worse.
I suggest to change this constant to something different which does not collide with other coins.
The text was updated successfully, but these errors were encountered:
prusnak
changed the title
Change address_version from P2SH
Change address_version for P2SH
Jun 25, 2018
Whilst it would be great to do that, as you pointed out most services only understand the 3 prefixed addresses. Changing the default version byte to something else would mean older wallets would not understand them and require adding yet another address generation option to each wallet so users can still generate the old 3 prefixed P2SH addresses.
Do you not think a better long term solution would be to migrate everyone to P2WSH and P2WPKH addresses which use the bech32 vtc prefix and thus negate this problem entirely?
Currently it is
5
like in Bitcoin making the P2SH addresses look the same (they start with3
). This is confusing for new people and will lead to coin loss. Lots of services use Segwit-in-P2SH as default, which is making the whole issue even worse.I suggest to change this constant to something different which does not collide with other coins.
The text was updated successfully, but these errors were encountered: