> For the complete documentation index, see [llms.txt](https://akashic-2.gitbook.io/akashic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://akashic-2.gitbook.io/akashic/ecosystem/ubiquitous-trust-network-utn.md).

# Ubiquitous Trust Network (UTN)

The **Ubiquitous Trust Network (UTN)** is the core intelligent coordination layer within the Akashic architecture. It is designed to **orchestrate decentralized services**, establish **cross-chain trust**, and enable seamless **collaboration between users, agents, assets, and systems** in a heterogeneous blockchain environment.

While Akashic Chain provides the foundational infrastructure (consensus, cross-chain communication, staking, security), **UTN is the intelligent layer** that gives meaning, behavior, and trust coordination to Web3 services.\
It transforms fragmented chains into a **unified, programmable service economy**.

### What is UTN?

UTN is a decentralized, composable service layer that enables:

* **Cross-chain service invocation and composition**
* **AI-driven intelligent agents to act on users' behalf**
* **Privacy-preserving computation (via FHE)**
* **Dynamic service validation through DDVS**
* **Trust scoring, arbitration, and service-level governance**

In essence, UTN is not a blockchain, but a **network of autonomous service protocols** that run atop blockchains enabling coordination, communication, and computation **without centralized intermediaries**.

### Core Components

**1. Intelligent Service Agents**

Autonomous agents that interact with smart contracts, protocols, or off-chain APIs on behalf of users, businesses, or applications. Agents can perform:

* Portfolio management (DeFi)
* Cross-chain asset routing
* RWA onboarding or verification
* AI-driven task execution (e.g. prediction, recommendation)

Agents are governed by deterministic logic and verified via DDVS nodes.

***

**2. Decentralized Distributed Validation Services (DDVS)**

A trustless validation system responsible for verifying agent behavior, service integrity, and state transitions across networks.

* Distributed validator nodes assess whether services meet agreed-upon protocols
* Replaces traditional oracles and centralized APIs
* Fully composable with CMQ and restaking incentives

***

**3. Cross-chain Message Queue Protocol (CMq)**

Enables secure and asynchronous communication between services across different chains.

* Guarantees message delivery, order, and execution validation
* Powers interactions between services deployed on Ethereum, BNB Chain, Solana, etc.
* Integrated with UTN for multi-hop trust paths

***

**4. Full Homomorphic Encryption (FHE)**

Enables private data computation without decryption.

* User requests, identities, and preferences remain encrypted
* Agents can execute logic without revealing sensitive information
* Supports regulated sectors like healthcare, finance, and government

***

**5. Service Composition Engine**

Allows UTN to build modular, reusable, interoperable services using:

* On-chain functions
* Off-chain data
* Agent logic
* Token-based service APIs

> UTN becomes a **service layer protocol**, not just infrastructure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://akashic-2.gitbook.io/akashic/ecosystem/ubiquitous-trust-network-utn.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.