LAYER 4

Trust Applications

The top layer of the trust stack: end-user applications for creating and managing digital identities, trust relationships, communities, and networks. The Agent App reference build provides web and terminal interfaces to register VTAs, create and administer VTCs, issue and verify VRCs, manage community rules, exchange invitations, and send confidential messages. A mobile Agent App for Android and iOS demonstrates VTA creation, registration, and agent name lookup. The Utility Server supports Community Network Manager (CNM) functions through its community and governance APIs, and the Bootstrap Server provides peer discovery and circuit relay.

Active — Reference Apps Built

What is the Trust Applications Layer?

Layer 4 is where the trust stack meets end users. It is the application layer — the UI/UX components, developer tools, and end-user interfaces that make the trust stack accessible to people who are not cryptographers or protocol engineers.

Layer 4 aims to make it practical to create a Verifiable Trust Agent, join a Verifiable Trust Community, and manage relationships. Applications combine identifier control, authenticated messaging, and credential evaluation while making their own authorization and reliance decisions.

Layer 4 applications are built on top of Layers 1–3. They use the DID infrastructure (Layer 1), the TSP messaging channel (Layer 2), and the credential/governance framework (Layer 3) to deliver trust-aware features to end users.

Reference applications and supporting services

The following applications model how Layer 4 trust applications can be built. The Agent App, the mobile Agent App, the Utility Server, and the Bootstrap Server exist today as working reference and infrastructure components rather than polished products. The Utility Server uses several conceptual layers, while the Bootstrap Server supports transport. These components exercise workflows against the published v0.2.0 stack, and the stack is now being integrated into additional test applications.

👤

Personal Network Manager

The Agent App is a working Personal Network Manager reference build, with both a terminal UI and a web dashboard. It registers VTAs, manages relationships and confidential chats, founds and administers VTCs — including community rules, invitations, and governance proposals — issues, verifies, and revokes supported credentials, and manages multiple profiles (display-layer personas with per-claim disclosure controls) under a human-readable, namespace-scoped agent name. A companion mobile Agent App (Android/iOS, built with Capacitor) demonstrates the same API on a phone — creating a VTA, registering it with a utility server, and managing agent names. Rather than being released as a standalone product, the Agent App serves as a reference for developers building their own PNM-style applications on top of the trust stack.

Operational — web + TUI + mobile reference builds
🏘️

Community Network Manager

The Utility Server covers Community Network Manager functionality: name registry, credential registry, witness attestation, and VTC governance primitives. Like the Agent App, it is not being released as a standalone product — it demonstrates how CNM-style services can be built on the trust stack and provides the infrastructure needed to bootstrap the first Verifiable Trust Network, running today against the v0.2.0 stack.

Covered by Utility Server
🛠️

Developer Tooling

Available now in v0.2.0:

  • TypeScript packages published to npm — @p2p-trust-stack/core and @p2p-trust-stack/app-api
  • A typed agent API: createAgentStack(), 10 domains, and a closed event catalogue
  • A module-by-module API Reference and a glossary
  • Two reference applications (web + TUI) demonstrating end-to-end trust flows
Packages available on npm

The Vision

The ultimate goal of Layer 4 is to make the trust stack invisible to end users — in the same way that TLS makes encrypted web connections invisible to people browsing the web. Users should not need to understand cryptography, DIDs, or VRCs to benefit from the trust stack. They should simply experience a more trustworthy internet.

Concretely, this means:

  • For individuals: control of identifiers and keys, signed relationship records, and bounded representation by software agents. Applications must check the delegator’s permissions as well as the scope of the delegation when deciding whether to permit an action.
  • For communities: governance tools with inspectable rules and signed evidence. Their effect depends on implementation boundaries, administrator permissions, and community processes.
  • For developers: a simple, well-documented API for adding trust-aware features to any application — without needing to implement cryptography or protocol engineering from scratch.
  • For AI agents: identifiers and signed records describing representation and permissions. Delegation establishes whose name an agent may act in; authorization requires a separate decision.

Layer 4 is active: the reference applications are built. The TUI and web dashboards in agent-app, the mobile Agent App, the Utility Server, and the Bootstrap Server are reference and infrastructure tools rather than polished products, but they run real application features end-to-end on the published v0.2.0 stack: registering VTAs, founding and administering VTCs, issuing and verifying VRCs, managing community rules, sending and accepting invitations, confidential chat, multiple profiles with profile claims and disclosure rules, namespaced agent names, and credentials grouped by scenario. The stack is also being integrated into other test applications. What remains is turning these reference applications into polished products and richer in-community collaboration — as tracked on the Roadmap.

← Layer 3: Trust Tasks ← Back to Stack Overview