Documentation.

What The Tree Fund is

One token, one treasury, one appeal at a time.

The Tree Fund exists to do one thing: take the trading fees earned by a single token and give them, in full, to charity emergency appeals. It does this in public, one appeal at a time, with a record that anyone can check against the blockchain.

The token is planned to launch on Pons V2 with an ETH pair on Robinhood Chain. The configured trading fee is 2.5%: a 1% base fee shared between Pons and the creator, and a separate 1.5% creator tax. Those rewards are intended to support the fund's designated appeal, and the charitable records remain separate from trade activity. The contract address, supply and final launch configuration are awaiting verification.

Which appeal that is gets decided on X. A charity posts an emergency appeal. Anyone who sees it replies to that post tagging @TreeDotFund. The bot reads the reply, records the appeal, and, once the charity has been checked, the appeal joins a queue. When it reaches the front, it goes live for a fixed window of 6 hours. During those hours every fee the token earns is credited to it. When the window closes, the charity is paid what was raised.

Three things follow from this design and are worth stating up front. First, the amount any appeal receives is not fixed, promised or predictable; it is whatever the token's trading fees add up to during that window, plus whatever people choose to send directly. Second, no one at The Tree Fund decides how much an appeal gets; the only decision a person makes is whether the account that posted the appeal is a real charity. Third, this site does not sell the token, does not have a buy button, and is not an invitation to buy anything. It exists so that the fees can be watched moving from the treasury to the charities, and so that anyone can check that they did.

The sections that follow explain each part in detail: how to start an appeal, how review and the queue work, where the money comes from and how it is counted, how donations and votes can extend a window, how a charity gets paid, and how to read the ledger.

Starting an appeal

Reply to the charity's post with @TreeDotFund. That is the whole instruction.

• The root-post rule
• One fundraiser per appeal
• What the bot ignores
• Who is credited

An appeal always begins with a post by a charity on X: the post in which the charity itself describes the emergency and asks for help. The Tree Fund does not create appeals from news articles, from posts by supporters, or from posts by anyone other than the charity, because the money is paid to the account that wrote the post.

To start the appeal, find that post and reply to it with the bot's handle:

Nothing else is required. The bot looks at the post you replied to, treats its author as the charity, and records the appeal. You may write anything else you like in the reply; the bot only looks for the handle.

Every appeal runs for the same window: 6 hours from the moment it goes live. The length cannot be chosen in the reply. If you write a duration, it is ignored. The window can grow afterwards, through donations and the holder vote, but never beyond 14 days in total.

The root-post rule

Your reply must be to the first post in the charity's thread, or a quote-post of it. Replies to later posts in the thread do not count and are ignored.

The reason is a quirk of how X builds threads. Every reply in a thread automatically carries the @-mentions of the earlier replies. Once the bot has been tagged under an appeal, the charity replying “thank you” to a supporter would itself contain @TreeDotFund, and without the rule that reply would start a second fundraiser for the wrong post. Checking that the parent is the root of the thread is how the bot tells a real trigger from an echo.

One fundraiser per appeal

Each post can have one fundraiser. If someone has already tagged the bot under a post, a second tag is recorded as a duplicate and the bot replies with the name of the existing fundraiser instead of creating another.

What the bot ignores

Mentions with no parent post. Replies to the bot's own posts. Replies whose parent was written by the bot. Posts by accounts The Tree Fund has blocked. Replies deeper than the root of the thread, as above.

Who is credited

The account that sends the reply is recorded as the person who started the appeal and is named on the fundraiser page. They receive nothing. The only account that ever receives money is the charity whose post was replied to.

Review, approval and the queue

Known charities start at once. New ones wait for a person to check them. Then everyone waits their turn.

When the bot records an appeal, it also creates or updates a record for the charity, keyed to the X account's permanent numeric ID rather than its handle, so a charity that changes its handle is still the same charity.

What happens next depends on trust.

