Skip to content
TIDE\n \n \n \n \n

Recurring execution protocol · Robinhood Chain

Non-custodial · Open source · Audited: not yet

Set the cadence.Capital follows.

You define the interval, the size, and the highest price you will pay. The vault holds your capital, executes on schedule, and refuses any fill outside your guard.

See how a cycle settles→
RETURNS TO CADENCE01CAPITALDEPOSITED02VAULTARMED03CADENCEWINDOW OPEN04EXECUTIONEXECUTINGPAIRUSDG → AAPLCYCLE—05SETTLEMENTCONFIRMED06NEXT CYCLESCHEDULEDNEXT WINDOW—SCHEMATIC

04 · Execution — Executing

One cycle routes to an allowlisted venue. The allowance is exact and revoked in the same call.

  1. Capital (Deposited): Capital enters the vault you own. Non-custodial, withdrawable at any moment.
  2. Vault (Armed): The vault holds it, idle, until a window opens. TIDE cannot move it.
  3. Cadence (Window open): Your interval elapses. Size and price ceiling were decided in advance.
  4. Execution (Executing): One cycle routes to an allowlisted venue. The allowance is exact and revoked in the same call.
  5. Settlement (Confirmed): Output is measured as a balance delta and checked against the floor before it is accepted.
  6. Next cycle (Scheduled): The cadence steps forward on its original grid. No burst catch-up after an outage.
Custody
Your vault, your keys. TIDE cannot move your assets.
Fee ceiling
0.50%
Hard-capped in the contract, not by policy.
Price guard
Every execution clears an on-chain floor, or it reverts.
Withdrawal
Always
Never gated. Not by a pause, not by a halt, not by a dead oracle.

The mechanism

Six stages. Every one of them verifiable.

CAPITALCADENCEWINDOWROUTESETTLEADVANCE
  1. Capital: Idle balance held in your own vault. Non-custodial, withdrawable at any moment.
  2. Cadence: You set the interval, the size, and the highest price you will pay.
  3. Window: The interval elapses. The vault reports itself executable — and why, when it is not.
  4. Route: One cycle is routed to an allowlisted venue. The allowance is exact and revoked in the same call.
  5. Settle: Output is measured as a balance delta and checked against the price guard before it is accepted.
  6. Advance: The cadence steps forward on its original grid. No burst catch-up after an outage.
01

Capital that waits is capital that drifts.

Deposit once. The balance sits in a vault only you can withdraw from — not a shared pool, not a contract TIDE can sweep, not an address anyone else controls.

02

A schedule is a decision made in advance.

Interval, size, and the highest price you will accept. Written to the contract, editable by you alone, and enforced whether or not you are watching.

03

The window opens on time, or it tells you why not.

When the interval elapses the vault reports itself executable. When it is not, it returns the reason — underfunded, paused, market closed, no price guard. Never a blank screen and a shrug.

04

One cycle. One allowance. Revoked in the same call.

The keeper routes a single cycle of capital to an allowlisted venue. The approval covers that exact amount and is set back to zero before the transaction returns.

05

What arrived is measured, not reported.

Output is the vault's own balance delta, checked against a floor derived from your limit price and the Chainlink reference. A short fill reverts the whole transaction and your capital stays where it was.

06

The grid holds.

The next window is set from the scheduled one, not from now, so cadence never drifts. And after an outage there is no burst of catch-up buys at whatever price the market happens to be.

The market

What a schedule accumulates.

Tokenized equities on Robinhood Chain track the underlying instrument. This is that instrument’s real price history — TradingView’s record, not ours.

Market data · TradingView

TIDE does not predict this line and makes no claim about it. What TIDE controls is the cadence you buy on and the highest price you will accept — and it proves both on chain, every cycle.

Guarantees

What the vault will not do.

A protocol’s promises are only worth the code that enforces them. Each of these is a refusal compiled into the contract, with the mechanism named beside it.

It will not move your assets.
Only the vault owner can call withdraw. The keeper's entire authority is to trigger one execution of a plan you configured.
It will not execute without a price floor.
A plan needs your limit price, a registry oracle, or both. With neither, canExecute returns Unguarded and execution reverts.
It will not let the keeper accept a bad fill.
minOut supplied by the keeper may only tighten the on-chain floor. A compromised keeper passing zero still cannot execute below your guard.
It will not leave an allowance standing.
The router is approved for one cycle's exact amount and reset to zero in the same transaction, before the output is even measured.
It will not overcharge you.
The fee is read from the registry and clamped locally against a compiled-in ceiling, so a compromised registry cannot raise it past 0.50%.
It will not trap you.
Withdrawal works while the vault is paused, while the protocol is halted, and while the oracle is down. The exit is never gated.
It will not strand what it bought.
Every asset a vault can accumulate, it can return — by address, not just the asset it spends. exitAll returns all of it in one transaction.

Status

Where TIDE is running, right now.

No registry is configured for Robinhood Chain Testnet in this build. The interface will read and write nothing until one is deployed and its address is set.