Tokenomics Audit: Report Scope and a Scan of 16 Firm Sites

Why tokenomics needs scope beyond a code audit

A tokenomics audit reviews the economic rules a token enforces and the assumptions those rules depend on. Its useful output is a set of reproducible findings: which incentive fails, under what conditions, who absorbs the loss and which change should be tested. A token allocation chart cannot answer those questions.

The boundary with security review needs care. Hacken's smart contract assessment methodology explicitly includes economic attacks and checks emission and fee mechanisms. Its separate token economy methodology includes code verification. There is overlap. The missing work is whatever your signed scope does not cover, especially assumptions about demand and participant behavior over time.

Consider a vesting contract that releases exactly the promised allocation. The implementation can be correct while recipients gain access to more tokens than available market depth can absorb under the modeled selling scenario. Neither finding contradicts the other. They concern different claims.

Commission the economic review against a versioned model and connect it to the deployed rules. For an existing report, start with the scope and finding status fields. For a new engagement, require the reviewer to state whether it tests the design, checks implementation or does both. A clean conclusion applies only to the tested assumptions and scope.

Our scan found one service offer on 16 readable sites

Finding a firm that discusses tokenomics is easier than finding a defined economic review. Our scan of an existing member-site list produced three topic matches. Reading the evidence reduced that to one explicit service offer. The difference matters when a founder is assembling a shortlist from search results.

Method

Source population

All 23 origins in the directory's earlier security disclosure survey, with their historical names retained and redirects followed.

Retrieved

September 5, 2026, local time in Kyiv. The saved request timestamps use Coordinated Universal Time.

Page selection

Homepage and sitemap discovery, including at most 3 alphabetically sorted child sitemaps, followed by up to 6 same-host candidate pages whose addresses or home-page link text matched tokenomics, token economy, economic or vesting language. Service-looking addresses preceded blog, news and audit archive paths.

Readable denominator

16 of 23 homepages returned HTTP 200 and at least 200 visible characters. The other 7 were excluded from the readable-site denominator.

Classification

Count configured economic terms first. Then read every matching page and require a description of tokenomics review work to classify an explicit offer. An educational article alone does not qualify.

Results

The reproducibility files are seo/research/member-tokenomics-survey.py and seo/research/member-tokenomics-survey-2026-09-05.json. They are retained in the repository, not published as downloads. The output preserves request outcomes and matched passages. A repeat run reproduced the headline counts.

Limits

• This historical directory sample does not represent the whole market.
• No match means no configured phrase appeared in the pages checked. It does not establish that a firm lacks the service. The crawler also encountered unavailable sitemaps.
• Hacken is a useful counterexample: its main site returned HTTP 403 in the scan, while its token economy methodology was independently accessible. The provider comparison below therefore uses additional primary sources.

What the report should contain

Ask for evidence that another reviewer can inspect. A rating without its input data cannot tell you whether the problem is an unsafe mechanism, an unsupported assumption or an absent document. Our proposed acceptance checklist below is a commissioning framework, not an industry certification standard.

A supply reconciliation must distinguish minting from unlocking. Minting increases issued supply. Unlocking changes availability according to the applicable schedule. Treating every unlock as newly minted supply can double-count the same allocation. Keep a separate ledger for tokens that are issued but unavailable, and state how treasury holdings enter the circulating-supply definition.

Price assumptions deserve their own input record. If rewards are paid in the protocol's token but operating expenses are payable in another asset, a token-denominated surplus does not establish that bills can be paid. Ask for the cash-flow result when token demand weakens, with the conversion assumption visible. Economics Design's due diligence scope explicitly includes scrutiny of financial-model assumptions.

For simulations, retain the model version and random seed where relevant. Specify participant policies rather than labeling everyone rational: a liquidity provider that exits when rewards decline behaves differently from a treasury that must sell on a fixed schedule. A reviewer should be able to change that behavior without rebuilding the entire report. Gauntlet's parameter methodology describes models tuned to actual market data; calibration is a question to ask, not a word to accept on the cover.

Also request a missing-input register. Tokenomics.com's published methodology scores an absent required input like an alert. That is a scoring policy. Your decision still needs the underlying distinction: missing evidence calls for investigation, while a demonstrated failure calls for a design response.

A usable finding identifies a causal chain. An unlock becomes available; some recipients sell under the stated policy; executable liquidity cannot support that flow within the specified tolerance. The reviewer can then test a changed release schedule against the same scenario. An observation that the token might fall in price supplies no comparable retest.

Failure classes: dilution, unlocks, yield and control

Use failure classes to choose scenarios, then decide which scenarios fit the actual mechanism. A large allocation or a high reward rate is an input to investigate. It is not a finding on its own.

An emission schedule review needs the denominator that matches the question. A recipient cares about its share of issued supply; a trader cares about tokens that can reach the market; governance depends on the voting rules. Applying one supply percentage to all those jobs produces reassuring numbers with incompatible meanings.

