Tezos Counter Issue

Fleeting

In tezos, you cannot submit more than one operation per account per block.

There is a counter associated to each account, this counter is incremented each time an operation is validated into a block.

Then if you need to send several transactions during the lifespan of a block (generally 30s), you forge several transactions that will have the same counter value. Therefore, only the first transaction will be accepted and the other ones will be rejected.

It’s not a big deal when you handle the signature automatically, you can gather transactions that failed, forge them again, sign them again and inject them again.

When you ask a user to sign the transaction though, for each rejected transaction, you have to forge it again and ask the user to sign it again before you inject it again (bad user experience…).

Permalink