HyperBridge
Start a project

Trust infrastructure · KTL

TrustLayer. Records you can prove were not changed.

TrustLayer, also called KTL, keeps a signed record of important actions, links each record to the one before it, and can require several people to approve before a record counts as trusted. Each organisation works in its own separate space.

Talk to usSee what it does

What it keeps

  • Signed records
  • A chain that shows any change
  • Approvals from several people
  • A separate space per organisation

Who it is for

When an approval or a contract is disputed, the question is always the same. Who did what, and has the record changed since?

  • Teams that approve things

    Contracts, payments, releases and other actions that should need more than one person's sign-off.

  • Compliance and audit

    A record that can be checked independently, rather than a log that anyone with access could edit.

  • Products that need proof

    Software that has to show its users, partners or regulators what happened and when.

What it does

Trust you can check, not just claim.

  • Signed records

    Every record is digitally signed, and the signature is checked before the record is trusted.

  • A tamper-evident chain

    Each record carries the fingerprint of the one before it. Changing an old record breaks the chain, and that shows.

  • Approval rules

    Require N approvers out of a named group of M before a record counts as trusted. Votes are signed and cannot be changed.

  • A space per organisation

    Each organisation has its own keys, records and approvals, with role-based access for admins, approvers and viewers.

  • Key management

    Create and register signing keys for an organisation, and verify records against the registered public key.

  • API and webhooks

    Add, verify and approve records from your own software, and be notified when a record becomes trusted.

How it works

Three steps to a trusted record.

  1. Register a key

    An administrator creates a signing key for the organisation. The public key is registered so anyone can check signatures.

  2. Sign and add a record

    The record is fingerprinted, linked to the previous record, signed with the organisation's key and added to the chain.

  3. Verify and approve

    Anyone can verify a record's signature. Approvers vote, and when the required number agree, the record becomes trusted.

TrustLayer

Make approvals provable.

Tell us what needs a record that cannot be quietly changed, and we will show how TrustLayer would handle it.

Talk to us

More from HyperBridge