Rearctor keeps project-token burns separate from protocol-funded REARC burns. Open Telemetry to switch between the two ledgers.
Where fees go#
Each fee vault allocates 30% to the protocol. The other 70% follows the project’s fixed creator, buyback and liquidity shares.
For example, if 100 USDC in fees is allocated and the project chose a 40/30/30 distribution, 30 USDC belongs to the protocol, 28 USDC to the creator, 21 USDC to project buybacks and 21 USDC to liquidity, subject to base-unit rounding.
Before graduation, trading fees reach the vault in USDC. After graduation, the locked V4 position can earn both USDC and project tokens. Collect V4 fees moves those earned LP fees into the vault for allocation; any Uniswap protocol charge is separate. Uncollected LP fees are not already available budget balances.
Project-token burns#
The project’s buyback share stays in its own vault. USDC is used to buy that project’s token; the purchased tokens and any project tokens already reserved in the buyback budget are burned. This does not buy or burn the platform token Rearc unless the project itself is Rearc.
Authorized admin wallets can open Control Room → Fees & treasury, choose the project and select Execute buyback & burn. At contract level, anyone may submit this fixed-destination operation and pay its gas. The caller cannot choose a different recipient or spend another project’s budget. A transaction can process only part of the available USDC; unused amounts remain reserved.
Each price-sensitive budget operation follows these rules:
- A budget swap is capped at 0.5% of the input reserve per execution.
- A pool permits one price-sensitive budget operation per minute, shared by project budgets and protocol-treasury trades.
- The spot price must remain within the contract’s narrow band, approximately 1%, of its opening price for the execution block.
- Minimum output and deadline checks must also pass.
Unspent funds remain in the original budget. Ordinary user buys and sells do not share this budget interval.
Burn collected tokens only burns the existing project-token buyback allocation without spending USDC, checking a market price, or consuming the interval. It remains available when a quote-asset restriction prevents swaps.
Graduation transfers to dead#
On an eligible owner-directed early graduation, accounted tokens left after the V4 deposit are transferred to the fixed dead address 0x000000000000000000000000000000000000dEaD. Direct donations and fee budgets are excluded. This transfer does not reduce ERC-20 totalSupply, spend buyback funds or increment project/protocol burn counters. Automatic graduation keeps its small remainders locked in the pool.
The token page shows the indexed graduation transfer separately, with its amount, recipient and explorer transaction link. It does not appear as a fee-funded buyback or a market trade.
Liquidity budgets#
Liquidity allocations stay in the vault before graduation. After V4 migration, Convert excess budget to paired asset can convert an excess USDC or token balance in bounded, guarded slices. Reinvest into locked liquidity adds both assets to the permanently locked position, up to 0.5% of its existing liquidity per execution. Unused amounts stay in the budget. Anyone can execute these fixed-destination operations; selecting Auto-LP at launch does not schedule them automatically.
Conversion, buyback and reinvestment share a 60-second cooldown per token. After converting, wait for the Control Room countdown before reinvesting. Buttons unlock after the app confirms the deadline against blockchain time; the cooldown is checked again before signing. Burning already collected tokens and collecting V4 fees do not use this timer. The error BudgetCooldown() (0x7943961c) means another budget operation used the interval; it does not mean the liquidity budget is lost.
Creator fees#
The creator share becomes claimable by the creator funds wallet fixed at launch. Connect that wallet, open the token page and use Creator fees → Claim creator fees when an amount is available. The Creator fees panel and the shortcut above the token description appear only when the launch creator or designated creator funds wallet is connected. The shortcut jumps to this panel. It shows the exact destination and available USDC and token balances. After graduation, use Collect V4 fees first to move any uncollected LP fees into the vault, then claim. Claims go to the designated beneficiary. A token holder does not receive creator fees merely by holding the token.
Rearctor treasury burns#
The Rearctor treasury tab tracks the protocol’s own 30% receipts. Allocated means earned entitlement; collected means paid into the treasury; awaiting collection means still claimable from the project vaults. Collected is cumulative and does not fall when treasury funds are later spent.
Protocol-funded REARC buybacks are manual and owner-authorized. There is no fixed burn percentage or automatic schedule. Once the official token exists and its pool is bound, the owner chooses a USDC amount, reviews it and confirms the operation. The amount is subject to available recorded funds, size limits, price protection and minimum output. The ledger records actual spending and tokens burned.
The treasury owner can also allocate protocol funds to operations and manage protocol token receipts. Protocol fees are therefore not irrevocably committed to future burns. Donations and creator rewards are excluded from recorded protocol-fee revenue. The frontend currently exposes collection, permanent pool binding and manual REARC buyback controls; additional treasury management functions exist at contract level.
Trace an execution#
Trace every burn links each project to its token page. Recent project burns cover all reactions; changing the burn-core selector changes the supply visual, not that global log. The separate Rearctor burn log links to the official token page. Live transaction links open the explorer; sample rows are explicitly illustrative.
The burn percentage counts this vault’s buyback burns against the initial one-billion supply. Independent burns by holders can reduce total supply without appearing in that buyback counter. Different token quantities are not added together as if they were one asset.
For terminology and current limits, see the FAQ.