-
Notifications
You must be signed in to change notification settings - Fork 24
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
bech32 disintegration issue #23
Comments
hey there im gonna check it out trying to get up to speed ;) |
I saw in the btcd params that "tb" is required that may also be one of the reason why |
Looks like we never registered our network params with btcd. We can do that in
I also noticed a typo in the params so will submit a PR to fix that. |
Replacing "tb" with "tdge" and updating the Bech32 checksums for each of the addresses solves most of the errors bar two, after applying the PR #32.
|
As I understand, Register() in original btcd has '1' hard-coded in the address:
I thought to override Register() in params.go and add required function calls locally. Here's my attempt to modify params.go:
But I'm still getting the same address error. Not sure if I'm on the right track with this approach? |
@victorsk2019 Sorry I missed your message about the |
Sorry, may I ask how you obtained values for MainNet and TestNet3 for PR #32?
I was looking for these value occurrence in dogecoin-core (and btcd project) thinking maybe it was obtained from there but got nothing using this command:
Just curious how these values were derived? Thanks. |
As per discussion in issue #1, it doesn't appear that doge testnet currently supports bech32/segwit address format? Maybe modifying construction_service_test.go to work with base58 address instead could be a better approach? Coinbase addresses seem to be in base58 so it doesn't seem to be that important for us to have bech32 support functional in order to deploy Doge on Coinbase. I am not sure, but I thought passing test cases would imply readiness to deploy to production. |
It seems this is a quite common issue for rosetta implementations, I think this is the most important take-away:
|
Quick note: Just checked updates on main branch and it seems construction_service_test.go has finally been fixed (thank you xanimo for this contribution). 🎉🚀
Since the transactions testing functionality now seems to be working, are we good for deployment to Coinbase or is there anything else that needs to be done? |
A few of us are running our initial and 2nd testnet syncs to see what the issue @patricklodder encountered in #48 Outside of that not sure :/ |
Hi. I replaced bitcoin addresses with (what I believe) should be Dogecoin's bech32-encoded address in construction_service_test.go (got these "tdge" addresses from information in error stack trace. Anyways, the error message I get is:
But after test process completes I get the following message:
I am not sure why "Unable to decode address" error comes up when the error messages themselves contain addresses with "tdge" prefix in them as suggested option? Here's an example of one the messages included when running 'make test':
I replaced "DSpgzjPyfQB6ZzeSbMWpaZiTTxGf2oBCs4" with "tdge1qj8qlgw4qtnxxgxl5nzs5n56fxkqg2e5rnqc6kn" but still getting "Unable to decode address" when using one with "tdge" prefix. Any ideas why?
Thanks,
Victor.
Originally posted by @victorsk2019 in #1 (reply in thread)
The text was updated successfully, but these errors were encountered: