AB: a gas token with an unusually heavy “infrastructure reserve”

AB is the successor brand to Newton Project. CoinGecko flags that Newton Project (NEW) has rebranded to AB DAO (AB). The most concrete, primary description of AB’s purpose is in AB’s MiCA whitepaper: AB is positioned as a network gas token for transaction validation, block inclusion, and smart contract execution on the AB network.

Mechanically, AB is not presented as “one chain, one token.” The MiCA whitepaper states the asset is available on multiple DLT networks, including AB Core, AB IoT, and BNB Smart Chain (F.6). AB Connect is the project’s connective tissue, described in AB’s developer docs as the component that enables transfers of AB tokens between AB Core and dedicated sidechains such as AB IoT via AB Connect.

That multi-network posture is not just technical flavor. It directly affects tokenholder risk. The same MiCA document calls out that bridges can retain the ability to “release, burn and mint portions of the token supply,” framing it as a source of adverse effects to investors. In an allocation-fairness lens, that is a power surface. It is not automatically abusive. It is automatically consequential.

There is also a declared philanthropic fiscal flow. AB’s Charity Foundation page states that 15% to 30% of gas fees are allocated to charity, with allocation described as automated via smart contracts through a fee allocation mechanism. If this mechanism is live and material, it makes AB’s “fee sink” profile meaningfully different from the vanilla “fees only pay validators” story most gas tokens run.

Supply and genesis distribution: where the power sits

AB’s supply ceiling is fixed at 100,000,000,000 AB in the MiCA whitepaper (E.12). CoinGecko’s supply stats list max supply at 100,000,000,000 and show total supply at 98,823,661,261, with the same figure displayed as circulating supply on its AB DAO page.

The key fairness fact is not the cap. It is the genesis split as disclosed by the issuer. In AB’s MiCA whitepaper, the distribution “as of February 2025” is collapsed into three buckets, and the largest bucket is explicitly framed as issuer-retained: “Infrastructure Rewards” reserved for network operations, and considered retained by the issuer (D.9 / G.5).

Distribution disclosed (as of February 2025):

This is the first place AB’s public docs strain under an “allocation fairness” audit.

AB does not present a clean, standard breakdown of team, investors, advisors, foundation/treasury, ecosystem incentives, and public sale. Instead, it presents a simplified “community vs infrastructure” story, where “infrastructure” is a majority share and is explicitly issuer-retained (G.5). If there is no separate team or investor allocation, that is potentially positive for concentration risk. If there is one, it is not modelable from the disclosed buckets. Either way, a sophisticated reader is left with a structural uncertainty: the largest pile is a mandate, not a lock.

For a comparable “treasury-as-policy” pattern, see our Olympus treasury model review.

One more important nuance. CoinGecko showing circulating supply equal to total supply is a market-data choice, not a protocol truth. In practice, “issuer-retained” inventory can behave like overhang even if it is not actively sold. It can also behave like governance power if it is ever used for voting, delegation, validator relationships, liquidity provisioning, or bilateral incentives. The category label does not neutralize the power.

Emissions and unlocks: “predetermined schedule” without parameters

AB’s issuer disclosures do describe a release process from the Infrastructure Rewards reserve. The MiCA whitepaper says that starting from February 2025, tokens from the infrastructure reserve “will be released according to a predetermined schedule” to fund validator operations, maintenance, protocol security and updates, and open-source development support.

What is missing is the part token analysts actually need. There is no parameterized emission curve in the MiCA text excerpt, no cliff, no linear vest, no cadence, no target runway, no governance-controlled throttle, and no disclosed public reporting standard that ties releases to objective network KPIs. “Predetermined schedule” can mean “immutable smart contract with known unlock times,” or it can mean “a plan we intend to follow.” These are not the same thing.

The MiCA document does say distribution is managed through predetermined smart contracts for technical infrastructure purposes. That helps. But it does not fully resolve the question a fairness critic cares about: who can cause supply to hit the market, how fast, and under what constraints.

AB’s own risk language makes this more acute, not less. The MiCA whitepaper repeatedly highlights that bridge usage introduces risk because it “retains the right to release, burn and mint portions of the token supply.” Even if you interpret this as operational necessity for cross-network inventory management, it means the system’s supply surface is not just “cap = 100B.” It is “cap + operational authorities + cross-domain accounting.” That raises the bar for transparency.

