Skip to content
ECZ-IDSDK
Free Passport: Get a FREE SDK Passport

Free identity

The free SDK Passport

One SDK Passport covers the library itself — not each release, and not each registry it is published to. This page is the whole of what the free identity establishes, and the four things it deliberately does not say.

The subject

One SDK Passport is one SDK or library

One SDK Passport is one logical SDK, library or package your organisation publishes.

What never becomes a second Passport

Releases, versions and registry channels of that library are not separate Passports.

The shape of the identifier

ECZ-XX-XXXXXX::SDK_PASSPORT-XXXXXX

A pattern, not a real record. The identifier of your organisation’s ECZ-ID Business Passport (the Parent) comes first, and the SDK Passport follows the :: separator.

Included

What the free Passport establishes

£0 · No card required · Permanent, not a trial.
  • A persistent ECZ-ID for the SDK or library.
  • Your organisation on the record as its operator. Its ECZ-ID Business Passport — Declared — FREE is created if you do not already have one.
  • A public Resolver record anyone can open, and the same record as machine-readable JSON.
  • A badge, a QR code and a share link.
  • Basic bindings to the public places where your SDK or library already appears.
  • Lifecycle and current public state, evaluated on demand.
  • Claim and recovery.
  • Basic participation in the Digital Entity Graph.
  • Essential lifecycle evidence, kept in LedgerCore.

Publishing the record is your decision. Nothing becomes public until you consent, and you can withdraw publication later.

Everything included free

Each free capability, in full

Every part of the free Passport that stands on its own has its own page: what it does, what it looks like, and where its claims stop.

The flow

How to get one

Six steps. ECZ-ID carries out the verification step; every other step needs something from you.

  1. Take the Passport

    Start in TrustOps with one sign-in. Your organisation's ECZ-ID Business Passport — Declared — FREE is reused or created, and your SDK or library gets its free SDK Passport — one ECZ-ID that does not change.

  2. Bind an asset

    Name an asset your SDK or library is known by — for example your published documentation. Binding never creates a second identity. Each binding records where it was learned.

  3. Choose and prepare a proof method

    Choose the live proof method that fits the asset: Domain /.well-known file or DNS TXT record. Places no live method reaches are marked Planned. Your ECZ-ID console gives you the exact value to publish for that method.

  4. Complete the proof and review

    Publish it on the asset you control, then tell ECZ-ID the proof is in place. The binding is reviewed before anything about it is published as verified.

  5. ECZ-ID verification, then the Resolver

    ECZ-ID checks the published proof and records the outcome with the time it checked. The Resolver then shows the binding with its proof method, its Last verified date and its Re-check due date — to anyone, with no account and no API key.

  6. Operate — re-check before reliance

    Keep the proof in place. A binding is verified as of a time, not indefinitely: ECZ-ID does not renew a bound binding, and after its method's freshness window a new binding is the fresh proof — re-check before reliance. Publish the ECZ-ID where people and machines already look. Strengthen only if it is useful: Parent verification, monitoring, evidence and authority are optional, and none is needed to hold a Passport.

The boundary

What the Passport deliberately does not say

These four distinctions are the whole reason the record is worth reading. A page may shorten its own copy; it may not weaken these.

  • DECLARED ≠ VERIFIED

    A DECLARED record states what your organisation says about itself, with the date it said it. It is not the outcome of an independent check.

  • Passport ≠ Binding

    The Passport identifies the SDK or library. A binding records a public place where it already appears. Adding a binding never creates a second identity.

  • Binding ≠ Authority

    A binding shows that a relationship has been declared. It does not grant, prove or imply authority to act.

  • Parent verification ≠ SDK verification

    A VERIFIED or ASSURED Parent verifies your organisation. It does not verify the SDK or library.

An ECZ-ID does not make anything safe, certified, approved or compliant, and holding one does not make you compliant with anything.

The Resolver is public, read-only proof of what is currently declared and verified, with the time it was read. A record is not a verdict, and the record itself says so and asks to be re-checked. Re-check before reliance.

Get a FREE SDK Passport

Where next

Keep going with ECZ-ID SDK.

Get a FREE SDK Passport