Projects
A project is where wallets, the things that trade them, and the dashboards that show them come together. Templates, paper and live, reading balances and P&L, sharing a design, and ending one.
A project holds one trading system: its wallets (labeled and grouped), its market, whether it's paper or live, the strategies, workflows, scripts, resting orders, liquidity positions and launches that trade it, and its dashboards. It's one document, so it can be versioned, diffed, exported, forked and written by an AI in one go.
Start one#
- From a template: Desk, Pair, Orders, Liquidity, Launch or Blank. Each asks for the pool or token it trades.
- From a number of wallets: a starter with that many paper wallets and an Overview tab.
- From the assistant: "set up a desk with five wallets trading VIRTUAL on Base" builds the whole thing.
- From someone else's design: fork a public project, or import a template file.
A project trades on its market's chain when that chain trades live (Robinhood Chain, Ethereum, Base, Arbitrum, Optimism, Unichain or Solana), and keeps its book in that chain's coin.
Inside a project#
| Part | Is |
|---|---|
| Wallets | Up to 200, each with a label, groups and a color |
| Tabs | Up to 30 dashboard tabs of up to 24 widgets |
| Shortcuts | Buttons that buy or sell across a selection of wallets: pick some at random, split evenly or with jitter |
| Strategies | Runs against the project's wallets |
| Workflows and scripts | Automation on the project's wallets |
| Positions | Liquidity ranges |
| Launches | The project's own token launches |
| Memory | Values workflows keep between runs |
An account has up to 10 projects.
Read it#
- Balances: every wallet's ETH, holdings, value and P&L, and the total.
- Fills: every trade, newest first.
- Automation: everything trading it, with what each made, and a week of P&L.
- P&L by origin: each shortcut, the order ticket, each strategy run, launch step and range rule, so you can see which part made or lost money.
Share a design#
- Export as a template: a file with wallet slots (no keys, addresses or balances), strategies, launches and tabs. Any value can become a question the importer answers.
- Make it public so others can fork it. Its strategies' code becomes readable, so it asks first.
- Importing or forking always makes a new paper project, with launches and range rules paused, and shows what it will create first.
End one#
Ending a project stops every strategy, order, workflow, range and queued program on it and returns its wallets to the account. You're shown what will stop first. A project can be reopened, or deleted for good by typing its name.