Autonolas

Simple Summary:

This proposal presents the DAO with a vote to

1. integrate into the Autonolas protocol the following contracts:

• Operator whitelist an utility smart contract for whitelisting operator addresses;
• ServiceRegistryTokenUtility a core smart contract for securing services with ERC20 tokens;
• ServiceManagerToken a periphery smart contract for management of service lifecycle, managing services secured with custom ERC20 tokens or ETH, eventually checks operators against the operator whitelist of service on the operator whitelist contact.

2. grant to the Autonolas Treasury contract the role of the drainer on ServiceRegistryTokenUtility

Acceptance of this off-chain proposal would be a first step toward widen the protocol functionalities. Specifically, once this proposal and the current on-chain proposals will be executed, it will be possible to

• manage an operator whitelist and have a permissioned operators set;
• secure services with both ETH 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 to the Autonolas Treasury and to transfer ownership rights of the deployed contract to the Autonolas Timelock (https://etherscan.io/address/0x3C1fF68f5aa342D296d4DEe4Bb1cACCA912D95fE) as such:

• grant drainer’s role on ServiceRegistryTokenUtility the Treasury calling changeDrainer(DrainerAddress).
• transfer ownership rights of ServiceRegistryTokenUtility to Timelock calling changeOwner(TimelockAddress);
• transfer ownership rights of the ServiceManagerToken to Timelock calling changeOwner(TimelockAddress);