What a key holds, and what it cannot

Inside your pipeline

What it holds

1. 01

   A double click

   Both clicks have one key, so one action and one prompt.

2. 02

   A retry after a timeout

   The retry finds the key and waits on the first answer.

3. 03

   A reload

   The queue is in storage, so the sent action is still known.

4. 04

   Two namespaces

   Same action, different keys: environments do not collide.

5. 05

   A reported hash used twice

   The ledger refuses to bind one hash to two actions.

Limits

What it cannot do

1. 01

   A send outside your pipeline

   Another wallet screen, a different tool or code that skips the client is invisible to the queue, and nothing here can stop it.

2. 02

   A second device before the ledger answers

   Browser storage is per browser. The ledger keeps a shared record and counts the repeat, but the first transaction may already be gone.

3. 03

   A state change after preflight

   A simulation describes this moment. The real transaction runs later.

4. 04

   Someone else's nonces

   Coordination covers signers your app controls. Others can only be read.

5. 05

   A false report

   The contract cannot read other transactions. An operator's hash and outcome are what the operator said; check them against the chain.

6. 06

   A wrong scope

   If your scope is too narrow, two different intentions look like one. If it is too wide, a repeat looks new. The choice is yours to get right.

Keep reading