AB

What is AB?

AB (ticker: ab; formerly Newton/NEW) is a multi-network blockchain ecosystem that positions itself as “infrastructure-first” rather than application-first, aiming to make cross-chain value movement and real-world asset (RWA) representation practical across heterogeneous chains while keeping the base layer cheap and high-throughput.

In AB’s own framing, the core problem is that most blockchains remain siloed and struggle to support high-frequency, low-cost activity alongside cross-chain settlement; AB’s proposed moat is a modular architecture that couples an AB “Core” network with domain-specific sidechains and an interoperability layer (“AB Connect”) intended to extend AB’s asset presence across networks such as Ethereum, Solana, and BNB Smart Chain, reducing dependence on any single execution environment while keeping AB as the common fee and transfer primitive. In practice, this places AB in the crowded “general-purpose L1 plus interoperability” category, where differentiation is less about raw claims (nearly every L1 advertises throughput and low fees) and more about whether the ecosystem can sustain non-speculative flows, credible cross-chain integrations, and a security model that is legible to external capital.

From a market-structure perspective, AB has tended to trade as a rebranded legacy network asset rather than as a new L1 discovery story, with major centralized exchanges explicitly supporting the Newton-to-AB ticker transition in early 2025 (for example, MEXC’s rebranding notice and HTX’s rebranding notice).

On the on-chain adoption axis, the cleanest comparable metric available for “DeFi gravity” is chain TVL; as of February 2026, DefiLlama’s AB chain page shows sub-$1m DeFi TVL, which implies AB is not currently competing for meaningful share against incumbent DeFi settlement layers and that most observed activity is more likely coming from exchange-led liquidity, wallet-led user acquisition, and non-DeFi transfers rather than sticky on-chain leverage and liquidity venues.

This gap between stated ambition (interoperable RWA rails and sidechain expansion) and observable DeFi capital is the central framing tension investors should keep in mind when evaluating AB’s “infrastructure” narrative.

Who Founded AB and When?

AB is the continuation of the Newton Project rather than a greenfield network, with Newton’s mainnet described by third-party exchange documentation as launching in December 2018 and using a “main chain + sub chain” structure.

The modern AB brand and ticker came later via a formal rebrand process that exchanges implemented around February 18, 2025, which is best understood as a coordination event across custodians, CEXs, and market data venues rather than a new genesis or token redenomination (MEXC notice, HTX notice, CoinGecko AB page noting rebrand). Governance and organizational accountability appear to be framed around an AB Foundation/AB DAO public identity in current materials, but the most concrete “who/what” identifiers available in primary sources are institutional rather than individual: the public-facing publisher of the protocol positioning and disclaimers is the AB Foundation via its whitepaper site and its EU-facing disclosure posture is expressed through publication of an AB MiCA whitepaper landing page.

Narratively, the project’s evolution has been a pivot from a vertically themed “commerce/e-commerce + blockchain” thesis (Newton-era materials emphasize retail and business applications) toward a more compliance-forward, infrastructure-neutral posture that repeatedly disclaims investment features and constrains AB’s role to gas for transaction processing and smart contract execution.

This shift matters because it implicitly acknowledges the regulatory and reputational cost of marketing tokens as quasi-investments; AB’s current documentation leans heavily into “utility-only” language and third-party responsibility for bridges and financial services, which can reduce some forms of issuer exposure while also limiting how aggressively the foundation can promote specific yield, governance, or profit-sharing narratives without contradicting its own disclosures.

How Does the AB Network Work?

AB today should be analyzed as an EVM-compatible execution environment (AB Core) sitting inside a broader multi-chain product stack, with public endpoints and chain metadata visible via Chainlist’s AB Core Mainnet entry (chain id 36888) and an explorer stack built on Blockscout as indicated by AB’s explorer pages.

The project’s own architecture description emphasizes high throughput, “instant confirmation,” low cost, and cross-chain operations with major networks (AB overview), while Newton-era third-party descriptions characterize the consensus as PoA; taken together, the most conservative reading is that AB inherits a permissioned or semi-permissioned validator design lineage, even if current marketing prefers the broader term “decentralization” without specifying validator admission rules in the snippets readily visible to the public.

For institutional risk models, the key question is not whether AB can process transactions cheaply (most EVM chains can) but whether the validator set, block production, and governance over protocol parameters is sufficiently decentralized and transparent to withstand both adversarial conditions and regulatory scrutiny.

Technically, AB differentiates itself less through novel cryptography (there is no prominent ZK/rollup-centric security argument in the primary docs surfaced here) and more through “heterogeneous modularity”: an AB Core plus specialized sidechains for verticals (payments, finance, gaming, DePIN/IoT) and an interoperability layer intended to move assets across ecosystems.

The ecosystem’s security perimeter therefore expands beyond base consensus into bridge operators and wallet software, which AB explicitly frames as being run by independent third parties for cross-chain services in its whitepaper disclosures—a helpful legal demarcation, but also an implicit admission that the user’s end-to-end risk depends on components outside the foundation’s direct control.

If AB’s usage concentrates in wallet-mediated cross-chain transfers rather than in-chain DeFi, then wallet security, key management choices (including MPC “keyless” UX claims in AB Wallet materials), and bridge implementation quality become first-order variables, not secondary ones.

What Are the Tokenomics of ab?

AB’s own whitepaper describes a fixed maximum supply of 100 billion tokens and provides a point-in-time breakdown “as of February 2025,” including a disclosed burned portion and an infrastructure reserve intended for network operations funding.

Under that framing, AB is not structurally inflationary in the “uncapped emissions” sense, but it can still be effectively inflationary to circulating supply if large portions of the infrastructure reserve are programmatically released over time; the whitepaper explicitly states that infrastructure tokens are released on a predetermined schedule to fund validator operations, maintenance, security, and development.

The existence of an already-burned tranche is economically meaningful only if burn continues as a function of usage or policy; in the absence of a transparent, ongoing burn rule tied to fees, the “burned to date” figure reads more like a historical supply adjustment than a durable value-accrual mechanism.

Utility and value accrual, as AB documents it, is narrowly defined: the token is positioned “exclusively” as gas for network transactions and smart contract execution, and AB’s materials explicitly disclaim governance rights, profit-sharing, or investment characteristics.

That design can be coherent for a pure-fee asset, but it also means the investment case depends heavily on sustained demand for blockspace and execution rather than on explicit cashflow routing to holders. In parallel, AB also exists as a token on other chains; for example, the user-provided BNB Smart Chain contract address 0x95034f653d5d161890836ad2b6b8cc49d14e029a corresponds to an AB token instance visible on BscScan.

For institutional diligence, that multi-deployment reality raises the usual questions about canonical supply accounting, bridge/mint authorities, and whether the market primarily prices the “wrapped” instances versus native gas demand on AB Core; in low-TVL ecosystems, it is common for trading liquidity and price discovery to be dominated by external chain deployments and CEX order books rather than by native on-chain activity.

Who Is Using AB?

The most defensible way to separate speculative interest from organic utility is to compare exchange-led liquidity and wallet-download narratives against on-chain capital stickiness. On the DeFi side, AB’s footprint appears small as of early 2026, with DefiLlama tracking AB chain TVL at roughly the mid-six-figure USD level, which suggests that, at least by DeFiLlama’s methodology, AB is not currently a primary venue for lending, AMMs, or liquid staking at scale.

That does not prove there is no usage—Blockscout explorers can show transfers and contracts—but it does imply that the “DeFi flywheel” (liquidity attracting developers attracting liquidity) is not yet visible in aggregated TVL. Instead, AB’s most visible product surface area is the wallet and cross-chain messaging: AB positions AB Wallet as a multi-chain hub with MPC/keyless UX and “gasless” aspirations, and the project’s roadmap and announcements emphasize wallet releases and user acquisition mechanics, which can drive activity that looks more like consumer fintech growth loops than like institutional DeFi liquidity formation.

