Whitepaper v1 is out: what coordination holds, and what it cannot

Product · Monitor

See what the chain actually did

After the wallet closes, an app often stops knowing things. Mutiq keeps reading: the hash, the receipt, the signer's nonce. Then it says submitted, pending, confirmed, reverted or replaced.

Illustration

HashReceiptNonce
One stateMutiq

Nonce Coordination

Latest, pending and the line

Every signer has one line of nonces. Mutiq reads latest and pending for a signer your app controls and compares them with what the app sent. A low-fee transaction at the front, a skipped number, a nonce already used by something else: each gets a plain hint.

Nonce 12confirmed
Nonce 13waiting, front of line
Nonce 14missing
Nonce 15waiting behind the gap

Illustration of a line with a gap

Why it matters

Pending is not an answer

Replaced

A faster twin

The wallet sped it up. The old hash is gone and the nonce is used.

Stuck

Low fee at the front

Everything after it waits. The way out is the same nonce with a higher fee, in the wallet.

Gap

A missing number

A script skipped a nonce, and later transactions wait for it.

Conflict

Two actions, one thing

Two open actions touch the same resource, and their order decides the outcome.

Conflict Inspector

Actions that share a key

You declare a conflict key for what an action touches, like profile:42. Open actions that share one are grouped, and two actions on one nonce or one function are flagged too. A namespace can make it strict: the ledger then refuses a new action while another with the same key is open.

Monitor toolkit

The whole trail, in one place

State Monitor

Five states, each read from chain data, with the block and gas once mined.

Replaced detection

A missing hash on a used nonce reads as replaced. Attach the new hash to keep following it.

Nonce report

Latest, pending, in flight, gaps and the next free number.

Stuck hint

Called out after five minutes at the front of the line.

Conflict groups

Declared keys first, then shared nonces, then same-function hints.

Activity Timeline

Local steps and ledger events side by side, newest first.

Any hash

Paste a transaction hash and read its state, no wallet needed.

Bound hashes

On the ledger a hash can belong to one action per namespace.

What it can see

Signers you control

All integrations
  1. 01

    Your connected signer

    Full nonce report, compared with what this app sent.

  2. 02

    Any public hash

    State, block and gas from the chain.

  3. 03

    Other people's signers

    No coordination. Mutiq cannot manage nonces it does not control.

Rollups may keep no public mempool, so latest and pending often match even with a send in flight.

Ready to coordinate?

Click one button twice and watch one action land in the queue. Then read exactly what it holds and what it cannot.

Not a trading bot · Not a wallet · Not a chain · Your wallet signs every transaction