One coin funds a treasury.
Liquidity puts it to work.
The intended automated loop uses main-coin fees to buy existing tokens, create Meteora pools and fund treasury-owned liquidity. Those positions can earn swap fees. After losses, costs and reserves, eligible profit can grow the treasury and fund token buybacks.
Start with fees the project actually owns.
The main coin has a designated trading venue and defined fee recipients. The project collects only its configured creator or liquidity-provider entitlement. Trading somewhere else does not automatically pay this treasury.
Seed capital pays for the first liquidity and operating costs. Main coin fees add funding over time. Both are recorded separately from strategy profit, so a deposit can never look like an investment return.
Existing tokens. Carefully chosen markets.
Acquire
Use treasury funds to buy the existing assets needed for a chosen pair.
Create pools
Create selected Meteora pools for existing token pairs and supply treasury-owned liquidity. The pilot used an existing pool to test the transaction cycle.
Manage
Monitor inventory and the earning range. Claim fees, rebalance or withdraw when the policy calls for it.
Creating a pool does not create demand. A position earns fees when swaps use its liquidity; an out-of-range position can hold market risk without earning.
The ledger includes the red days.
A position can collect fees while losing more on the tokens it holds. Closing the position returns those tokens; it does not sell them or remove their price exposure.
The simulator models loss recovery. The allocation ledger uses reviewed capital flows and estimated asset values, subtracts previous allocations, and preserves a cash reserve. Earlier losses must recover before additional profit can be recorded. Records are linked to wallet-reviewed actions. Reinvestment allowances fund deposits; buyback allowances can only buy the saved main coin. Recording alone moves no funds.
Give each eligible dollar a destination.
Reinvest
Increase productive liquidity when the strategy and the available cash support it.
Build reserves
Keep operating cash and a buffer for adverse markets.
Buy back the main coin
Spend a recorded buyback allowance on individually signed market purchases. Retaining or burning purchased tokens is a separate policy decision. Neither guarantees a higher token price.
The initial scenario uses 60% / 20% / 20%. Your saved policy can change these assumptions.An automated goal. A manual pilot.
The intended production engine selects eligible pairs, creates and funds pools, monitors positions, claims fees and routes eligible proceeds under a defined policy. Visitors should be able to follow the public record without connecting a wallet. A separate scheduled devnet runner has completed a bounded cycle including new pool creation, funding, fee collection and withdrawal. Continuous production strategy selection, hardened custody and mainnet execution remain unfinished.
The current pilot treasury has one owner, who approves each transaction in their own wallet. Feeform prepares and simulates the transaction, records its review and tracks confirmation. The server never receives the wallet’s private key.
Approved pools, per-action input limits, slippage limits and a pause control apply inside the app. The owner can still transact directly outside Feeform. Automated spending is off; shared custody is an optional future change.
Be precise about what has been built.
Live information
Meteora pool discovery uses live market data. Wallet-position reads require a configured mainnet RPC. Data failures are shown explicitly.
Working simulator
Saved scenarios model fees, inventory changes, costs and allocations. They are not historical backtests.
Reviewed execution
The manual pilot prepares swaps, deposits, fee claims and withdrawals for wallet review. Pool creation and burns are disabled during the pilot. A transaction is shown as successful only after chain confirmation.
The owner-signed swap, deposit, fee claim and full withdrawal pilot is complete and reconciled. New capital actions are paused while launch testing continues. The main token has not launched. DBC and DAMM v2 fee readers verify treasury entitlements. Separate test-network rehearsals have finalized DBC and DAMM fee claims, migration and a fee-funded buyback. This proves transaction mechanics, not a profitable production strategy. Claims receive wrapped SOL and main tokens in the treasury. Main-coin fees are recorded as funding. Production profit-allocation recording and spending are held while the new accounting and execution paths undergo verification. Fourteen devnet stages completed, including a separate liquidity deposit, nonzero fee claim and full withdrawal. The devnet test used artificial prices and recorded a loss. A separate offline test now covers a positive allocation, real transaction builders, synthetic wallet signatures, finalized receipt handling and ledger reconciliation. Both accounting endpoints must have verified inventory before allocations can qualify. Production allocation spending remains held for release review. Direct DAMM claims and buybacks also verify the pool’s migration origin against its configured DBC source. Confirmed actions are matched only after their finalized capital flow is reviewed. Automatic buybacks, staking rewards and an on-chain spending vault are not live.
Open the workspace Read proposed terms