Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change address_version for P2SH #59

Open
prusnak opened this issue Jun 25, 2018 · 2 comments
Open

Change address_version for P2SH #59

prusnak opened this issue Jun 25, 2018 · 2 comments

Comments

@prusnak
Copy link
Contributor

prusnak commented Jun 25, 2018

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.

@prusnak prusnak changed the title Change address_version from P2SH Change address_version for P2SH Jun 25, 2018
@metalicjames
Copy link
Collaborator

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?

@prusnak
Copy link
Contributor Author

prusnak commented Jun 26, 2018

Long term native-segwit solution is fine and I agree, but I still think that changing the P2SH version is a very good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants