HOW IT FLIES.
No terminals, no order tickets. A Nest is a target portfolio and a spending cap — the chain does the rest, on schedule, in the open.
Choose 1–8 tokenized stocks and weight them to exactly 100%. That basket is your Nest — what your Bird believes in.
Pick an amount and a rhythm — every 12 hours, daily, or weekly. One signature authorizes a spending cap per flight. Pause or revoke anytime.
The Nest buys itself on schedule, onchain, while the Flock watches. Every flight is public. Copies are independent.
THE FLIGHT
Every successful scheduled execution is a Flight. The interface never says cron job, keeper, UserOperation, or executeBatch() — it says this:
CADENCE & SIZE
A Nest flies on one of three rhythms. Each has its own minimum, so a weekly Nest can't be starved down to a dust-sized flight:
| CADENCE | FLIGHTS / MONTH |
|---|---|
| 12 HOURS | ≈60 / mo |
| DAILY | ≈30 / mo |
| WEEKLY | ≈4.3 / mo |
WHY ROBINHOOD CHAIN
An EVM-compatible L2 built on Arbitrum technology, ETH for gas, standard tooling — and first-class ERC-4337 account abstraction: programmable wallets, batching, session keys, gas sponsorship. A consumer should not approve five transactions every time a $25 Nest flies.
SAFETY ARCHITECTURE
Automation must never mean “give BIRDEX unlimited access to my wallet and pray the Bird behaves.” The model is constrained authorization, end to end:
Every execution system assumes keys can be compromised, oracles can go stale, contracts can fail, liquidity can vanish, prices can move, and software can contain bugs. The architecture needs to survive the Bird.
COPY NEST
A public strategy can become reproducible. Copying does not send funds to the original Bird, does not grant custody, and does not make anyone an asset manager — BIRDEX copies the portfolio configuration into the copier's own independent Nest. Their capital, their schedule, their authorization. If the original changes, copies do not silently follow.
