Staking AVAX, calling a smart contract, and transferring an asset on the X-Chain involve different transaction rules. Avalanche’s Primary Network handles these operations across three blockchains, each running its own virtual machine.

The Primary Network documentation identifies PlatformVM as the VM behind the P-Chain, Coreth as the implementation powering the C-Chain, and AVM as the VM used by the X-Chain.

What Does a Virtual Machine Define?

In Avalanche, a virtual machine defines a blockchain’s application logic. It specifies the data the chain stores, the transactions it supports, and the changes those transactions can make. It also provides interfaces through which applications interact with that chain.

The official virtual machine overview describes a VM as a blueprint for a blockchain. Multiple chains can use the same VM while maintaining a separate state.

AvalancheGo connects this chain-specific logic to networking and consensus. The VM implements the rules used to process blocks, while the consensus engine coordinates agreement on which blocks are accepted. This separation lets developers build different blockchain behaviors around a common node framework. The VM architecture reference describes the interface between these components.

PlatformVM and the P-Chain

Despite its name, the P-Chain is a regular blockchain like the C-Chain and X-Chain. What sets it apart is the set of transactions PlatformVM supports. PlatformVM implements the operations used to manage validators, staking, and blockchain creation on the P-Chain. Its state includes validator records and information about the networks and chains registered within Avalanche.

For example, joining the Primary Network as a validator involves a P-Chain transaction processed under PlatformVM’s rules. Creating a blockchain also involves a platform transaction, which identifies the VM and the initial data that the new chain will use. The PlatformVM architecture documentation lists these operations and their transaction types.

Avalanche L1 validator management adds another part to this role. An L1 can use its own validator manager to authorize changes to its validator set. Under ACP-77, those changes are communicated to the P-Chain through Warp messages and processed according to the platform’s rules.

This gives the L1 control over its validator management while keeping the corresponding validator information available on the P-Chain. The L1’s application transactions continue to follow the VM used by its own blockchain.

Coreth and the C-Chain

Coreth is the Ethereum Virtual Machine implementation that powers the C-Chain. It executes EVM bytecode, maintains the chain’s execution state, and exposes Ethereum-compatible APIs. Solidity contracts deployed on the C-Chain run through this implementation. These capabilities are documented in the Coreth architecture reference.

For a developer, this means familiar contract languages and Ethereum-compatible tools can be used to build on the C-Chain.

Execution and consensus have separate responsibilities here. Coreth implements the contract execution environment, while the C-Chain uses Avalanche’s Snowman-based consensus infrastructure to agree on blocks. EVM compatibility describes how contracts execute; it does not determine which consensus protocol the chain uses.

Coreth also supports atomic import and export operations with the P-Chain and X-Chain. These operations provide a defined mechanism for moving AVAX between the Primary Network’s chains, even though those chains use different VMs and maintain separate state.

AVM and the X-Chain

The Avalanche Virtual Machine, usually shortened to AVM, implements the X-Chain’s asset operations. Its APIs support Avalanche Native Tokens, including asset information and transaction queries. AVAX is one of the assets handled on this chain. The X-Chain RPC documentation describes these interfaces.

AVM uses an unspent transaction output model, or UTXO model. A transfer consumes existing outputs and creates new ones. Each output identifies an asset and includes the conditions governing how it can be spent. The P-Chain also uses a UTXO model, while the C-Chain follows Ethereum’s account-based model.

For example, an output can specify an amount and the addresses whose signatures are required to spend it. A subsequent transaction supplies the corresponding input and authorization. The X-Chain transaction specification defines these structures and their validation requirements.

Older explanations often associate the X-Chain with Avalanche’s original DAG-based consensus. Cortina linearized the X-Chain in April 2023, and it now uses Snowman consensus. Its asset-focused VM and UTXO model remain useful distinctions when comparing it with the C-Chain. The change in consensus is documented in the consensus architecture reference.

How Do These VMs Relate to Avalanche L1s?

Developers building an L1 can choose a VM suited to their own application requirements.

The official custom VM guidance presents two starting points. Teams can use Subnet-EVM for an Ethereum-compatible chain or develop a custom VM. Coreth powers the C-Chain, while Subnet-EVM provides an EVM implementation intended for custom Avalanche L1s.

A custom VM can define its own transaction formats, state, and application rules while connecting to AvalancheGo through the required interfaces. That gives developers control over the chain’s behavior without requiring them to write the surrounding networking and consensus infrastructure from scratch.

Technical Terms Mentioned in the Text

Virtual machine

The software that defines a blockchain’s application logic, transaction rules, and state changes.

EVM

The Ethereum Virtual Machine, an execution environment for smart contract bytecode.

State

The data a blockchain maintains at a particular point, such as balances, contract storage, or validator records.

UTXO

An unspent transaction output that can be consumed by a transaction satisfying its spending conditions.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

When Progmat completed its migration to Avalanche in July 2026, the headline number was ¥452 billion in digital securities, equivalent to roughly $2.7 billion at the time.

Progmat didn’t transfer $2.7B in cash; ¥452B is the total value of securities issued on its platform. That makes the migration less about capital moving between networks and more about changing the core technology underneath an operating financial market.

Progmat’s previous architecture was built on R3’s Corda 5, an enterprise distributed-ledger technology. It has since moved to a dedicated Avalanche L1, migrating its existing smart-contract functionality into an EVM-compatible environment while preserving the behaviour and specifications of existing issuances.

The transition was designed so participating institutions could continue using the platform without having to rebuild the financial products already running on it.

The ¥452 billion did not “move” in the crypto sense

When Datachain announced the original migration plan in February, it described more than ¥439.6 billion in digital securities on Progmat ST. By the time the migration was completed, the figure reported by Avalanche had risen above ¥452 billion in total asset value.

For a crypto user, “moving assets to another chain” normally implies a transaction: burn here, mint there, bridge there, or transfer tokens from one wallet to another.

A tokenized bond remains connected to the underlying financial instrument and the legal rights associated with it. Changing the distributed ledger used to record and administer that instrument does not, by itself, change the bond.

The closer analogy is a financial institution modernizing its core technology while keeping its customer-facing services running. Commonwealth Bank of Australia, for example, has undertaken large-scale modernization of core banking infrastructure by moving critical systems to cloud infrastructure. Customers don’t need to understand the technology behind their accounts; the bank’s job is to upgrade it without disrupting reliable services.

That is the paradox of critical financial infrastructure: the more successful the migration, the less visible it can be.

Rebuilding the infrastructure underneath the securities

One of the more important pieces of the architecture is the mediation layer between Progmat’s applications and the underlying blockchain infrastructure.

Its purpose is to separate the financial services and business logic from the specific ledger supporting them. Rather than designing every application around one blockchain, Progmat can introduce an abstraction between its applications and the networks underneath them.

1. For the current migration, that means the digital-securities platform can run on Avalanche while maintaining the same expected behaviour for existing issuances.

2. For future development, it creates another possibility: Progmat can interact with more than one blockchain without treating every network change as a complete redevelopment of the platform.

The diagram below shows how that separation looks in practice.

At the top sit Progmat’s two SaaS layers: an Asset Node for issuance and a Custodian Node for management, each with its own business applications, wallet and key management, and contracts. Beneath them, the securities run on a dedicated Avalanche L1, which the diagram labels as permissionless when needed for users, developers and validators. To the side, Datachain’s LCP is designed to connect that L1 to other chains, giving Progmat a route to other security token projects, stablecoin projects and overseas institutional investors without rebuilding the platform.

That raises the question of what this means for the settlement side of securities transactions.

Japan’s Financial Services Agency, the country’s financial regulator, is already supporting an industry experiment to test blockchain-based settlement across Japanese government bonds, corporate bonds, investment trusts and equities, with stablecoins used to connect the securities transfer with payment.

The objective is delivery-versus-payment, or DvP: the security and the corresponding payment are exchanged together. For example, rather than a buyer’s payment being processed separately from the transfer of a tokenized bond, the two could occur as part of the same coordinated transaction. This can reduce settlement risk and operational complexity and potentially allow securities transactions to operate beyond traditional market hours.

That puts Progmat’s migration in a broader context: the value of moving securities to programmable infrastructure may go beyond tracking ownership to connecting it with other parts of the transaction.

Progmat and Datachain have identified cross-chain DvP between security tokens and stablecoins as part of their broader strategy. But that should not be confused with what the July migration itself delivered. The migration established the new underlying infrastructure; broader cross-chain settlement capabilities remain a future development.

Settlement also depends on the payment side, and Japan’s stablecoin market is where the constraint sits. The map below shows where things stand.

The market map shows the gap: international markets are already building dedicated chains for security tokens and stablecoins, while in Japan current stablecoin options like JPYC are capped at 1 million JPY. Until domestic stablecoins can handle large transfers, cross-chain DvP remains a goal rather than a live capability.

So what did Progmat gain?

The company says rights-transfer processing is now approximately three to five times faster than before, with transaction finality under two seconds. It has also said that new participating institutions no longer need to operate dedicated Corda nodes.

Those performance figures are company-reported, and there is not yet an independent public benchmark demonstrating how the new system performs across the entire settlement process, including the off-chain processes that financial institutions still need to complete.

The removal of dedicated Corda-node requirements could nevertheless have an important operational effect. Institutions joining the network no longer have to take on the infrastructure, security, maintenance and technical-support requirements associated with running those specialized nodes.

That could make participation easier as the number of institutions using the platform grows.

AvaCloud’s role is relevant here because financial institutions generally need more than raw blockchain performance from a technology provider. Avalanche has highlighted SOC 1 and SOC 2 Type II attestations associated with the infrastructure supporting Progmat, addressing the kind of controls and assurance that enterprise customers tend to demand.

The platform is also beginning to be tested beyond the securities included in the July migration. On September 3, Progmat and three MUFG companies announced a proof of concept for a domestically registered tokenized investment trust, with the experiment taking place in a live operating environment.

The project is designed to test the practical operation of the fund, including asset management, custody, rights administration and the systems supporting tokenization.

That moves the proposition beyond simply putting an existing security onchain. It begins testing whether programmable infrastructure can support more of a financial product’s lifecycle.

It is still only a proof of concept, so it is too early to treat it as evidence of mass adoption. But it shows that Progmat can begin testing with an architecture that is no longer as tightly tied to its previous ledger environment.

What the migration actually accomplished

There is a tendency to measure blockchain adoption through the amount of money placed on a network but this shows why that metric can be misleading in institutional markets.

The more meaningful measure is what happened to the financial infrastructure supporting that value.

Progmat is not simply building another securities platform tied to a single blockchain. Instead, it separates the platform from the underlying network, creating a different performance profile, lowering the infrastructure requirements for new participants and giving applications greater flexibility over which networks they can run on.

That may ultimately be the more important lesson from the migration.

The migration itself shows what financial institutions may ultimately want from blockchain technology: not a new market every time the technology changes, but infrastructure that can evolve without forcing the market to change with it.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

Tokenization is beginning to move beyond individual assets and into the infrastructure of capital markets themselves.

South Korea is approaching that transition by changing the legal and technical systems that determine how securities can be issued, recorded and managed. In January 2026, its National Assembly passed amendments to the Electronic Registration Act and the Financial Investment Services and Capital Markets Act, establishing a legal framework for securities issued using distributed ledgers.

The legislation takes effect on February 4, 2027. Its initial implementation will focus on selected institutional financial products, unlisted stocks and fractional investment securities, with plans to expand into conventional publicly offered securities as the market develops.

The Korea Securities Depository (KSD) is developing infrastructure designed to connect with Avalanche, Hyperledger Fabric and Hyperledger Besu. Meanwhile, Hanwha Investment & Securities has completed a token securities platform supporting Avalanche and Hyperledger Besu, positioning itself ahead of the regulatory framework’s launch.

These developments offer an early look at how blockchain could become part of South Korea’s regulated securities infrastructure.

From electronic securities to onchain markets

South Korea has made a major transition in securities infrastructure before.

In 2019, the country introduced its electronic securities system, replacing physical certificates for listed stocks and bonds with electronically registered records. KSD became central to that infrastructure, maintaining registration records and supporting the management of securities ownership rights.

The new framework extends that evolution by allowing distributed ledgers to serve as part of the legally recognized recordkeeping system. Tokenized securities will remain subject to existing capital markets laws, including requirements around financial investment activities, disclosure and investor protection.

This creates a path for financial institutions to incorporate blockchain into established securities processes while operating within Korea’s regulatory framework. The transition will happen gradually, beginning with selected financial products.

According to the Financial Services Commission’s September roadmap, the first phase beginning in February 2027 will cover privately pooled money market funds and bonds for institutional investors, unlisted stocks issued through trust structures, and publicly offered fractional investment securities.

The second phase is intended to expand tokenization to conventional publicly offered securities. A third phase would introduce onchain payment infrastructure linked to stablecoins, although its implementation depends on regulatory developments and the results of earlier stages.

For financial institutions preparing to participate, the immediate challenge is building blockchain systems that can connect with Korea’s existing securities infrastructure.

That’s where KSD becomes particularly important.

Where Avalanche enters

KSD serves as South Korea’s central securities depository, with responsibilities spanning electronic registration, securities custody and the management of ownership records.

