Timeline
What has shipped, what is being built now, and what is planned. Generated from the delivery record through a public allowlist: statuses move here when they move on the board, wording never changes without review. Dates are shipped facts; targets are targets, not promises.
August 2026
4 Aug 2026 First contract on the Stellar test networkDelivered
A trial contract proved the whole code-to-deploy path in week one, so the real registry could follow without tooling risk.
10 Aug 2026 Trust registry live on the test networkDelivered
Register, rotate key, revoke and query proven in a live demo, twelve days ahead of the committed date.
11 Aug 2026 Gates Foundation grant announcedDelivered
USD 500,000 over 24 months to build the open-source digital public infrastructure, announced publicly.
13 Aug 2026 Registry wired to the production platformDelivered
The same evening a wallet completed the first real verification carrying a registry verdict, and the registry check passes with all network access blocked.
17 Aug 2026 Issuers bound to Stellar accountsDelivered
Every live issuer bound to the Stellar account it controls through the SEP-57 identity-verifier interface, so Stellar applications can check issuer standing on-chain.
18 Aug 2026 Civitas ID branding live on the platformDelivered
The production issuer and verifier platform carries the Civitas ID name on all its surfaces.
25 Aug 2026 Registry status drives the wallet catalogueDelivered
From this day registry status decides which services appear in the wallet catalogue, so a suspended issuer disappears from it with no separate step.
26 Aug 2026 One visibility rule for every public listingDelivered
Every public service-listing door computes its visibility from registry status, so a suspended issuer disappears everywhere with no separate step.
26 Aug 2026 Paging and filters on the registry administration pageDelivered
The registry administration page gained paging and filters for its long tables.
September 2026
3 Sep 2026 Contract governance moved to a two-of-three quorumDelivered
Revocation, upgrades and role rotation now need two of three governance keys. A rehearsal of the mechanism, not yet distributed control: the public-network runbook requires a key ceremony that places the keys with three separate holders.
8 Sep 2026 Trust-layer hardeningDelivered
The hardening queue of the trust-layer stage closed: quorum administration, attribution of registry writes and scheduled renewal of entries. The threat model stays a living record in which every open threat ends as mitigated or accepted.
10 Sep 2026 Every new service starts with its own identity logDelivered
From this day a service is created together with its signed key log: the application carries the key ceremony, and approval registers the service under its self-certifying identifier.
15 Sep 2026 Separate keys for changing a log and for publishingDelivered
Owner keys, held by the owner in the Service Admin, are the keys that change an institution's log; a dashboard key is a publishing key, from which the platform accepts credential schemas only, and the platform refuses its schemas once its user is deleted.
16 Sep 2026 Owners review, repair and sign their schema listsDelivered
An owner sees every published schema with its verdict under the log's history, keeps or drops each, and signs the list once; no owner signature is placed over a list the owner has not seen.
24 Sep 2026 Institutions own their identity logs, witnessed on-chainDelivered
Each institution keeps a signed log of its own identity keys and published credential schemas; a ledger contract with no administrator and no upgrade path witnesses that log, so a forged copy cannot pass as the original and nobody, Civitas included, can rewrite anyone's history. Every service with an active registry entry now runs on its own witnessed log.
25 Sep 2026 First round of user acceptance testingDelivered
A first round of user acceptance testing ran on the production platform with participants in Kenya recruited by a partner organisation, covering the full flow from identity verification to a job offer from a test employer.
28 Sep 2026 The registry administration page shows each institution's logDelivered
For every registered institution the administration page shows its DID log, the schemas it lists, its latest version and whose witness counts, and the public addresses a verifier reads.
In progress now
Civitas-branded wallet releaseIn progress
The white-label build exists and reached external testers through a beta channel in the Kenya user acceptance test of 25 September 2026; a public store release and the first partner deployment are the remaining steps.
Document verification activationIn progress
Document-based identity verification is integrated in wallet onboarding and runs in sandbox; the current integration does not yet cover the refugee identity card issued in Kenya, a second provider for Kenya is being integrated, and production activation is pending.
Planned
early 2027 First standards-compliant releasesPlanned
W3C Verifiable Credentials 2.0 and the OpenID exchange protocols replace the current credential rail in stages, with no switch-over day for users.
first half of 2027 Open-source release of the stackPlanned
Full release of the code (MPL 2.0 intended) and the governance content (CC BY 4.0), with implementing-partner documentation and runbooks.
with the migration Wallet redesign for low-literacy usersPlanned
A redesigned wallet for people with low literacy and low-cost phones; specified, no screens built.
2027 Governance framework publicationPlanned
Institution onboarding, trust-registry governance, schema standards, and safeguarding adapted to Kenya and Colombia.
2027 Goal-path enginePlanned
From one missing credential resolved at a time to a planned path from a stated goal to the credentials it needs.
2027 Cross-network recognition gatewayPlanned
A queryable way for one network to publish which other networks' issuers it accepts, built on the emerging trust-registry query standards.
2027 to early 2028 Wallet assistant, pilot-readyPlanned
Conversational guidance in local languages under bounded, revocable delegation with an auditable action log. No assistant code exists today.
follows partner agreements Field pilots in Colombia and KenyaPlanned
None is live today and none is dated; pilot results are published before anyone is asked to depend on the piloted capability.
no date; after the next contract library audit Mainnet deploymentPlanned
The contracts move to the Stellar public network only after the audit of the next release of the contract library they build on, and after a rehearsed key ceremony places the governance keys with three separate holders.
Status, 4 November 2026: 17 delivered milestones, 2 in progress, 9 planned. Every entry links to the technical page that explains it; anything labelled planned carries no shipped code.