> For the complete documentation index, see [llms.txt](https://docs.motion.tips/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motion.tips/readme.md). # What is $MOTION? **Somebody tips you. That's the door.** $MOTION is a closed tipping protocol on the X timeline. A hand-picked set of accounts, the **allocators**, hold a weekly allowance of real $MOTION to give away. ## The loop 1. **An allocator tips somebody.** A public reply on X carrying real $MOTION. Who they tip is up to them. 2. **You get paid, and put forward.** The $MOTION is yours whatever happens next. The tip is also a soft invite: one person's public judgment, not a seat. 3. **Motion scans the account.** Sign in with X. The protocol checks account age, your links to accounts it already trusts, and farm signals. A person makes the final call. 4. **You take a seat.** Motion indexes your bagwork from that day: posting, replying, quoting, retweeting. 5. **You pass it on.** Tip forward from the timeline, or claim to a wallet. No application, and no wallet until you claim. You can't ask for a tip or buy one. ## Why it's closed An open system with points attached gets gamed. The open beta took 225,000 tip bot requests in 72 hours, so V2 grows one tip at a time. ## Can I earn by posting? No, that system is gone. Posting is what an allocator sees before tipping you, and what earns points once you are inside. The tip comes first, and nothing you post while outside counts. ## If you get tipped The bot's reply links to [motion.tips/join](https://motion.tips/join). Sign in with X and the scan starts itself. Then you wait. There is no queue position to watch, because a farm could time a batch against it. The decision lands on that screen, sometimes with a **TAKE YOUR SEAT** button. A tip is not a guaranteed seat, and not every account clears bot verification. Scan criteria and scoring weights stay unpublished, because a judgment mechanism only works while it can't be gamed. ## What a seat gets you * **You get indexed**, from your seating day and not before. * **Bagwork earns points.** Posts are picked up every 10 minutes and scored every 30. [Earn Points](/qualify-and-earn.md) covers what earns nothing. * **Points weight your share** of a pro-rata airdrop. * **You can pass value on.** Tips vest over 60 days, and a claim pays out what has vested. Claiming needs a verified X account. [Tipping](/tip-on-the-timeline.md). ## Becoming an allocator Tipped, then verified, then earning points on bagwork, then holding an allowance. Promotion is a hand decision, with nothing to apply for. Allocators earn no points while they hold the role. ## You shape this An allowance is a vote about what Motion becomes, not a faucet. The people allocators pick get indexed, get scored, and one day hold allowances themselves. So the protocol measures the choosing: an allocator's standing comes from the engagement their picks draw from other members in the 24 hours after a tip. A tip nobody engages with scores zero. [The Leaderboard](/leaderboard-and-tip-allocation.md). ## What about my beta points? Frozen. Nothing from the beta carries into V2. Your tip history stays; the balance you can forward or claim goes to zero. ## Where the $MOTION comes from Tips move inside Motion's ledger and never touch the chain, so tipping costs no gas. Claiming is the one on-chain moment, under a signed permission the chain enforces: a daily limit, a season limit, an expiry. [Treasury & Delegation](/technical/delegation.md). ## At a glance | Item | Value | | --------------------- | ---------------------------------------------------------------------- | | Allocator allowance | 70,000 $MOTION a week, 5,000 max per tip, no daily cap | | Allowance week | Turns over Monday, UTC. No roll over | | Keeping the allowance | Tip on two separate days in any seven | | Posts | Picked up every 10 minutes, scored every 30 | | Tips received | Vest over 60 days (59 in practice, one-day head start) | | Chain | Robinhood Chain (id `4663`) | | Token address | `0xB0Fea401F1ee62F0e7cC3Bdf94b20c25aB5117e2` | | Explorer | [robinhoodchain.blockscout.com](https://robinhoodchain.blockscout.com) | **Next:** [How It Works](/how-it-works.md) walks one tip to a seat. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.motion.tips/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.