-
Notifications
You must be signed in to change notification settings - Fork 114
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 Taproot #263
Comments
Thanks for the issue. Good idea. I wasn't aware of BitBox. Do you know if they have any documentation for their taproot? For example what does the master public key format look like |
Currently it's just a plain |
@chris-belcher Let me know as soon as you have a patch. I have exactly this problem and can test it. |
It seems internally, descriptors are used already:
It looks like extending this to accept descriptors directly from the config is the way to go, and would make EPS more flexible and forwards-compatible. @chris-belcher do you plan to work on it? |
I don't plan to work on it for at least several months. I'd prefer not to have the config file use descriptors instead of |
There is no need to remove support for Fyi, Electrum is not the only wallet using Electrum backends, many wallets do. |
@chris-belcher I use both wallets (electrum and BitBoxApp). If EPS is not patched, sooner or later I will be forced to use another implementation. I do not use taproot addresses at the moment. But I can't work with the latest version of BitBoxApp because EPS brings this error and disconnects. |
Ah I see, yes adding additional ways to tell EPS about addresses to watch is fine. As long as it continues to work for Electrum users. |
The BitBoxApp supports Taproot receive addresses since the last release. BitBoxApp users who use EPS now get warnings like
Address not known to server
.It would be great if they could configure EPS to track Taproot addresses from an xpub/descriptor.
The text was updated successfully, but these errors were encountered: