> 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/tip-on-the-timeline.md). # Tipping Send a $MOTION tip with one reply on X. If you get tipped, you can claim it, or leave it, and it adds to your tipping allocation. ## Built so you never sign up There is no signup and no wallet connection, you don't even sign into the app. Everything is tracked on the backend for ease of use: if you have a tipping allocation, you can start tipping right on your timeline. The only time you sign in with anything is when you claim. For that, you sign in with X to verify your identity, paste in the wallet address you want, and hit claim. Everything else is handled on the backend. ## The tip bot Tipping runs through one account: [**@tipmotion**](https://x.com/tipmotion). The bot picks up your tip command and hands it to the backend system for processing, usually within a minute or two. ## How to tip Reply to any post you want to tip: ``` @tipmotion ``` For example: ``` @tipmotion 1000 ``` That sends 1,000 $MOTION from your allocation to the post's author. `@tipmotion` and the amount come first, ahead of anything else in your reply. Whole numbers only; commas are fine. Another way to tip is to add a reason after the amount: ``` @tipmotion ``` For example: ``` @tipmotion 1000 good post on pons ecosystem, volume is one of the defining factors of a winning launchpad ``` *\[screenshot placeholder, a real tip reply on the timeline]* Behind the scenes: the backend identifies the command, checks your allocation, and moves the tip from your allocation to the target profile's received allocation. The recipient can claim it, or tip it forward to someone else. Things to know: * **`@tipmotion` comes first.** The bot mention and the amount lead your reply, your words come after them. * **Tips are final.** No undo. * **The bot answers you.** Wait for its reply before assuming anything: a confirmation means your tip settled, and if something was off, not enough allocation, a malformed amount, the bot says so right in your thread. The only tip-bot handle is **@tipmotion**. The protocol never DMs and never needs anyone to sign in with a wallet. ## Where tips come from Tips come from the tipping allocation treasury, using counterfactual transactions: a chain of tips is tracked off-chain until it is eventually claimed by an end user, and every tip is backed by the same locked treasury that runs the burns. Tips are capped at **10,000 $MOTION per tip**, with a daily limit of **50,000 $MOTION** per account. We suggest a culture of responsible tipping, keep individual tips around 1,000 to stretch your allocation across more creators. Caps respond to economic inputs and market dynamics, and can change. ## Getting tipped A tip lands keyed to your X account and waits for you. No deadline, nothing expires. You have two options, and you can mix them: * **Tip it forward.** A received tip adds to your balance, pass some or all of it on to another creator straight from the timeline. * **Claim it.** Turn it into real $MOTION in a wallet of your choosing. ## Claiming 1. **Log in with X** on your [motion.tips](https://motion.tips) profile. That's the whole identity check, no wallet connection needed. 2. **Paste in the wallet address** where you want your $MOTION sent. 3. **Hit claim.** The treasury sends everything you hold on-chain, in one transaction you can watch on the explorer.
The claim screen on motion.tips: the claimable balance, a field for the payout address, and one CLAIM ALL button.
Use a self-custody address, one whose keys are yours. Tokens sent to an exchange deposit address can be lost outright, and no one can pull them back. Tips don't earn points: a tip is generosity, not bagwork. --- # 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/tip-on-the-timeline.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.