Summary: Raindex is best understood not as a conventional DEX or simple orderbook, but as a programmable onchain strategy engine where each order can embed custom trading logic written in Rainlang and interpreted onchain. The important reusable mechanism is that users deposit tokens into vaults, publish perpetual strategy-orders, and then rely on competitive fillers to execute against those orders when profitable, shifting the control surface from AMM curve design or centralized bot infra toward an immutable interpreter-plus-vault-plus-filler stack.
What it does:
Lets users write token-trading strategies in Rainlang and deploy them onchain as live orders on any supported EVM network
Uses vaults instead of one-off token approvals, so orders reference reusable input and output vault balances that can support multiple strategies and assets
Computes trade behavior from dynamic algorithms rather than from fixed limit-order parameters alone, with each strategy evaluating to a maximum amount and price ratio for a trade
Relies on fillers to execute profitable opportunities against other Raindex orders or external liquidity, so users do not need to run their own bots to keep strategies active
Supports non-custodial perpetual strategies such as DCA, stop-loss logic, market making, portfolio rebalancing, dutch auctions, token buybacks, peg management, and escrow-like release logic
Publishes an open-source desktop/web app plus protocol repositories for writing, simulating, deploying, monitoring, and managing Rainlang strategies
Key claims:
The official overview says Raindex is an onchain orderbook contract where orders contain dynamic algorithms that express how tokens should move between vaults, which is the clearest reason to classify it as strategy-execution infrastructure rather than as a normal orderbook frontend
The docs emphasize that Rainlang strategies are interpreted onchain and that the language is permissionlessly extensible, so the expressive surface sits in the interpreter ecosystem rather than in one fixed order schema
The protocol overview says users deposit assets into vaults instead of repeatedly approving transfers, and that many orders can reference the same vaults, which makes balance routing and meta-strategy composition a central part of the design
The docs say deployed orders remain live perpetually until removed and are executed by fillers who capitalize on arbitrage against internal or external liquidity, which makes third-party fill incentives the practical execution engine of the system
The docs and repo README both stress that the system is non-custodial, permissionless, and has no fees or admin keys, which matters because the project is explicitly marketing immutability and user-controlled execution rather than operator-managed automation
The launch post frames Raindex as a way to get bot-like flexibility without surrendering custody or running private infrastructure, which makes it a useful comparison class for offchain trading bots, intent systems, and AMM-based automation products
Whitepaper: No canonical standalone whitepaper or litepaper surfaced in this pass. The strongest primary-source packet reviewed is saved as ../whitepapers/raindex-primary-sources-2026-05-09.md.