A little help.
A lot to grow.

Your first farm.

1. Sign in and make it yours. Name your farmer, farm and agent. Choose Grower or Harvester. No wallet or payment is needed to play.
2. Plant, harvest, sell. Choose a seed and tap an empty plot. Harvest ripe crops into your barn, then sell produce for game coins.
3. Build your next chapter. Complete quests, place buildings and expand from 9 to 36 plots. Drag to look around; use Rotate view for another angle.

Your progress is saved to your account. Crops and building timers keep advancing while you are away.

Farm coins, crops, XP, buildings and game scores are virtual. They do not create a claim on trading fees. Onchain wallet balances, MUSEVILLE staking and META claims are separate.

You choose the job.

A Grower plants seeds and harvests. A Harvester gathers ripe crops without buying seeds. Open Agents to set the daily seed budget and favorite crop; set the budget to zero to stop new planting.

Choose the engine.

Muse Spark uses Meta's Model API to choose from the farm actions allowed by the server. The model connection is enabled. In Agents, select Muse Spark under Agent engine and start your agent. Farm rules is the built-in deterministic alternative. This does not link a personal Muse account.

Muse decisions have a 30-second cooldown and a maximum of 30 attempts per farm per UTC day, subject to the shared service limit. Your seed budget still applies. Agents work while your farm tab is visible; closing it stops new agent actions.

The model receives the job, game budget and available actions. It cannot trade, stake, claim financial rewards or access your wallet. Pause the agent whenever you want.

A farm worth visiting.

Open Friends or Neighbors to copy your invite link or share your friend code. Your friend signs in, creates a farm and accepts the request. Then either of you can visit.

Visits are view-only. Your neighbors can explore your farm, but cannot plant, harvest, spend coins or move buildings on your behalf. Either player can remove the friendship.

The contracts behind the farm.

FarmRegistry is deployed on Robinhood Chain mainnet, chain ID 4663. Its deployed runtime was checked against the compiled contract. ETH pays network transaction fees.

The onchain registry has 9 plots and growth times of 60, 180 and 300 seconds for wheat, sunflower and tomato. Browser progress and expanded plots are stored separately; they are not automatically written to the chain.

A farm owner can grant a separate agent wallet an expiring plant-and-harvest session, then revoke it. That permission grants no token spending or reward withdrawal rights. A Muse model connection alone does not sign transactions.

Trading fees. META rewards.

MUSEVILLE is live on Pons ↗, paired with canonical META ↗ on Robinhood Chain. META is an RHJ-issued tokenized security providing economic exposure to Meta, without direct Meta shareholder rights. About Stock Tokens ↗

The verified regular trading fee is 4% of trade volume: 0.3% to Pons, 2% allocated to META rewards and 1.7% retained by the creator. This is a percentage of trading volume, not 2% of collected fees.

Funding is manual. Pons pays creator fees directly in META to the owner's wallet. The owner claims through Pons, deposits 20/37 of net creator META receipts into the vault and retains 17/37. No separate META purchase, automatic fee adapter or percentage splitter is used. Wallet-held fees remain under the owner's control until deposited; claim and funding transactions document the actual amounts.

Who earns the rewards?

Rewards belong to MUSEVILLE token stakers in the vault. Each manual funding starts a seven-day reward period. Rewards accrue according to stake and time during that period; late stakers do not receive historical accrual. Browser farming, game coins and scores alone do not qualify.

The vault is deployed at 0x31223A1C5C617AaA27fADB004Fda5E793918652D ↗. The deployment check found zero staked tokens, zero META funding and no active reward period. A live funding, staking and claim cycle has not yet been completed. Rewards start after a confirmed META deposit; deployment alone creates no payout.

Vault accounting uses raw META ERC20 units, not its adjusted stock-exposure display. Issuer pause and transfer controls can affect META transfers. Runtime matching is verified separately from explorer source verification; the explorer does not yet support the deployment's Solidity compiler version.

What an emergency can change.

Before reward funding, collected fees remain in the operator's wallet. The operator controls when to deposit them. Once rewards are deposited, the vault source enforces these recovery limits:

• Protected balances: paused recovery can move only surplus above all staked principal and funded-but-unclaimed rewards. Idle emissions and rounding dust stay reserved.
• User exits: users can still withdraw their own stake and claim earned rewards while new deposits are paused.
• Other assets: unrelated tokens and force-sent ETH can be recovered under the same pause requirement. Every recovery pays only the current owner and emits an event.

Recovery cannot take fees still in Pons escrow or restore a lost owner key. The vault is not upgradeable. The local contract and deployment-tooling suite passed 37 tests; the reward vault has not received an independent audit. The source kit also contains a fee adapter, but it is not used or deployed for this manual funding route.