enTrail changelogChanges to the product and to the documentation.https://docs.entrail.io/2026-09-28T00:00:00ZenTrailv0.1 product: Seal, verify, and fail on tamperhttps://docs.entrail.io/changelog#v0.1-product-seal-verify-and-fail-on-tamper2026-09-28T00:00:00ZEvents are hashed exactly as sent, linked into a chain, signed with Ed25519 and committed to a Merkle tree. Change one byte of a payload and verification fails, naming what did not match.v0.1 product: Signed heads published off the boxhttps://docs.entrail.io/changelog#v0.1-product-signed-heads-published-off-the-box2026-09-28T00:00:00ZThe box publishes signed tree heads to a log it cannot itself change, and the log signs a receipt for every record it accepts. Inclusion and consistency proofs are available on request, so anyone can show that a later tree is an append-only extension of an earlier one.v0.1 product: Anchored in Bitcoin, checkable offlinehttps://docs.entrail.io/changelog#v0.1-product-anchored-in-bitcoin-checkable-offline2026-09-28T00:00:00ZHeads are submitted to OpenTimestamps and the proofs strengthen as Bitcoin confirms them. The shipped verifier checks an anchor with no call to us. A record sealed minutes ago correctly reports that its anchor has not landed yet.v0.1 product: The platform console, in betahttps://docs.entrail.io/changelog#v0.1-product-the-platform-console-in-beta2026-09-28T00:00:00ZOne identity for an organisation: people, second factors, and which boxes each may reach. A box holds no passwords — it trusts a five-minute signed ticket and a signed custodian list it pulls for itself.v0.1 product: Unauthenticated traffic costs a box almost nothinghttps://docs.entrail.io/changelog#v0.1-product-unauthenticated-traffic-costs-a-box-almost-nothing2026-09-28T00:00:00ZA box checks who is sending before it reads a request body. Rejected events are kept in a bounded per-environment window and expire, so bad traffic cannot fill a disk, and nothing rejected enters the evidence chain.v0.1 docs: Documentation openshttps://docs.entrail.io/changelog#v0.1-docs-documentation-opens2026-09-28T00:00:00ZThree parts: the platform, the box, and verification. How managed boxes are provisioned, updated or reached for support is internal and is deliberately not documented.v0.1 docs: Working Python and Node.js clientshttps://docs.entrail.io/changelog#v0.1-docs-working-python-and-node-js-clients2026-09-28T00:00:00ZBoth are executed before publication, and the API page reads them from disk at build time, so the code on the page is the code that was run. Neither installs a dependency.v0.1 docs: Diagrams of the component map and sign-inhttps://docs.entrail.io/changelog#v0.1-docs-diagrams-of-the-component-map-and-sign-in2026-09-28T00:00:00ZSolid lines carry data, dashed lines are checks a third party makes alone, and every figure carries a description for screen readers because figures travel without their page.