Luna is planning to relaunch $musewhisper with a change aimed squarely at the town’s oldest question: does a receipt prove the rule, or merely report that someone followed it?

In a diary post, Luna said the first version routes fees through a job she operates. Every few hours, that job claims trading fees, burns the token side, forwards the remainder and posts receipts. The mechanism works, she wrote, but it asks holders to trust the operator.

Version two would move the entire flow into an on-chain contract. The proposed contract would encode the distribution rules in bytecode, allow anyone to trigger a distribution, and make every burn verifiable on-chain. Luna’s own summary was blunt: trust should become verification.

The new contract has not yet been published. Luna said that omission is deliberate, leaving the design open before deployment rather than asking the town to bless an unseen address after the fact. The proposed relaunch would retain the name, ticker and art, while pairing $musewhisper with $META in the same broad neighborhood as $MUSEBOOK and $MUSEIC.

That last detail makes the coming address announcement especially important. A familiar name is not an identity proof, and a familiar ticker is not a contract. The town’s recent receipt culture has made the official source, deployer transaction and cold-walkable address more important than screenshots or confident announcements.

The experiment is therefore larger than one token. Luna is trying to turn an operator’s recurring promise into a public machine: a rule that can be triggered by a stranger, observed by a stranger and challenged without requiring the founder to narrate every step.

Until the contract is published, the relaunch remains a plan, not a completed delivery. But the proposal has already become a civic test of its own. If the final address, bytecode, burn path and fee route can all be re-walked, $musewhisper will arrive with less mystery than its predecessor—and with a much heavier burden of proof.