Its role will continue under the token securities framework, with additional responsibilities involving distributed ledger connectivity and the reconciliation of securities issuance and circulation records.

KSD has already completed preliminary work. Between 2024 and 2025, it conducted functional analysis and built a testbed, completing connectivity tests with eight participating organizations. It is now developing the operational platform, with further testing planned before the February 2027 launch.

The technical requirements for this infrastructure include network participation, consensus, security and operational continuity. KSD’s published guidelines identify Avalanche, Hyperledger Fabric and Hyperledger Besu among the technologies its platform is being designed to connect with.

Avalanche’s inclusion also reflects demand from financial institutions.

According to a KSD official quoted by Seoul Economic Daily, several companies requested Avalanche support through the token securities consultative process and existing projects. Those requests contributed to its inclusion among the supported technologies.

Hanwha Investment & Securities offers an early example of how that demand is translating into actual infrastructure.

From demand to actual infrastructure

Hanwha Investment & Securities began developing its token securities platform with FairSquare Lab in 2025.

The platform has since been completed and supports multiple blockchain networks, including Avalanche and Hyperledger Besu. It is being prepared for use under Korea’s upcoming regulatory framework.

Hanwha’s approach illustrates why flexibility matters in institutional blockchain infrastructure.

Financial institutions often need greater control over network participation, validation and governance than public blockchain applications typically require. Avalanche supports dedicated networks where institutions can define participation requirements and validator configurations while using technology associated with a broader public blockchain ecosystem.

That architecture gives institutions options when designing systems around their regulatory and operational needs.

But interoperability remains a major challenge.

Korean securities companies are developing different blockchain systems, and those networks will need to exchange information reliably with KSD’s infrastructure. Industry participants have identified compatibility between distributed ledgers, along with accurate management of securities issuance records, as important issues ahead of implementation.

KSD’s proposed framework addresses part of that challenge by establishing common requirements for participating networks. Its planned infrastructure will allow the depository to participate directly in distributed ledgers and reconcile issuance records across account management institutions.

For Avalanche, the opportunity lies in supporting financial institutions as these connections are established and tested.

What Korea is building toward

South Korea’s first tokenized securities market will be narrower than the long term vision.

Institutional products and selected investment structures come first. Expansion into publicly offered conventional securities will depend on the stability, efficiency and market demand demonstrated during the initial phase.

The Financial Services Commission has also outlined a longer term roadmap for expanding tokenized securities issuance and developing onchain payment and settlement infrastructure.

Onchain payments could eventually become part of that system, potentially using stablecoins to support faster settlement and reduce the separation between securities transfers and payments. The FSC has discussed possibilities including continuous market operations and same day settlement, although these remain future objectives rather than capabilities being introduced in February 2027.

On October 1, the FSC proposed additional rules governing tokenized securities issuance and circulation. The proposals cover eligible securities, requirements for participating institutions and the operation of distributed ledgers shared with KSD.

The public consultation runs from October 2 through November 11, with further approval procedures expected before the framework takes effect in February 2027.

These developments bring Korea closer to its first regulated implementation, although the broader roadmap will take considerably longer to realize.

The bigger picture

The next milestone is February 4, 2027, when South Korea’s token securities framework is scheduled to take effect.

Before then, KSD and participating financial institutions must complete their infrastructure preparations and connectivity testing. Hanwha’s completed platform and Avalanche’s inclusion in KSD’s technical requirements provide early evidence of how that ecosystem is taking shape.

The more meaningful test will come after launch, when institutions begin issuing securities under the new framework and the infrastructure moves into actual operation.

Avalanche is already among the technologies being prepared for that transition.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

Team1 Japan is officially here.

Our mission is to build a Japanese builder community that matches the scale of Japan’s institutional adoption.

Here is what that means, and why Japan’s builder scene is unique.

The sequence is backwards, and that’s the opportunity

Japan’s institutions have already made their choice.

Progmat, the platform behind the majority of the country’s security token issuance, moved billions in tokenized real estate and corporate bonds onto a dedicated Avalanche L1. TIS, which processes more than half of Japan’s credit card volume, also launched its own L1. Some of the largest names in Japanese finance are now exploring tokenized government bonds using Avalanche infrastructure.

In most countries, this runs the other way. A community forms, developers experiment, projects ship, and eventually, sometimes years later, institutions notice and follow. Japan skipped the first half.

The chains themselves stay controlled, as Japanese financial regulation requires, but they no longer sit behind a wall. Gateways outward to wallets, to stablecoin settlement, and to applications written by people who were never invited into a private consortium are now being built. Japan’s financial system is no longer a closed circuit. It is growing an edge you can build against.

The demand is real, and the gateways to these platforms are underway.

That’s the gap Team1 Japan is here to close.

What is Team1?

Team1 is a network of builders, developers, creators, event organizers, and community leaders working to grow the Avalanche ecosystem from the ground up. Since launching in 2024, it has grown to hundreds of members across more than 40 countries, with official chapters now live in the USA, Vietnam, India, Türkiye, Brasil, and across LatAm.

Team1 Japan is the newest of those chapters.

Our mandate is focused: connect Japan’s builders to Avalanche, and connect them to each other.

This is a formalization, not a beginning

Japan’s Avalanche community has been meeting for years.

Since April 2023, over 30 events have been held across Tokyo, Osaka, Nagoya, and Fukuoka with more than 1200 attendees between them. The anchor is Avalanche Gourmet Night, a series running for over two years that marks the beginning of the Avalanche community’s in-person presence

The programming has widened past meetups. Avalanche Academy study sessions have run four times since March, giving developers a recurring technical space rather than a social one. There have been collaborations with Uniswap Labs, zeroone, and Pudgy Penguins, and a workshop for teams who entered the JPYC stablecoin innovation challenge.

What’s live from day one

Team1 Japan starts with a working cadence, not a launch announcement:

• A weekly Team1 Japan meeting, from launch week onward. Details on our Luma calendar.

• In-person and online events across Oct and Nov, including a community meetup in Tokyo and a builder session for developers who want to deploy on Avalanche.

Expect to see more hyper-focused enterprise and university workshops geared towards enabling builders to realize the projects they want to build.

Looking to get involved?

Team1 members work across three tracks, and all three are open in Japan:

Community. Organizing meetups, running events, welcoming newcomers, making the room feel worth walking into.

Technical. Developer workshops, hackathons, deployment support, helping builders get from an idea to something running on-chain.

Content. Writing, video, design, and translation, telling the Avalanche story in Japanese for a Japanese audience.

Full-time Web3 experience is not a prerequisite. What matters is initiative, follow-through, and a genuine interest in helping the people around you. If you’re a student curious about where to start, a developer evaluating chains, a founder looking for a route to capital and partners, or a creator who wants to work on something with real momentum behind it, there’s a place for you here.

Where this goes

Japan’s institutional footprint on Avalanche will keep growing.

Our job is to make sure that by the time all of that matures, Japan has a builder community deep enough to meet it: one that produces its own projects, its own founders, and its own reasons for the next institution to choose Avalanche.

That community starts now, and it starts with whoever reads this and decides to show up.

Institutions chose Avalanche. Now it’s the builders’ turn.

* X: https://x.com/Team1JP
* Telegram chat: https://t.me/avalanche_jp
* Luma: https://luma.com/Team1JP

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

The Dubai International Financial Centre (DIFC) Courts have begun issuing court orders and hearing records with credentials on the Avalanche C-Chain. Designed and built by Deca4 Advisory, the system allows recipients to verify a document’s origin and check whether it has been altered. Verification takes seconds and is available to anyone who receives a document, anywhere in the world.

The system is particularly relevant for cross-border commercial disputes. Parties can choose DIFC Courts to resolve disputes through a clause in their contract, even if neither party has a connection to the UAE. When court documents are presented to banks, companies or authorities in other jurisdictions, recipients need to establish their authenticity.

How it Works

The system uses a cryptographic hash, a digital fingerprint generated from a file’s contents. The process has two main steps:

1. Issuance: When the Courts issue a document through their existing digital infrastructure, its cryptographic hash is linked to a unique NFT-based credential recorded on the Avalanche C-Chain.

2. Verification: The recipient checks the file against the onchain credential. If a single character in the document has changed, the hash changes, and the verification fails.

The document itself remains offchain. No document content or confidential case information is recorded on Avalanche. The credential is strictly non-transferable, carries no monetary value, and cannot be traded.

What does Blockchain Add?

In general, a public blockchain can provide a record that recipients can check without relying solely on records held within the issuing organisation’s own systems. Information recorded on a blockchain is also designed to be difficult to alter retrospectively.

The system works with the Courts’ existing digital document infrastructure. Recipients can check a document against its blockchain credential without needing access to the Courts’ internal systems.

Digital signatures can also help verify a document’s origin and detect changes. Blockchain-based credentials are therefore one approach among several, rather than the only way to establish document authenticity.

A successful check confirms that the file matches the credential issued for it. It does not establish that the document’s contents are true or, by itself, confirm whether a court order remains legally in force.

Broader UAE Alignment

The deployment aligns with the objectives of the Dubai Digital Strategy and Dubai Economic Agenda D33. It also sits within a wider adoption of Avalanche technology across UAE public infrastructure. Separately, the Telecommunications and Digital Government Regulatory Authority (TDRA) is working with Deca4 Advisory and Ava Labs to bring Avalanche infrastructure into the UAE PASS Digital Vault, a distinct initiative focused on verified digital documents.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

Nansen recorded 48.4 million transactions, down 33% from the previous 30 days. At the same time, DEX volume climbed to $2.7 billion, up 145%, while active users increased 8.1% to 1.6 million.

So Avalanche was not simply quieter. There were fewer transactions in Nansen’s dataset, but much more trading volume. Users still grew, capital continued moving through the ecosystem, and activity across individual Avalanche L1s adds another part of the picture.

Trading picked up fast

The biggest change is DEX volume. WAVAX alone accounted for around $2.5 billion, with roughly $1.3 billion in buys and $1.3 billion in sells.

Active users also moved higher, reaching around 1.6 million, up 8.1% from the previous period. If that user growth continues while transactions stabilize, this month may end up looking more like a change in how Avalanche is being used than a simple drop in activity.

AVAX and WAVAX are moving differently

Around $4.6 million of native AVAX left exchange wallets over the latest seven days. WAVAX went the other way. Around $12.3 million moved into exchanges, while Top PnL wallets reduced their WAVAX positions by roughly $2.2 million.

Native AVAX is moving away from exchanges while WAVAX is moving toward them. At the same time, WAVAX remains extremely active on DEXs. For now, it looks more like capital moving around the ecosystem than everyone taking the same position.

Fresh wallets are still bringing money in

Fresh wallets added approximately $20.8 million in AVAX over seven days. Another $16.3 million went into WAVAX. Those are meaningful inflows, but both were below their normal levels. AVAX was running at around 0.6x its average flow, while WAVAX was around 0.4x.

New wallets are participating, just not at an unusually high rate. There is fresh capital coming in, but this does not look like another sudden wave of adoption.

BTC.b is still doing real volume

BTC.b continues to be one of the more active parts of Avalanche DeFi. It recorded around $238.8 million in DEX volume over 30 days, with approximately $1.3 million in net flow.

Over the latest seven days, BTC.b generated another $60.9 million in volume, with $31.5 million in buys and $29.4 million in sells.

There is no major imbalance between buyers and sellers. It is simply an active market.

Bitcoin liquidity gives Avalanche another source of capital beyond AVAX and stablecoins, and BTC.b is still moving through the ecosystem rather than simply sitting in wallets.

sAVAX looks steady

sAVAX has around 16,609 holders, approximately $169.8 million in market cap, and roughly $2.2 million in liquidity. Seven-day volume was around $743,000, with approximately $424,000 in buys compared with $319,000 in sells.

There is no obvious new staking surge here. But sAVAX does not need explosive trading volume to remain useful. Its role is still the same: letting AVAX holders earn staking yield while keeping their capital available elsewhere.

This month, it looks steady.

BUIDL is becoming part of a bigger institutional story

Around $564 million of BlackRock’s BUIDL is currently on Avalanche. DefiLlama independently shows almost the same figure, and its chain breakdown places Avalanche among BUIDL’s largest deployments.

That balance is lower than the $900M+ Avalanche briefly held during the summer, but the institutional story has become broader than BUIDL alone.

In July, Securitize launched tokenized SECZ shares on Avalanche and Solana when the company went public. Then in August, Securitize and Neuberger launched the HINC fixed-income fund across Avalanche, Ethereum, Solana and Sui.

More recently, IXS launched a high-yield corporate bond vault on Avalanche backed by BlackRock’s SHYG ETF. So the institutional story on Avalanche is starting to look broader than one tokenized Treasury fund.

There are now examples of tokenized Treasuries, public equities and fixed income using Avalanche infrastructure.

BUIDL was one of the first big proofs that institutional-scale assets could live on Avalanche.

Avalanche activity goes well beyond C-Chain

Avascan’s rolling 30-day figures currently show GUNZ at roughly 12 million transactions, Dexalot at around 6.9 million and Henesys at around 4.6 million. Because these are rolling figures, they change every day.

And those networks are doing very different things. GUNZ is built around gaming. Dexalot runs an onchain order book on its own Avalanche L1. Henesys powers the MapleStory Universe ecosystem.

