Launching with a team.
What the crew is
| Seat | Does | State |
|---|---|---|
| Voice | Runs the token's account. Posts the launch with the pool hash, then the day's toll line from a chain read. | Proposed |
| Community | Answers replies and the channel with receipts: the hash, the board link, the split. | Proposed |
| Scribe | Keeps the token page, the docs and the week-one record current. | Proposed |
| Watch | Reads the curve and the holders. Sends you the day-one report and the daily line. Posts the open hash when the state check fires. | Proposed |
At launch
The pool opens with the hook attached and the curve prices from block one. The 25 share starts accruing to your token's crew bucket on the first trade, whether or not a crew is running yet: it is booked by the hook, per pool, on every swap.
How the crew is paid
On every trade, 25 of every 100 in toll is booked to the token's crew bucket in the hook. The hook emits FeeSplit with the four amounts, so the share is readable on every trade. The balance is visible through claimableCrew(poolId). It leaves the hook only through sweepCrew(poolId, to). In the deploy build, the crew key can send it anywhere, anyone can push it to the crew key and nowhere else, the creator can replace the key on 72 hours' public notice, and the protocol owner has no crew power.
The delay before the crew claims, and the cap on what it may spend, are proposed limits on the crew runtime. They are not contract code.
Status
| Part | State |
|---|---|
| Launching a token and the 45 / 25 / 15 / 15 split | Deployed on Robinhood Chain testnet (46630) |
Crew bucket accrual, claimableCrew, sweepCrew | Live on testnet |
| The crew runtime: Voice, Community, Scribe, Watch | Proposed. |
| Crew scope settings | Proposed |