The dispute: what the evidence chain brings to the table
Last updated: · Leutrim Miftaraj
In a conflict, what counts is not what happened but what can be proven. The evidence chain is built for this: append-only, hash-chained, protected against alteration at database level — with the path to qualified timestamps under Art. 41 eIDAS.
Two-sidedness
Server logs prove things for their operator; mandate evidence proves things for both sides: issuance, every verification with primary code, every escalation decision, the revocation — one chain that principal and verifier alike can export.
Integrity as mathematics
Every entry binds the hash of its predecessor; update and delete are blocked by trigger — even for administrators. The export carries an integrity root: a single altered entry visibly breaks the entire chain.
Qualified timestamps
Daily anchoring of the root through a QTSP (prepared at Mandact, active once connected) lifts the chain to eIDAS evidentiary value (Art. 41: presumption of accuracy of date and integrity) — technical evidence becomes privileged evidence.
Key takeaway
Whoever has the better chain wins the dispute before it begins. Which is why it usually never happens.
Try it yourself
Issue your first agent mandate and check your first decision with its receipt — free, in a few minutes.