Charities that The Tree Fund has already checked are on an allow list. Their appeals are approved the moment they are recorded, and join the queue without anyone looking at them. There is a setting that can extend the same treatment to X accounts carrying business or government verification; it is currently off, so verification on X on its own does not skip review.

Every other appeal is held. It exists in the database, but it does not appear on the site, it is not in the queue, and it receives nothing, until a person at The Tree Fund approves it. That check is the only thing standing between the fee stream and a fake charity, so it is not automated and will not be. If an account is found not to be a charity, it can be blocked, and every future appeal from it is refused automatically.

The bot's first reply, sent as soon as the appeal is recorded, says that the appeal has been received and that approved appeals join the queue. It does not say the appeal has been approved, because at that point it has not.

The queue

Only one appeal grows at a time. The number is a setting; it is one today, and it will never be more than two.

When an approved appeal arrives and nothing is live, it starts within a minute. When something is live, it waits. The site shows it as queued, with its position. Queued appeals start in the order they were created, and the next one starts in the minute after the current window closes. There is no way to jump the queue.

A queue of approved appeals is visible to everyone. Appeals still waiting for review are visible to no one.

Adding to an appeal directly

Every appeal has its own address. ETH sent there is added to its total and can extend its window.

• Adding time
• After the window closes

Trading fees are the main source of money for an appeal, but anyone can add to it directly.

Each appeal is given its own address on Robinhood Chain when it is created, shown on its page with a QR code. Sending ETH to that address is the donation. There is no form and no account.

If you donate on the site with a connected wallet, the site sends the transaction from your wallet and then reports it; the donation is checked against the chain and credited within seconds, along with a message if you left one. If you send ETH to the address from any other wallet, or from an exchange, a watcher reads the address's incoming transactions every few minutes and credits it the same way. Either way the donation appears on the appeal page and on the ledger with the transaction hash, the amount, the sending address and the message.

Adding time

Donations extend the window. Every 0.01 ETH (0.01 ETH by default) adds one hour, rounded down. A donation of 0.025 ETH adds two hours; a donation of 0.005 ETH adds none but still counts in full towards the total. Extensions stop at the 14-day cap.

After the window closes

Donations sent after an appeal has closed still belong to the charity. They are added to the payout waiting to be sent. They do not reopen or extend the window.

The holder vote

People who hold the token can vote once each to unlock one free 24-hour extension.

Separately from donations, holders of the token can extend the live appeal without spending anything.

To vote, connect a wallet on the appeal page. The site reads the wallet's token balance directly from the chain; it needs to hold at least 1,000,000 tokens. Each wallet can vote once per appeal. When 10 votes (10 by default) have been cast, 24 hours are added to the window. That happens once per appeal, and like everything else it cannot push the window past the 14-day cap.

Voting moves no tokens and costs nothing. A vote is a row recording the wallet address and its balance at the time.

The $TREE token

A planned 1.5% creator tax, recorded separately from charitable outcomes.

• Trading charges
• Follow the contribution
• Timing and net amounts
• What holding the token means

The Tree Fund ($TREE) is planned to launch on Pons V2 on Robinhood Chain, paired with ETH. The configured trading fee is 2.5%: a 1% base fee and a separate 1.5% creator tax. The base fee is shared between Pons and the creator; with buybacks switched off, the creator receives 70% of that base fee as well as the creator tax. TREE creator rewards are intended to support the fund's designated appeal. Generating rewards, collecting them, and confirming a charity payment are separate steps.

Trading charges

Base trading fee: 1%, shared 30% to the protocol and 70% to the creator. With buybacks off, that is 0.3% protocol and 0.7% creator base-fee share.

Creator tax: 1.5%. This is The Tree Fund's creator-tax funding stream.

Combined normal trading rate: 2.5%. This excludes gas, price impact and any applicable launch-window charges. These are trade-fee terms, not a claim that an equivalent amount of ETH instantly reaches a charity.

A separate launch anti-snipe charge applies to non-exempt buys during the initial three-second window, starting at 99% in the launch second and decaying. The normal 2.5% figure does not include that launch-window charge, network fees, or later donation-route costs.

