Economy

The shape, in one paragraph

Scanning is free. Revoking is free: you pay only the network gas your wallet quotes you, because the transaction is a plain approve(spender, 0) and this app takes no cut of it. A future cleanup, the batch operation that sweeps a set of dust positions into a single token, carries a fee of 1% of what you actually receive, capped at $5 per cleanup job. If the cleanup does not settle, no fee is taken. Converting the result into a Stock Token does not trigger a second fee. That is the whole revenue model.

What is charged for

• Scan. Free. The scan is a read against a database that was populated by an indexer running against your RPC. Charging per scan would price a lookup that costs the operator nothing.
• Approval Review. Free.
• Revoke. No protocol fee. Your wallet pays gas to the network; nothing is siphoned on top.
• Cleanup. 1% of the net output, capped at $5 per job. Detailed below.
• B2B API. Wallets, trackers and launchpads that embed the scan and cleanup will be priced on a subscription or volume basis. No such billing exists today; there is no authenticated caller distinct from an anonymous browser to bill against.
• Sponsored cleanups. A partner can cover a user’s cleanup fee within a public per-partner cap. The receipt names the sponsor. Nothing hidden.

The fee formula

The formula is a pure function, mirrored on-chain once a cleanup executor is deployed:

gross      = amountOut * 1%
gross_usd  = gross valued at price(tokenOut)
capped     = min(gross_usd, $5)
net_fee    = capped * (1 - bag_discount_bps / 10000)

Three properties matter:

• The number the user sees before signing equals the number the contract debits. There is one formula, in one place; Solidity will call the same math. A preview that drifts from the settled amount is the sort of surprise this project treats as a breach of the safety promise, not a UI polish task.
• The cap is honored, or the fee is not computed. “$5” is a USD figure and the chain has no dollars. Honoring the cap requires a live price for the output token. Where a price is missing, the fee refuses to compute rather than silently ignoring the ceiling.
• No fee on a failed cleanup. The fee is debited in the same transaction that pays the user, or not at all. This is a contract-level property; it is not enforced by the UI.

The threshold rule

The Cleanup Planner does not suggest a job whose expected net ( output minus fee minus gas) falls below your threshold. The alternative would be a plan that instructs you to spend $8 in gas and fee to recover $3 of dust, which is worse than leaving it alone.

Positions below the threshold accumulate in the plan across scans until a group of them, swept together, clears it. This is deliberate, not a bug: dust becomes worth cleaning up when it is worth cleaning up, and the planner’s job is to refuse to say otherwise.

The threshold is per-user, expressed in USD. It shares the “no price, no plan” discipline of the fee formula: without a live valuation of the output, the planner returns unavailable rather than assuming.

Who pays and for what

• The user pays only for a cleanup that actually settled in their favor. Never for a scan, never for a revoke, never for a cleanup that reverted.
• An embedding wallet or launchpad pays for its integration — the scan/cleanup surfaced inside their own product. It can also subsidize its users’ cleanup fees.
• An AI agent integrator pays for API calls, simulations, and execution receipts on the read side.
• A token project can pay for a verified metadata review — a public methodology reading their contract and its privileges. It cannot buy a “safe” classification. The methodology and any conflict disclosure are public; the review is a document, not a badge.

The BAG token, as a plan

Everything in this section is a plan. There is no BAG contract today; no discount is applied to any fee shown in the app; no supply, treasury, or vesting number appears on any interactive surface. Publishing a discount chip against a token that does not exist would fabricate a price cut, which is the same class of harm as inventing a price.

When BAG launches it does not replace USDC as the fee currency, is not required for base scan/revoke, and does not grant its holders the right to change the allowlist, the audit policy, min-out logic, or to seize user funds. Governance is scoped explicitly to non-security parameters: integration priorities, public dashboards, and ecosystem grants.

Planned supply and distribution:

• Fixed supply of 1,000,000,000 BAG. No further emission.
• 90% public distribution — fair launch and liquidity, user incentives, ecosystem programs.
• 10% treasury — 12-month cliff, then linear vesting over 24 months.

Planned utility:

• Up to 30% discount on the cleanup fee when paid in BAG. The discount is applied on the already-capped fee; the cap itself does not move.
• Pro features: AutoClean rules, extended history, multi-wallet dashboard.
• API credits for AI agents and small integrators.
• Bond for external risk reporters and token curators in a future Risk Network.
• Voting on non-security parameters only. The rules above (no seizure, no allowlist rewrite, no audit-policy edits) are outside the governance surface by construction.

Where fees go

Any fees the protocol eventually earns are earmarked, in order:

• Security — audits, monitoring, bug bounty.
• Infrastructure — indexer, simulation, routing, the database that answers the read endpoints.
• Ecosystem incentives for wallets and launchpads that embed the product.
• A reserve for compensation of confirmed technical incidents. This reserve does not cover market losses or illiquid positions.

The team does not promise BAG holders a revenue share or a guaranteed buyback. Anyone claiming otherwise on behalf of this project is not doing so with authority.

What is deliberately absent

The following are missing on purpose. They will remain missing until the underlying reality catches up, because a placeholder in any of them would be worse than nothing on the page users sign against.

• Fiat prices anywhere in the UI. No dollar figures on balances, no “you’ll save $X” text, no recoverable-value totals. The moment a real price provider is wired in, these surfaces get real numbers — not before.
• BAG discount chip on the fee preview. There is no BAG, so a “20% off” label would refer to a token that cannot be bought or held. Once BAG is deployed and a real balance can be read, the chip appears and shows what was actually earned.
• Treasury or supply counters. There is no treasury yet, no vested-tokens progress bar, no “% distributed” figure. The plan is above; the state does not yet exist.
• Sponsor badges on receipts. Nobody is sponsoring yet; a sponsor badge without a signed budget would be either a hidden debit or a broken one. The receipt type carries a payer field for when there is something to record.
• The cleanup fee itself, as a live charge. The cleanup executor is not deployed. Revokes cost only network gas; nothing in this build takes a protocol fee.

The stricter statement of the same policy, and every other structural property of the app, is on the Safety & Methodology page.