Types of Smart Contracts
Arcana uses multiple smart contracts that work together to achieve user data privacy and access control. Some of these contracts are deployed by default while others are deployed when dApps register with Arcana Network.
Arcana uses upgradable proxy contracts to implement the Arcana Network protocol.
Proxy Contract Patterns
There are multiple upgradable proxy contract patterns that are available. For example, diamond proxy, transparent proxy, beacon proxy and UUPS proxy.
Arcana uses the following proxy contract patterns while implementing the Arcana Network protocol:
- UUPS proxy
- Beacon proxy
Arcana Contract Categories
Arcana smart contracts can be categorized depending upon whether their primary function context is a dApp or the Arcana blockchain protocol as a whole. These two categories are:
-
Core System Contracts: These contracts are used to implement the core Arcana Network protocol, and are singleton in nature. All of the system contracts implement the protocol logic but not all of them store data (program state).
-
dApp Contracts: These contracts are deployed per dApp. The deployment happens after a dApp is registered with the Arcana Dashboard. Only registered dApps can integrate with Arcana SDKs.
