VerifableStart a record
Verifable Wallet · Personal + Business

See the request. Know your authority. Decide.

The same person may act for themselves, represent an organisation, or work under a narrow mandate. The Wallet keeps the active context beside the request, selected evidence, policy and resulting receipt.

This origin links the public Web Wallet, Wallet Playground, and configured .trust workspace. The separate native Wallet is available through a controlled Windows pilot.

Native Wallet · presentation request · illustrative preview
Verifable Aholahti Reuse Oy
Presentation request

Share product condition evidence?

North Harbour Materials asks for the smallest evidence set needed to assess Lot A.

Acting as Aholahti Reuse Oy Reuse officer · mandate valid until 30 Sep
Requester
North Harbour Materials
Purpose
Assess panels for their next use
Share
Condition grade · custody event
Keep private
Workforce IDs · supplier notes
Record type
Continuing asset record

Agent proposal Human approval required by policy.

Evidence checked · 4 sources · 1 policy warning

Public now Web Wallet

Receive supported OID4VCI offers into a session-only browser store and inspect local activity.

Controlled native pilot Native Wallet

Receive credentials, review requests, consent, share, and retain local activity.

Public now Wallet Playground

Run issuer and verifier tasks in the browser with exact requests and outcomes.

Deployment-resolved workspace Organisation workspace

Organisation identity, portable mandates, bounded agents, approval policy, and receipts share one operational model.

Human agency

Room to imagine. Structure to act.

People choose the lives, work and communities they want to build. The Wallet supports that agency with personal control, portable evidence and explicit consent.

Clear permissions, verifiable evidence and accountable controls. Visible roles, policy, approvals and receipts make shared action dependable.

Reliable context can support repair, reuse, stewardship and better next uses—the practical work behind circular decisions and regenerative outcomes.

Business Wallet planner

Map the first real wallet decision.

Choose the actors, work, authority model, and systems around one concrete workflow. The browser turns those choices into a structured brief and an initial topology immediately.

01
Who needs to act?

Select every actor that participates in the first flow.

02
What should it do first?

Start with tasks. Protocol adapters follow from the selected work.

03

Name the initiating event, decision, counterparty, and expected result.

04
05
Which systems must the first flow reach?
The wallet as a window

See the situation. Decide with context. Act within authority.

Personal and Business Wallet are distinct contexts through which the same person can act. The wallet brings the actor, represented organisation, evidence, policy, and expected result into the same view. Local material remains legible, and an open protocol carries each accountable exchange.

Each verified connection preserves context that would otherwise be lost. Event history shows how confidence accumulated; disclosure review shows the smallest selected credential-and-fact path combination that satisfies the current request. Read “Imagination Architectures and the Work of Trust” ↗

Channel context belongs in that review too. An NFC, Bluetooth, or local wireless exchange can record the terminal, person, vehicle, or place the holder says they can see, alongside the independently authenticated protocol peer and relay limits. Policy may use that combined evidence to advance, warn, or stop the request; consent remains an explicit decision.

Who you arePerson + organisationThe active context stays visible
What you knowCredentials + product recordsSource, provenance, and uncertainty travel with each fact
Who you can reachPeers + public networksOpenID4VC · DIDComm · AT Protocol
What you may doConsent + bounded authorityPeople decide; agents operate within scope

Implemented · opt-in Veritas is inside the wallet. The adapter makes credential metadata queryable with exact provenance; the current build still selects SQLite by default.

Controlled native pilotOpenID4VCReceive and presentation engine
Public libraryDIDComm 2.1Secure peer messaging · native relationship binding inactive
Opt-in native experimentBluesky / AT ProtocolConnected-service identity · durable key lifecycle expanding
Native binding inactiveAgentic authorityExplicit principal, mandate, policy, and receipt
Circular operations · regenerative outcomes

Make accountable choices across a product’s next life.

A product or asset record carries material, condition, provenance, and lifecycle history. The Business Wallet establishes which organisation, person, or bounded agent may add the next event. Construction and real estate are a focus, alongside batteries, textiles, electronics, and other product groups.

Circular operations handle practical loops: maintenance, repair, reuse, remanufacture and recycling. The wider regenerative ambition asks what those choices restore and enable for people, communities and ecosystems. The Wallet carries the evidence, active principal and authority into each decision.

See product groups and template status →
  1. 01Read the recordMaterial · condition · provenance
  2. 02Evaluate evidenceVeritas · source · uncertainty
  3. 03Check authorityPerson · organisation · mandate
  4. 04Record the resultActor · principal · evidence · outcome
Delivery and evidence

Inspect the exact product boundary.

The protocol engine is public today. Wallet source on GitHub is announced, Windows is the controlled native pilot, Linux desktop is coming, and MSIX + App Installer is under evaluation. Open the table for implementation evidence and deployment boundaries.

Explore the public Verifiable protocol stack ↗
Open the complete capability evidence table Binding · evidence · boundary
Product operationBinding / availabilityEvidence and boundary
Verifiable protocol stack Public library Apache-2.0 first-party libraries implement OpenID4VC, DIDComm Messaging 2.1, WebAuthn Level 3, CTAP 2.3, selective disclosure, sensitive-memory abstractions, and TPM integration.
Public issuer + verifier Active on this origin Live OID4VCI offer and OID4VP request widgets on the shared test tenant.
Native credential receive Controlled native pilot OpenID4VCI pre-authorised-code receive is app-wired and reachable from the native wallet.
Native presentation Controlled native pilot The native Home surface exposes Present when a credential is held. The routed flow includes request intake, consent preview, disclosure, a sharing receipt, and local activity.
Veritas evidence database Public release pending Queryable evidence, possible worlds, durable history, peer operation and explainable answers. The repository address is announced and opens shortly; it may return not found until publication.
Veritas credential memory Adapter inactive by default An implemented and tested Veritas-backed store makes credential metadata queryable; the current build still selects SQLite by default.
DIDComm peer relationships Native binding inactive DIDComm Messaging 2.1 is implemented in the public Verifiable stack. Peer relationships are not yet available in the native wallet.
Bluesky / AT Protocol Opt-in native experiment A connected-service OAuth path resolves handle, DID, PDS, and authorisation server. Durable key material, refresh, recovery, and wider platform callbacks remain in development.
Organisation roles + portable mandates Native binding inactive Organisation roles, portable mandates and delegation chains are not yet available in the installed wallet.
Hardware-backed holder keys Holder-key binding inactive Hardware-backed protection for production holder keys is in development and is not active today.
CTAP 2.3 + enterprise trust Enterprise binding inactive CTAP 2.3 foundations exist in the public library. Enterprise provisioning and attestation are not yet available in the wallet.
Public wallet source Publication inactive The native wallet will be open-sourced on GitHub. Until the repository and reproducible release artifacts are public, only the Verifiable protocol library is linked as public code.
Linux desktop Package inactive Linux is a committed target. No Linux wallet download is available yet.
MSIX / App Installer delivery Public channel inactive Windows web installation and managed updates are planned. No signed public installer is available yet.

Certification, marketplace onboarding, ecosystem listings, and awards are named only when a dated external record exists. Interoperability results include the exact profile, builds, trust material, date, and terminal outcome.

Choose the next concrete step

Run an exchange or take the structured brief with you.

The technical journey carries protocol, security, and deployment detail beyond this task-first page.