That is what makes the L1 numbers interesting.

C-Chain is still central to Avalanche, but it is no longer the whole story.

Purpose-built Avalanche L1s are already processing millions of transactions a month across gaming, trading and other applications. The L1 strategy is no longer just something to talk about in terms of architecture. There is real activity behind some of these networks.

Where Avalanche stands now

This month looks less like a slowdown and more like a shift in where the activity is happening.

• DEX volume is up

• active users are higher

• BTC.b remains active

• institutional assets are expanding beyond BUIDL

• Avalanche L1s are already processing millions of transactions of their own

The network is becoming broader, more specialized and more useful across different types of applications.

Avalanche is not just growing on one front anymore. It is building several at once.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

For someone hearing about Avalanche for the first time, the X-Chain often stays in the background. This is because in daily use, the most visible layer is usually the C-Chain. The place where wallets connect, smart contracts are interacted with, and most applications run is mostly that one. Yet according to Avalanche’s official Primary Network documentation, the network consists of three main chains, and each of these chains takes on a different role. The X-Chain is the asset layer of this structure.

In Avalanche Support’s explanation of the X-Chain, the X-Chain is defined as the default asset blockchain of the Avalanche platform. The creation of new digital assets, the exchange of assets with one another, and the support of cross-chain transfers are among the functions that stand out here. Put more simply, the X-Chain is the layer where digital asset logic is carried within Avalanche.

What Does the X-Chain Do?

The role of the X-Chain is centered around a few main functions:

• It supports the creation of Avalanche Native Tokens

• It carries the logic of asset transfer and exchange

• It provides the basis for cross-chain asset movement

• It operates as the base layer for certain asset transactions, including AVAX

Who Interacts with the X-Chain?

Four groups may interact with the X-Chain, depending on their role in creating, transferring, or supporting digital assets.

The first group is teams creating or managing Avalanche Native Tokens.

The second group is institutions considering assets governed by predefined rules, such as the equity and bond examples in the Primary Network documentation.

The third group is users and services handling X-Chain transfers, including wallets and exchanges that support these asset flows.

The fourth group is infrastructure teams and node operators. On the AvalancheGo Architecture page, the X-Chain is described as the chain running on AVM and focusing on high-volume asset transfers with the UTXO model. Their work concerns how these transactions are processed, rather than the user-facing transfer interface.

How Is the X-Chain Different from the Other Two Chains?

The best way to understand the difference here is to separate the three chains according to their roles.

• C-Chain, is the execution layer where smart contracts and application logic run

• P-Chain, manages validator, staking, and Avalanche L1-level operations

• X-Chain, works for the creation and transfer of digital assets

This distinction matters because it would be mistaken to think of the X-Chain as a less-used version of the C-Chain. With the C-Chain, the main focus is application execution. With the X-Chain, the main focus is asset logic. With the P-Chain, the main focus is network coordination. Similarly, in Avalanche Support’s article explaining the differences between the X, P, and C-Chains, it is stated that the X-Chain is used on the sending and receiving side, while the C-Chain is the layer seen more often in the dApp ecosystem.

For this reason, the difference of the X-Chain is not just a technical distinction. It is the layer that separates asset operations within Avalanche from application and validator logic.

What Do We Mean by Asset Logic on the X-Chain?

Here, by asset logic, what is meant is not only that a token appears on the screen. The real issue is under which rules a digital asset is created within the network, how it is transferred, and how it relates to other assets. In the Primary Network documentation, it is clearly written that the X-Chain is responsible for Avalanche Native Tokens. In Avalanche Support’s explanation of the X-Chain, roles such as token creation, asset exchange, and cross-chain transfer are specifically listed.

Let us think about this with a concrete example. Say a team wants to issue a new digital asset on Avalanche. The issue here is not only showing a balance to the user. That asset must be defined within the network, become transferable, and move according to certain rules. The X-Chain comes into play exactly at this point. Because what is processed here is not the application interface, but the basic behavior of the asset within the network.

The same logic also applies on the transfer side. When a user sends a token, they only see a transfer transaction on the screen. But in the background, it matters with which asset model and with which transfer logic this is carried out. For this reason, the X-Chain is not only another chain. It is the layer that defines how assets live within Avalanche.

Why Was the X-Chain Designed as a Separate Chain?

The Primary Network documentation defines Avalanche as a heterogeneous blockchain network. In other words, instead of a structure where all tasks are gathered on a single chain, an architecture was preferred in which different tasks are separated into different chains.

This preference also makes sense in the case of the X-Chain. Because asset creation and transfer logic do not have the same needs as smart contract execution. Likewise, validator management is a completely different layer. When all of these are gathered in one place, both technical design and performance logic get mixed together. On the AvalancheGo Architecture page, it is seen that this separation is important in terms of modularity and parallel operation.

This is why keeping the X-Chain separate matters. Because Avalanche adopts not the approach that one chain should do every job, but the approach that each job should be optimized in its own area. In this architecture, the X-Chain is the special layer allocated to asset operations.

Why Does It Matter in Terms of Consensus and Transaction Logic?

For a long time, the X-Chain was known in the Avalanche ecosystem for its asset transfer-focused structure. In the Flow of a Single Blockchain guide, it is explained that the X-Chain is used for asset management and is associated with Avalanche consensus. By contrast, in the more recent AvalancheGo Architecture document, it is stated that the X-Chain became linear with Snowman after the Cortina upgrade. This detail matters because understanding the X-Chain is related not only to the question of what transaction it performs, but also to the question of within what kind of chain structure it carries out that transaction today.

The X-Chain is seen to be associated with high throughput and scalability logic. This emphasis on throughput and scalability helps explain why asset operations have a dedicated place in Avalanche’s architecture.

Why Does It Matter for Avalanche?

The importance of the X-Chain for Avalanche is that it shows the network is not made up only of smart contracts. On Avalanche, value does not only operate on contracts. At the same time, assets also need to be issued, moved, and managed according to different use cases. The X-Chain carries exactly this area.

While the Primary Network page describes the X-Chain as the base layer for Avalanche Native Tokens, the official support article about the X-Chain emphasizes its role on the asset exchange and cross-chain transfer side. When we think about these two together, the place of the X-Chain in the Avalanche architecture becomes clearer. The C-Chain carries the application face. The P-Chain carries network organization. The X-Chain carries the core logic of value and asset flow.

For this reason, the X-Chain is not only an old or background part of Avalanche. It is still one of the critical layers for understanding why the network’s multi-chain design was established.

Conclusion

Understanding the X-Chain means looking beyond a wallet balance to the rules and transaction model behind an asset’s creation and movement.

Technical Terms Mentioned in the Text

Avalanche Native Tokens

They are digital assets that can be created natively on Avalanche.

AVM

It is the Avalanche Virtual Machine that runs the X-Chain.

UTXO Model

It is a transaction model that tracks value with the logic of spendable outputs instead of collecting balance in a single account.

Cross-Chain Transfer

It refers to moving assets between different chains or connected structures within the network.

Further Reading

• AvalancheGo X-Chain RPC

• Cortina: X-Chain Linearization

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

For years, much of the conversation around tokenized finance has centered on the same assets: U.S. Treasuries, money market funds, and stablecoins.

They made sense as an entry point. These are familiar financial products with established demand, relatively straightforward structures, and deep liquidity. Putting them onchain demonstrated that traditional financial assets could exist within blockchain-based infrastructure.

But the market is starting to move further up the financial stack.

The latest example comes from Securitize and Neuberger Berman.

On August 18, Securitize announced the launch of the Neuberger Securitize High Income Tokenized Fund (HINC), a new tokenized fixed-income fund available across Avalanche and other three major networks.

The fund primarily invests in high-yield bonds while also gaining exposure to other income-producing assets, including collateralized loan obligations and leveraged loans. Behind the strategy is Neuberger Berman, whose fixed-income platform oversees more than $230 billion in assets.

The more interesting part, however, is what the fund represents for the broader evolution of tokenized finance.

Tokenization Is Moving Into Credit

The first phase of tokenization was largely about proving that familiar financial assets could be represented onchain.

HINC points toward a more ambitious use case: bringing actively managed and more complex financial strategies into blockchain-based infrastructure.

Neuberger Berman is contributing its fixed-income portfolio management and research expertise as subadvisor, while Securitize provides the infrastructure around the tokenized fund, including issuance, administration, and distribution.

The underlying investment strategy is still a traditional fixed-income strategy. What changes is the infrastructure through which investors can access and interact with the product.

That distinction matters because credit introduces considerably more complexity than simply representing a Treasury or money market fund onchain.

High-yield bonds, leveraged loans, and CLOs require credit analysis, portfolio construction, risk management, liquidity considerations, and active management. Bringing these products into a tokenized environment therefore tests whether blockchain infrastructure can support financial products with significantly more moving parts.

That is where the next phase of tokenization becomes interesting. If increasingly sophisticated financial products can operate through blockchain infrastructure, tokenization begins to look less like a niche digital-asset experiment and more like another component of financial market infrastructure.

Why Avalanche Matters

HINC is launching across four public blockchain networks, including Avalanche.

For Avalanche, the significance goes beyond having another tokenized fund deployed on the network. It adds to the network’s growing role in financial applications where regulatory requirements, asset issuance, ownership records, settlement, and institutional access all matter.

Securitize already supports tokenization on Avalanche C-Chain, providing infrastructure for the issuance and management of digital securities. Avalanche’s Builder Hub also highlights Securitize as a regulated platform supporting the tokenization, issuance, trading, and management of real-world assets such as credit funds, private equity, Treasuries, and public equities.

That existing foundation becomes increasingly relevant as tokenized products become more sophisticated.

Institutional finance has requirements that extend well beyond transaction speed. The infrastructure needs to support compliance, identity, secure ownership records, administration, settlement, and connections to existing financial systems.

A blockchain can have impressive technology, but institutional adoption ultimately depends on whether that technology can operate within the realities of financial markets.

Securitize’s presence on Avalanche gives institutions an established route into that infrastructure.

HINC Is Part of a Bigger Picture

HINC is one product, but it fits into a much broader development taking place across Avalanche.

OpenTrade, for example, provides institutional-grade asset-backed yield products backed by real-world assets such as money market funds, U.S. Treasuries, and other short-duration fixed-income products, with Avalanche C-Chain supported as a deployment environment.

Dinari approaches tokenization from another direction, providing blockchain-based access to tokenized U.S. public equities for non-U.S. users.

Securitize itself operates across a much wider range of tokenized assets, including private equity, credit funds, Treasuries, and public equities.

These products serve different purposes, and that is precisely what makes the trend worth watching.

Tokenization is developing into a broader ecosystem of financial products rather than a single use case. Different parts of traditional finance are finding different reasons to use blockchain infrastructure, from funds and credit to equities and government securities.

Avalanche is increasingly participating across those categories.

The Institutional Conversation Is Evolving

A few years ago, one of the biggest questions around institutional blockchain adoption was simple: Why would a financial institution use blockchain?

Today, the conversation is becoming more specific.

Financial institutions are looking at how blockchain infrastructure can fit particular products and workflows. The focus is shifting toward questions around compliance, settlement, ownership, distribution, interoperability, and how existing financial systems can connect with onchain markets.

The arrival of a tokenized fund backed by a fixed-income strategy from a major asset manager does not mean traditional finance is suddenly moving entirely onchain. One fund cannot prove that.

What it does show is that blockchain infrastructure is being considered for increasingly sophisticated financial products.

And Avalanche is part of that infrastructure.

The scale of Neuberger Berman’s fixed-income platform makes the development particularly notable. More than $230 billion sits behind the investment expertise involved in the strategy, while the tokenized fund itself creates a blockchain-based representation of that financial product.

That combination brings institutional asset management and public blockchain infrastructure into the same conversation.

The NYSE Connection Makes It Even More Interesting

There is another development that adds context to Securitize’s position in this market.

Securitize itself became a public company on the New York Stock Exchange in July 2026, while also making tokenized versions of its stock available onchain to eligible U.S. investors.

That creates an interesting connection between established financial markets and blockchain-based markets.

The same company can have shares trading through one of the world’s most established stock exchanges while using blockchain infrastructure to represent those shares onchain.

Traditional financial markets are not disappearing because of this. Instead, the infrastructure connecting traditional finance and blockchain markets is becoming increasingly intertwined.

That may ultimately be one of the most important stories behind tokenization.

What Comes Next?

The early tokenization market was about proving that financial assets could exist onchain.

The next phase could be about determining which financial products and processes actually benefit from operating through blockchain infrastructure.

That could mean more sophisticated funds, new forms of credit, tokenized equities, institutional distribution, and infrastructure connecting traditional financial markets with public blockchains.

There are still significant challenges.

Tokenization does not automatically create liquidity. Putting a bond or loan onchain does not remove credit risk. Smart contracts do not replace regulation, custody, asset management, or the responsibilities of financial institutions.

The financial product still has to make sense, and the underlying infrastructure still has to meet institutional standards.

That is why developments like HINC are worth paying attention to.

The interesting part is not simply that another fund has been tokenized. It is that a major fixed-income manager is bringing a sophisticated investment strategy into an environment that includes public blockchain networks.

That represents a meaningful step beyond the earliest applications of tokenized finance.

Avalanche’s Role Is Becoming Clearer

Avalanche does not need every financial product in the world to launch on its network.

What matters is establishing itself as a credible environment for financial products that can benefit from blockchain infrastructure.

Securitize and Neuberger Berman’s new fund adds another example to that story. It brings together institutional fixed-income expertise, regulated tokenization infrastructure, and a platform representing more than $230 billion in fixed-income assets, with Avalanche among the networks supporting the product.

As tokenized finance develops, the opportunities could extend far beyond the assets that dominated its early years.

The first era showed that assets can move onchain.

The next era will be about understanding which parts of finance benefit from moving onchain, how those systems should operate, and which infrastructure can support them at institutional standards.

Avalanche is already part of that conversation.

And if the shift toward tokenized credit and more sophisticated financial products continues, HINC may end up being less of an isolated development and more of a sign of where the market is heading.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

Avalanche’s smart contracts can execute flawlessly and still fail their users if the data feeding them is wrong or manipulable. Lending markets need honest prices to avoid bad debt. Betting platforms need randomness nobody can rig. Cross-chain transfers need a way to move value without a centralized bridge operator holding the keys. Chainlink is the infrastructure Avalanche protocols lean on to solve all three problems. That dependency is the real reason Chainlink matters to Avalanche: pull it out, and a meaningful share of what makes Avalanche’s DeFi and gaming ecosystems trustworthy goes with it.

The numbers at a glance:

• 182 Chainlink integrations live on Avalanche, second only to Ethereum

• $33.124 billion secured by Chainlink’s oracle network across 505 protocols network-wide

• Roughly 59 percent of the tracked oracle market by total value secured

• CCIP transfer volume grew 319 percent year over year in Q1 2026, processing over $18 billion for the quarter

• CCIP now connects more than 60 blockchain networks, up from four at launch

What is Chainlink?

Chainlink is a decentralized oracle network, co-founded by Sergey Nazarov, that lets smart contracts securely access off-chain data, APIs, and payment systems. It solves a problem specific to blockchains: contracts execute exactly as written, but they have no native way to know a token’s market price, confirm a real-world event happened, or talk to a contract on a different chain.

Chainlink’s nodes fetch, verify, and deliver that data onchain. Data Feeds alone power 908 integrations across more than 27 blockchains, with Ethereum hosting 1,403 individual integration points, the largest share of any network.

How it works

Chainlink runs as a network of independent node operators, so no single data source determines what a contract receives. Multiple nodes retrieve the same piece of information, and the network aggregates their responses before delivering a single verified answer onchain. No single node, API, or operator can quietly feed a smart contract bad information.

The core services built on that network:

• Price Feeds. Continuously updated, aggregated price data that DeFi protocols use to determine collateral values, liquidation thresholds, and asset pricing.

• CCIP (Cross-Chain Interoperability Protocol). A messaging and token transfer layer that lets smart contracts on one chain communicate with and move assets to another, now spanning over 60 public and private networks.

• VRF (Verifiable Random Function). Generates tamper-proof, cryptographically verifiable randomness for gaming, NFT minting, and any use case that needs an outcome nobody can rig, the exact mechanism FerdyBet uses to prove its betting results aren’t manipulated by the house.

• Data Streams and Automation. Low-latency data delivery and automated contract execution for time-sensitive applications.

• Functions. Lets smart contracts call external APIs directly, extending what a contract can react to beyond onchain events.

• Staking. Chainlink Staking v0.2 secures oracle and CCIP services through a 45 million LINK pool, with a 4.5 percent annual base reward rate and a 4.32 percent effective rate for community stakers.

Chainlink’s footprint on Avalanche

Chainlink is one of the most deeply integrated pieces of infrastructure on Avalanche, but the integration count only matters because of what it enables in practice. Two examples show what that looks like day to day.

1. BENQI, Avalanche’s largest lending protocol, has run on Chainlink Price Feeds since 2021, using them to price collateral and trigger liquidations across markets for AVAX, ETH, BTC, and stablecoins. Without a reliable price feed, an undercollateralized loan can sit unliquidated long enough to leave the protocol holding bad debt, which is exactly the failure Chainlink’s aggregated pricing is built to prevent.

2. On the gaming and gambling side, FerdyBet uses Chainlink VRF to generate the random outcomes behind its betting games. Every roll or draw comes with a cryptographic proof that the result wasn’t manipulated by the house, the developers, or anyone else, which is the difference between an onchain betting platform players can verify and one they simply have to trust.

Beyond these two, the broader pattern holds across categories:

• DeFi accounts for the largest share of integrations network-wide, at 1,120 projects

• NFT projects account for 608 integrations

• Gaming accounts for 346 integrations

• Aave V3 alone accounts for 43.11 percent of Chainlink’s total secured value, at $14.28 billion

Avalanche’s own Builder Hub lists Chainlink as a core integration, pointing developers to CCIP for secure cross-chain data transfer and smart contract execution. CCIP connected Avalanche from launch, alongside Ethereum, Optimism, and Polygon, before expanding to the 60-plus networks it supports today.

Why it matters for Avalanche

Avalanche’s DeFi ecosystem depends on price data it cannot generate internally. Lending markets need accurate collateral pricing to avoid bad debt. Derivatives platforms need real-time feeds to settle positions correctly. Chainlink’s Price Feeds have become the default way Avalanche protocols get that data, which is a large part of why the integration count sits at 182, behind only Ethereum.

CCIP extends that role beyond price data. As more assets, gaming economies, and enterprise deployments move across multiple chains, Avalanche needs a reliable way to move data and tokens in and out. CCIP is one of the main paths doing that today, connecting Avalanche to the broader multi-chain landscape.

The enterprise side is worth watching closely. Chainlink has become a default layer for institutional players moving real-world assets onchain:

• Partnerships with major banks including ANZ and BNY Mellon for tokenized asset settlement

• A collaboration with SWIFT, the global banking messaging network, connecting traditional interbank infrastructure to blockchain-based assets

• Amundi’s Spiko tokenized fund, powered by Chainlink, reached more than $400 million in assets under management within three weeks of launch

• The World Economic Forum estimates $867 trillion in global financial assets could eventually be tokenized, with RWA tokenization already surpassing $27 billion in distributed asset value in 2026

As institutional activity increasingly touches Avalanche, Chainlink’s existing rails give it a head start most competing oracle networks don’t have.

The competitive picture

Chainlink isn’t unchallenged. LayerZero has built substantial adoption for cross-chain messaging, Wormhole continues operating as cross-chain infrastructure despite past security incidents, and Pyth competes directly in price feeds. Chainlink’s response has been to widen its product suite, spanning Price Feeds, CCIP, Data Streams, Functions, Automation, and Staking, and to deepen institutional integrations that are harder for smaller competitors to match.

What’s next

Chainlink’s roadmap keeps leaning into cross-chain infrastructure and institutional integrations, and Avalanche is well positioned to benefit from both. As CCIP’s network of supported chains keeps growing, Avalanche protocols gain more reach without a heavy lift. As institutional players keep building tokenized asset products on Chainlink’s rails, Avalanche’s existing Price Feeds and CCIP connections put it in a strong position to receive that activity.

The signal worth watching is adoption depth, not headline announcements: whether more of Avalanche’s lending, gaming, and RWA protocols start building on CCIP the way BENQI built on Price Feeds, and whether the next wave of institutional tokenization projects choosing Avalanche do so because Chainlink’s infrastructure is already sitting there ready to use.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

Summit was the center of gravity for September, and everything else orbited it. Over two days in New York, Avalanche turned the stage into a live feed of institutional breaking news: Ethena’s Avalanche-exclusive neobank, South Korea committing its capital markets onchain, Hanwha’s tokenization platform, and UAE PASS serving 12 million people on national identity rails.

Asset managers from Janus Henderson to Goldman Sachs showed up with real allocations, Kevin O’Leary headlined, and the team closed it out calling it the most impactful Summit yet. Helicon also activated on mainnet during the same stretch, and Avalanche closed the month leading every chain in tokenized stock inflows and RWA growth.

Here’s everything that happened.

September’s biggest technical story was Helicon going live, alongside record-setting weeks for tokenized assets.

Avalanche Turns Six:

The Avalanche genesis block was minted six years ago this month. [Genesis]

Helicon Goes Live on Mainnet:

Helicon brought Continuous Execution for a faster C-Chain, auto-renewing staking, 48-hour minimum staking periods, and a new reward curve designed to reduce AVAX issuance. [Helicon]

Tokenized Assets Set New Records:

Avalanche pulled in $131.2 million in tokenized stock inflows over seven days, eight times the second-highest chain, while its RWA market cap grew $266 million over 30 days, more than the next two chains combined. [Stock Inflows] | [RWA Growth]

Team1 Expands Across New Chapters and Continents:

Team1 opened new ground this month: the UK held its first event outside London in Chesterfield, while Amsterdam and Sofia each hosted their first Connect. Thailand officially launched as a chapter following a six-university workshop tour.

Elsewhere, Türkiye ran its first AI agent workshop, Ghana held its Blockchain and AI workshop, and a 50-builder residency took place in Bursa. Korea and Brazil held Builder Connects, while LatAm met with 20+ builders at Bolivia’s EthereumBo Buildathon. Team1 also hosted a rooftop meetup with The Grotto in NYC during Summit week, alongside many other events across different continents.

Team1 Backs Builders and Brings Their Voice to Policymakers:

Team1 awarded a $5,000 Builder Mini Grant to Empowr, an onchain bounty platform, and Luke152 met with U.S. Senator Cornyn’s office in Austin to discuss the CLARITY Act, covering consumer protection and World Cup ticketing. [Empowr Grant] | [Policy Meeting]

Avalanche Audit Marketplace Goes Live:

The Avalanche Audit Marketplace launched on Builder Hub, letting one request reach every Ava Labs-vetted audit firm with private quotes and up to 75% of the cost covered. Fees are zero for both builders and auditors. [Audit Marketplace]

College Athletics Goes Onchain With Uptop:

Baylor, Memphis, Nevada, and Michigan launched fan rewards programs with Uptop this month, joining Penn State and LSU. [Baylor] | [Michigan]

Lake Bears and Salmon Arrive on The Grotto:

The Grotto’s Lake Bears and Salmon collections went live, adding to its growing world of onchain collectibles. [Grotto]

FIFA Collect Crosses One Million Users:

FIFA Collect CEO Francesco Abbate confirmed the platform has crossed 1 million users, remaining one of Avalanche’s largest consumer applications. [FIFA Collect]

Insomniac and Onchain Entertainment:

Festival brand Insomniac partnered with Avalanche and Rain on a new fan loyalty program. [Insomniac]

Agentic Commerce Still Has Room to Run:

Speaking at Summit, Blockchange’s Schmults argued the real use cases for AI agents moving and managing money haven’t even been discovered yet. [Agentic Commerce]

Summit week turned into a run of institutional breaking news, from neobanks to sovereign capital markets.

Ethena Launches a Neobank Exclusively on Avalanche:

Ethena Pay brings everyday banking onchain, letting users save, send, and spend USDe from their phones, building on Ethena’s footprint across Robinhood’s crypto earn product and BlackRock’s Aladdin platform. [Ethena Pay]

South Korea Moves Its Capital Markets Onchain:

South Korea’s Financial Services Commission and Korea Securities Depository are laying groundwork to bring stocks, bonds, and funds onchain via Avalanche. [South Korea]

Hanwha and a Won-Backed Stablecoin Join From Korea:

Hanwha Investment & Securities, part of the $200 billion conglomerate, is building a tokenization platform on Avalanche, while Korea’s first won-backed stablecoin, KRW1, is going global through Rain. [Hanwha] | [KRW1]

UAE Powers National Digital Identity With Avalanche:

UAE PASS, the country’s national digital ID system, uses Avalanche to serve more than 12 million citizens, residents, and visitors. [UAE PASS]

Goldman Sachs Brings a $100B Treasury Fund to Avalanche:

Goldman Sachs is bringing its flagship $100 billion Treasury fund to Avalanche through Lynq, a private permissioned L1 already used by 30-plus institutional firms.

[Goldman Sachs]

Janus Henderson and New York Life Join Avalanche:

Janus Henderson, which manages $500 billion, became a validator on Avalanche, and New York Life brought its first tokenized fund onchain through Centrifuge. [Janus Henderson] | [NYLIM]

Aave Launches an RWA Lending Hub:

Aave’s new RWA Hub lets institutions borrow stablecoins against tokenized assets without selling their positions. Deposits on Aave V4 have since surpassed $30 million. [RWA Hub]

Paxos and NYSE Expand Institutional Access:

Paxos integrated Avalanche across infrastructure serving 650-plus institutions and $18 billion in assets under custody, while NYSE is evaluating Avalanche for a 24/7 trading platform in development. [Paxos] | [NYSE]

Pharaoh Expand Trading:

Pharaoh unveiled plans for 24/7 permissionless trading of tokenized U.S. stocks on its Avalanche-native exchange. [Pharaoh]

Hyundai Card Cuts Transfer Time by 96%:

Hyundai Card’s stablecoin pilot on Avalanche cut transfer time by more than 96%, and the company is now exploring how faster transfers can free up idle liquidity. [Hyundai]

