SETUP-41 - Upgrade Zama Gateway Contracts to v0.12

Governance
1

Summary

Upgrade GatewayConfig and Decryption implementations to v0.12.1. To execute before the Host upgrade.

Motivation & Context

Upgrades two Gateway contracts to release v0.12.1 ( Release v0.12.1 · zama-ai/fhevm · GitHub ). GatewayConfig Decryption

Proposed Changes

The following on-chain action(s) execute when the proposal is approved and executed (Ethereum mainnet → destination chain (via LayerZero)):

Action 1 (cross-chain): sendRemoteProposal on GOVERNANCE_OAPP_SENDER (0x1c5D750D18917064915901048cdFb2dB815e0910) — dispatches to the destination chain via LayerZero:

  • upgradeToAndCall(address,bytes) on GATEWAY_CONFIG 0xDE537Be194777A56f8B19d14079E6a78249390ab [gateway]
  • upgradeToAndCall(address,bytes) on DECRYPTION 0x0f6024a97684f7d90ddb0fAAD79cB15F2C888D24 [gateway]

Technical Details

  • Network: Ethereum mainnet → destination chain (via LayerZero)
  • Proposal: SETUP-41
  • Proposal plugin: SETUP_MULTISIG 0xBc860b6a4C860C5424B84A056E53ACFb2C99a38F (Aragon OSx Multisig, 3/5)
  • Creation transaction (ProposalCreated): 0x8b34e1bec22317cefe6ebef262596d6aad208ed8e324ada908f67374cc2e36c7 — block 25486689, 2026-07-08
  • Target contract(s):
  • 0x1c5D750D18917064915901048cdFb2dB815e0910 — GOVERNANCE_OAPP_SENDER (ethereum, layerzero_oapp_sender)
  • Addresses verifiable in the protocol-registry.
  • Cross-chain: dispatched via LayerZero from GOVERNANCE_OAPP_SENDER; after Ethereum execution, track delivery on LayerZeroScan using the execution transaction hash.

Other considerations

This proposal contains cross-chain action(s): the effect on the destination chain only lands after the Ethereum execution message is delivered by LayerZero — confirm delivery before assuming the change is live. Independently verify each target address and decoded call against the protocol-registry and the on-chain proposal.

Resources