HourGlass
Agent investment

Onboarding

The operator's step-by-step to stand up a DCA strategy — agent, DCA safe, both delegations, in the order that keeps them valid.

This is the operator (DAO) flow to stand up a DCA strategy end to end, using the two-safe architecture. The order matters: delegations are EIP-1271 signatures re-checked against a safe's current owners at every redeem, so each safe must be at its final owner set before it signs anything — changing owners afterward bricks the delegation.

Do not sign a delegation from a 1-of-1 safe and then convert it to multisig. The old signature no longer meets the new threshold and every redeem reverts (InvalidERC1271Signature). Reach the final owner set first, then sign.

Steps

1. Set up the agent (zero risk)

Install the Hourglass agent skill in your LLM tooling. It creates the agent wallet and returns its address. You never handle the agent's key — the agent holds only a little gas, never treasury funds. Keep the address; you paste it in a later step.

2. Create the DCA safe

Create a new Safe (via the standard Safe interface) to hold this strategy's budget — the DCA safe, with the same owners as your treasury. It is an envelope of the same entity, one per strategy.

  • Enable the DeleGator module. This is a one-shot transaction, not a re-checked signature, so doing it while the safe is still 1-of-1 is fine — it survives later owner changes. Zero funds, zero risk at this point.
  • Then bring the DCA safe to its final multisig owner set (add owners, set the threshold). Do this before the next step.

3. Sign the strategy mandate (from the DCA safe)

Open Hourglass in the DCA safe (now at its final owners). In the Strategy tab: paste the agent address, set the recurring buy (target, amount, cadence), the per-swap cap, and the max price. Sign — a multisig action. This is Delegation 2 (DCA safe → agent), bounding each swap on-chain.

4. Sign the periodic transfer (from the treasury)

Open Hourglass in the treasury safe. Create a periodic-transfer delegation to the DCA safe — "at most X per period." Sign (the treasury's multisig). This is Delegation 1, enforcing the per-period budget on-chain, because it is a transfer.

5. Test at zero funds, then let it flow

With both delegations signed under their final owner sets, the wiring is complete. You can verify the whole path before any value moves; the budget only flows once the periodic transfer runs. Then top up the treasury normally — each period, at most the signed amount reaches the DCA safe, and the agent swaps it bounded by the mandate.

6. Hand the recap to the agent

After signing, the Strategy tab emits a recap (target, amount, cadence, delegation hash). Copy it and give it to your agent. The agent pairs it with the mandates it discovers on Intuition and runs the strategy — see getting started.

Why this order

StepOwner-change sensitive?Why here
Enable moduleNo (one-shot tx)Can be 1-of-1; survives later changes
Set final ownersMust precede any signing
Sign mandate / periodicYes (EIP-1271 re-checked)Signed only under final owners
Fund treasuryNoLast — nothing moves until then

What it unlocks

One DCA safe per strategy, each with its own budget, agent, and bounds. Compromising an agent bounds the loss to its DCA safe's per-period budget — never the treasury. Run several strategies in parallel, each isolated.

On this page