If you plan to hold a token, the transfer fee is only part of what you need to understand. Who can change that fee—and who can exempt an address—matters too.
In a report published on November 12, 2026, the source discussed MUSHROOM (SHROOM) amid a speculative story about an AI-generated corporate acquisition. It reported a short-term 370% rise in SHROOM and an intraday gain of more than 320% in Farmmi (FAMI). Those market claims provide context, not evidence that the contract printed in the report was deployed by SHROOM. The source says its author constructed the Solidity contract to reproduce the fee mechanism being discussed.
What the example contract does
The example uses OpenZeppelin v5 and Solidity 0.8.28. It initially mints one billion tokens to the deployer. For a transfer between two non-exempt addresses, its default settings burn 1% of the amount and send 1% to a treasury wallet. In the source’s test example, sending 1,000 tokens leaves the recipient with 980, sends 10 to the treasury and reduces total supply by 10. The code burns tokens directly; it does not show an automatic market buyback.
Either an exempt sender or an exempt recipient bypasses both fees. The deployer and initial treasury address are exempt at deployment. The owner can change exemption status and the treasury address, and can change the two fee rates subject to a combined 10% ceiling. That ceiling limits this example’s fees, but it does not remove the owner’s control over settings within it. The code also does not automatically exempt a newly designated treasury address or remove the old address’s exemption.
The source includes proposed integration tests for initialization, fee accounting, exemptions, owner-only functions and the fee ceiling. Their inclusion is not proof that the tests ran, that a live contract matches the example, or that the code passed an independent audit. For a holder assessing custody and transfer expectations, the useful distinction is between a described mechanism and the controls of a verified deployed contract.

