# Incorporation of Protocol v1.1.1

- Space: [Olas (prev Autonolas)](https://snapshot.box/s:autonolas.eth.md)
- Author: 0x34471096285C2B59164E20c03f6977423a450039
- State: Passed
- Voting type: Basic
- Start: 2023-05-14 09:25 UTC
- End: 2023-05-17 09:25 UTC
- Votes: 3
- Quorum: 6,000,000 voting power
- Open in Snapshot: https://snapshot.box/#/s:autonolas.eth/proposal/0x1624db6f6e9c6df84824eeaa4a9e72ad2f2d5214ff87c78bd9f6e485f6d11778

## Results

- For: 95,000,832 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

**Simple Summary**: 

This proposal presents the DAO with a vote to
1.  integrate into the Autonolas protocol the following contracts:

- [Operator whitelist](https://etherscan.io/address/0x42042799B0DE38AdD2a70dc996f69f98E1a85260) an utility smart contract for whitelisting operator addresses;
- [ServiceRegistryTokenUtility](https://etherscan.io/address/0x3Fb926116D454b95c669B6Bf2E7c3bad8d19affA) a core smart contract for securing services with ERC20 tokens;
- [ServiceManagerToken](https://etherscan.io/address/0x2EA682121f815FBcF86EA3F3CaFdd5d67F2dB143) 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](https://etherscan.io/address/0xa0DA53447C0f6C4987964d8463da7e6628B30f82) the role of the drainer on [ServiceRegistryTokenUtility](https://etherscan.io/address/0x3Fb926116D454b95c669B6Bf2E7c3bad8d19affA )

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](https://github.com/valory-xyz/autonolas-registries/blob/main/docs/AgentServicesFunctionality.pdf) 
- [Autonolas-registries:README.md](https://github.com/valory-xyz/autonolas-registries/blob/main/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](https://etherscan.io/address/0x3Fb926116D454b95c669B6Bf2E7c3bad8d19affA) the Treasury calling changeDrainer(DrainerAddress).
- transfer ownership rights of [ServiceRegistryTokenUtility](https://etherscan.io/address/0x3Fb926116D454b95c669B6Bf2E7c3bad8d19affA) to Timelock calling changeOwner(TimelockAddress);
- transfer ownership rights of the [ServiceManagerToken](https://etherscan.io/address/0x2EA682121f815FBcF86EA3F3CaFdd5d67F2dB143) to Timelock calling changeOwner(TimelockAddress);

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

