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

Product

One app for orderly transactions

Mutiq sits above the contracts and wallets you already use. It gives each request a key, checks it against your rules, sends it once, and reads what became of it. It is not a trading bot, a wallet or a new chain.

Queue

Give every logical action one key, hold the repeats, and keep one state for each action until it finishes.

Action QueueRepeat detectionDeadlines
Explore the queue
Preflight

Run your rules, then a simulated call and a gas estimate. A request that would fail stops at a readable reason.

Execution PolicySimulated callGas estimate
Explore preflight
Monitor

Read submitted, pending, confirmed, reverted or replaced from the chain, with nonce hints and conflict groups.

State MonitorNonce hintsConflicts
Explore the monitor

How a request moves

Ten steps, one action

01

Namespace

One name per app or environment. Its keys, rules and roles are its own, and the creator's address is part of its id.

02

Logical action

Signer, target, value, call data and a scope you choose. This is what counts as the same thing.

03

Idempotency key

keccak(namespace, logical action). Computed the same way in TypeScript and in the contract.

04

Queue

First request wins. The repeat changes one counter and nothing else.

05

Execution Policy

Allowed target, function and count per window. Refused work ends here, with a reason.

06

Transaction Preflight

Parameters, target code, a simulated call from the signer, gas, and whether the balance covers it.

07

Single-flight send

One wallet prompt per key. A repeat in flight gets the first request's answer.

08

Nonce Coordination

Latest against pending for a signer the app controls, with hints for gaps and stuck fronts.

09

State Monitor

The hash, the receipt and the nonce become one of five plain states.

10

Activity Timeline

Every local step and every ledger event, in one place. The ledger part is public and outlives your browser.

No wallet needed

Try it without sending

The double-click demo runs the real client code on a pretend slow network. The queue, rules and preflight work without a connected wallet or a deployed ledger. Sending a transaction always goes through your own wallet.

Open the demo
Hosted Developer API
Planned
$MUTIQ credits
Planned
Premium monitoring
Planned
Client package
In the repository, not on npm
The ledger contract
Written and tested, see the token and security pages

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