# Smart Contract Architecture

SmartVaults.ai is built on the Binance Smart Chain (BSC) and uses smart contracts to manage deposits, lock periods, profit allocation, and referral distributions.

The architecture is designed to provide a structured, transparent, and automated framework for protocol operation without relying on manual intervention for core functions.

***

### **Blockchain Foundation**

SmartVaults.ai is deployed on:

* **Binance Smart Chain (BEP-20)**

The protocol uses USDT on BSC as its primary settlement asset for vault participation and profit distribution.

***

### **Core Contract Components**

The system consists of multiple functional contract layers.

#### **Vault Locking Contracts**

These contracts:

* Accept participant deposits in USDT
* Assign funds to the selected vault plan
* Enforce the defined lock duration
* Track participant positions within the vault structure

Each vault operates according to predefined smart contract rules.

***

#### **Profit Distribution Contract**

This contract is responsible for:

* Receiving realized protocol profits
* Calculating participant allocations
* Applying the protocol fee structure
* Distributing net returns according to vault participation

Only realized profits are processed through the distribution logic.

***

#### **Referral Management Contract**

This contract:

* Tracks referral relationships
* Applies the multi-level referral structure
* Distributes referral allocations automatically
* Ensures predefined percentages are executed without manual adjustment

All referral flows follow fixed protocol logic.

***

### **Core Functional Logic**

The smart contract architecture is designed to automate the protocol’s main operational processes, including:

* Deposit handling
* Vault assignment
* Lock period tracking
* Profit calculation
* Participant distribution
* Referral payouts

This creates a consistent and verifiable infrastructure layer for the platform.

***

### **Automation by Design**

SmartVaults.ai uses smart contracts to reduce operational dependency on centralized control.

This means:

* Vault rules are predefined
* Distribution logic is executed automatically
* Referral payouts follow fixed allocation paths
* Core participation mechanics are enforced on-chain

This structure improves consistency, transparency, and auditability.

***

### **Security Controls**

The protocol architecture includes multiple control mechanisms designed to reduce administrative risk.

These include:

* **Multisig treasury management** for sensitive administrative functions
* **24-hour timelock protection** for critical upgrades or changes
* Restricted access to privileged functions
* Planned third-party contract audits

These controls are intended to support secure deployment and transparent governance.

***

### **Designed for Transparency**

A key objective of the contract architecture is public verifiability.

The system is intended to provide transparent visibility into:

* Vault balances
* Participant positions
* Distribution logic
* Historical performance data
* Referral allocations

This allows participants to review protocol behavior directly on-chain.

***

### **Built for Scalability**

The architecture is designed to support future protocol growth, including:

* Additional vault structures
* Expanded reporting layers
* New strategy modules
* Broader governance functionality

This modular setup allows SmartVaults.ai to evolve without changing its core logic.


---

# Agent Instructions: 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://smartvaultsai.gitbook.io/smartvaultai-docs/technology/smart-contract-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.