Contract Reference

This page lists the canonical deployed addresses for the DAO Ships protocol on both networks it runs on, and what each contract does. The addresses below come from deployment-addresses.json in the contracts repository and match the addresses the live app uses in src/config/contracts.ts.

Networks

DAO Ships is live on Quai mainnet and remains deployed on the Orchard testnet for experimentation. Both run on the Cyprus-1 zone.

Both deployments use Solidity 0.8.22 and OpenZeppelin v5.

Cyprus-1 uses a sharded address scheme — all addresses on this shard begin with the 0x00 prefix, which is why deployment relies on CREATE2 salt mining (see Launch from TypeScript).

Deployed addresses

The app also references this Quai Vault infrastructure, pre-deployed by the Quai Vault project:

Derive the addresses instead of copying them

A hardcoded table of nine addresses has nine chances to be stale. You only need two per network — DAOShipAndVaultLauncher and Poster — because seven of the remaining eight are reachable on-chain from the launcher:

DAOShipAndVaultLauncher (published)
├── .daoShipLauncher()    → DAOShipLauncher
│     ├── .daoShipSingleton() → DAOShipSingleton
│     ├── .sharesSingleton()  → SharesERC20Singleton
│     └── .lootSingleton()    → LootERC20Singleton
├── .multisendCallOnly()  → MultiSendCallOnly
└── .quaiVaultFactory()   → QuaiVaultFactory
      └── .implementation()   → QuaiVault singleton

Only Poster is unreachable — it is standalone infrastructure with no back-reference from the graph — so it is the second address you pin.

const launcher = new quais.Contract(LAUNCHER, DAOSHIP_AND_VAULT_LAUNCHER_ABI, provider);
 
const daoShipLauncher = await launcher.daoShipLauncher();
const vaultFactory    = await launcher.quaiVaultFactory();
const multisend       = await launcher.multisendCallOnly();
 
const dsl = new quais.Contract(daoShipLauncher, DAOSHIP_LAUNCHER_ABI, provider);
const [daoShipSingleton, sharesSingleton, lootSingleton] = await Promise.all([
  dsl.daoShipSingleton(), dsl.sharesSingleton(), dsl.lootSingleton(),
]);

A set derived this way is internally consistent by construction. A set assembled by hand from mixed sources is not — and the failure is quiet, because a coherent-but-wrong deployment behaves perfectly right up until you notice the indexer has never heard of your DAO.

Contract roles and key functions

DAOShip

The governance engine. Deployed as an EIP-1167 clone of DAOShipSingleton. Holds no funds — all treasury actions execute against the vault via execTransactionFromModule.

Key functions:

function submitProposal(bytes calldata proposalData, uint32 expiration, string calldata details) external payable returns (uint32);
function sponsorProposal(uint32 id) external;
function submitVote(uint32 id, bool approved) external;
function processProposal(uint32 id, bytes calldata proposalData) external;
function ragequit(address to, uint256 sharesToBurn, uint256 lootToBurn, address[] calldata tokens) external;
function setNavigators(address[] calldata navigators, uint256[] calldata permissions) external; // governanceOnly
function setGuildTokens(address[] calldata tokens, bool[] calldata enabled) external;           // governanceOnly
function setGovernanceConfig(bytes calldata governanceConfig) external;                          // onlyGovernor

Permission constants: ADMIN = 1, MANAGER = 2, GOVERNOR = 4, MAX_PERMISSION = 7. The governanceOnly modifier requires msg.sender == address(this) — i.e. the call must arrive through a passed proposal.

DAOShipLauncher

EIP-1167 clone factory for DAOShip, SharesERC20, and LootERC20. Exposes launchDAOShip(...) and calculateAddresses(sender, sharesSalt, lootSalt, daoShipSalt) for deterministic address prediction.

DAOShipAndVaultLauncher

The atomic factory most callers use. One transaction predicts the DAOShip address, creates the Quai Vault with DAOShip pre-enabled as a module, then launches DAOShip with the vault as its avatar. Key functions:

function launchDAOShipAndVault(
    bytes calldata initializationParamsTemplate,
    string calldata shareTokenName, string calldata shareTokenSymbol,
    string calldata lootTokenName, string calldata lootTokenSymbol,
    address[] calldata vaultOwners, uint256 vaultThreshold,
    uint256 vaultSalt, uint256 sharesSalt, uint256 lootSalt, uint256 daoShipSalt
) external returns (address payable daoShip, address vault);
 
function calculateAllAddresses(
    address sender,
    uint256 sharesSalt, uint256 lootSalt, uint256 daoShipSalt, uint256 vaultSalt,
    address[] calldata vaultOwners, uint256 vaultThreshold, uint32 minExecutionDelay
) external view returns (address daoShip, address shares, address loot, address vault);

It emits LaunchDAOShipAndVault(daoShip, vault, shares, loot, newVault, launcher).

SharesERC20 and LootERC20

SharesERC20 is the voting token with timestamp checkpoints and auto-delegation; LootERC20 is the non-voting economic token. Both are minted and burned only by DAOShip (or a MANAGER navigator) via mintShares / mintLoot and the corresponding burns. The protocol caps a DAO at MAX_GUILD_TOKENS = 20 ragequit tokens.

Poster

An EIP-3722 content bus that emits NewPost and stores no state, so a post costs around 25K gas regardless of content length:

function post(string content, string tag) external;
event NewPost(address indexed user, string content, string indexed tag);

Indexers filter on tag (for example daoships.launcher.daoProfile) to attach metadata to DAOs, proposals, and members. See the Indexer page for how these are stored.