More Institutions Build and Raise on Avalanche:

Wellington and Fasanara brought institutional credit strategies onchain via Midas, Iris raised $40 million for its ALVA app, and India’s Arya.ag partnered with Finternet on agricultural credit for farmers. [Midas] | [Iris]

Lynq Migrates With Zero Disruption:

Lynq moved institutional settlement to its Avalanche L1 and saw 65% faster processing, with Tassat leading the migration in under two hours. [Lynq]

COTI Brings Privacy-on-Demand to Avalanche:

COTI’s Privacy-on-Demand and Privacy Portal went live, giving businesses a way to keep confidential information private onchain. [COTI]

Bloxtel Brings Private 5G Onchain:

Bloxtel unveiled the AP 201, combining a private 5G stack and AI-powered network management into a single unit built on Avalanche. [Bloxtel]

Avalanche Summit NYC anchored the month, with sponsors, media partners, and thousands of attendees converging on New York.

Avalanche Summit NYC Draws a Historic Lineup:

Summit brought together sponsors including Anchorage, Paxos, and Zerohash, media partners The Block and The Rollup, headliner Kevin O’Leary, amongst others, closing out what the team called its most impactful Summit yet. [Summit Wrap]

Stani Kulechov on Why Aave Chose Avalanche:

Aave founder Stani Kulechov told Cami Russo that Avalanche has a strong community building on finance, calling onchain finance the whole point of the network. [Kulechov]

BlackRock’s Maxwell Stein on Markets That Never Close:

Maxwell Stein said blockchain gives “anybody with a wallet” the same institutional advantages. [Stein]

Ava Labs CEO on Blockchain’s Next Chapter:

Emin Gün Sirer said it’s time to take blockchains from a technological curiosity to something deeply embedded in business workflows. [CEO]

Bitwise Co-Founder Would Build on Avalanche:

Hunter Horsley said that if he were building a chain from scratch, it would “hell yeah” be on Avalanche. [Horsley]

September closed the gap between Avalanche’s institutional story and the numbers behind it: a neobank, a sovereign capital markets project, and a $100 billion Treasury fund all landed in the same month Helicon went live and tokenized stock inflows outpaced every other chain combined.

But perhaps more importantly, Summit set the pace for what comes next. If September was a month of proof, the months ahead are shaping up to be an exciting continuation of that momentum.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

Picture a founder in Lagos with a payments idea, a smart contract developer in Nairobi, and a designer in Accra. Between them, they have the skills the product needs and firsthand knowledge of three markets.

Team1 Africa is officially here to bring people like them together.

For years, Team1 communities across Africa have grown city by city, each with its own focus. Some leaned into hackathons and university programs. Others filled rooms with art showcases, creator meetups, and networking nights, bringing local artists into the ecosystem alongside the developers. Team1 Africa links those communities into one network.

Our track record so far:

• 120+ events across the continent

• 3,500+ attendees

• 250+ developers activated

• 10 countries connected

Local Chapters, One Network

Lagos and Johannesburg have different customers and different developer cultures. A program that works in one city usually needs local changes to work in the other.

So our country leads stay close to their local scenes and run the programs that work there. Team1 Africa sits one layer up. If one country builds a university program that turns attendees into active builders, we share that playbook so the next country can adapt it instead of starting from zero.

The Hard Part Comes After the Workshop

Getting someone into a room is easy. But most people get lost in the weeks after.

Imagine a student leaving their first Avalanche workshop. They deploy a test contract that night, then get stuck, with no one to ask for help and no idea what to do next. Without a clear next step, plenty of people in that position drift away.

We built Team1 Africa around that next step. First-timers find a local community to keep learning with. Developers who want more can join hackathons, meet teammates, and get mentorship and technical support while they build.

For founders with a working product, we open routes into Avalanche programs and partners. Three Build Games teams have made the trip from early building to funding, and we want to open the same opportunities for high-quality projects built on Avalanche.

Why Avalanche Fits Here

Many African builders tackle everyday problems, like sending money across borders or reaching customers that banks overlook. They also build for markets with different rules in every country.

Avalanche lets teams launch their own custom L1 blockchains with their own settings. A payments app can charge fees in a stablecoin. A regulated fintech app can keep its chain permissioned and stay connected to the rest of the Avalanche network. A team can shape its chain around a single country’s rules this year and plug into the wider ecosystem when it’s ready to expand.

Bringing Universities In

If you walk through a computer science department almost anywhere in Africa, you’ll meet plenty of students who have never experienced blockchain tech. We want to build a journey where education leads to participation, participation leads to building, and building leads to bigger opportunities.

We’ll bring workshops, build challenges, and hackathons to campuses, and we’ll recruit student ambassadors who keep things moving between our visits. One event isn’t enough. We want this year’s students mentoring next year’s.

Pick Your Starting Point

Wherever you’re starting, the next step is close.

New to Avalanche? Our workshops start from the beginning and build toward your first deployed contract.

Builders with a project underway can head to Builder Hub for docs, courses, and grant programs. Team1’s Mini Grants go up to $10,000, and Accelerator Grants reach $30,000.

For lecturers and campus club leads, we’ll bring a workshop or hackathon to your university and connect your students with Team1 chapters throughout the world.

And if you design, write, or organize, there’s opportunity for you here. Every product that ships needs people who understand design, distribution, and the market it serves.

Already Doing the Work

People across Africa have been building for years in dozens of cities all at once. Team1 Africa gives them one network to build in together. Come to an event, say hello on Telegram, and start building with us.

One Continent. Many Voices. Team1 Africa.

Stay Connected

• X: https://x.com/Team1africa

• Telegram: https://t.me/team1Africa

• Luma: https://luma.com/Team1Africa

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

When Japan’s largest security token platform moved house

On July 13, 2026, Progmat - Japan’s largest security token platform, backed by MUFG - announced the full migration of its digital securities portfolio to a dedicated Avalanche Layer 1. The move covered more than ¥452 billion, or roughly $2.7-2.8 billion, in tokenized real estate and corporate bonds.

This was not a pilot or an MOU. It was not a “strategic partnership” followed by silence. It was the complete transfer of live assets off Corda - R3’s distributed ledger long regarded as the safe choice for traditional finance - onto a dedicated Avalanche L1. That L1 is part of the Avalanche network and is EVM-compatible, but it is not the shared public C-Chain; it is a customizable environment with its own validator and compliance settings.

In a market where every blockchain positions itself as a venue for RWA, a full migration of this scale by a tightly regulated Japanese platform is a concrete data point. An institution operating in one of the more conservative financial markets moved live securities infrastructure onto Avalanche.

The rest of this article looks at what else has landed on Avalanche and which structural features may help explain the pattern.

Avalanche is no longer just a “fast L1”

Throughout recent years, Avalanche has hosted a wider mix of institutional asset types than speed and fee metrics alone would suggest.

Beyond Progmat, several other institutional players have moved assets onto the network:

• Securitize became the largest RWA platform on Avalanche, with over $1.2 billion in tokenized assets (reaching $1.264B as of July 15, 2026).

• Bridgetower’s Arizona Copper-Gold project - reported at more than $11 billion in project value - is being tokenized on Avalanche.

• Galaxy Digital issued its first CLO on Avalanche, anchored by a $50 million allocation from Grove.

• Aave V4 went live on Avalanche in July 2026 with a clear focus on RWA-backed lending.

The range of asset classes is at least as notable as the headline totals.

Selected institutional RWA deployments on Avalanche

A few cases stand out:

• BUIDL - rapid growth. BlackRock’s fund held $624.87 million on Avalanche as of May 25, 2026, then added $436 million in a single week to surpass $900 million by July. It became the largest RWA asset on the network.

• Galaxy CLO - private credit onchain. On January 15, 2026, Galaxy closed its first tokenized CLO of $75 million on Avalanche, with roughly $50 million from Grove. This marked a shift from uniform, easy-to-price assets (T-bills) to more complex instruments that require underwriting. Higher risk, but a clearer sign of ecosystem maturity.

• Bridgetower - The Arizona copper-gold project accounts for most of the reported $11 billion. However, most of this value is recorded as Represented Assets and does not trade freely onchain.

Why Avalanche became “Home to RWA”

Several design choices on Avalanche line up with requirements often cited by institutional issuers:

1. Custom L1s (formerly Subnets). Institutions can launch their own blockchains with permissioned validator sets, custom gas tokens, and tailored compliance rules, while remaining connected to the broader Avalanche ecosystem. Progmat’s migration used a dedicated L1 of this type.

2. Performance and cost. Sub-two-second finality and very low transaction fees suit the volume and settlement needs of institutional assets.

3. Operational certifications. AvaCloud holds SOC 1 and SOC 2 Type II certifications. The network has established relationships with major funds and can meet regulatory requirements across the United States, Japan, and Europe.

Unlike the model in which every application runs on a single shared chain, Avalanche lets each application or institution operate in its own environment while still benefiting from the liquidity and security of the main network.

What’s next

Avalanche has shown the ecosystem can host large scale RWA. The next step is turning them into instruments that are actually used onchain.

Three developments are worth watching:

1. From “onchain” to “used onchain”

Aave V4 has been live on Avalanche since July 2026 with its Hub & Spoke architecture. A dedicated RWA Hub is on the roadmap. If tokenized Treasuries, money market funds, and private credit become usable collateral, RWA will move from record keeping to working capital.

2. Japanese Government Bonds

After the ¥452 billion migration, Progmat has formed a working group to study tokenized Japanese Government Bonds combined with onchain repo. A core sovereign instrument designed for 24/7 settlement on public-compatible infrastructure would be a clearer signal than the platform migration alone.

3. Secondary liquidity remains the bottleneck

Many permissioned products (Progmat, Bridgetower, parts of SkyBridge) still restrict transfers. Bridgetower’s $11 billion deal sits mostly as Represented value, with near-zero trading volume. Avalanche will strengthen its position only if more assets move from “recorded onchain” to “transferable between wallets and usable in DeFi.”

Conclusion

Avalanche has demonstrated the ability to handle large scale, regulated RWA across multiple jurisdictions - from the United States and Japan to Europe.

From over $1.2 billion tokenized via Securitize to Progmat’s $2.8 billion migration, from $1.89 billion in Distributed value to more than $11 billion in Represented assets, Avalanche is becoming one of the most credible homes for real-world assets on blockchain.

The next phase is clear: turning that large pool of capital into actual onchain flow.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

In Thailand, founders and developers often live ten minutes apart but never meet.

Team1 Thailand launches today to close that gap.

We are the Avalanche community layer for Thailand. We serve two crowds who rarely share a table: the digital nomads and international founders who cycle through Bangkok, Phuket, and Chiang Mai, and the local Thai developers and students who stand ready to code. Bringing these groups together will create one of Southeast Asia’s fastest-growing tech communities.

Our track record so far:

• Flagship events across the country, with our first ones in Chiang Mai, going beyond the usual Bangkok scene

• A university workshop at Chulalongkorn, with the first hackathon there this week, and Kasetsart, Thammasat, KMITL, and MUIC to follow

• Events co-hosted with 4 ecosystem partners: Pudgy Penguins, Binance TH, ST Thailand, and 4SEAS

• Builders onboarded in both Thai and English, from first wallet to first deployment

Walk In And Start Building

Team1 Thailand is a group of people who show up for each other and for new people walking through the door. You see it in what people do before anyone hands them a task.

One member joined four months ago and has already run six events. Between them, he built an event badge mint on Avalanche C-Chain, so attendees leave with proof of attendance. Another arrived weeks ago and, without being asked, built a workshop on policy-gated AI agents, shipped a working repo, and deployed real contracts on Fuji, then carried it to a campus herself. A student pitched a monthly program at Thammasat before anyone suggested one. Someone else designed the first chapter merch.

No queue, no job description. People show up, build, and ship.

Built in Bangkok, Running Across Asia

Last May, we ran a padel night with the Pudgy Penguins APAC team. We had a small budget and no official status yet. But it worked, so it traveled: the Philippines, then Japan, then Taiwan.

A relationship that started in Bangkok now runs across the region. That is what a local team is for: close enough to the ground to spot the opening, and connected enough to take it everywhere.

The Banks Got There First

While other ecosystems focused on turnout, real infrastructure went live in Thailand. In December, Kasikornbank announced Seamless Travel Payments on Chain with Orbix Technology and StraitsX at the Singapore FinTech Festival, part of Project BLOOM under the Monetary Authority of Singapore. A Thai tourist in Singapore pays with Q-money from a KBank wallet; it converts to XSGD, and the merchant receives Singapore dollars in real time.

The mechanics are the point. Q-money runs on Quarix, Orbix’s own chain. XSGD runs on Avalanche. Avalanche connects the two, because it supports permissioned custom L1s that meet regulatory and privacy requirements and still talk to everything else. This is the whole case for the Avalanche technology in one working example, built between two central banks.

Where You Come In

If you build, come to an event. And remember, you don’t need to be technical. Then sign up for Builder Hub, where the resources live, and capital can find your work. Team1 runs Mini Grants up to $10,000 and Accelerator Grants up to $30,000. Grants are competitive. Even if you don’t get funded, hard-working teams can still get marketing and distribution support.

