This referendum proposes a small production test of Hydration’s cross-chain governance deployments on Ethereum, Robinhood Chain, HyperEVM and Base. It will publish two independent transfer actions per chain, allowing the Technical Committee (TC) to fast-track one and veto the other.

Cross-chain governance lets Hydration OpenGov administer assets and contracts on other EVM chains. A referendum can authorize native-token transfers, contract calls, ownership changes and upgrades through the deployed governance controllers.

When a referendum enacts, the governance dispatcher on Hydration publishes destination-specific messages through Wormhole. Wormhole Guardians attest to those publications, and anyone can relay the signed messages to the destination controllers. Each controller verifies the source and destination, records the authorized action, and starts its review period. Relayers cannot change the authorized calls.

The destination controllers currently use these controls and periods:

• Normal execution: An OpenGov action becomes executable 24 hours after it is queued on the destination chain. Anyone may execute it during the following 7 days.
• TC fast-track: The destination’s 4-of-7 TC Safe may execute an authenticated OpenGov action before the 24-hour delay ends. It cannot change the action’s contents.
• TC veto: The TC Safe may permanently veto an ordinary OpenGov action while it remains unexecuted and unexpired. Veto remains possible after the initial 24 hours; once execution is available, transaction ordering determines which succeeds first.
• TC emergency recovery: The TC Safe may propose recovery actions, including asset migrations, ownership transfers or controller upgrades. These have a fixed 30-day delay, followed by a 7-day execution window. The TC cannot fast-track its own recovery actions.
• OpenGov veto of recovery: OpenGov can cancel a pending TC recovery action through a cross-chain cancellation action. That cancellation follows the normal destination delay, but the TC cannot veto it. It must execute before the recovery action executes or expires.

Expired actions cannot execute. Sensitive controller changes must pass through an authorized action; the deployer has no retained administrative authority. The system relies on Hydration governance, Wormhole Guardian verification and the deployed controller contracts.

For this test, the referendum publishes eight separate actions:

• Ethereum: two transfers of 0.000001 ETH; TC fast-tracks the first and vetoes the second.
• Robinhood Chain: two transfers of 0.000001 ETH; TC fast-tracks the first and vetoes the second.
• HyperEVM: two transfers of 0.000001 HYPE; TC fast-tracks the first and vetoes the second.
• Base: two transfers of 0.000001 ETH; TC fast-tracks the first and vetoes the second.

All transfers target the deployment account: 0x75aE7FDE85b447Aa02E36332F681903f3EE48630.

Each controller has been prefunded with 0.000002 native tokens. After one successful transfer and one veto, it should retain 0.000001 - half its starting balance.