-
Notifications
You must be signed in to change notification settings - Fork 5
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
Recover pubkey #36
Comments
@xoloki can support on crypto |
Raised issue 173 on micro-stacks repo. Using @noble/secp256k1 lib directly (bypassing micro-stacks) allows correct stacks address to be recovered. |
github-project-automation
bot
moved this from ✅ Done
to 📖 WIP - Reopened
in Stacks sBTC Project
Mar 16, 2023
radicleart
added a commit
that referenced
this issue
Mar 17, 2023
radicleart
added a commit
to stacks-network/sbtc-bridge-api
that referenced
this issue
Mar 17, 2023
This was referenced Mar 17, 2023
Merged
radicleart
added a commit
to stacks-network/sbtc-bridge-api
that referenced
this issue
Mar 17, 2023
* Feature: issue 38 - Op drop support - Includes fix for issue 36 - recover pubkey. - Includes some ui fixes and improvemnts * OpDrop Support and recovering public key from the script sig on unwrap. See stacks-network/sbtc-bridge-web#38 and stacks-network/sbtc-bridge-web#36
radicleart
added a commit
that referenced
this issue
Mar 17, 2023
github-project-automation
bot
moved this from 📖 WIP - Reopened
to ✅ Done
in Stacks sBTC Project
Mar 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Peg out request transmits a signature of data in the transaction.
In order to be able to filter in the UI for peg outs initiated by the current user we need;
From this we should be able to recover the users stacks pubkey and therefore display their transaction history.
The text was updated successfully, but these errors were encountered: