-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
How to spend the UTXOs on a "commit tx recovery key" address? #2054
Comments
I have this same issue. Missed a step of adding to bitcoin.conf to expand the 25tx limit and now have a ton of sats stuck on addresses where the reveal was never sent. |
I'm a little confused about what a "commit tx recovery key" address is. What are the steps you used to get the address? |
There are some others here who have encountered the same issue. |
from what I was able to gather, the reason bitcoin core can't just send the commit tx output is because it's not aware of the specific script path that ord uses which at the very least includes the rune name (possibly the supply, minting specifics, etc. not sure if thats in the op_return or in the witness) so somehow will need to add that information to the createrawtransaction in bitcoin-cli so that the spend conditions are satisfied, my guess is it's stored in the wallet redb in ord but no idea how to recover it |
I transferred funds to a "commit tx recovery key" address generated by ord. The balance is visible in my Bitcoin Core wallet, but I can't spend the funds.
When I try to inscribe, it shows an error message.
error: Failed to send commit transaction because: JSON-RPC error: RPC error response: RpcError { code: -26, message: "non-mandatory-script-verify-flag (Witness program was passed an empty witness)", data: None }
When I try to transfer out, it shows:
error: JSON-RPC error: RPC error response: RpcError { code: -6, message: "Signing transaction failed", data: None }
I imported the recovery phrase into Sparrow wallet, but the UTXOs in these addresses cannot be displayed. How can I resolve this issue?
The text was updated successfully, but these errors were encountered: