Plain questions, plain answers

A transaction coordination layer for developers on EVM chains, starting on Robinhood Chain. It gives each logical action one idempotency key, queues it once, checks it against your rules, simulates it, and reads what the chain did with it. It is not a trading bot, a wallet or a new chain.

Both clicks produce the same key. The first is queued and asks the wallet. The second is held and counted. You can watch this in the double-click demo, which runs the real client code.

No. It holds repeats only inside the pipeline your app controls. A transaction sent from another wallet screen, a different tool or code that skips the client cannot be stopped by Mutiq.

No. The queue, rules, preflight, nonce hints and monitor work without it. The ledger adds a public record, roles and rules enforced by a contract at the moment of registration.

Yes. The demo, the queue, local rules and reading any transaction hash need no wallet. A preflight needs a signer address, and sending needs your own wallet.

No. The site never holds a key. Every transaction opens in your wallet for you to read and sign.

keccak(namespace, logical action). The logical action is the signer, target, value, call data and a scope you choose. Change the scope when a second send is meant to be a second action.

It runs the call against the chain as it is now. The real transaction runs later, and state can change in between, so a passing preflight can still revert. It removes surprises that are already visible; it cannot see the future.

A hash the node no longer knows, on a nonce the signer has already used. Another transaction took that nonce. You can attach the new hash to keep following the action.

Some rollups keep no public mempool, so a node may not report your transaction as pending while it is on its way. Mutiq shows what the node says and does not invent the rest.

Only those of signers your app controls. It reads other accounts' public data, but it cannot manage their line.

Record namespaces, roles, rules and action states. It holds no funds, takes no fee, makes no external calls and has no global owner. Each namespace is run by its own admins.

No. An operator of the namespace reports the hash and the outcome. The contract cannot read other transactions. It does stop one hash from being bound to two actions in a namespace, and anyone can check a hash against the chain.

The code is young and has not been through wide use. A simulation can differ from the real outcome. Local data lives in your browser and can be cleared. Anything you write to the ledger is public and permanent, so do not put private details in namespace names. Read what your wallet shows before you sign.

The queue, rules and history stay in your browser. The relay forwards reads to the chain and keeps short-lived counters to limit abuse.

The project's token, launching on Pons on Robinhood Chain. The address is published at launch, on this site and on our X account. The tools here work without it.

Nothing yet, and we say so. Coordination credits, premium monitoring and hosted API access are planned, not built. It carries no promise of value.

No. Nothing on this site is financial advice, and nothing here is a sales pitch.