PSBTs & the request() interface

Signing a PSBT

For anything the friendly methods don't cover — marketplace listings, multi-party trades, multi-input transactions — build a PSBT (Partially Signed Bitcoin Transaction) yourself and hand it to the wallet for signing. The user sees exactly what they're signing; you never see their key.

// unsignedPsbt: hex or base64, built by your backend.
// Every input the wallet signs must carry its previous transaction (nonWitnessUtxo).
const { psbtHex, txHex } = await dogesoft.signPsbt(unsignedPsbt, {
  finalize: true
});
// psbtHex: the signed PSBT, base64-encoded (despite the name). hex is an alias.
// txHex:   broadcast-ready raw transaction, only when finalize is true
//          and every input in the PSBT is now signed.

// Or review + sign + broadcast in one call (PSBT as hex):
const { txid } = await dogesoft.pushPsbt(unsignedPsbtHex);

signPsbt() signs the inputs the connected account controls (or only the ones you name in inputToSign) and leaves every other input untouched, so several parties can sign the same PSBT in turn. Broadcast the final txHex from your backend with POST https://explorer.dogesoft.io/api/tx/broadcast (body {"hex": "…"}). pushPsbt() takes a hex PSBT, shows the same review, signs every remaining input and broadcasts. It fails if the transaction still isn't fully signed.

Marketplace flow — list, buy, cancel

A Doginals marketplace signs the listing, the purchase, and a self-send cancel as PSBTs through the same signPsbt() / pushPsbt() pair above. The listing stays a signed record. The purchase transaction carries one Doge Soft marketplace tag (BUY, AUCTION_SOLD, OFFER_ACCEPT, GIFT, BUNDLE, PARTIAL_FILL, COLLECTION_TRANSFER).

1. List — your backend builds an unsigned PSBT (inscription input + price output). The seller signs it without finalize. Store the signed PSBT; do not broadcast it.
2. Buy — your backend takes the stored listing PSBT, adds the buyer's payment inputs/outputs and change, and returns an unsigned-for-buyer PSBT. The buyer signs with finalize: true, and your backend broadcasts the resulting txHex (or the buyer calls pushPsbt()).
3. Cancel — your backend builds a PSBT that spends the listed inscription back to the seller. The seller signs it and you push it.

Signing a listing — ANYONECANPAY

A listing PSBT at step 1 has only the seller's inscription input — the buyer's payment input doesn't exist yet. For the seller's signature to still be valid once your backend adds that payment input later, the seller must sign with SIGHASH_SINGLE|ANYONECANPAY (0x83), not the plain SIGHASH_ALL that signPsbt() uses by default. Pass it per input via options.inputToSign:

// Seller signs only their own input, ANYONECANPAY so a buyer can add
// payment inputs later without invalidating this signature.
const { psbtHex } = await window.dogesoft.signPsbt(listingPsbtHex, {
  inputToSign: [{ inputIndex: 0, sighashType: 0x83 }]
});
// Store psbtHex. Do not broadcast — it isn't a complete transaction yet.

Any other value is rejected outright rather than silently signed as ALL. A single top-level options.sighashType applies to every signed input that doesn't set its own — useful for pushPsbt(), where the buyer's own new inputs still sign as plain ALL by default.

// Batch a listing flow by looping signPsbt() once per item,
// sequentially (one approval each). Works in both hosts.
async function signPsbtsDogesoft(items) {
  const out = [];
  for (const item of items) {
    const { psbtHex } = await window.dogesoft.signPsbt(item.psbtHex);
    out.push({ ...item, signedPsbtHex: psbtHex });
  }
  return out;
}

The request() interface

The provider also has a generic dispatcher, shaped like the EIP-1193 pattern many wallet adapters expect. These method strings behave the same in the extension and the mobile app:

const result = await window.dogesoft.request({
  method: "doge_requestAccounts"
});

const sent = await window.dogesoft.request({
  method: "doge_sendDoge",
  params: { to: "D…recipient", amount: 1 }
});

For signing (signMessage, signPsbt, pushPsbt), call the methods directly as shown above. Their request() parameter shapes aren't the same in both hosts yet. An unknown method string rejects with Error('DogeSoft: unknown method "<method>"'). See Errors.