Project treasury
Fund and reconcile explicit ERC-20 budgets. Allocation is separate from lending, reserve backing and earned revenue.
In this chapter
Actual cash, explicit budgets
A project treasury has an explicitly configured project authority, spending authority and supported asset list. The project authority creates named budgets. Anyone can fund a budget through an exact ERC-20 transfer, but funding does not create a personal refund right, supplier receipt or revenue classification.
Operations, Lending, Reserve and Buybacks are the local example budget names. No automatic allocation percentages are selected. The same cash is assigned to one budget at a time. A Lending or Reserve label does not move money into a lending or redemption contract.
Accounted funds = cumulative explicit funding − cumulative payments Budget reallocation does not increase accounted funds
Reallocation and payments
Only the project authority can move a balance between existing budgets. Only the spending authority can pay a recipient from a funded budget. Each payment reference is single-use across the entire treasury, preventing repeated settlement with the same reference.
The contract checks the sender and receiver balance changes. Unsupported transfer taxes or an asset deficit revert payments and their accounting. Normal spending authority is separate from the two administrators who approve exceptional recovery and upgrades.
Launchpad fees and operating revenue
Long is the selected launch venue, with the exact preset and fee integration still under review. Creator fees do not automatically reach this treasury. A separate, locally implemented treasury-buyback contract can spend explicitly funded cash after two administrator approvals. A budget label or direct transfer to that contract does not invoke its funding method or execute a purchase.
Only fees actually collected and reconciled can be classified as revenue outside this contract. Token sale liquidity, lender principal, reserve contributions, treasury funding and borrower repayments are not interchangeable revenue categories. The owner will decide allocations from actual available funds.
Unexpected transfers and recovery
Direct ERC-20 transfers outside fundBudget appear as unallocated cash. They cannot be silently assigned to a budget or spent through normal payment calls. Native ETH is not a supported budget-funding path.
A risk pause stops new budget creation and funding, while authorized payments from existing budgets remain available. Recovery stops normal operations. Both administrators must approve activation and each recovery transfer. Unreadable token snapshots are marked unavailable rather than reported as zero.