e.state.conflict.act.diverged.f¶
This group already has a different act in flight at that point in its key history, so signing this one would fork it.
Retrying the same thing changes nothing.
What a response says¶
This member has already signed {mine} at that point in {gid}'s key history, and this proposal is {named}. Two events at one sequence number would collect signatures with nothing to reveal the split.
The placeholders are filled from gid, mine, named, which travel positionally in the args member of the response.
What to do¶
Named for the ACT rather than for any one kind of act, because the fork does not care what the events were: a registry inception and an issuance proposed at the same moment collide exactly as two registry inceptions do. Both members proposing independently is the ordinary way it happens. Agree on one proposal and assemble that.
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.act., e.state.conflict.act.diverged..
Declared in heti.