On partnerships and institutional adoption, the public, high-confidence signals available in primary sources are limited mostly to infrastructure claims and exchange rebranding support rather than named enterprise deployments. AB’s own architecture page lists target asset categories like gold, fiat currencies, commodities, real estate, and IP under an RWA umbrella, but it does not, in the surfaced material, enumerate regulated issuers, custodians, or banks actively tokenizing these assets on AB.

The publication of an AB MiCA whitepaper landing page is notable as a compliance posture signal in the EU context, but by itself it should not be conflated with regulatory approval, licensing, or endorsement; it primarily indicates an attempt to align disclosures with the EU’s Markets in Crypto-Assets framework rather than proof of institutional usage.

A cautious investor should therefore treat “RWA integration” as an intent statement until counterparties, issuance structures, and enforcement mechanisms are independently verifiable.

What Are the Risks and Challenges for AB?

Regulatory exposure for AB is best framed as a gap between issuer self-classification and regulator interpretation. AB’s whitepaper asserts a “utility token” classification and disclaims governance, profit-sharing, or investment features, and it places cross-chain services outside the foundation’s scope by labeling them third-party operated.

This posture can reduce some forms of direct issuer liability, but it does not immunize the asset from being treated as a security in particular jurisdictions, especially if distribution practices, promotion, or secondary-market dynamics resemble investment solicitation. In addition, if the network’s practical consensus model resembles PoA or a tightly permissioned validator set—as suggested by Newton-era descriptions—then the centralization surface expands: validator concentration, infrastructure reserve control, and upgrade authority can all become focal points for both regulatory and investor scrutiny, independent of token “utility” language.

Competitive threats are straightforward and severe. On the base-layer axis, AB competes against a long tail of EVM L1s and high-throughput non-EVM chains, where the market has already converged on “fast and cheap” as table stakes and where liquidity and developer mindshare are heavily path-dependent.

On the interoperability axis, AB competes against specialized bridge ecosystems and messaging layers, as well as against wallets that have become de facto cross-chain routers without needing to own a base chain.

The fact that AB’s DeFi TVL is currently small by industry trackers implies a cold-start problem: without meaningful native applications and capital, AB risks being relegated to a “ticker and wallet” story rather than becoming a settlement venue where fees and security demand are endogenous.

Finally, multi-chain token instances (such as the BSC contract you provided) create additional economic ambiguity: if most activity is on external chains, AB Core’s blockspace demand may not scale with market cap, weakening the causal link between ecosystem adoption and token value capture.

What Is the Future Outlook for AB?

Near-term viability hinges on whether AB can translate product shipping (wallet iterations, cross-chain tooling, and sidechain scaffolding) into measurable on-chain usage that is not purely speculative. AB has published ongoing roadmap materials and frequent wallet-focused announcements, including an official post about AB Wallet 2.0 that emphasizes referrals and task-based points, and a broader AB roadmap page describing staged releases across AB Core, bridges, and wallet infrastructure. In parallel, the existence of a formal MiCA whitepaper landing page suggests AB expects compliance narrative and disclosure posture to matter for distribution and partnerships, particularly in EU contexts where service providers face clearer obligations under MiCA.

Structurally, AB’s core hurdle is that interoperability claims are only as credible as the weakest operational link: bridges, wallet signing flows, custody assumptions, and the governance of upgrades. If AB’s foundation continues to disclaim control over cross-chain service operators, then the ecosystem’s risk is dispersed across multiple entities; that can be healthy if it reflects real decentralization, but it can also complicate accountability when incidents occur.

For AB to mature into an infrastructure asset with institutional relevance, the burden is to show sustained usage on AB Core (transactions, contracts, developers, and ideally TVL growth that survives market drawdowns) and a security/validator model that is legible and auditable to third parties, rather than relying on generalized throughput claims and cross-chain aspirations.