These are the checked launch settings, not a verified live token configuration. Total supply, developer purchase, token address and exact supply allocation are awaiting launch verification; none is invented here.

Follow the contribution

An eligible trade generates creator tax. Fees accumulate, may require conversion, and are collected into the treasury. Confirmed rewards are allocated to eligible appeals and submitted in donation batches. The public record distinguishes “creator tax generated”, “creator rewards collected”, “allocated to this appeal”, “accepted by donate.gg”, and separately verified charity payouts. The additional creator base-fee share is accounted for separately by receipt-backed collection, not added into a per-trade creator-tax event.

Before graduation, this ETH-paired curve generates creator fees in ETH. After graduation, fee activity can be denominated in ETH or TREE; TREE-denominated fees need conversion before ETH can be collected. The activity feed displays the actual recorded asset and amount, not an estimated ETH donation.

For a fee base of 1 ETH, 1.5% is 0.015 ETH. This illustration is not a quote or a promise that precisely that amount has reached a charity. The live feed uses the actual recorded tax, including contract rounding.

Pledges, matching and custom fundraisers are planned features. They are not available now.

Timing and net amounts

The fund checks eligible batches every 15 minutes with a 0.01 ETH minimum payout and no maximum on the principal submitted. A 15-minute check is an eligibility check, not a promise of a completed payout every 15 minutes. This does not impose a 0.01 ETH minimum on individual supporters. Chain finality, pending batches, gas, conversion and provider processing can delay completion. Smaller funds remain recorded for later processing or reconciliation.

The approved donation route has a separate 3% provider fee plus variable bridge and conversion costs. Net charitable amounts can therefore be lower than the gross ETH submitted. A provider acceptance receipt is not proof of a charity bank payout.

What holding the token means

Holding or trading $TREE is not itself a direct donation or a charitable tax receipt. This page promises no investment return, charity ownership, token-holder payout or governance entitlement. Token activity and confirmed charitable outcomes are shown separately.

For Engage Nepal, the selected campaign highlights Nepal relief while supporting Engage Nepal's work generally; contributions are not restricted to that specific appeal.

Where the fees come from

The planned creator tax is 1.5%; launch configuration still requires verification.

• Claims
• What the token is, and is not

The planned launch uses a 1% Pons base trading fee, shared 30% to the protocol and 70% to the creator, plus a separate 1.5% creator tax. With buybacks off that is 0.3% protocol, 0.7% creator base-fee share and 1.5% creator tax: a 2.5% combined normal trading rate before gas, price impact or launch-window charges. The final contract configuration must be verified at launch.

The Tree Fund intends the creator-tax funding stream to support charitable appeals. A generated fee is not yet a donation: collection, allocation, provider acceptance and confirmed charity payout remain separate recorded stages.

Claims