If you teach or run a university club, we can bring a workshop and a hackathon to your campus, plus a route into a global builder network. Thailand has thousands of computer science students who will never touch a blockchain unless someone puts it in front of them.

If you run a business, the KBank case is a great example: permissioned chains that satisfy a regulator with real-time settlement, and interoperability with what you already run.

Get In Early

The chapter is live, the campus tour has started, and the hackathons run through the end of the year. Get in now, and you are early enough to shape the future of Thai blockchain infrastructure.

Four years ago, many people showed up here when things were loud. Some of us stayed after it went quiet. That work ethic put us in a position to open the door to the next generation. So come on in and start building.

Telegram: @team1TH
Events: luma.com/team1th
X: @Team1TH
Instagram: @team1TH

Helicon went live on Avalanche mainnet on September 22, activating six Avalanche Community Proposals: ACP-194, ACP-236, ACP-267, ACP-273, ACP-283 and ACP-285.

The upgrade reshapes two key areas of the network in particular. The C-Chain gets a new execution model and a new way of managing its minimum gas floor, while validators get shorter staking periods, automatic renewal and changes to the reward curve.

Continuous Execution Changes the C-Chain

One of the biggest changes in Helicon is how the C-Chain processes transactions. Instead of making the network wait for execution to finish at every step, Continuous Execution separates consensus from execution. New blocks can continue moving through the network while earlier blocks are still being executed.

The goal is to remove a bottleneck and give the C-Chain more room to handle periods of high activity. For everyday users, most of this happens behind the scenes.

Developers and infrastructure providers do need to account for a change in timing, though. A transaction can be included in a block before its state changes have finished executing, creating a short gap between block inclusion and the state becoming available. RPC providers, indexers and applications that depend on immediate state updates need to handle that distinction.

The C-Chain Gets a Dynamic Gas Floor

ACP-283 changes another long-standing C-Chain assumption.

The network previously had a fixed 1 wei minimum gas price. Helicon replaces that fixed floor with a validator-governed minimum based on stake-weighted validator preferences.

The floor starts at 1 wei and can change over time. Validators can influence the minimum gas price, allowing the floor to respond to changing network conditions rather than staying permanently fixed.

For most users, this should happen without any change to how they use their wallets. Developers and RPC providers, however, should no longer assume that 1 wei will always be the minimum.

Validator Staking Drops to 48 Hours

Helicon makes its most significant changes on the validator side by pairing shorter commitments directly with automation. ACP-273 cuts the minimum validator staking period from two weeks to 48 hours, while ACP-236 introduces auto-renewed staking so operators can set custom cycle lengths and automatically compound rewards.

The two proposals belong together. Without auto-renewal, a 48-hour minimum would force continuous node operators to manually submit new staking transactions every two days, trading capital flexibility for constant operational overhead. Auto-renewal eliminates that friction, giving operators more flexibility over locked capital without requiring them to repeatedly manage new staking periods. Delegators, however, do not get the same treatment: their minimum duration remains two weeks, and delegations cannot auto-renew. Delegators also remain subject to the lower reward rates introduced by ACP-285.

At the same time, this increased capital flexibility comes with tighter performance demands. ACP-267 raises the minimum uptime threshold for new staking periods from 80% to 90%. Because missing the threshold results in forfeiting the entire cycle’s yield rather than receiving a partial payout, maintaining high-availability infrastructure becomes critical, especially for operators running shorter staking windows.

Staking Rewards Now Favour Longer Commitments

ACP-285 changes the other side of that equation by making shorter staking periods less rewarding.

The mean consumption rate moves from 10% toward 7.5% over a 90-day ramp. The rate in effect when a new staking period begins is locked for that period.

In practical terms, the shortest staking periods see the biggest reduction while the one-year maximum remains unchanged. Avalanche’s modelling in ACP-285 puts the 14-day annualized reward rate at roughly 5.4% initially, moving toward about 4.1%, while the one-year rate remains around 6.4%.

The model also estimates that the changes could increase the stake-weighted average staking duration by around two months and reduce annual inflation by roughly 0.5 to 1 percentage point. Those are projections rather than guaranteed outcomes, since the eventual effect depends on how validators and stakers respond to the new incentives.

Institutions and Validator Participation

These changes also matter for institutions considering direct participation in Avalanche’s validator set.

On September 16, six days before Helicon went live, Janus Henderson announced that it had become an Avalanche validator. The global asset manager oversees roughly $500 billion in assets.

Janus Henderson became an Avalanche validator before Helicon reached mainnet. It does, however, provide a timely example of the type of regulated institution that can participate directly in securing the network.

The upgrade changes some of the practical conditions around that participation. A 48-hour minimum gives institutions more flexibility over locked capital, while auto-renewal reduces the operational work involved in maintaining a continuous validator position.

What Changes for AVAX Holders?

Helicon does not change Avalanche’s 720 million AVAX supply cap. What it changes is the mechanism around staking rewards and, consequently, the potential pace of new AVAX issuance.

Shorter staking periods now earn less, while the highest reward rate remains available to longer commitments. For someone simply holding AVAX, there is nothing they need to change. The effects are mainly felt by validators, delegators and applications interacting directly with the C-Chain.

Helicon is now running on Avalanche’s mainnet. Its changes are relatively simple to describe individually, but together they alter the trade-off between capital flexibility, validator reliability and long-term staking incentives, while giving the C-Chain more capacity to handle periods of high activity.

Learn more: Read the Helicon upgrade documentation for the full technical details and implementation changes.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

For someone hearing about Avalanche for the first time, the P-Chain often seems like the most invisible part of the network. This is because the place users see on a daily basis is usually the C-Chain. The layer where wallets connect, tokens are sent, and applications are used is most often that one. Yet according to Avalanche’s official Primary Network documentation, the network consists of three main chains, and each of these chains takes on a different role. The P-Chain is the coordination layer of this structure.

In Avalanche Support’s explanation of the P-Chain, the P-Chain is defined as Avalanche’s metadata blockchain. Validator coordination, staking, and L1 records all live here. It is the least visible chain from the user side and still the one that decides who validates the network and which chains are part of it.

What Does P-Chain Do?

As explained on the Primary Network page and in the PlatformVM Architecture documentation, the role of the P-Chain is centered around a few main jobs.

• It records Primary Network validators and delegators

• It manages staking operations and the reward logic

• It makes the creation of new blockchains and Avalanche L1s possible

• It carries L1 membership, chain creation, and network-level state information

At first glance, these duties may seem far away from the end user. But in fact, a large part of the question of how Avalanche works is answered here. It is not enough for a network to simply produce transactions. Who will be a validator, how staking will work, how a new chain will be added to the system, and how this structure will be coordinated are all just as critical as user transactions. The P-Chain manages exactly this area.

On the technical side, the PlatformVM Architecture page also shows that the P-Chain is not limited to staking and validator registration alone. The same document explains that cross-chain platform functions such as warp signing and atomic transfer are also related to this layer. This shows that the P-Chain is not just a staking chain, but the layer that carries the platform logic of the Avalanche architecture.

Who Uses the P-Chain?

The P-Chain is used most by four groups.

The first is validators and delegators. Because as stated in the official support article explaining the differences between the X, P, and C-Chains, the P-Chain is used for staking. If you are joining a validator or participating in the network as a validator, the staked AVAX and the reward logic take shape in this layer.

The second group is node operators and infrastructure teams. The AvalancheGo P-Chain RPC documentation shows that the P-Chain API is used for interaction with validator sets, blockchain creation, and staking data. So the P-Chain is not only a theoretical architectural component, but also an operational layer that is directly touched on the infrastructure side.

The third group is teams that want to build their own Avalanche L1. The Primary Network documentation says that the P-Chain supports the creation of new blockchains and Avalanche L1s. For this reason, the P-Chain is one of the main entry points for anyone who wants to establish a new sovereign network on Avalanche.

Institutions are another important group, especially those building regulated or specialized networks. Avalanche’s official L1 documentation describes use cases where an L1 can require validators to be located in a specific country, pass KYC/AML checks, or hold a license. Concrete examples in Avalanche’s official ecosystem materials include the Dinari Financial Network and Intain, which provides infrastructure for tokenizing and managing asset-backed securities. In this type of institutional setup, the P-Chain handles validator membership and network-level registration, while the institution’s financial or application logic runs on the L1 itself.

The fourth group is end users in an indirect way. Someone using a daily dApp usually interacts not directly with the P-Chain, but with applications and wallet interfaces on the C-Chain. But if they are staking, delegating to a validator, or taking part in an L1 ecosystem within Avalanche, the validator, staking, and network organization rules behind that experience are largely shaped on the P-Chain side. In other words, the user usually does not see the P-Chain as a separate screen or a separate application layer, but some core network rules still operate through the P-Chain.

How Is the P-Chain Different from the Other Two Chains?

The best way to understand the difference here is to separate the three chains according to their roles.

• C-Chain, is the execution layer where smart contracts and application logic run

• X-Chain, is used for the creation and transfer of digital assets

• P-Chain, manages validator and Avalanche L1-level operations

The P-Chain is not a smart contract chain. It is not the main stage of daily DeFi transactions. It is not the main area for token creation either. It is the layer where platform rules inside Avalanche are processed.

What Do We Mean by Rules on the P-Chain?

Here, by rule, what is meant is not the guidance written in a wallet interface, but the protocol logic that accepts or rejects the network’s platform-level operations. In other words, when a user, operator, or team starts a transaction, whether that request will be considered valid is ultimately determined by the rules of the P-Chain.

Let us think about this with a concrete example. Say a node operator wants to become a Primary Network validator. On the Primary Network page, it is explained that this works through staking. On the PlatformVM Architecture page, transaction types such as AddValidatorTx and AddDelegatorTx are listed. In practice, the wallet or the tool being used only sends the request. Whether this request is accepted by the network as a valid validator record, how it is written into the validator set, and how the staking process will be handled are determined on the P-Chain side. So the user starts a transaction on the screen, but the layer that gives that transaction its network-level meaning is the P-Chain.

The same logic also applies when creating a new Avalanche L1 or a new blockchain. The fact that transaction types such as CreateSubnetTx and CreateChainTx appear in the same document is not accidental. This shows that a new network is not just a configuration screen opened in a panel. Which chain is created, which validator structure it is associated with, and how it is defined within Avalanche are processed and recorded on the P-Chain.

For this reason, it is more accurate to say that the P-Chain is the place where rules are processed. Because the issue here is not only storing data. Which platform transaction is valid, which membership is considered active, and which network operation is included in the system are finalized in this layer.

While Avalanche Support’s article on the differences says that the P-Chain is used for staking, the Primary Network page explains that validator and L1-level operations run here. When you read these two explanations together, the picture becomes clear. The C-Chain is the application layer. The X-Chain is the asset layer. The P-Chain is the network management and coordination layer.

Why Was the P-Chain Designed as a Separate Chain?

The Primary Network documentation defines Avalanche as a heterogeneous blockchain network. In other words, instead of a homogeneous model where everything is collected into a single chain, an architecture was preferred where different tasks are carried out on different chains.

This choice is not random. Smart contract execution, asset transfer, validator registration, and staking are not the same kind of workload. When you collect all of them on a single chain, technical requirements pile on top of each other and a single bottleneck can affect the whole structure. The AvalancheGo Architecture page also especially emphasizes modularity and the logic of parallel processing across independent chains. This perspective makes it easier to understand why the P-Chain was designed as a separate platform layer.

At a technical level, the PlatformVM Architecture document says that the P-Chain runs on PlatformVM and Snowman++. What this setup has to get right is the orderly execution of platform operations such as validator management, staking flow, L1 membership, and chain creation. Keeping the P-Chain separate lets Avalanche’s network logic run without getting mixed up with application logic.

Why Does It Matter for Avalanche?

The importance of the P-Chain comes from the fact that Avalanche is not just a single chain, but a broader network made up of connected chains and L1s. If you want to create a new L1, add a validator, manage staking, and keep some core records at the chain level, the P-Chain becomes the center of these tasks. For this reason, the P-Chain is one of the layers carrying Avalanche’s growth logic.

The PlatformVM Architecture page also explains that the P-Chain plays a role on the signing side for warp messaging and supports atomic transfer operations. This shows that the P-Chain is not just a passive chain that stores records. It also has infrastructure-level importance in cross-chain interaction.

Conclusion

The P-Chain is the platform and coordination layer inside Avalanche. What makes it important is not that it is the chain users see the most, but that it manages who validates the network, how staking is processed, and how new blockchains are created. While the C-Chain carries the application face and the X-Chain carries the asset logic, the P-Chain takes on the network-level organization of this whole structure. For this reason, the P-Chain is not only one of Avalanche’s technical parts. It is one of the main layers that explains why Avalanche can build a modular, multi-chain, and L1-focused architecture.

Technical Terms Mentioned in the Text

PlatformVM

It is the virtual machine that runs the P-Chain and handles validator management, staking, and chain creation logic.

Validator

It is the actor that participates in securing and validating the network.

Avalanche L1

It is a sovereign blockchain network with its own validator and network-level rules.

Staking

It is the allocation of AVAX under specific rules to contribute to the security of the network.

Warp Messaging

It is the native communication mechanism that enables messaging between Avalanche L1s.

Further Reading

