philcoin tools for Phil
Solana devnet

Fees in, supply out

Point a coin's fees at a vault. The vault has one rule: whoever burns a set amount of the coin takes the fees. So as soon as the fees are worth more than that many coins, it pays someone to buy them and burn them.

Any coin can have one. Nobody can withdraw from it, including whoever opened it. Every step is gated by Phil's upload server, running on Solana.

How it works

  1. A vault is opened for a coin

    Opening uploads the vault's rule (which coin, how many must be burned) through Phil's upload protocol. If Phil's server accepts it, the rule is written once. There is no instruction that changes it and none that withdraws.

  2. The coin's fees are pointed at the vault

    The vault's address is an ordinary Solana address. Whatever SOL arrives there is the pot.

  3. Someone burns the coins and takes the pot

    Say the rule is a million coins, and a million coins cost 1 SOL on the market. Once the vault holds a little more than 1 SOL, anyone can buy a million, burn them, and receive the pot at a small profit. The burn is done by Solana's own token program, and the SOL moves only after it succeeds, in the same transaction.

  4. Repeat

    Fees keep arriving, and each time they pass the price of the threshold, the same thing happens. The fees have bought coins off the market and destroyed them, without the vault ever trading.

Why it pays a burner instead of buying

What it guarantees, and what it does not

Open one

On devnet, the maintainers can open a vault for any coin: on GitHub, Actions, Open a burn vault, Run workflow, with the coin's mint address and the threshold. The vault's address appears on this page; that is the address to point fees at. To run your own, fork the repository: the program and its tests are in burn/.

Where Phil is in this

Both instructions, opening a vault and burning, are uploads through UploadServer, the function Phil's compiler backend emits for its upload protocol. Phil's code checks the handshake, the policy and that the bytes match their declared SHA-256, and only if it accepts does the vault act. The vault's own logic (calling the token program, moving the SOL) is ours and is not Phil.

This is a community project and is not affiliated with Phil or Solana.