How to enable user-signed PSBT flow for inscription funding #4428
Unanswered
karthias93
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone 👋
I’m building a marketplace where users can create inscriptions directly from their own wallets (like UniSat or Xverse), instead of the admin’s ord wallet paying for the inscription.
The goal is:
Backend (server) prepares the commit PSBT using the user’s UTXOs.
User signs the PSBT in their own wallet (UniSat/Xverse).
After commit tx confirms, the admin wallet performs the reveal transaction to finalize the inscription.
However, the ord wallet inscribe command automatically creates and signs both commit + reveal transactions using the ord wallet’s own funds, and there’s no flag like --commit-txid or --external-psbt to attach a custom commit transaction.
I’ve seen that --dry-run can output the unsigned PSBTs, but it still builds them from the ord wallet’s internal UTXOs.
👉 Question:
Is there currently a way (or upcoming plan) to:
provide a user-signed commit PSBT to ord for the reveal phase, or
use an external PSBT that’s already signed by the user as the commit transaction input for inscription?
Essentially I want users to sign and fund their own inscription, and the admin wallet only handles the reveal.
Any suggestions, examples, or upcoming support for this flow would be super helpful 🙏
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions