-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support mainnet or testnet addresses on any derivation path #52
Comments
To add to this, I don't believe I'm able to generate testnet address even with the testnet path. Using |
Hi @kyranjamie. so if I understood well, we want to generate a testnet address for any derivation path. Your idea is passing a flag for such a case, right? can you elaborate a bit more? |
Hi @neithanmo, yeah that's pretty much it. From a consumer point of view: Here's what we have now:
here's what we're after
Stacks doesn't follow BIP-44 exactly, which is why we need this behaviour. |
This flag or network information is already part of the transaction structure,, isn't it? |
Good point. If we can infer chain from the tx, and keep the API as it is now, that would be great. |
Sorry @neithanmo Consider the address generation methods, such as |
Ok, I see that function. Yes, It seems that we can not generate a testnet address there. I am not well versed in JS, but maybe we can define an overloaded function, and have another backend function on the ledger internal side, that allows us to pass in this flag. let me dig a bit more at what we have internally, and how we can overcome this issue. |
as an update. #55 is a wip that addresses this. |
I don't believe there's an immediate rush for this feature, however inline with the expected behaviour of our addressing conventions, we do need to be able to specify network in addition to derivation path.
This could be in the form of an additional flag passed to the device.
The text was updated successfully, but these errors were encountered: