0xeb2a22b2…914esent to0x34471096…0039·#25,476,048·view on Etherscan
Olas protocol security hardening and Community Multisig guard whitelist extension. This proposal: (1) de-whitelists the same-address multisig implementations (GnosisSafeSameAddressMultisig on Ethereum and the ServiceRegistryL2 of each supported network: Gnosis, Polygon, Arbitrum, Optimism, Base, Celo, Mode; and additionally the PolySafeSameAddressMultisig on Polygon) by calling changeMultisigPermission(address,false), removing the same-address multisig adoption path from service deployment; (2) extends the Community Multisig GuardCM allowlist via setTargetSelectorChainIds with 19 additional (target, selector, chainId) combinations enabling emergency pause actions across Ethereum and all supported L2 networks (Dispenser setPauseState, ServiceManager and RegistriesManager pause, and TargetDispenserL2 pause on each L2) together with the Mode ServiceRegistryL2 and ServiceRegistryTokenUtility drain backfill; and (3) de-whitelists the OLAS fixed-price-token mech factories on the Mech Marketplace of each network where they are currently enabled (Ethereum, Gnosis, Polygon, Arbitrum, Optimism, Base and Celo) by calling setMechFactoryStatuses(address[],bool[]) with a status of false, removing the ability to create any new mech that takes payment in OLAS. In accordance with Autonolas DAO Constitution at ipfs://bafybeibrhz6hnxsxcbv7dkzerq4chssotexb276pidzwclbytzj7m4t47u