Return unstaked DOT to the Treasury & DCA into HOLLAR
Summary
Hydration's DOT staking position on Polkadot has been wound down and is now fully unbonded. This referendum brings the DOT home: it transfers 540,305 DOT of unstaked principal and 10,908 DOT of accumulated staking rewards — 551,213 DOT in total — from the protocol's staking accounts on Asset Hub to the Hydration Treasury, and then converts the Treasury's DOT into HOLLAR gradually via DCA.
What the call does
1. Repatriation (XCM to Asset Hub). The call instructs Hydration's sibling account on Asset Hub — which holds an Any proxy over both staking accounts — to transfer the DOT from each account directly to the Hydration Treasury:
13RSNAx31mcP5H5KYf12cP5YChq6JeD8Hi64twhhxKtHqBkg (principal): 540,305 DOT
14kovW62mmGZBRvbNT1w5J7m9SQskd5JTRTLKZLpkpjmZBJ8 (rewards): 10,908 DOT
Each account sends its own funds in its own transfer, so DOT minted on Hydration always corresponds 1:1 to DOT deposited into Hydration's sovereign account on Asset Hub. Small dust remainders (< 0.3 DOT) stay behind to cover fees; the proxy relationships remain in place.
2. DOT → HOLLAR DCA (scheduled 50 blocks after enactment). A Treasury-owned rolling DCA schedule is created, selling 22 DOT every 5 blocks (~30 seconds) along the canonical DOT → aDOT → HOLLAR route with 1% slippage protection, continuing until the Treasury's DOT balance is exhausted — roughly 9 days of continuous execution for the full amount.
Execution notes
- Withdrawal of the unbonded funds and removal of the expired governance locks on the staking account are handled separately via the existing proxy setup and complete before this referendum's enactment.
- The design is safe against ordering issues: if enactment happens before the staking account is fully withdrawable, that transfer simply does not execute and nothing is at risk — it can be re-run by a follow-up referendum. The rewards transfer and the DCA are unaffected.
- Executed end-to-end on a chopsticks fork of Hydration + Asset Hub: transfers arrive in full, the DCA schedule is created and trades execute as specified.
Preimage hash: 0x5f847f928bc3e1d1f05f92772bd5eabcf881e4a82490f5eefc32fea22467d687 (length 440)