Public ledger
Placeholder dataDonations sent, and results confirmed.
Two figures are tracked separately: the amount sent to partner organisations, and the planting a partner has since confirmed in writing. Funds sent are not evidence of trees planted, so the two are never combined into a single number.
Counted from filed partner reports only.
Across 0 on-chain transactions.
Across 0 countries.
0.0% of supply, held by 0 wallets.
The ledger is empty because nothing has been sent yet. Once the mint is live these values are read from the contract and the indexer rather than from a file maintained by hand.
Live from the contract
Not deployedOnce the collection is deployed this block reads the contract directly: tokens minted, the total it has forwarded to the reforestation reserve on its way to One Tree Planted, and the stage that total has unlocked. Nothing here will come from a database, so there is nothing for us to overstate.
The route
How a mint reaches the charity.
The mint settles in $TREE on Robinhood Chain. Charity donation addresses accept what they can realise, which in practice means mainnet ETH. So the share is converted and bridged before it is sent, and each step is published.
- 01
The mint splits itself
Enforced by the contract60% of every mint leaves the buyer for the reforestation reserve inside the minting transaction. The contract enforces it: the share cannot be skipped, delayed or reduced, and it never passes through the contract's own balance.
- 02
Creator fees are harvested
Anyone can trigger$TREE launches on Pons, which accrues creator fees in an escrow rather than pushing them to a wallet. Our fee recipient is a contract whose only ability is to claim that balance and send it to the reserve. Anyone can trigger it, and it can pay nowhere else, so nobody has to be trusted to remember and no key sits online waiting to.
- 03
$TREE is swapped for ETH
Anyone can triggerThe reserve sells into the Uniswap v4 pool the launch graduates to. Anyone can call swap(): it takes no arguments, sells at most a fixed amount per call, and refuses to trade below a price floor written in at deployment. The proceeds stay in the reserve, so triggering it hands the caller nothing.
- 04
ETH is bridged, addressed to the charity
Anyone can triggerAnyone can call bridge(), which hands the reserve's ETH to the Arbitrum bridge already addressed to the donation address. The destination is not a parameter and cannot be changed. Robinhood Chain settles to Ethereum, so the withdrawal waits out a challenge period of about a week before it can be completed.
- 05
The withdrawal is completed on Ethereum
Anyone can triggerAfter the challenge period, anyone can execute the withdrawal on Ethereum and the ETH lands at One Tree Planted's published address. It was addressed there when the bridge call was made, so nobody holds it in between and no wallet of ours is ever on the receiving end.
Be clear about what this costs. No step on this list is a wallet of ours moving money. The split is enforced by the mint contract; the other four are calls anyone can make, that take no destination, and that pay the caller nothing. The reforestation reserve is a contract with no owner, no withdraw and no setter, so the money it holds has exactly one exit and it ends at One Tree Planted.
What is left to trust is narrower, and worth stating rather than burying. The reserve is deployed by us, so its code and its immutable destination are what you are checking, once, before you mint — not our conduct afterwards. A sale open to anyone can be sandwiched: the price floor written into the contract bounds how badly, but does not reduce it to zero. And a bridged amount is not a delivered one until the withdrawal is completed on Ethereum, about a week later, so ETH sitting in transit is normal rather than a warning sign.
The ledger
Not deployedOnce the reserve is deployed, every swap and every bridge appears here on its own, read from the contract's logs with the hash of the transaction that produced it. No step can be listed here without having happened, and none of it is entered by us.
Recipient
Where the route ends.
Step 04 of the route above sends to the public crypto donation address published by One Tree Planted, a US 501(c)(3) reforestation non-profit. Sending to a public donation address is the whole of the relationship: the organisation has not reviewed, approved or endorsed this project, and receives nothing from us other than the donation.
- Organisation
- One Tree Planted
- Website
- onetreeplanted.org
- Address published at
- onetreeplanted.org/pages/donate-crypto
- Relationship
- Public donation address. No agreement, sponsorship or endorsement.
- Donation address
- 0x62233D5483515A79ac06CEcEbac7D399fDF8a99b
The address is the one published on One Tree Planted’s crypto donation page. Check it there yourself before relying on it: transfers cannot be reversed, and the contract bakes the recipient in permanently.
Donations
Transactions, in order.
No donation has been made. The first batch will appear here with its transaction hash, amount and destination project on the day it settles.
| Batch | Date | Amount | Transaction | Project | Status | Trees reported |
|---|
A dash in the final column means the funds have been sent but no partner report has been filed. It is neither a zero nor an estimate. The field stays empty until a document supports it.
Projects
Named planting sites.
No project is registered. Sites are added here once a partner has confirmed the location, area and planting window in writing.
Method
How a figure reaches this page.
- 01
Mint settles
The reforestation share accumulates in a dedicated address. No claim is made at this stage.
- 02
Batch is sent
Once the balance clears the partner's minimum it is sent in a single transaction. The hash is published the same day, before any allocation is known.
- 03
Partner allocates
The partner names the site and planting window in writing. That confirmation moves the affected tokens to Young Tree.
- 04
Report is filed
A dated report with counts and site photographs. Only then does a tree count appear in the table above and the tokens reach Mature.
- 05
Records are not back-filled
If a report never arrives, the row keeps its dash permanently. Figures are not estimated and batches are not removed.