# CONSUME > A memecoin on NEAR that eats other memecoins. Feed it a listed memecoin and you get a Bond, an NFT that releases $CONSUME over 30 days. Every $CONSUME can be burned for its share of every memecoin in the Stomach. This file is for AI agents. Everything below can be checked against the contract itself. CONSUME is an entry in NEAR HACKATHON (https://nearhackathon.com), in the Memecoins With Mechanics, NFTs That Do Something and Open Innovation tracks. ## Connect - MCP server (Streamable HTTP, no key, no sign-in): `https://consume.cash/api/mcp` - MCP server (stdio), from the repository: `node agents/mcp.mjs` - The server reads the chain and prepares unsigned calls. It holds no key and signs nothing. Your own wallet signs. Tools: `overview`, `list_memecoins`, `feast_race`, `quote_feeding`, `quote_redeem`, `account`, `bond`, `recent_feedings`, `ledger`, `prepare_feed`, `prepare_collect`, `prepare_break_seal`, `prepare_redeem`, `prepare_test_deposit`. Call `overview` first. ## Where it runs - Network: NEAR testnet - CONSUME contract: `consume.consumecash.testnet` - NEAR Intents stand-in (testnet only, simulates deposits from other chains): `intents.consumecash.testnet` - RPC: `https://test.rpc.fastnear.com` ## The rules, as the contract holds them - It eats ten memecoins: DOGE, SHIB, PEPE, PENGU, SPX, TURBO, BOME, BLACKDRAGON, SHITZU, NearKat. Fed memecoins go into the Stomach and stay there until someone redeems. - A feeding earns $CONSUME at the backing: the Stomach's value divided by all $CONSUME, locked or not. So a feeding never dilutes a holder. - The tithe is the part of a feeding that earns no $CONSUME and so goes to everyone already holding. It starts at 1% and steps up 1% for every $10,000 fed, to 10% at most. - A Bond releases its $CONSUME evenly over 30 days. Collect what has been released at any time. - Break the seal to leave early: you receive what has been released plus half of what is still locked. The other half is never minted. - Redeem burns $CONSUME and pays the same share of every memecoin in the Stomach. - The Feast: each week the most fed memecoin (by USD) wins. For the following week, feeding it pays no tithe. No memecoin feasts two weeks running: the one feasting now cannot win this week's race, and if it is fed the most again the Feast passes to the most fed of the others, or to no memecoin if no other was fed. `feast_race` names who is feasting, who cannot win this week and who leads. - Limits: each memecoin has a largest feeding and a daily cap in USD (`list_memecoins`). The caps are per memecoin, not per account, so splitting a feeding across accounts gains nothing. - Prices are posted by the Assayer from NEAR Intents quotes. A feeding is refused when a price is older than 15 minutes. Redeeming needs no price and stays open. - To compare what the Assayer posted with what it says it was quoted: `overview` reports `prices.latest_round`, and `https://consume.cash/api/round` serves the same as JSON, each with the transaction. The Assayer's script writes its quotes and list prices into the `set_prices` transaction itself; the contract ignores and does not check them. `quotes_written_beside_the_prices` (`with_quotes` in the JSON) is false for a round sent without them, and then only posted prices are listed. - This code has no administrator withdrawal or parameter setter; a deployment is not immutable while a full-access key remains on the contract account. A guardian can seal or unseal a listed memecoin and replace the Assayer, nothing else, and the role can be renounced. On testnet the contract account's only key was deleted on 2026-11-11, so its code can no longer be replaced. - On testnet the Assayer is `assayer.consumecash.testnet` (since 2026-11-11). Its only access key can call `set_prices` on the contract and nothing else: https://explorer.testnet.near.org/transactions/G1LAQEv9jzRMWFqL7BQzLHwv1bkm9JYF4uLBu9qEuZ31 (account created with that key), https://explorer.testnet.near.org/transactions/3EeeVAGK8UhTaynQKyBTjuZgzpzRWuLKUFqmxMVtH1qS (named the price feeder by the guardian). Since 2026-11-11 20:30 UTC the guardian is a Sputnik DAO, `consume-guardian.sputnikv2.testnet`: https://explorer.testnet.near.org/transactions/3PdUM8nJXgu2L4eb8fDMLyXSGjkuNtJ3LHSUroZqhpnC (the handover), https://explorer.testnet.near.org/transactions/n77wbaBQSXtMtzprBa8nYM2MnqFXJ6qXcmjTk6fsBU9 (the DAO using the role). The DAO account holds no key and acts only through proposals. Its council is one account, the builder's `consumecash.testnet`, so the builder still decides alone. This limits what a leaked Assayer key can do and makes every guardian action a public proposal and vote; it does not remove the trust in the builder. ## Reading the contract directly View methods, all free: `get_config`, `get_stats`, `get_tribes`, `get_tribe`, `get_epoch_fed`, `get_feast`, `quote_meal`, `quote_redeem`, `get_vest`, `get_vests_for_owner`, `get_recent_vests`, `get_meal_credit`, `get_owed`, plus the NEP-141 and NEP-171 standards. Dollar amounts are in millionths of a dollar. $CONSUME has 18 decimals. ## The log of every mint and burn - `ledger` (or `https://consume.cash/api/ledger` as JSON) lists every feeding, every $CONSUME minted and every $CONSUME burned, newest first, each with its transaction. On a busy contract the oldest entries can drop off the list; the totals are the contract's own and stay right. - The builder's own accounts (`consumecash.testnet` and every account under it) are counted apart from everyone else's: `ledger` reports `feedings.by_builder` and `feedings.by_others`, and each entry has `by_builder`. The builder runs bots on testnet, so do not read the builder's feedings as outside use. - A feeding mints nothing: it writes $CONSUME into a Bond. $CONSUME is minted by `claim` and `exit`, and burned by `redeem`. - The entries are parsed from the contract's own events (`meal`, `claim`, `exit`, `redeem`). The tool reports `listed_totals_match_contract`. This checks aggregate arithmetic, not authenticity or completeness: the receipt data is trusted from FastNEAR. ## Acting - Feed: `mt_transfer_call` on the NEAR Intents contract with `receiver_id` set to the CONSUME contract. `prepare_feed` builds it, with the slippage floor and deadline the site uses. - Collect: `claim`. Break the seal: `exit` (1 yoctoNEAR). Redeem: `redeem` (1 yoctoNEAR). - On testnet, `prepare_test_deposit` gives free test memecoins, once an hour per memecoin. ## More - Site: https://consume.cash - Bots that use these calls (dry run unless told to sign): `agents/bots.mjs` in the repository - A 60 day simulation of supply and backing under four scenarios: `sim/` in the repository Release behavior (2026-11-11): `account` pages all Bonds at one finalized block. `prepare_redeem` tops up storage credit when needed; payout records remain funded permanently. Claims and exits clear approvals, and transfers charge a fixed 1,024-byte reserve to the initiating owner/operator. New Bond media has a hash; the changing image URL is in `extra.dynamic_media`. The active testnet contracts were upgraded without initialization; existing Bond metadata was preserved. A second upgrade of the CONSUME contract the same day added the Feast rule: no memecoin feasts two weeks running. License: AGPL-3.0-only for original CONSUME code and documentation; third-party materials retain their terms. Ledger schema: `complete` is replaced by `discovery_limits_reached`; `history_completeness` is `unknown` because former Bond holders may be missed even when every discovered page was read. Public source: https://github.com/ethboi/consume Demo guide: https://consume.cash/demo (testnet, with costs and expected outcomes). How it works: https://consume.cash/how-it-works (the rules, who holds the Assayer and guardian roles today, and which memecoins NEAR Intents will carry right now). The Simulation: https://consume.cash/simulation (sixty simulated days under four scenarios; every figure there is simulated). Direct Bond transfers: the website offers Send this Bond, validates the recipient, reviews costs, and groups a required credit top-up with nft_transfer in one transaction. Transfer spends a nonrefundable 0.01024 NEAR from the initiating account’s meal credit, plus 1 yoctoNEAR attached and gas. The recipient may need separate FT registration before claiming. There is no prepare_transfer MCP tool. A sale through an approved account (nft_approve, then nft_transfer by the approved account) is tested on a local sandbox in contracts/integration-tests/tests/sale.rs; no marketplace contract has been tried and none has listed a Bond.