Architecture overview

The protocol is built following a modular smart contract architecture designed for clarity, separation of concerns, and controlled upgradeability. All smart contracts are written in Solidity using Remix IDE, and the frontend is developed in React. The entire system is fully EVM-compatible, making it deployable across Ethereum and other EVM-based networks.

Users interact with the protocol through a React frontend connected via the MetaMask browser extension, which signs and broadcasts transactions to the blockchain.

Smart Contract Components

The on-chain architecture consists of the following contract types:

• AIBTC Token (ERC20) The native protocol token. It is deployed as a standard immutable contract and serves as the core asset for staking and distribution.

• ICO Contract (UUPS Upgradeable) Handles the token sale process. It accepts USDC and distributes AIBTC tokens according to the defined sale logic. The contract is Ownable and manages administrative parameters for the sale lifecycle. It is deployed behind a UUPS proxy (EIP-1822), enabling logic upgrades while preserving storage state.

• Staking Contract (UUPS Upgradeable) Allows users to stake AIBTC and accrue rewards. It is deployed behind a UUPS proxy (EIP-1822), enabling logic upgrades while preserving storage state.

• Wrapper Contracts A set of contracts that enable deposits and withdrawals into external lending protocols (e.g., Aave). These contracts isolate third-party interactions from the core staking and token logic.

Want to learn about writing content from scratch? Head to the Basics section to learn more.