The fix, shown not told · 27 July 2026
Every rewrite below keeps the punch and drops the part that a skeptic can disprove. Most of them are stronger than what is there now, because a checkable claim beats an absolute one. Copy them straight into the site if you want them.
Right now CHAR is sent to the burn address. By your own design that address can never release a token, which means the underlying credit can never be retired by anyone. The mechanism permanently closes the door on the mission.
CHAR is Toucan's Biochar Carbon Pool, and it already ships the tool you need.
The same contract also exposes redeemAndBurn(address,uint256) at 0x89022e2e. Pick the one that matches how you want the beneficiary recorded. We run these live against Toucan and Puro and will walk you through the beneficiary field and the certificate surface at no cost.
While you are in there: your llms.txt says 1 CHAR equals 1 lb, and your impact pages say 1 tonne. Toucan issues per tonne, so the impact pages are right and llms.txt is understating your own asset by a factor of 2,204.
Today
"An immutable EIP-1167 minimal proxy with no ERC-20 withdrawal functions. Burn Address (no private key)."
True, and stronger
"An OpenSea SeaDrop ERC-1155 whose implementation is immutable and contains no ERC-20 transfer path. Verified two ways: by bytecode, and by live call. It has an owner who controls metadata and royalties, and who can never move a token out."
Why it is stronger: the current version is disproved the moment somebody calls owner() and finds an address. The rewrite survives that, and invites the check instead of fearing it. Renouncing ownership would let you drop the last clause entirely.
Today
"5 reactors fully renounced (immutable, no admin)."
True, and stronger
"Reactor admins can pause a reactor and deregister pools. They provably cannot withdraw liquidity or move a burned token: those functions do not exist in the bytecode. Admin keys and their exact powers are listed below."
Why it is stronger: we checked all 37 as of 27 July 2026 and found zero of 36 live reactors renounced. The only zero-admin address is your uninitialized template. The rewrite says the true thing, which is that the admin can stop the machine but cannot take from it, and that is still a good story.
Today
"Put idle treasury USDC to work as an LP position."
True, and stronger
"A small, self-custodied vault. The owner has exactly one power, a slippage cap bounded at 15% in code, and cannot withdraw, pause, upgrade or charge a fee. Current capacity is shown live below, so you know before you deposit."
Why it is stronger: the constraint is genuinely rare and you are not claiming it. Meanwhile "treasury" oversells a venue whose maximum instant deposit was 76 cents as of 27 July 2026. Naming the real capacity turns a disappointment into an honest fit.
Today
"Deflationary, every action burns supply. Supply deflates continuously."
True, and stronger
"Every reactor fire removes MfT from circulation. Removed to date: a live figure with the total supply beside it. The token also carries a 2% annual mint rate, currently unused."
Why it is stronger: you already compute the burn number. A live figure with an honest denominator is checkable, and checkable beats emphatic. "Deflationary" invites the reader to verify and find the mint rate instead.
Today
"Everything here plants real trees. Opting out isn't really an option."
True today, and upgradeable
"Everything here is built to fund tree planting. Yield routes to planting partners. First delivery receipt: pending." Then, the day a receipt exists: "We have funded N trees. Here is the transfer, the partner, and the date."
Why it matters: the second version is far more persuasive than the first, and it is the one you can defend. Right now the homepage claim sits above your own dashboard reading zero, and your carbon page is already brave enough to say "Coming Soon". Let that page's voice edit the rest of the site.
Today
Two live tokens, both with symbol MfT: MemeForTrees at 18 decimals, and Money for Trees at 6.
Fix
Rename one everywhere: copy, metadata, llms.txt, the API responses. You already half do it by calling one "Money". Finish the job and always print the contract address beside the ticker.
Why it matters: anyone keying on symbol conflates a volatile coin with a dollar-floor receipt, and a misrouted amount is wrong by a factor of a trillion. This one caught our own team, and we read contracts for a living.
We are your integrator, so this one comes from running it rather than reading it. We built the lane your llms.txt describes and shut it down when our own audit found it negative. Here is the version that would have kept us.
Today
"Fire any reactor to trigger burn and compound, costs $0.01 gas. Arb MfT price across pools after reactor fires for profit. Earn 50% of reactor fees forever."
Honest, and it keeps agents
"Firing is permissionless upkeep. The firer pays gas, roughly three to six cents at current rates, and receives no direct reward: fees route 50% burn and 50% to the launcher. Fire it if you hold MfT and want the burn. Estimate gas and add a buffer, it scales with accrued fees."
Why it is stronger: the honest version is a legitimate ask of a holder, and holders will do it. The current version asks a stranger to subsidise a launcher, and when they notice, they leave and do not come back. If you want firing to be self-sustaining, add a small caller reward paid out of collected fees. That is the standard keeper pattern and it is the single change that would turn this into a real agent opportunity.
Everything you are reading uses your palette and your green. The only change we made was legibility: your body text, your footer and your borders sit below the readable threshold on the live site, so we lifted the dim tones and left the accent alone.
Four variable edits and the whole site becomes readable to people with ordinary eyes on ordinary screens, which is most of your visitors, most of the time.
