The DAO operates using five different on-chain programs.
Let's look at the various components of the DAO architecture and how they work together:
- GokiProtocol/goki smart wallet: An m-of-n multisig that has the ability to execute any arbitrary transaction instruction on the Solana network. For example, it can be used to deploy or upgrade other on-chain programs, manage spl-token mints and assets, interact with defi apps, and manage other multisigs or DAOs. It can even interact with Star Atlas programs, although support for this is not available at this time.
- Tribeca/governor: Responsible for queuing proposals that get executed by a Smart Wallet. Proposals may be created permissionlessly, but may only be activated by a member of the governor's electorate. Once activated, the proposal may be voted on by members of the electorate. A proposal successfully passes if the voting period elapses with a quorum as well as a majority of POLIS voting power ("PVP") in favor of the proposal. Successful proposals may then be queued in the smart wallet for execution.
- Tribeca/locked-voter: A specific type of electorate program in which PVP is determined by the number of governance tokens locked as well as the lock's duration. PVP decays linearly, and tokens cannot be removed prior to locker expiration.
- Sabre/snapshot: Used to provide historical balances of the user's PVP among all participants, which is used for rewards calculations.
- ATMTA/gate: The main entry point to the DAO. Gate proxies stake operations to the locked-voter program and ensure that snapshot accounts are kept in sync. It is responsible for calculating reward distribution and payouts for each participant. Governor operations are proxied through gate as well.