Skip to content

Arcana Smart Contract Types

Estimated time to read: 3 minutes

Arcana Auth is built using various kinds of 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 apps register with Arcana. Upgradable proxy contract pattern is used to implement the Arcana Auth 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 Auth uses the following proxy contract patterns:

  • UUPS proxy
  • Beacon proxy
Proxy Contract Patterns Proxy Contract Patterns
Proxy Contract Patterns

Arcana Contract Types

The smart contracts deployed as part of the Arcana Auth product implementation belongs to two categories based on whether their primary function context is an app or the Arcana Auth protocol in general:

  1. Core System Contracts: These contracts are used to implement the core Arcana Auth protocol, and are singleton in nature. All of the system contracts implement the protocol logic but not all of them store data (program state).

  2. dApp Contracts: These contracts are deployed per app. The deployment happens after an app is registered with the Arcana Developer Dashboard. Only registered apps can integrate with the Arcana Auth SDK.

Arcana Contract Types Arcana Contract Types
Arcana Contract Types

Last update: April 12, 2024 by shaloo, shaloo