> For the complete documentation index, see [llms.txt](https://despend.gitbook.io/despend/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://despend.gitbook.io/despend/technical-architecture/detailed-explanation-of-hierarchical-technical-architecture.md).

# Detailed explanation of hierarchical technical architecture

#### Basement support layer

The modular blockchain architecture features three core components: 1) Computing Engine: Optimized PoSP consensus mechanism enabling real-time RWA stake adjustments 2) Cross-Chain Hub: Integrated with LayerZero and CCIP protocols for seamless connectivity across 12 major blockchain networks 3) Compliance Middleware: Embedded RegTech module ensuring real-time synchronization with regulatory frameworks in Hong Kong and Singapore

#### Smart Contract Layer

Complete Contract Codebase: Github.com/OmniSense/SmartContracts Application Interface Layer Standardized Access Solutions: Payment API: Supports ISO8583 traditional protocol and Web3.js dual-mode Data Gateway: Provides SQL/GraphQL dual query interfaces Security Sandbox: Isolated environment for third-party DApp plugins


---

# 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:

```
GET https://despend.gitbook.io/despend/technical-architecture/detailed-explanation-of-hierarchical-technical-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.