enTrail

Overview

The parts, and how they fit

Three things to understand: the platform, which holds who you are and what you may reach; the box, which takes your events and seals them; and verification, which anyone can do without an account.

enTrail component mapYour systems send events to your Evidence Box, which seals them and publishes signed heads to a public log that is anchored in Bitcoin. The platform tells the box who may reach it. Anyone holding a receipt checks the log and the anchor without an account.The platformorganisations · users · access · boxesYour systemsapps · servicesagents · collectorsYour Evidence Boxone machine · your data never leaves itIngestauthenticate · validateSealchain · sign · MerkleBox consoleprojects · keys · trailStorageevents · archivePublic logsigned headsproofsBitcoinanchorvia OTSAnyone holding a receiptan auditor, a regulator, your customer — no account, and nothing of ours to trusteventsreceiptwho may enterheadsyou keep itchecks, without usenTraildocs.entrail.io
Solid lines carry data. Dashed lines are checks a third party makes on their own. Your events live on one machine; what leaves it are signed heads that contain no payload.

What each part is

PartWho runs itWhat it holds
Your Evidence BoxUs, in our environment (v1 is managed boxes only)Your events, your keys, your chain. One machine, not shared.
The platform consoleUsOrganisations, users, two-factor, and who may reach which box. No event data.
The public logUsSigned tree heads and proofs. No payloads, ever.
BitcoinNobodyA time bound we cannot move, reached through OpenTimestamps.
The verifierWhoever is checkingRuns anywhere. Needs a receipt, not an account.

End to end

  1. Your application sends an event to your box, authenticated with a project key. The box answers in milliseconds with a hash you keep. That hash is your receipt.
  2. Shortly after, the box seals a batch: it chains the events, signs the batch, and commits it to a Merkle tree.
  3. The head of that tree is published to a log your box cannot reach or change, and later anchored in Bitcoin.
  4. Anyone you hand a receipt to can check it against the log and the anchor with no account. Once they hold the anchor proof, that part of it depends on nobody — not the box, and not us.

Try it

The console is live in beta at demoplatform.entrail.io. Registration is open, so you can create an organisation and sign in while reading these pages. It is a beta environment rather than production: use it to try the system, not to hold evidence you need later.

Where to go next

What is not here, and how to get it

How managed boxes are provisioned, updated, monitored or reached for support is ours to operate and is not documented here. Every box today is managed by us; running one in your own environment is a later part of the model and is not offered yet.

Some things are left out deliberately rather than by omission. Exact rate limits and lockout thresholds, the parameters behind password hashing, internal storage layout, and the detail of how boxes are operated are not published: printing a threshold tells whoever is probing it exactly where the edge is, and it helps nobody who is integrating honestly.

None of it is secret from you. If you are completing a security review, sizing a bulk import, or need a specific number for a control, email info@entrail.io and we will give it to your team directly. The cryptography is the opposite case and is published in full, because a proof you cannot check independently is not a proof.

Found a weakness? Tell us before you tell anyone else, at info@entrail.io, and give us a reasonable chance to fix it. We would much rather hear it from you.