Autonolas

Simple Summary: This proposal presents the DAO with a vote to

1. integrate into the Autonolas protocol the following contracts:

• ServiceRegistryL2 a core smart contract for securing services with chain native tokens
• ServiceRegistryTokenUtility a core smart contract for securing services with ERC20 tokens
• Operator whitelist a utility smart contract for whitelisting operator addresses
• ServiceManagerToken a periphery smart contract for management of service lifecycle, managing services secured with custom ERC20 tokens or chain-native token,and checking operators against the operator whitelist of a service as specified on the operator whitelist contract.
• GnosisSafeMultisig a smart contract for Gnosis Safe multisig implementation of a generic multisig interface.
• GnosisSafeSameAddressMultisig a smart contract for Gnosis Safe verification of an already existent multisig address.
• StakingVerifier a smart contract for staking contract implementation and instance verification.
• StakingFactory a smart contract for creating new staking contract instances.
• OptimismTargetDispenserL2 a smart contract for processing tokens related to staking incentives and data received on Mode, and data sent back to L1

2. grant to the OptimismMessenger the role of the drainer on ServiceRegistryL2 and ServiceRegistryTokenUtility

Acceptance of this off-chain proposal would be a key step towards bringing Olas registry functionalities to Mode. Specifically the above contracts enable the following:

• manage an operator whitelist and have a permissioned operator sets;
• secure services with both chain-native token and ERC20 tokens;
• re-deploy in one-shot deployed services by using operators pre-signed message hashes;
• drain eventual slashed security bonds.

More information on the contracts and the new functionalities are outlined in detail here:

• AgentServicesFunctionality
• Autonolas-registries:README.md

Specification: The Autonolas protocol will call upon the Valory deployer (or any other deployer taking these actions first) to grant the drainer’s role and to transfer ownership rights of the deployed contracts to the OptimismMessenger as such:

1. grant drainer’s role by calling changeDrainer(OptimismMessenger) for the following:

• ServiceRegistryL2
• ServiceRegistryTokenUtility

2. transfer ownership rights to OptimismMessenger (unique Timelock executor L2 contract on Mode) by calling changeOwner(OptimismMessenger) for the following contracts:

• ServiceRegistryL2
• ServiceRegistryTokenUtility
• Operator whitelist
• ServiceManagerToken
• GnosisSafeMultisig
• GnosisSafeSameAddressMultisig
• StakingVerifier
• StakingFactory
• OptimismTargetDispenserL2