e.state.conflict.duplicity.f¶
This identifier's key history forks: two valid, conflicting events share one place in it.
Retrying the same thing changes nothing.
What a response says¶
Two valid but conflicting events share sequence number {sn} in the key history of {aid}, and the superseding rules don't reconcile them, so that identifier is duplicitous.
The placeholders are filled from aid, sn, which travel positionally in the args member of the response.
What to do¶
Duplicity is a finding about the controller, not a problem with your request; more evidence cannot unfork a log. The identifier named may not be the one you asked about: a fork in a delegator's key history destroys its delegatee's verifiability just as surely as one in the delegatee's own.
Where it sits¶
| Sorter | e — Error. The problem clearly defeats someone's intentions. |
| Obstacle | e.state. — The condition of the target |
| Disposition | f — Final. Retrying the same thing changes nothing. |
A handler can match this code exactly, or by any prefix above it: e.state., e.state.conflict., e.state.conflict.duplicity..
Declared in heti.