Skip to content
Launch app
Browse documentation

Pending or rejected signature

What to do when a wallet request is waiting, declined or unsuccessful.

Reviewed .

Two kinds of signing#

Some actions ask your wallet for a message signature — a public profile, a market proposal. They cost no gas, send nothing to the chain, and complete the moment the server has verified the signature.

Everything that moves money asks for a transaction. Every such control takes two deliberate acts: the ticket arms, the confirmation sends, and Enter never submits. A first position on a market may be two transactions in a row, an approval and then the position; if you decline the first, the second is not sent.

The four states#

  • Waiting for your wallet… — the wallet prompt is open. Nothing has been sent.
  • Sent. Waiting for it to be mined… — the transaction has a hash, which is shown in full so you can paste it into the block explorer. Pressing the button again now would send a second transaction.
  • Done — it is on chain. — the receipt reported success.
  • It failed. — with one of the messages below.

The interface waits up to two minutes for a receipt. If none arrives it reports "Sent, but the receipt never arrived. Check the hash." (or the wallet's own timeout message) and keeps the hash on screen. That is not proof of failure: look the hash up in the explorer before sending again.

If you declined it#

"You declined it in your wallet. Nothing was sent." That is all that happened. There is nothing to undo.

Other messages#

  • "A request is already waiting in your wallet. Open the wallet and answer it before trying again." — you have an unanswered prompt; find it in the wallet.
  • "Your wallet has not authorised this site. Unlock it and connect again." — the wallet is locked or the site's permission was revoked.
  • "The transaction was mined and reverted — it was charged for and did nothing." — the chain accepted the transaction and the contract refused it. Gas was spent; no position, lock or claim changed. The most common causes are a position below the minimum or above your capacity, a market that closed between the ticket and the confirmation, or an earliness weight that fell below the floor you signed — the ticket refuses that last one deliberately, rather than letting it cost you.
  • A one-line message in the wallet's own words, trimmed — when none of the standard codes applied.

The interface never shows a provider's stack trace, and it never paints a success state for something that did not reach the chain: on a stage without contracts, every button says "Nothing was sent" and shows the exact call it would have made.

Before pressing again#

  1. If a hash is shown, look it up. A pending transaction will land or fail on its own.
  2. If the wallet has an open prompt, answer it.
  3. If the message says the transaction reverted, read the ticket's limits — the capacity line names the bound that binds — and adjust the amount.