Tamper-proof records that hold up when both sides disagree.
Sigilbase creates tamper-proof records of the events that matter in a dispute, such as a notice served or a deliverable submitted. Each event is hashed, chained and sealed into a signed checkpoint, so you can prove a record was not altered after the fact. Verification needs no trust in Sigilbase, and no account.
When a deal turns sour, each side produces its own version of what happened and when.
A timestamp in your own system proves nothing to a counterparty who assumes you could have changed it.
Proving you served notice on a date can decide a claim, yet the proof usually rests on trust.
The Sigilbase event model, applied to a served notice.
Sigilbase records each disputable moment as one event: an actor, an action, and a payload. Examples include a notice served, a deliverable submitted, an SLA breach observed, or terms accepted. Here a company records serving a notice of breach.
{
"actor": "org:acme-ltd",
"action": "notice.served",
"payload": {
"counterparty": "org:widgetco",
"matter": "contract:2024-118",
"document_sha256": "c41b…7d02",
"method": "email+post",
"reference": "notice-of-breach-03"
}
}
Sigilbase hashes each event with SHA-256 and chains it to the previous one, so the record of when you served notice cannot be moved or edited without breaking every hash after it.
Sigilbase seals recent events into a signed checkpoint every few minutes, and either party can recompute the chain and signatures offline with the standalone verifier.
A log records events. Sigilbase makes them provable.
| Question | A record in your system | Sigilbase |
|---|---|---|
| Can either side rewrite the record in its favour? | Yes, each keeps its own copy | No, any change breaks verification |
| Can the counterparty verify without trusting you? | No, they must accept your word | Yes, offline with the standalone verifier |
| Does the proof survive the vendor disappearing? | No, it lives in one party's system | Yes, the evidence bundle verifies on its own |
| Is each event sealed and independently checkable? | No | Yes, in a signed checkpoint |
The record holds even when you and the counterparty disagree.
Sigilbase gives both parties the same sealed record, so a dispute is no longer your word against theirs. Each side can hold the evidence bundle and check it, and a tampered copy fails verification on either desk.
Sigilbase is not a party you have to believe. The standalone verifier runs offline and depends on nothing from us, so the counterparty confirms a record was not altered without taking Sigilbase, or you, on trust.
On the Business tier, Sigilbase publishes each checkpoint root to an external, public anchor, placing those roots beyond even our reach so verification never depends on records we could later change.
Questions about dispute-proof records.
What are tamper-proof records?
Tamper-proof records are records you can prove were not changed after they were made. Sigilbase creates them by hashing each event, chaining it to the one before, and sealing it into a signed checkpoint. Any later edit, deletion or reordering breaks verification, so the record either checks out intact or it does not.
How do I prove a record was not altered?
You prove it by running the standalone verifier against the evidence bundle. The verifier recomputes the hash chain and checks the signatures offline, and it reports the exact sequence number of any record that fails. Because the bundle carries its own proofs and public keys, the other side can run the same check independently.
Can the other side verify the record without trusting me or Sigilbase?
Yes. Verification uses an open-source standalone verifier that runs offline and depends on nothing from you or from Sigilbase. The counterparty checks the evidence bundle themselves, so the proof does not rest on either party's good faith.
Is a Sigilbase record admissible as legal evidence?
Tamper-evidence can strengthen the evidential integrity of a record, but admissibility and the weight given to evidence are decided by the court and depend on the jurisdiction and the facts of the case. We are not lawyers and offer no legal advice. What Sigilbase provides is a technical guarantee, verifiable by anyone, that a record was not altered after it was sealed.
What kinds of events can I record?
You can record any event that might later be disputed, such as a notice served, a deliverable submitted, an SLA breach observed, or terms accepted. Sigilbase seals whatever fields you put in the event payload, including a hash of an attached document. What each record contains is up to you.
Join the waitlist
Building now. Early access for teams that need records both sides can trust.
Could not save your email. Try again or write to hello@sigilbase.io.
No spam, one email when it opens.