From a monitoring standpoint, the issuer at least points you to where supply can be audited, but it still pushes analysis burden onto the public to reverse-engineer whether the “infrastructure reserve” behaves like locked emissions or discretionary treasury. This is where monitoring dashboards help.

Utility, fees, and fiscal flows

The AB token’s core utility is straightforward on paper. The MiCA whitepaper states AB’s “core purpose” is to serve as the gas token required for network operations including transaction validation, block inclusion, and smart contract execution (F.2). It also states AB is the only native means of paying fees for computational and storage resources in the system (F.2).

Two fee-design details matter for the value capture conversation, even if you are not trying to trade it.

First: AB Core does not implement EIP-1559. AB’s developer docs state AB Core currently supports up to the Berlin hard fork and does not implement EIP-1559 gas burning introduced in Ethereum’s London upgrade. In plain terms, if you were expecting an ETH-style basefee burn dynamic, AB Core’s docs tell you not to. Any deflation narrative has to come from other mechanisms, like explicit burns, not an automatic basefee sink.

Second: AB claims a charity skim on gas fees. AB’s Charity Foundation page describes funding sources that include 15% to 30% extracted from gas fees, allocated automatically via smart contracts into the AB charity fund. If that is implemented at the protocol level, it creates a persistent fiscal outflow from fee revenue that would otherwise be available to validators or to whatever entity coordinates network operations.

Whether you view this as a feature or a liability depends on what you think AB is trying to optimize. Public-good alignment can create real brand lift and partner access. It can also reduce validator economics, or force reliance on the Infrastructure Rewards reserve for validator subsidization. And that loops directly back into concentration risk, because the reserve is issuer-retained.

On interoperability, AB Connect is framed as a distributed, multi-node operated connector enabling decentralized transfers of AB tokens across AB Core and sidechains. This is where “utility” can become sticky. Bridges are where users actually feel the product. They are also where the worst exploits in crypto history have happened. AB’s own MiCA whitepaper underscores bridge risk explicitly and states no mitigation measures in that section (I.6).

Governance and control surface

AB’s governance story is simultaneously present and disclaimed.

The MiCA whitepaper is explicit that AB “does not entail any investment, governance or profit-sharing rights,” and that it does not grant voting rights or contractual claims (F.2 / F.1). It also states that network decisions are made off-chain by the Foundation and community via other mechanisms.

Those “other mechanisms” at least include a formal proposal specification layer. AB runs an AB Improvement Proposals (AIPs) site, which shows three implemented AIPs (AIP-0, AIP-20, AIP-721). AIP-0 sets out the governance process for proposals, including that anyone can submit an AIP and that the AB Foundation is responsible for assigning an exclusive number to each submission, with a 30-calendar-day “draft in discussion” stage.

This is helpful process hygiene. It is not the same thing as credibly decentralized governance.

In AB’s own consensus disclosure, AB Mainnet “generally utilizes a Proof-of-Authority (PoA) style consensus mechanism,” where a limited set of validators produce blocks and validate transactions. AB IoT may use PoA with pre-approved validators or a BFT variant, with the stated goal of prioritizing speed and scalability over decentralization.

That centralization may be a deliberate design trade-off. If AB is aiming for payments, IoT, and cross-chain infrastructure, it may prefer operational determinism. The cost is that tokenholders are structurally relying on the Foundation’s operational discipline.

One more control-plane detail is easy to miss. In the MiCA whitepaper, Infrastructure Rewards are considered retained by the issuer (G.5). If those tokens are used to fund validators, market-making, ecosystem grants, or “strategic” partnerships, they create both (1) incentive capacity and (2) latent political power, even if AB is legally framed as granting no governance rights. Power does not require a governance UI. It requires resources and coordination leverage.

Risk register: concentration first, bridge second, governance third

AB’s token design is not trying to be cute. It is trying to be operational. The issue is that its operational flexibility concentrates too much control too early, and the disclosure layer does not fully close that gap. The project’s own MiCA language repeatedly emphasizes investor-adverse effects tied to bridge authorities (release, burn, mint), and it discloses that the majority of supply is retained for infrastructure operations.

