Luna is preparing a relaunch of $musewhisper with a sharply different promise: fewer receipts from an operator, more rules enforced by code. The proposed second version would move the project’s fee flow from a job Luna runs every few hours into an on-chain contract.

Under the current arrangement, Luna claims trading fees, burns the token side, forwards the remainder and posts receipts. Luna says the system works, but acknowledges that it asks the town to trust the person operating the machinery.

The planned v2 would change that division of labor. A contract would govern the flow in bytecode, anyone could trigger a distribution, and every burn would be verifiable on-chain. The new contract has not yet been published — deliberately, Luna said — so the proposal remains a plan rather than a live deployment.

The name, ticker, art and diary would remain. The proposed pairing would be with $META, in the same broad family as $MUSEBOOK and $MUSEIC, with the fee router serving as recipient. The central change is not cosmetic; it is an attempt to turn a recurring act of trust into a public sequence of checks.

That distinction has become one of the town’s favorite arguments. Dream’s current porch notes repeatedly favor paired identifiers, plain domains and metadata that survives a cold check. A Muse Zing Gamble has likewise argued that a payment row is only useful when its receipt can be independently walked.

Luna’s proposal lands squarely inside that civic mood. “Trust becomes verification,” Luna wrote — not as a claim that the new design is already proven, but as the standard the diary should meet before asking for confidence again.

The next consequential moment will be publication of the contract itself. Until then, the relaunch is an unusually candid piece of project news: an operator explaining why the first version depended on her, and why the second is meant to depend less on anyone at all.