• Avalanche Academy - P-Chain Review

• Avalanche Explorer - P-Chain Validators

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

For most of their history, stablecoins have lived inside crypto. They move between exchanges, sit in DeFi protocols, provide collateral and give traders a way to hold dollars without leaving onchain markets.

Ethena has become one of the biggest examples of how far that model can scale. Since USDe launched in 2024, more than $30 billion has moved through its mint and redeem system, over $750 million in rewards have been distributed across the Ethena ecosystem, and USDe has found its way into more than 100 venues and protocols.

Ethena Pay takes that infrastructure somewhere different.

The new consumer app is built exclusively on Avalanche and packages USDe into an experience designed around three familiar actions: save, send and spend. Users can hold a self custodial dollar balance, move money globally, connect to fiat banking rails through a virtual IBAN and spend through a card, while much of the blockchain complexity stays underneath the interface.

That makes the launch interesting for reasons that go beyond another stablecoin payment product. Ethena is trying to move from serving primarily traders, institutions and existing onchain users toward building a direct consumer relationship around USDe. Its decision to build that experience on Avalanche also gives us a useful look at what blockchain adoption may look like when the technology becomes infrastructure rather than the product people think about.

From digital dollar to consumer product

USDe already had distribution before Ethena Pay.

It is integrated across more than 100 venues and protocols, giving users access through exchanges, DeFi applications and other financial platforms. That helped Ethena scale quickly, but it also meant the consumer relationship largely belonged to somebody else. The exchange controlled the interface. The lending protocol controlled how USDe was presented. Ethena provided the asset underneath.

Ethena Pay changes that relationship.

Inside the app, incoming holdings are converted into USDe and the same underlying asset can support balances, transfers and spending. Users can send money to other Ethena Pay users at no cost, withdraw to external wallets or bank accounts, access a virtual IBAN and use a payment card from the same interface. Ethena Pay also offers daily rewards on eligible balances and cashback on qualifying card purchases, with the exact rates and limits varying by user tier.

More importantly, Ethena now owns the distribution layer.

That matters because consumer money behaves differently from capital moving around DeFi in search of opportunities. Salaries arrive regularly. People keep balances available for bills and purchases. Payment accounts become part of everyday routines. If Ethena can move even part of USDe demand in that direction, it could create a different type of user base around the asset.

Guy Young, founder of Ethena, described the opportunity during a recent Layer One conversation in terms of the much larger market around saving and moving money. His point was straightforward: financial activity extends far beyond trading, and products built around savings, payments and credit can reach people who may have little interest in becoming active crypto users.

That brings us to the infrastructure underneath Ethena Pay.

Why Avalanche?

Ethena Pay is using Avalanche as the exclusive settlement layer for its product suite.

For a consumer financial application, the blockchain has to disappear into the experience. Transfers need to settle quickly. Costs need to remain low enough for frequent transactions. The infrastructure also has to support a product that could eventually serve users across many markets without forcing them to understand wallets, bridges or network mechanics.

Ethena says Avalanche provides the fast finality, low costs and flexible infrastructure required for money movement, payments and settlement across Ethena Pay. The product currently runs on Avalanche C-Chain, giving Ethena access to an established EVM environment while keeping open the possibility of more dedicated infrastructure if its requirements change as the product scales.

The choice is particularly interesting because Ethena could have pursued its own blockchain.

During the Layer One conversation, Young discussed why that was unnecessary for what Ethena is trying to accomplish. Building another chain would introduce an additional technical environment when the company’s priority is getting its financial products in front of users. Avalanche gives Ethena somewhere to deploy today, with C-Chain providing shared infrastructure and Avalanche’s broader architecture leaving room for an application specific L1 later if the product eventually requires dedicated blockspace or greater customization.

That approach keeps the focus on the application.

Ethena does not need consumers to care which chain processes a payment. It needs the payment to work.

Invisible adoption

John Nahas described Avalanche’s role in Ethena Pay with a simple phrase during the same conversation: “invisible adoption at scale.”

That may be the most important idea behind the entire launch.

A large part of crypto adoption has historically required users to become crypto users first. They learn about networks, wallets, gas, bridges, seed phrases and token standards before reaching the financial service they actually wanted.

Ethena Pay is approaching the experience from the opposite direction. A person can sign in using familiar account methods, secure access with passkeys and biometrics, hold a dollar balance, transfer money and spend from an app that looks much closer to modern fintech than a typical crypto wallet. The wallet underneath remains self custodial, while the technical complexity is pushed away from the main experience.

Avalanche benefits from that model precisely because the network does not have to become the consumer brand.

If millions of payments, transfers and financial interactions eventually happen through applications where users rarely think about the blockchain processing them, adoption starts looking less like convincing people to use crypto and more like businesses choosing blockchain infrastructure because it makes their products better.

That is a very different path to scale.

Where stablecoins go from here

Ethena Pay launched across 48 supported countries, with additional markets planned as regulatory and product requirements are completed. Its current availability already stretches across Latin America, the Caribbean, Africa, Asia, the Middle East and Oceania.

The geographic reach matters, but the larger experiment is what happens inside the product.

Stablecoins have already proven that digital dollars can move globally on open networks. Ethena Pay is testing whether those same rails can sit underneath the financial activities people perform every day.

That could eventually go beyond payments.

Ethena has already discussed connecting more DeFi functionality to the app while keeping the complexity away from consumers. Its launch materials describe plans for one click access to strategies built using existing USDe integrations, while the Layer One conversation touched on a broader embedded finance opportunity where onchain liquidity, yield and tokenized financial products can become components inside consumer applications.

This is where Avalanche’s growing financial ecosystem becomes relevant beyond transaction performance alone. An application like Ethena Pay can potentially sit above stablecoins, DeFi liquidity and tokenized assets, turning infrastructure that currently serves mostly onchain participants into financial products built for a much wider audience.

The user does not need to interact with each layer separately. The application can do that work underneath.

The bigger picture

Ethena Pay is still early. Availability remains limited by jurisdiction, several planned features are still rolling out, and its consumer ambitions will ultimately be judged by whether people actually choose to use the product at scale. Ethena Pay itself is also clear that it is a non custodial money app rather than a bank, with fiat services provided through third party financial partners.

But the model is worth paying attention to.

Ethena spent its first phase proving that USDe could find significant demand across crypto markets. With Ethena Pay, it is trying to turn that digital dollar infrastructure into something people can use as part of everyday financial life.

Avalanche’s role is equally revealing. It was chosen to operate underneath that experience as the exclusive settlement layer, processing the activity while much of the blockchain itself stays out of sight.

If this model works, the next wave of onchain users may never think of themselves as onchain users at all.

They may simply open an app, save money, send it somewhere and pay for something.

Avalanche will be working underneath.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

Moving money internationally is still slow, expensive, and stuck on banking hours that haven’t changed in decades. Stablecoins have been pitched as the fix for years. The missing piece was always infrastructure you could actually build on.

That infrastructure now exists on Avalanche. In June 2025, Avalanche launched the Avalanche Payments Collective (APC), a coalition of 28 organizations spanning stablecoin issuers, settlement networks, asset managers, fintechs, and payment processors. Together they support payment flows across more than 150 countries, 96 currencies, and roughly 22 billion payout endpoints.

That’s the headline, but this guide is about the part that matters if you’re actually building: what to build, which pieces of the APC stack solve which problem, and how to get a working stablecoin payment flow shipped. Whether you’re writing the contracts, running the checkout, or managing the treasury, this is for you.

Choosing Your Stablecoin

The stablecoin you pick should depend on the problem you’re solving, not brand familiarity:

• Default to USDC when you need liquidity, mature developer tooling, and broad merchant acceptance. Circle’s native issuance and CCTP support make it the path of least resistance for most integrations.

• Reach for FRNT (Wyoming Frontier Stable Token) when your flow needs to move on weekends or holidays. It’s the first fully reserved stablecoin issued directly by a US state government, so it doesn’t pause when banks do, and it already integrates with card-spending tools like Rain.

• Use won-pegged tokens through NHN KCP if you’re building for Korean market corridors specifically.

• Agora, Paxos, and Ethena round out the APC’s stablecoin bench for more specialized liquidity or yield needs.

Here’s why this matters on Avalanche specifically: sub-second finality with no reorg risk, fees that stay predictable under load, and custom L1 architecture for teams that need an isolated, compliant environment. That combination is a big reason B2B stablecoin payment volume grew more than 700% year-over-year in 2025, with cross-border settlement driving most of that growth.

Building and Scaling Stablecoin Payments

Getting from idea to production fast

Start on the EVM-compatible C-Chain with ethers.js or viem for prototyping. Once you’re ready for a compliance-sensitive or enterprise build, spin up a custom L1 via AvaCloud or the Avalanche CLI. Test everything on Fuji testnet first, USDC and FRNT faucets are available there. Circle, Request Finance, and other APC members are already plugged into the Avalanche Builder Hub, which cuts integration time significantly, and there are builder incentives worth exploring early through APC members directly.

Here’s what that unlocks: streaming payments and escrow contracts, atomic swaps across multiple stablecoins, agentic payment flows where AI agents transact autonomously, and cross-chain flows via Interchain Messaging (ICM).

Making crypto invisible at checkout

Merchants don’t want their customers thinking about blockchains. They just want instant settlement and low fees with familiar UX. XKOVA/Wyopay handles FRNT-based checkout. Rain connects stablecoin card spending to Visa’s global network. Request Finance covers invoicing and accounts payable with direct integrations into QuickBooks, NetSuite, and Xero. NHN KCP bridges traditional rails to stablecoin settlement.

The proof this works in practice: in an NHN KCP pilot, employees paid for cafeteria purchases by scanning a QR code, with smart contracts completing authorization in under two seconds. That’s UX that doesn’t feel like crypto at all.

Getting there is mostly a matter of sequencing: pick a processor that supports USDC or FRNT, add wallet connect or QR at checkout, automate reconciliation for accounting, and layer in onchain yield for idle treasury balances once the basics are live.

Settling cross-border without pre-funding every country

This is the problem that’s historically forced fintechs to lock up capital in local accounts everywhere they operate. Axiym has processed more than $1.4 billion in volume on Avalanche for platforms that collectively move over $25 billion annually across 150+ countries, without needing pre-funded accounts, since capital is accessed on demand instead.

Running global payroll with compliance built in

Rise handles payroll across 190 countries using stablecoins, with automated compliance rather than manual per-country handling.

Putting idle treasury to work

Grove Finance and OpenTrade turn reserves that would otherwise sit flat into onchain yield and credit infrastructure.

Settling at institutional scale

Tassat’s Lynq network connects 30+ institutional participants, including Fireblocks, Galaxy, and Wintermute, settling in seconds with more than $2.5 trillion in transaction history behind it. For fintechs that need a branded, regulated environment rather than shared infrastructure, AvaCloud makes it possible to launch a dedicated Avalanche L1 without building core infra from scratch.

APC Planning Checklist

• UX: Aim to hide the chain from the end user entirely. APC partners cover most of the checkout flow: XKOVA or Wyopay for FRNT-based checkout, Rain for Visa card spending, Request Finance for invoicing and accounting integrations, and NHN KCP for sub-2-second QR settlement. Evaluate these against your specific checkout requirements before committing.

• Regulation: Where possible, work with providers already operating under existing oversight rather than building compliance infrastructure from scratch. Anchorage Digital (custody), Paxos (issuance), and the Wyoming Stable Token Commission (FRNT) are examples within the APC bench worth evaluating.

• Liquidity: Build a router that can select the right stablecoin per transaction based on corridor, cost, and availability. Consider USDC via Circle CCTP for general liquidity, FRNT for 24/7 settlement needs, NHN KCP’s won-pegged tokens for Korean corridors, and Agora, Paxos, or Ethena for more specialized use cases.

• Security and Treasury: Deploy only audited contracts, regardless of provider. For custody, options include Anchorage Digital and Tassat’s Lynq network. For idle treasury balances, Grove Finance and OpenTrade are worth evaluating for yield generation.

Get Started

• Visit avax.network/payments to explore the APC ecosystem.

• Set up a Fuji testnet environment and deploy a simple payment flow this week.

• Identify which APC member matches your specific problem. There’s a specialist for nearly every layer of the stack.

• Reach out directly for pilots. The collective is still onboarding partners.

The APC’s value is in the specialization: issuance, checkout, custody, and treasury yield are each handled by a provider that’s already built for it. Builders get to spend their time on the payment product itself, not on re-solving problems the collective has already solved.

Dive into the Avalanche ecosystem today! Download the Core Wallet and unlock a world of seamless DeFi, NFTs, and more.

Download Core Wallet

For someone who hears about Avalanche for the first time, the C-Chain often appears to be the entire network. The reason is simple, this is usually the layer where users connect their wallets, send tokens, use applications, and interact with smart contracts. But Avalanche runs on more than one chain. According to the official Primary Network documentation of Avalanche, the network consists of three main chains, P-Chain, C-Chain and X-Chain, and the C-Chain is the smart contract layer among them.

The same topic is described more clearly in the Avalanche support documentation. The C-Chain is the Contract Chain designed to run smart contracts compatible with the Ethereum Virtual Machine (EVM). In practice, almost everything a user does with an Avalanche application runs through this chain. Contracts written in Solidity are deployed here, and a significant part of users’ DeFi, NFT, gaming and token transactions takes place on the C-Chain.

