> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/creators/manage-a-token.md). # Manage a token Pool pages show positions, activity, and **Buy**, **Sell**, and **My requests** actions. Selling your available shares uses the same holder flow as any other wallet; see [Sell pool shares](/takes-docs/holders/redeem-tokens.md#sell-pool-shares). There are no creator fee settings: the creator share is fixed by the fee distributor. ## Creator earnings Takes registers the basket's author as each pool's creator with the network's fee distributor, for new and existing pools. From then on the creator share of every request fee accrues to that wallet, together with any share the pool earned before registration. Signed in, you can read your earned, claimed and claimable amounts per network. Claim on each network with one distributor transaction for all its pools; anyone may submit the claim, and it always pays your wallet. Only the registered creator can hand future creator shares to another wallet; shares already earned stay with the current one. ## Update the description In Your baskets, choose **Edit basket**, update its thesis, icon or composition, then choose **Publish changes**. The thesis must remain nonempty. Publication appends a new immutable basket version for future pools. Existing pools retain their original version, thesis and icon. Their chain, name, symbol, composition, asset leverage and initial seed stay fixed. There is no separate website or authenticated API action to edit an existing pool's description. You can monitor positions, fills, funding, and request activity on the token page. For authority details, see [Roles and permissions](/takes-docs/security-and-trust/roles-and-permissions.md#roles-and-permissions). ## Publication and progress The editor keeps unpublished changes in memory. Leaving or reloading discards them; there is no saved draft or autosave. A failed publication keeps the form for retry. Published baskets live on the server. The author can publish a new immutable version; existing deployments keep their original version. Deployment configuration is public and selects a version, chain, effective leverage per asset and exact USDC funding. Markets, directions, order and weights stay fixed. Quotes include minimum funding, mint fees, activation reserve, net strategy equity and effective exposure. Quotes remain estimates. Prepared reviews and wallet progress persist in browser storage scoped to the API, wallet and basket, with chain/version identity. Known hashes resume tracking after reload. If the wallet outcome is unknown, check wallet activity before taking further action; no manual hash-recovery form is provided. Native USDC funding must retain enough balance for gas. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://takes.gitbook.io/takes-docs/creators/manage-a-token.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.