Unlocks need market structure as well as dates. A volume figure measures past trading, not the liquidity available to absorb a sale at an acceptable price. Identify the venues and the pricing snapshot used in the scenario. Test the loss of a liquidity provider or venue access when that dependency matters to the launch.

Yield should be decomposed by funding source before it is annualized. New token issuance, trading fees and temporary third-party incentives behave differently when usage declines. An annualized reward display is not a promise that the funding source persists. Model the participant who exits when an incentive ends, including the effect of that exit on the remaining participants.

Applying the questions to Aerodrome

The Aerodrome documentation, read on September 5, 2026, illustrates why roles matter. Liquid AERO rewards liquidity providers; locked veAERO carries voting rights and access to exchange revenue. Voting power depends on both the amount locked and the remaining duration. The page also says a deposit cannot earn swap fees and AERO rewards concurrently.

A model that treats all AERO holders as earning the same yield therefore misses a contractual distinction. So does a concentration check that ranks liquid balances as though they were voting power. Trace the rights attached to the position before deciding which balances belong together.

Liquid reward position

Test net issuance against the participant's retained share. Include the assumed sales or reinvestment of rewards.

Voting position

Evaluate usable voting power under the actual locking and delegation rules.

Revenue flow

Check whether external payments continue under the weaker-usage scenario and which participants can claim them.

Do not freeze a protocol's policy from an old explainer. Aerodrome's current page says further details of the AERO Fed's operation with Aero are still to come. Record that uncertainty as an unresolved model input. Pool-allocation voting should not silently become an assumption that holders control every aspect of monetary policy.

Wallet concentration has a similar attribution problem. An exchange custody address may represent many users, while related addresses can represent one decision maker. Keep both the address-level measurement and the entity-level interpretation, with unresolved ownership marked unknown. A reviewer who cannot explain those classifications has not established the control distribution.

When in the lifecycle to run the review

Begin once the team has an economic model that can be challenged, before commitments make changes expensive. ShellBoxes lists both prelaunch reviews and reviews after significant design changes. Economics Design describes its due diligence service as an engagement for clients who already have a basic model. Neither means waiting until an exchange deadline.

1. Name the decision the review must support.
2. Freeze the input package: allocation ledger, unlock schedule, role permissions and the financial assumptions. Assign a version so a later report cannot accidentally describe a different launch.
3. Run economic scenarios while the design can still change. Feed findings into implementation requirements and the code-review scope.
4. Retest the revised model, then reconcile the relevant deployment parameters with it. Preserve unresolved findings beside the approval decision.
5. Set rerun triggers based on the assumptions that mattered, such as an emission change or a material loss of liquidity. Give someone responsibility for noticing the trigger.

The purpose of an audit schedule is to put evidence before the decision it is supposed to support. If the vesting commitments are already fixed, say which remedies remain available. A report can recommend a change the team lacks authority to make; the implementation plan must expose that constraint.

For an existing protocol, connect the trigger list to contract monitoring and preserve the off-chain assumptions as well. A market-maker withdrawal will not necessarily produce a contract event. Our discussion of crypto launch models provides context for deciding which commitments deserve review before they become binding.

Provider comparison by published scope

Choose the kind of work before choosing the firm. The following comparison uses provider-owned material opened during this research. It is not a ranking, and the supplementary sources are outside the bounded member-site scan.

Service labels do not make these engagements interchangeable. An existing lending market may need parameter research, while an issuer with an incomplete allocation model needs design work before independent review can be meaningful. If the designer also reviews the model, ask which assumptions receive a separate challenge and how disagreements are documented.

Search snippets can also misstate the current offer. Our direct retrieval of the Chaos Labs homepage described enterprise artificial intelligence infrastructure, while search results displayed financial-risk service copy. That discrepancy does not establish that those services ended. It leaves current tokenomics-review availability unverified, so we have not listed it as a confirmed comparable offer.

No verified like-for-like price set emerged from these sources. Request a quote against the same input package and deliverables. ShellBoxes states that pricing follows scoping. Compare the modeling effort and retest coverage before comparing totals; a redesign project and an assessment of an existing model purchase different work.

Use our member directory and ShellBoxes profile for firm context. In an audit brief, name the economic question and the evidence required to close it. A request for a tokenomics badge leaves too much room for incompatible proposals.

Code audit vs tokenomics audit

Resolve overlap by assigning evidence ownership. The two reviewers may need to examine the same reward function, but they should not leave each other responsible for an assumption neither tested.

A small immutable token without rewards may not justify the same simulation effort as a protocol whose incentives govern liquidity. Scope accordingly. The review still needs to account for distribution commitments and any off-chain dependencies it relies on.

Before accepting the combined result, match the model version to the implementation references and read the remaining findings. The due diligence checklist covers the separate task of linking deployed contracts to evidence. Keep the economic model beside that evidence, with its unresolved inputs and the conditions that require another review.