TempleDAO currently relies on a Gnosis Safe multisignature contract for the protocol’s administrative and treasury operations. The TempleDAO Multisig owns all of the protocol contracts. The multisig’s address is 0x4D6175d58C5AceEf30F546C0d5A557efFa53A950. Every Temple master is an owner on the multisig.
All protocol policies and on-chain operations are restricted by onlyOwner. Additionally, none of Temple’s smart contracts are upgradeable, so if a contract’s logic needs to be changed, the contract must be entirely redeployed.
We are working on building out a series of AMO contracts to further automate and decentralize our treasury and governance decisions. Read more about our vision for governance at TempleDAO.
The Temple Team Payments contract is the only part of the protocol that is pausable by the Temple Multisig. This pause control would allow Temple to halt claims of team payments in the event of an emergency, such as a mistake in how much $Temple is claimable for a given team member.
The remainder of the TempleDAO protocol remains immutable and forever functional in the face of adversity. If there were truly a catastrophic event, Temple could emigrate its liquidity to effectively pause the AMM. Anyone else, however, would still be able to permissionlessly provide liquidity on the Temple AMM. We want this immutability to serve as a symbol of trust that Temple cannot rug critical mechanisms such as Temple Defend or the Core Vaults.
A Timelock is a smart contract that requires any calls made to a contract to pass through a time delay, allowing users to exit the contract in advance of the change taking effect if they so desire. Since the protocol has no upgradeable contracts, and governance is not handled on-chain by the DAO, Temple does not implement any timelocks.