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

# 4. Application Architecture

![](https://qspear.gitbook.io/~gitbook/image?url=https%3A%2F%2F2125013008-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FkqLTe4judBHHTmhMtFOk%252Fuploads%252Fgv6mdxxVBwWXtSyJlg2A%252F1.png%3Falt%3Dmedia\&width=768\&dpr=4\&quality=100\&sign=b265ad19\&sv=2)

**4.1 High-Level Architecture**

The application consists of the following components:

1. **Client Application**: User interface for interaction with the blockchain.
2. **Fabric Network**: Composed of peers, orderers, and channels.
3. **Asset Registry**: A ledger maintaining details of each tokenized asset.
4. **Chaincode**: Smart contracts that define the rules for token creation, transfer, and ownership management.
5. **Database**: For storing non-blockchain data (PostgreSQL).
6. **Identity Management**: Controls user access and permissions.
7. **REST API**: NestJS
8. **Front End**: Reactjs

**4.2 Component Interaction**

* Clients interact with the Fabric network via SDKs (GO).
* Chaincode handles business logic and state changes.
* The ordering service manages the transaction order and consensus.

#### &#x20; <a href="#id-5.-implementation-details" id="id-5.-implementation-details"></a>