About every 30 minutes, an automated job checks whether an appeal has been live since the last claim. If none has, it does nothing, and the credit keeps building up in the escrow. If one has, it reads the balance owed, claims it, and records the transaction. The claim is an ordinary public transaction on Robinhood Chain, listed on the ledger with its hash, the exact amount received (read from the contract's own event, not estimated), and the window of time it covers.

If the job fails part-way through, which can happen with any network, the next run finishes recording it from the on-chain receipt. A claim is never missing from the ledger because the software stumbled.

What the token is, and is not

The token exists so that its trading fees can be given away. The Tree Fund does not sell it, does not recommend buying it, does not show a price, and promises no return of any kind. The amount raised for any appeal depends on trading volume, which The Tree Fund does not control and will not forecast. The launchpad contracts the token runs on have not completed an audit.

How fees are counted for each appeal

Each claim is credited to the appeal that was live. All the arithmetic happens in the database, in wei.

• Wei and rounding
• What an appeal's total is made of

When a claim lands, it has to be credited to an appeal. This is called an allocation.

With one appeal live at a time, the allocation is simple: the whole claim goes to that appeal. The only complication is the handover. Claims happen on a half-hour cycle and windows close on their own schedule, so a single claim can cover the last minutes of one appeal and the first minutes of the next. In that case the claim is split between them in proportion to the seconds each was live during the claim's window. Both allocations are recorded against the claim on the ledger.

Wei and rounding

ETH amounts are stored in wei, the smallest unit: 1 ETH is 1,000,000,000,000,000,000 wei. Every total on this site is kept as a whole number of wei in the database, and every addition, split and comparison is done there too, never in a web browser, because browsers handle numbers of that size imprecisely. What you see on the site is a display of the exact figure, not a calculation performed by the page.

What an appeal's total is made of

An appeal's total is two numbers added together: fees allocated from claims while it was live, and ETH sent directly to its address. Both are shown separately on the appeal page and on the ledger, and both are paid to the charity.

The life of an appeal

Pending, queued, live, closed, paid.

Every appeal moves through the same states, and the state is always shown on its page.

Pending review: recorded from a reply on X, waiting for a person to approve the charity. Not visible on the site.

Queued: approved, waiting for the live slot. Visible, with its position.

Growing: live. Receiving fee allocations and donations. Countdown running.

Closed: the window has ended. No further fee allocations. A payout has been created for the full amount, and the bot has replied under the starter's post to say so. The final claim may still be settling for up to half an hour; if part of it belongs to this appeal, it is added to the payout before the payout is sent.

Paid: the payout has been sent and confirmed. The page shows where the money went and links the proof.

Rejected: reviewed and refused. Not visible on the site.

A minute-by-minute job handles the transitions: closing windows that have ended, starting the next appeal in the queue, and creating payouts. Every transition and its reply draft are written in one database transaction, so an appeal cannot close without its payout being created, or start without its position in the queue being taken.

How charities are paid

The charity chooses. Its own wallet, a US nonprofit rail, or a bank transfer from us.

When an appeal closes, its payout is created and waits. It is sent by one of four routes, chosen by the charity.

To the charity's own wallet. The charity logs in on this site with the X account that posted the appeal (see the next section), which creates a wallet for it if it does not have one, and clicks Claim. The treasury sends the ETH to that wallet on Robinhood Chain. This is immediate and costs nothing beyond network gas. The charity then holds crypto and decides what to do with it.

Through donate.gg. For nonprofits listed on donate.gg, most of which are in the United States. The Tree Fund moves the funds to a network donate.gg supports and sends them through donate.gg's relay contract; donate.gg converts them to US dollars and pays the nonprofit by bank transfer. donate.gg charges a fee for this, which The Tree Fund shows against the payout. The charity supplies only its donate.gg listing ID.

Through Endaoment. For US 501(c)(3) organisations with an Endaoment profile, in the same shape as donate.gg: The Tree Fund moves the funds and Endaoment grants the dollar value to the organisation.

By bank transfer in pounds or dollars. The Tree Fund converts the ETH itself, donates the proceeds to the charity by bank transfer or through the charity's ordinary donation page, and attaches the receipt to the appeal page. Nothing about crypto reaches the charity. This is the route most UK charities are expected to choose, and it is available to any charity anywhere.

A payout that the charity has not yet claimed or chosen a route for simply waits. It is not redirected and it does not expire. The Tree Fund will try to reach the charity on X.

Costs

Nothing is kept by The Tree Fund. The costs that reduce a payout are network gas for the claim and payout transactions, the exchange spread on a bank-transfer conversion, and the fee charged by donate.gg or Endaoment where those routes are used. All of them are visible on the ledger against the payout.

For charities

If your X account posted the appeal, logging in with it is your proof.

You do not need to contact The Tree Fund to be paid. You need to prove you are the account that posted the appeal, and logging in with that account is the proof.

Go to the charities page and choose Log in with X. Use the same account that posted the appeal. The site checks that the logged-in account's ID matches the account whose post started the fundraiser. If it does, you see your appeals, their amounts, and any payout waiting to be sent.

Then choose how you want to be paid. If you choose your own wallet, one is created for you on login if you do not already have one, and a Claim button appears against each closed appeal; pressing it sends the ETH and shows you the transaction. If you choose donate.gg or Endaoment, enter your listing ID and The Tree Fund does the rest. If you choose bank transfer, The Tree Fund will contact you on X within two working days to arrange it.

You can change your choice later; any payout still waiting is re-routed.

For UK trustees

The Charity Commission's guidance on investments asks trustees to decide, and record the decision, whether the charity will accept cryptoassets, and to consider the source of funds. Choosing the bank transfer route means the charity never holds crypto and the decision does not arise. The complete public ledger on this site is intended to answer the source-of-funds question. Gift Aid does not apply to donations made in crypto, and The Tree Fund will not claim otherwise.

Reading the ledger

Every row links to the block explorer. Nothing on it can be edited after the fact.

The ledger is the complete record of money moving through The Tree Fund, and it is the answer to the question anyone should ask of a project like this, which is “how do I know?” Every row links to the public block explorer for Robinhood Chain, where the same transaction can be seen independently of this site.

Claims: the treasury collecting accumulated fees from Pons. Each row shows when, the period it covers, the amount received, and the transaction hash.

Allocations: how each claim was divided among appeals. Usually one row per claim at 100%; two rows around a handover.

Donations: transfers to an appeal's address. Sender address, amount, message, hours added, and the transaction hash.

Payouts: money leaving the treasury to a charity. Route, amount, status, and either the transaction hash (on-chain routes) or the receipt (bank transfer).

Two things are deliberately not published: the wallet addresses charities are paid to, and The Tree Fund's internal notes on a payout. Everything else is.

Checking a claim yourself

Open the claim's transaction on the explorer. The transaction is sent by the treasury address to the Pons fee escrow contract. Its event log includes a Claimed event whose amount matches the ledger row. Add up the allocations for that claim and they equal that amount. Add up an appeal's allocations and donations and they equal the total on its page. Compare that total to its payout.

Public treasury

The Tree Fund's designated treasury and TREE creator-reward recipient — a transparency reference, not a donation address.

The Tree Fund operates one publicly identifiable treasury wallet on Robinhood Chain. It is the token's designated creator-reward recipient, and it is where eligible creator rewards are claimed when collection is enabled and verified.

Eligible creator rewards accrue in the Pons fee escrow and are claimed into this treasury when collection is enabled and verified. The treasury also holds operational gas reserves. Its wallet balance is not the fundraiser's donated total: fees generated, collected creator fees, and donate.gg receipts are tracked separately on each fundraiser record.

Not a donation address

This is a transparency reference, not a direct-donation address. To donate, use a fundraiser's currently available donation instructions. The treasury address is published so the chain of fee collection can be checked independently — it is not a send-to address for supporters.

Outgoing transfers alone are not proof of charity receipt. A confirmed charity payment is recorded separately as a payout, with its route and proof. Fundraiser records separately show generated tax, collected fees, and donate.gg acceptance.

Collection and automatic claiming are not active or verified until the launch record confirms it. Nothing here implies $TREE has launched.

What the bot does

It reads mentions every two minutes, replies three times per appeal, and nothing else.

@TreeDotFund is an automated account. This is everything it does.

Every two minutes it reads new mentions of itself. For each one it follows the reply to its parent post, checks the rules described under Starting an appeal, and records the outcome. Every mention it has ever seen is logged with what was done about it, so the same mention is never processed twice, and a mention that failed because of a temporary error is retried rather than lost.

It replies under the post that tagged it, at three moments, with these messages:

when the appeal is recorded;

when it goes live;

when the window closes.

It does not post on its own timeline, follow accounts, send direct messages, or reply anywhere except under the post that tagged it. Replies are written to a queue first and sent by a separate step, so a fault on X's side delays a reply rather than duplicating it.

The bot reads only what X makes public: the reply, the parent post, and the public profile of the charity (name, handle, avatar, verification, website). It stores those, and the handle of the account that sent the reply. It does not store anything else about the sender.

Things we should say plainly

Where the trust still sits, and what we will not claim.

The launchpad contracts the token runs on have not completed an audit. A flaw in them could stop or divert the fee stream. We would rather you heard that here than discovered it.

The treasury is a wallet that The Tree Fund holds. Every claim, donation and payout it makes is public and checkable, but until it is replaced by a contract, you are trusting The Tree Fund to run it honestly. The intention is to move it to a contract that anyone can trigger and no one can redirect, once the volume of money justifies the cost of building and auditing one. Until then the ledger is the safeguard.

The amount any appeal raises depends on trading volume, which nobody controls. An appeal can raise very little. The Tree Fund will not forecast amounts, and the site does not show a token price.

This site does not sell the token, does not recommend it, and is not an invitation to buy it. Nothing on it is financial advice.

Appeals are reviewed by a person, and the review can be wrong. If an approved appeal turns out not to have been a genuine charity, The Tree Fund can close it early and will hold any money raised for a genuine charity working on the same cause, and will say so on the ledger.

Gift Aid does not apply to donations made in crypto.

Glossary

The words used on this site, defined.

Appeal

a charity's emergency post on X, and the fundraiser created from it.

Window

the period during which an appeal receives fees. 6 hours from the moment it goes live, plus any extensions, up to 14 days in total.

Queue

approved appeals waiting for the live slot, in the order they were created.

Claim (also sweep)

the treasury collecting accumulated fees from the Pons fee escrow. Happens about every 30 minutes while an appeal is live.

Allocation

the share of a claim credited to a particular appeal.

Deposit address

the address created for each appeal to receive direct donations.

Treasury

the wallet that is the token's creator fee recipient, claims fees, receives swept donations, and pays charities.

Payout

a record of money leaving the treasury to a charity, with its route and proof.

Wei

the smallest unit of ETH. 1 ETH is 1,000,000,000,000,000,000 wei. All totals are stored in wei.

Robinhood Chain

the Ethereum layer-2 network the token, the treasury and every appeal address live on. Its public block explorer is where every transaction can be checked.

Pons V2

the planned launchpad for $TREE. Its final contracts and fee configuration are awaiting launch verification.

Fee escrow

the Pons contract in which the treasury's unclaimed fees accumulate.

Allow list

charities The Tree Fund has checked, whose appeals skip review.

Questions we get

Short answers to the things people ask most.

Can I start an appeal for my own charity?

Yes. Reply to your own post. It goes through the same review as any other.

Can I start one for a charity that has not posted anything?

No. The appeal has to be the charity's own post so that the money goes to an account the charity controls.

I tagged the bot and nothing happened. First check that you replied to the first post in the thread, not to a reply. Then look for the bot's reply under your post; mentions are read every two minutes, so allow a few minutes. If the bot replied “received”, the appeal is waiting for review and will appear on the site once approved.

Can I make the window longer than 6 hours?

Not when you start it. Once it is live, every 0.01 ETH donated adds an hour and a successful holder vote adds 24 hours.

Can the window be extended after it closes?

No. Donations after closing still go to the charity, but time is not added.

Who can see a pending appeal?

Only The Tree Fund. It appears on the site once approved.

What happens to fees when no appeal is live?

They stay in the Pons escrow, unclaimed, until the next appeal goes live. They are then claimed and credited to that appeal.

Does The Tree Fund keep any of the money?

No. Network gas, exchange spread on a bank-transfer conversion, and the fees of third-party rails such as donate.gg are the only deductions, and each is shown on the ledger.

How do I know the charity actually received it?

Open the payout on the ledger. On-chain routes link the transaction; bank transfers link the receipt.

Why not run several appeals at once?

Because a fee stream split ten ways gives ten charities a trickle. One at a time gives one charity something worth having, and the queue means everyone gets their turn.

Can a charity refuse?

Yes. A charity that does not want the money can tell The Tree Fund on X and the appeal is closed and hidden. Any money already raised is held for a genuine charity working on the same cause.