Return EURC and DOT stranded on a Safe multisig address to its owner

Summary

This referendum moves 9,998 EURC and 0.5 DOT from the Hydration EVM account 0x1517C2625c88Dc0BfD98ACFac665CCDE8750E150 to 0xB6F4A5e7DE61CAc0a853dbf7DB2b23abe84b95e6, the address requested by the owner. It runs on the Root track because it dispatches on behalf of an account that cannot sign on Hydration.

Background

0x1517C2625c88Dc0BfD98ACFac665CCDE8750E150 is a Safe multisig contract deployed on Base. Safe is not deployed on Hydration, so the same address on Hydration's EVM is a plain account with no key behind it and no contract to control it. The tokens that were sent to this address on Hydration are therefore stuck: they are held by the account 12ZuLmUK9pXEs19f7b71tMC3ffCNdbUCNwXbK2dfF5XzXWZs (the Hydration mapping of that EVM address) and nobody can sign for it.

The owner has proven control of the Safe by signing a message from it on Base that names the exact assets and the destination: "I would like the tokens on Hydration EVM chain to be transferred to the signer of this address being on Hydration, no need to bridge: 0xB6F4A5e7DE61CAc0a853dbf7DB2b23abe84b95e6. Tokens in question being 9998 EURC and 0.5 DOT." (https://app.safe.global/transactions/msg?safe=base:0x1517C2625c88Dc0BfD98ACFac665CCDE8750E150&messageHash=0xfa6910e997fc2f3c4434b38059e4ffbf4c85a5188ea33c93c82857b6ce0956ee). The Safe is a 1-of-1 multisig and 0xB6F4A5e7DE61CAc0a853dbf7DB2b23abe84b95e6 is its sole owner, so the destination is the same key that controls the Safe.

What the call does

The call is a batch of two dispatchAs steps, each acting as the stranded account and transferring the full balance of one asset to the destination: first EURC (Wormhole, asset 44), then DOT (asset 5). The destination is the Hydration account of 0xB6F4A5e7DE61CAc0a853dbf7DB2b23abe84b95e6, which the owner already uses on Hydration. No treasury funds are involved and no other account or parameter is touched. The stranded account is emptied and reaped.

Verification

The full call was executed on a fork of mainnet at block 15130242 and via the live runtime's dry-run API under Root origin: both inner dispatches returned Ok, 9,998 EURC and 0.5 DOT arrived at 12ZuLmUsavxb5EokjC3gb2cyj7f1vcgVVkyFNSSuZ7WatqHU, and the source account was reaped.

Preimage hash: 0xcbdc27c862e24bfafefb3cf0a71799c3afc47f1baba30b17e05dd031a6a665b3
Track: Root

Return EURC and DOT stranded on a Safe multisig address to its owner

This is a proposal to give back some lost crypto tokens to the person who owns them.

What happened

Someone sent 9,998 EURC and 0.5 DOT to an address on Hydration.
That address was supposed to be controlled by a Safe multisig on Base.
But Safe doesn't work on Hydration, so nobody had the key to move the tokens.
The tokens got stuck.

The fix

The real owner proved it was theirs by signing a message on Base.
The owner asked for the tokens to be sent to 0xB6F4A5e7DE61CAc0a853dbf7DB2b23abe84b95e6.
This proposal moves the tokens to that address.
Tests showed the transfer works and the empty account gets cleaned up.
No one else's money is touched.