ConsumeFeed the Serpent

NEAR testnet · a guided demo

Feed. Pass the Bond. Redeem.

About two minutes once your wallet is funded. Test memecoins have no value, and arrivals from other chains use a stand-in for NEAR Intents.

  1. Get ready

    Open the feeding panel and connect a NEAR testnet wallet, or press “No wallet? Try as a guest.” Choose PEPE, then press “Get free test PEPE.”

    Costs and caveats

    This is the live testnet product. Use the faucet if you need test NEAR, and keep at least 0.2 NEAR available for a first feeding’s storage and gas. “Get free test PEPE” credits free test PEPE; it does not bridge real funds.

  2. Feed $10 of test PEPE

    Choose $10, read the quote, press “Feed the Serpent” and approve in your wallet. A Bond card appears.

    Costs and caveats

    The quote shows the tithe and the $CONSUME locked in your Bond before you sign. The Bond’s number and transaction link are your evidence. Dollar amounts here value test tokens at quoted prices, not money deposited.

  3. Pass the payout to another wallet

    In Bonds, choose “Send this Bond” and confirm. Switch to the recipient: the same Bond appears with the same schedule.

    Costs and caveats

    Enter a second existing testnet account you control and review the address. The transfer spends 0.01024 NEAR of storage credit plus gas; if needed it adds 0.1 NEAR of refundable credit first. No payment is collected. A sale through an approved account is tested on a local sandbox, and no marketplace has listed a Bond.

  4. Collect, or finish immediately

    Collect what has been released so far, or choose “Break the seal early” to see the entire exit now.

    Costs and caveats

    A Bond releases continuously over 30 days, so after a short wait there is a small amount to collect. The recipient’s Collect registers them for $CONSUME if needed and pays them, not the sender. Before you break the seal, the preview shows the payout and the half of the still-locked amount you give up. Confirm only after reading it.

  5. Burn and redeem

    In Redeem, choose an amount of your collected $CONSUME, inspect the basket and press “Burn and redeem.” Open its transaction and the Ledger to check the result.

    Costs and caveats

    “Burn and redeem” burns those tokens and credits your share of the test memecoins to your test Intents balance. The first redemption may add 0.1 NEAR of credit for payout records.

Why take part?

  • A contest between memecoin communities. The most fed memecoin of a week pays no tithe the next.
  • Your claim vests over 30 days. Pass the Bond on, wait and collect, or leave early and forfeit half of what is still locked.
  • No promised profit. Falling memecoin prices can lower the basket’s value, and most activity so far is the builder’s own.
The whole case

The Feast makes the basket a contest between memecoin communities. Suppose DOGE wins this week: next week a $10 DOGE feeding at unchanged prices puts the full $10 toward its Bond, while a rival paying a 1% tithe puts $9.90 toward its Bond. No memecoin feasts two weeks running, so the week after that the Feast passes to the most fed of the others, and DOGE’s supporters must sit one out before they can win it back.

The trade-off is explicit: your claim vests over 30 days. You can pass the Bond to someone else, wait and collect, or leave early and forfeit half of what is still locked. Keeping your original coins avoids these fees and constraints. The reason to participate is the shared basket and community contest, not guaranteed profit; falling memecoin prices can lower the basket’s value.

That appeal is a hypothesis. Current automated activity is run by the builder; independent user adoption has not been established.

Check the evidence

The details

Bond 26’s transfer and collection were sent through the NEAR CLI between builder-owned accounts. The demo notes distinguish live evidence from sandbox tests and include the recording script.

The automated checks exercise the site and deployed contracts on a local NEAR sandbox with a test wallet. They are not a recording of a third-party wallet session.

The builder holds the key that posts prices and the only vote in the DAO that is the guardian. Since 2026-11-11 prices are posted from a separate account, assayer.consumecash.testnet, whose only key can post prices and do nothing else. The guardian, which can replace that account, has been a DAO since 2026-11-11, with the builder's account as its only council member. The contract account's key was deleted on 2026-11-11, so its code can no longer be replaced. Read the trust assumptions before evaluating the design.

Try the live testnet demo