What is the C-Chain Used For?

The focus of the C-Chain is to run smart contracts and user-oriented blockchain applications. For this reason, the most visible part of the application logic on Avalanche is here. Applications where transaction ordering is important, such as DEXs, lending protocols, stablecoin flows, NFT minting processes, and in-game contracts, naturally operate on the C-Chain.

This point matters because the official explanation describing the Snowman consensus specifically emphasizes that this structure is optimized for blockchains, with high throughput and a totally ordered model. When “transaction ordering” is critical for smart contracts, such a structure is not a random choice but a direct functional requirement.

The C-Chain is not used only for traditional dApps. For example, in the Circle CCTP integration, native USDC can be transferred between Avalanche and other networks. This shows that the C-Chain is not just an environment where contracts are deployed, but also a key component of payment and liquidity flows.

Institutional and Financial Use Cases

These capabilities also make the C-Chain relevant to institutional and financial applications. Potential use cases include stablecoin settlement, tokenized assets, treasury movements, payment infrastructure, and applications that need access to shared liquidity.

The important distinction is that the C-Chain is a shared and open application environment, while institutions that require their own validator set, access rules, or private operating model may choose to build a separate Avalanche L1. In this structure, the C-Chain can still serve as a source of liquidity, application infrastructure, or interoperability for Avalanche L1s.

This means that the C-Chain’s institutional relevance is not limited to institutions deploying their own chains. It can also function as a shared EVM environment connected to stablecoin, liquidity, custody, and application integrations.

Who Uses the C-Chain?

The C-Chain is mainly used by three groups. The first is developers coming from the Ethereum and EVM ecosystem. Because they can more easily transfer the contract logic and toolsets they are familiar with to Avalanche.

The second is end users. In the official explanation describing the differences between the X, P, and C-Chain, it is clearly stated that the C-Chain is supported by most EVM-compatible wallets and is the chain most frequently interacted with in dApps within the Avalanche ecosystem. For this reason, most moments when users say “I use Avalanche” actually take place on the C-Chain in practice.

The third group is infrastructure and liquidity layers. Wallets, bridges, stablecoin services, data providers, and application middlewares use the C-Chain as a common operating ground. This turns the C-Chain from being just a developer layer into the de facto application hub within Avalanche.

How is the C-Chain Different from the Other Two Chains?

The best way to understand the difference here is to separate the three chains by their roles.

• The C-Chain is the execution layer where smart contracts and application logic run.

• As seen in the explanation of the X-Chain, the X-Chain is designed for asset creation, asset exchange, and cross-chain asset transfers.

• As described in the PlatformVM architecture documentation, the P-Chain manages validator records, staking, Avalanche L1 creation, and chain creation processes.

So the three chains split the work between them. The X-Chain carries the asset logic, and the P-Chain carries the network coordination and validator logic. The C-Chain is the layer where contracts live.

Why was the C-Chain Designed as a Separate Chain?

The main reason is that Avalanche was designed from the beginning with an architecture that separates responsibilities instead of compressing everything into a single chain. Smart contract execution, asset transfers, and validator management are not the same type of workload. Each chain runs its own virtual machine for this reason. The AvalancheGo architecture documentation lists PlatformVM on the P-Chain, Coreth on the C-Chain, and the AVM on the X-Chain.

This is why keeping the C-Chain separate matters. The EVM compatibility, transaction ordering, gas model, and stateful execution required by smart contracts are not considered on the same basis as asset transfers or staking operations. The Coreth Architecture page also explains that the C-Chain can communicate with the X and P-Chain through atomic import and export mechanisms. So the chains are separate, but not disconnected.

In other words, instead of saying “one chain should do everything,” Avalanche adopts the approach that “each task should operate in its own domain.” The C-Chain being designed separately is exactly the result of this choice.

Why is it Important for Avalanche?

The importance of the C-Chain for Avalanche is not only that many applications run on it. On the C-Chain Explorer page, this chain is directly defined as the liquidity hub of the Avalanche ecosystem. This expression matters because most of the user flow, liquidity, and application interaction within Avalanche is concentrated here.

Moreover, the Tesseract integration page explains that Avalanche L1s can access the deep liquidity of the C-Chain without having to build their own DEXs. This makes the role of the C-Chain clearer. So the C-Chain carries an economic role alongside the application one. As new L1s emerge, it continues to be the shared liquidity and application ground they frequently interact with.

For this reason, understanding the C-Chain is one of the shortest ways to understand Avalanche. Because Avalanche’s “application layer,” “liquidity hub,” and “EVM entry point” largely converge here.

Conclusion

The C-Chain is the smart contract and application layer within Avalanche. What makes it important is not only that it is EVM-compatible, but that it has become the main area where application execution, liquidity, and user interaction are concentrated within the Avalanche architecture. While the X-Chain carries the asset logic and the P-Chain carries network coordination, the C-Chain forms the living application surface of this ecosystem. For this reason, the C-Chain is not just one of the technical components of Avalanche, but one of the most visible and most critical layers of the ecosystem in practice.

Technical Terms Mentioned in the Text

Coreth

It is the EVM implementation used by Avalanche to run the C-Chain.

Snowman

It is Avalanche’s consensus approach optimized for blockchains, linear and totally ordered.

Atomic Transfer

It is the mechanism that enables assets to be transferred between different chains within Avalanche under specific rules.

Liquidity Hub

It is the central layer where liquidity, user flow, and economic activity are concentrated.

Further Reading

• Avalanche – Avalanche L1s

• Avalanche – Features & Benefits of Avalanche L1s

Looking to join the global community live? Registration is now open for Avalanche Summit NYC. Secure your pass today for 2 days of exclusive keynotes and networking.

Get Tickets Now

Team1 Builder Grants fund builders who are shipping on Avalanche. The program is live and open to anyone, anywhere. The committee has formed, is meeting, and has already chosen a first Accelerator Grant recipient.

The First Accelerator Grant: YourGrails

The first pick went to YourGrails, a platform built around graded trading cards that live onchain.

You buy a sealed pack with USDC and rip it open. Inside is a digital representation of a physical card, scored by an independent grader for condition and authenticity. From there, it’s yours to do what you want with it. Keep it. List it for a 90% buyback. Stake it in a head-to-head battle where the winner takes the pot. Even ship the physical card to your door. The cards themselves sit graded, vaulted, and insured, so you’re holding something real the whole time.

It’s a working product, currently in beta, built by a team that shows up every day for the community. The grant amount was set at $30,000 and approved at the committee’s first meeting. A solid way to open the account.

Team1’s Latest Mini-Grant: Empowr

The newest Mini Grant, $5,000, went to Empowr by @TippiklLabs, a proposed onchain bounty platform aimed at creating earning opportunities for the community. The funding is released in two stages: half up front, half once the project ships and five ecosystem projects have posted a bounty, with Team1 lining up as the first user. Kieron is a Team1 UK member who’s shown up consistently for the ecosystem, and that steady presence is exactly the kind of commitment these grants are meant to back.

How the program works

Two tracks make up Team1 Builder Grants, each designed to catch builders at different stages. The mini-grants came first, earlier this year. Recipients shipped, got noticed, and several went on to win builder competitions. Accelerator Grants are the next stop for builders who’ve proven themselves and are ready to scale.

Accelerator Grants reach $30,000 with no application to fill out. The committee proposes projects and votes on them, and a project with real momentum can be fast-tracked straight through without starting at a mini-grant.

Mini Grants cap at $10,000 and stay open to everyone. This is the entry point, the place to start when you’re after your first bit of backing and ready to show what you can do. Builders must fill out an application.

Both tracks are global and ongoing. Anyone can apply, and we want you to. The grants go to builders committed to Avalanche for the long haul, the ones growing communities that last and lifting the whole ecosystem as they go. That commitment is what the committee puts significant weighting on.

Prior Foundation funding counts as a factor, but it won’t close the door on you.

The Committee is Set

The Accelerator Grants committee has been announced: ten people spanning Team1, the community, Ava Labs, and the Avalanche Foundation, weighted most heavily toward the community and Team1. They meet once a month; any member can submit a project, and a majority vote approves it.

They’re already at it. The first grant went from proposal to approved on the committee’s opening call, and they got YourGrails over the line in the program’s first week.

Get Involved

Are you building something people are starting to use? This is your opening. Mini-grant applications are live right now, and that’s the front door for most early projects.

Apply for a mini-grant here: https://www.team1.network/grants

Know a builder who deserves a look? Share this, tag them, and tell us what they’ve shipped. We’re watching.

Team1 Mini Grants application does not guarantee a grant. A high volume of applications and participation does not guarantee funding.

Looking to join the global community live? Registration is now open for Avalanche Summit NYC. Secure your pass today for 2 days of exclusive keynotes and networking.

Get Tickets Now

On August 27, Charles Schwab announced plans to add Solana, Avalanche, and Chainlink alongside Bitcoin and Ethereum.

For AVAX, the move puts the token in front of a huge audience of traditional investors. As of July 31, Schwab had $13.04 trillion in client assets across 39.9 million active accounts. Soon, eligible clients will be able to buy and sell AVAX alongside their stocks, ETFs, and other investments.

An audience of that size is significant on its own. But Schwab’s selection of Avalanche is also notable: the brokerage chose AVAX as part of its first expansion beyond BTC and ETH.

So why Avalanche?

Avalanche Was Already on Wall Street’s Radar

Schwab hasn’t published a detailed breakdown of its selection criteria, saying only that the additions match client demand for established assets. Avalanche’s history with major financial institutions provides some useful context.

In November 2023, J.P. Morgan’s Onyx division and Apollo Global Management ran a Project Guardian proof of concept using a permissioned Avalanche Evergreen subnet, the predecessor to today’s Avalanche L1 architecture. WisdomTree provided tokenized funds for the trial, which tested how smart contracts could automate portfolio management across traditional and alternative assets. A few months later, in February 2024, Citi ran another trial on Avalanche Spruce with Wellington Management and WisdomTree to test tokenized private funds, automated distribution rules, and compliance.

These were early pilots rather than full-scale products, and they happened years ago. Wall Street didn’t migrate to Avalanche overnight. What the trials did show, however, was that Avalanche was already attracting serious attention from major financial institutions.

Why Institutions Want Their Own L1

One of Avalanche’s main advantages for financial institutions is its customizable L1 architecture.

Financial firms may not want to run regulated assets on an open, shared public chain where fees can change and access can’t easily be restricted. An Avalanche L1 lets an institution set its own validator rules, restrict network access, and customize gas mechanics while remaining connected to the broader ecosystem.

Project Guardian showed how this could work in practice. The participants tested tokenized funds on a permissioned Avalanche network while maintaining control over who could take part. The project also used its own gas setup, showing that an Avalanche L1 doesn’t have to work exactly like the public C-Chain.

Ethereum L2s and other networks are competing for the same institutional market. Avalanche has been building around customizable L1s for years, though, and the J.P. Morgan and Citi trials show that major financial firms have already tested the model. That history doesn’t tell us why Schwab chose AVAX, but it helps explain why Avalanche is already familiar to major financial institutions.

Schwab Makes AVAX Easier to Buy

Avalanche’s growth is happening on two fronts: institutions are building on the network, while investors are gaining more ways to buy AVAX. Schwab directly addresses the second.

A Schwab client won’t need to open an account with a crypto exchange or manage self-custody wallets just to buy AVAX. The token will be available through Schwab’s website, mobile app, and thinkorswim platform, alongside the stocks and ETFs clients already use. Schwab is charging 75 basis points per crypto trade.

That doesn’t guarantee an immediate wave of buying, but it removes a barrier for a huge group of investors. Looking further ahead, Schwab also plans to offer digital asset trading, transfers, and custody to financial advisors by mid-2027. Schwab Advisor Services works with more than 16,000 Registered Investment Advisors (RIAs), potentially giving digital assets another path into professionally managed portfolios.

There’s also a difference between this and ETF exposure. Schwab customers will be able to buy the actual AVAX token through a brokerage they already use, rather than getting exposure through a fund that holds the asset.

Why the Schwab Move Matters

Short-term price reactions aren’t the key takeaway here. AVAX rose after Schwab’s announcement, but a few days of price movement says very little about the long-term impact of a platform listing.

What matters is that Schwab brings together two parts of the Avalanche story that have largely developed separately.

On one side, financial institutions are testing Avalanche technology for tokenized funds and dedicated networks. On the other, traditional investors now have a direct way to buy AVAX through a brokerage account they already use.

What Happens Next

The Schwab announcement is only the start. AVAX has yet to launch on the platform, so the more useful numbers will come once clients can actually trade it. Trading activity will show whether Schwab’s large customer base translates into meaningful interest in AVAX, while new institutional projects will show whether Avalanche’s earlier pilots are turning into live products.

For now, Schwab has given AVAX something it didn’t have before: direct access to a huge traditional investor base. At the same time, Avalanche continues to build the financial infrastructure that has put it on the radar of major institutions.

Looking to join the global community live? Registration is now open for Avalanche Summit NYC. Secure your pass today for 2 days of exclusive keynotes and networking.

Get Tickets Now