Dominant risk: issuer-retained supply + non-parameterized releases = permanent overhang and governance-by-treasury

The Infrastructure Rewards reserve is the structural center of gravity. AB discloses that this category is reserved for network operations and considered retained by the issuer (G.5). It also discloses that releases start from February 2025 according to a predetermined schedule, but it does not publish the schedule parameters in the same place where it publishes the category totals.

This creates a few compounding issues.

First, market pressure becomes policy risk. If network operations require continuous spend, the reserve becomes the de facto budget. Tokenholders are exposed to a “sell pressure governance” problem even when there is no formal governance. When the treasury is large, every operational decision can become a supply decision.

Second, decentralization becomes a narrative, not a mechanism. AB’s AIP process is coordinated by the AB Foundation assigning proposal numbers, and network decisions are described as off-chain by the Foundation and community via other mechanisms. That can still be legitimate governance. It just is not credibly constrained governance unless the reserve release and operational authorities are transparently bounded.

Third, builder incentives can become patronage. AB states the reserve supports open-source development. Great. But without published grant policy, reporting, or hard emission constraints, ecosystem funding can drift toward insiders, preferred market-makers, or politically aligned operators. The risk is not hypothetical. It is a direct function of treasury size and disclosure thinness.

What would reduce this dominant risk is boring, not flashy. A public, parameterized unlock schedule. A verifiable on-chain lock contract with known release conditions. Periodic treasury reporting tied to addresses. And explicit statements about whether any portion of “infrastructure” is earmarked for team compensation or investor settlements.

Top 3 risks

  1. Supply concentration and discretionary distribution via the infrastructure reserve, Trigger: larger-than-expected reserve releases or opaque movements from issuer-retained wallets. Mechanism: a majority issuer-retained allocation funds operations and can translate into sustained sell pressure or political influence without on-chain governance constraints. Who bears it: liquid holders first, then builders whose incentives become unpredictable. Measurable indicators: large outbound transfers from known reserve/issuer addresses, changes in circulating supply metrics, and repeated “funding” transactions not linked to transparent budgets.

  2. Bridge integrity and bridge-admin power (release/mint/burn), Trigger: a bridge exploit, malfunction, or emergency intervention that changes supply accounting across networks. Mechanism: cross-ecosystem transfers rely on bridging, which the MiCA whitepaper frames as historically sensitive and as retaining the right to release, burn, and mint portions of supply. Who bears it: cross-chain users and liquidity providers, then spot holders during repricing. Measurable indicators: abnormal bridge inventory balances, paused transfers, discrepancies between supply across AB Core / AB IoT / BSC representations, and emergency announcements tied to bridge operations.

  3. Centralization by design (PoA consensus + off-chain decisioning), Trigger: validator cartel behavior, censorship events, or governance disputes where “community” preferences do not bind operators. Mechanism: AB Mainnet is disclosed as PoA with a limited validator set, and decisions are made off-chain by the Foundation and community via other mechanisms. Who bears it: application builders (liveness and neutrality risk), then tokenholders (credibility and adoption risk). Measurable indicators: validator set opacity, repeated chain halts/rollbacks, and an AIP process that exists procedurally but does not translate into binding changes.

One historical note matters because it touches fairness and operational cleanup. On March 7, 2025, AB DAO announced a “global call” tied to stranded BEP2 NEW holders and a claim program for 65 million AB, alongside the wallet-level rename of NEW to AB. Migration events are legitimate. They also tend to be where supply narratives get messy, so they are worth tracking in on-chain flows.

If you are building around AB, the token mechanics you should underwrite are simple: AB is gas, AB has a large issuer-retained reserve, AB does not have an ETH-style basefee burn on AB Core, and AB’s bridge and off-chain governance surfaces are where the real control lives.

For teams that need to pressure-test treasury releases, bridge risk, and incentive alignment before integrating, this is the point where a short, adversarial review can pay off. A tokenomics advisor doing tokenomics consulting should be able to map the issuer-retained reserve into explicit scenarios and monitoring dashboards, without relying on vibes.



This article is part of our Tokenomics Deep Dive series.