Summary
Governance action: “Recover tokens send to $ZAMA contract”.
Motivation & Context
A few users have sent $ZAMA to the $ZAMA contract itself following the auction. As a courtesy we can use recovery functionality built into the contract to give these back. The transactions can be seen here: https://etherscan.io/token/0xa12cc123ba206d4031d1c7f6223d1c2ec249f4f3?a=0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3
Proposed Changes
The following on-chain action(s) execute when the proposal is approved and executed (Ethereum mainnet):
Action 1: call recoverERC20 on ZAMA_TOKEN (0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3)
Action 2: call recoverERC20 on ZAMA_TOKEN (0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3)
Action 3: call recoverERC20 on ZAMA_TOKEN (0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3)
Action 4: call recoverERC20 on ZAMA_TOKEN (0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3)
Technical Details
- Network: Ethereum mainnet
- Proposal: SETUP-29
- Proposal plugin: SETUP_MULTISIG
0xBc860b6a4C860C5424B84A056E53ACFb2C99a38F(Aragon OSx Multisig, 3/5) - Creation transaction (ProposalCreated):
0x8b55e9e45329e4320a81a97c2cdb598ef156554a795bdf38490296f7ad3e38bc— block 24376837, 2026-02-03 - Target contract(s):
0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3— ZAMA_TOKEN (ethereum,erc20)- Addresses verifiable in the protocol-registry.
Other considerations
Single-chain governance action; effects apply once the proposal is executed on Ethereum mainnet. Independently verify each target address and decoded call against the protocol-registry and the on-chain proposal.
Resources
- DAO proposal: SETUP-29: Recover tokens send to $ZAMA contract
- Creation transaction: https://etherscan.io/tx/0x8b55e9e45329e4320a81a97c2cdb598ef156554a795bdf38490296f7ad3e38bc