Protocol
Keepers
Who can run a Rind keeper, bonding in $RIND, the bounty pool and slashing for bad execution.
Keepers are the part of Rind that acts. They watch positions, and when a stop fires, they submit the sale. Anyone can run one.
What a keeper does
- Reads every armed position and the current reference prices.
- Detects when a price is at or below a position's trigger.
- Builds a route to sell the position into USDG on whitelisted venues.
- Submits the execution transaction on Robinhood Chain.
The vault contract checks everything itself. It verifies the price is fresh, the market state allows a trigger, the trigger is actually hit, and the output meets the slippage cap. A keeper cannot fire a stop that has not been hit, and cannot take your tokens.
Who can run one
The keeper network is permissionless. You need:
- A Robinhood Chain RPC endpoint. The public RPC is rate-limited and not recommended for production, so use a dedicated provider.
- ETH on Robinhood Chain for gas.
- A $RIND bond, once bonding is live.
- Keeper software. A reference implementation is planned for the keeper network launch in Phase 2.
Bonding
Keepers post a bond in $RIND. The bond is collateral for good behaviour. A larger bond can raise a keeper's priority when several keepers compete for the same execution.
| Item | Intended design |
|---|---|
| Bond asset | $RIND |
| Minimum bond | Set by governance |
| Unbonding delay | A fixed period, so slashing can apply after exit |
| Priority | Higher bond and better history rank first |
The bounty pool
30% of every exit fee goes to the keeper bounty pool. A keeper that executes a stop correctly earns a bounty from the pool. Bounties reward two things:
- Speed. Executing soon after the trigger is hit.
- Quality. Returning more USDG relative to the reference price.
Slashing
Slashing exists for bad execution that the contract checks cannot fully prevent. At a high level, a keeper's bond can be reduced for:
| Behaviour | Example |
|---|---|
| Repeated poor routes | Consistently returning far less than available venues |
| Self-dealing | Routing through a pool the keeper controls to capture value |
| Griefing | Spamming executions designed to fail and delay others |
Slashing parameters and the process for proving bad execution will be published before the keeper network opens. They are subject to governance.
Liveness
Rind relies on at least one honest keeper being online. If no keeper acts, a stop that should fire will wait. Several independent keepers, competing for bounties, make that unlikely. See Risks and disclaimers.
The keeper network is planned for Phase 2. Bonding requires $RIND, which has not launched. Follow @Rind_rwa for the official announcement.