Track market-moving stories before they get noisy

Not financial or tax advice. PANews content is strictly educational and informational and is not investment advice, financial advice, tax advice, legal advice, or a solicitation to buy or sell any digital asset, security, or financial product. Do your own research and consult qualified advisers.

Disclosure. PANews may publish sponsored content, partner content, advertisements, affiliate links, event promotions, and market commentary involving Web3 projects, service providers, or financial products. PANews personnel, contributors, or affiliates may hold digital assets or other interests related to covered topics. See our Terms of Service.

This site is protected by reCAPTCHA.

Project World is continuously optimizing its front-end UI, with user deposits secure and transactions functioning normally.

World, a full on-chain prediction market in the Solana ecosystem, announced in a post that its website is currently experiencing high traffic, with over 1 million users accessing the platform. User deposits remain secure, platform transactions are executing normally, and backend systems are operating as expected. The team is continuing to optimize the frontend user interface, and the overall operation of the platform is in good condition.

18 minutes ago

Iranian officials announced that Iran will escalate its crackdown operations in response to U.S. attacks.

Iranian officials have stated that Iran will escalate its retaliatory strikes in response to the U.S. attack. (Jinshi)

18 minutes ago

US Treasuries extended their decline after the repurchase announcement, with the market viewing the $6 billion cap as insufficient.

The U.S. Treasury Department said it will purchase between $40 billion and $60 billion in long-term government debt in the first operation of its expanded repurchase program, demonstrating Secretary Bessent’s resolve to curb the recent rise in borrowing costs. U.S. Treasuries extended their earlier decline following the announcement, indicating the program’s size fell short of some investors’ expectations. The success of the expanded purchase program remains to be seen. After the program was first announced last month, yields fell before rebounding later. The benchmark 10-year yield hit its highest level since 2023 last week. Economist Guha, a former staffer at the New York Fed, noted: “The challenge always lies in whether the impact of these interventions can persist without larger fundamental changes.” Moreover, the maximum size of the repurchase operation does not mean the Treasury will necessarily purchase that amount of Treasuries. However, in repurchases targeting long-term nominal debt, the department typically buys the full amount; since the program was relaunched in 2024, it has only failed to do so in two of 52 such operations. (Jinshi)

18 minutes ago

Eric Trump mocks Joe Biden’s son Hunter Biden over the botched launch of the LAPTOP token, saying he should go back to painting.

US President Donald Trump’s second son Eric Trump reposted a post about the meme coin LAPTOP’s sharp price crash after its launch, commenting: “Hunter should go back to painting.” His remarks target Hunter Biden, son of former US President Joe Biden, who launched the meme coin LAPTOP. The reposted post notes that LAPTOP plummeted 98% within minutes of going live, adding that the project had originally planned to allocate a portion of its tokens to users who incurred losses from TRUMP-related transactions.

18 minutes ago

Solana ecosystem prediction market World officially launches, opening to over 1 million waitlist users.

Solana ecosystem full on-chain prediction market World announced that its independent platform World.xyz has officially launched, with over 1 million users on its waitlist. The platform offers thousands of markets spanning sports, cryptocurrency, politics, finance, economics, and culture, covering all NFL regular seasons, 7 soccer leagues, F1 races, the 2026 U.S. midterm elections, and Federal Reserve interest rate decisions. Since integrating Phantom in July, World has launched more than 150,000 markets. Each market on the platform consists of "Yes" and "No" contracts, priced between $0 and $1, and settled using Phantom’s U.S. dollar stablecoin CASH. Technically, World leverages Chainlink Data Streams and Chainlink Runtime Environment to provide market data and automated settlements, reducing manual intervention and dispute resolution wait times. Prediction markets for stock price movements, gold, silver, oil, natural gas, computing power, and weather will be rolled out sequentially.

18 minutes ago

Bubblemaps: 80% of LAPTOP traders are losing money, with two traders suffering losses ranging from $100,000 to $1 million.

Bubblemaps posted that profit and loss data for LAPTOP traders shows roughly 80% of participants are in the red, describing the token’s market performance as a "bloodbath". Specifically, two traders lost between $100,000 and $1 million, 100 lost over $10,000, 700 lost more than $1,000, and around 11,000 traders posted small losses. Bubblemaps did not further disclose the statistics’ time frame or the scope of the wallet sample used.

18 minutes ago

Network Hits Monthly Peak on a Weekend@AlgoFoundation recorded its highest daily transaction volume of the month on Sunday, with the network processing over 876,000 transactions in a single day. The figure marks a new milestone for the period and is notable given that weekend sessions typically bring reduced activity across digital asset markets.

According to verified data from Chainspect, Algorand maintained a consistent throughput of more than 10 transactions per second (TPS) throughout the day. Holding that rate over a full weekend session runs counter to the liquidity contractions that tend to suppress on-chain activity across the broader market during those periods.

Context: A Network Built for High ThroughputThe result fits a broader pattern of growing network utilisation.

On the infrastructure side, the network has also been expanding its validator base.

Sunday's reading of 10-plus TPS reflects real demand rather than benchmark conditions, making it a more meaningful signal of network health.

Sources:
Chainspect: Algorand TPS and Network Stats
Algorand Foundation: June 2026 Algo Insights Report

The $7 Billion Race to Save Crypto From Quantum Computers

Algorand Hits Weekly Transaction PeakThe Algorand network recorded a localized surge in activity on August 31, processing over 584,000 transactions in a single 24-hour window, according to @AlgoFoundation. The figure represents the busiest day on the network within the prior seven-day period, pointing to a meaningful short-term uptick in on-chain demand for the $ALGO-powered layer-1 blockchain.

While a single-day reading does not on its own signal a structural shift, it sits against a backdrop of steadily rising cumulative activity. Total transactions on the network rose to 3.64 billion as of June 2026, with node participation increasing by nearly 3% month-over-month. The network has added users and validators at a consistent pace throughout the year, and daily spikes of this kind tend to reflect bursts of activity tied to specific applications or ecosystem events.

Broader Activity Trends Support the MomentumThe single-day figure is consistent with a wider pattern of growing engagement on Algorand in 2026. USDC transacted volume on the network rose by more than 72% month-over-month to approximately $751 million in June, the highest monthly level recorded in the first half of 2026. Algorand also reported 1.8 million new smart contract deployments in a recent quarter, a 25.7% increase.

Builder activity has been a consistent contributor to on-chain volume. Builder activity saw a sharp recovery in May, with contracts deployed rising 47% and new asset creation more than tripling from April. Algorand's real-world asset ecosystem processed more than 23.2 million tokenized asset transactions during the second quarter, underscoring that the network's growth is tied to actual usage rather than speculation.

On the regulatory front, the network has also gained a clearer footing in the United States. In March and April 2026, both the Securities and Exchange Commission and the Commodity Futures Trading Commission jointly categorized $ALGO as a digital commodity. This official recognition removed significant compliance hurdles that had previously kept many large investors on the sidelines.

The August 31 transaction spike adds another data point to what has been a year of building momentum for the Algorand network, even as token price has lagged behind on-chain fundamentals.

Sources:
Algorand Foundation: June 2026 Algo Insights Report
Crypto Briefing: Algorand Sees 1.8M New Contract Deployments
Cryptonomist: Algorand Price Rally and Institutional Milestone

Table of contents

AI agents are increasingly asked to make payments, sign code and manage digital operations, yet the channels they use offer no cryptographic identity and force users to hand over their private keys. The Algorand Foundation is trying to close that gap with AC2, an open protocol announced Aug. 25, according to a release from the foundation.

How AC2 works AC2, short for Agentic Communication and Control Protocol, establishes a direct, end-to-end encrypted WebRTC connection between a user’s wallet and an AI agent. When an agent needs to perform a signing operation, such as a payment, a git commit or an API authorization, it sends a request that the user reviews and approves in their own wallet, and the signature is delegated back. The private key never leaves the user’s control.

The protocol is designed to support a broad range of agentic workflows: a coding agent can draft code and ask the developer to approve the final signature, an assistant can route payment details to a wallet for approval, and a shopping agent can construct a mandate defining what it is authorized to buy and at what price.

The design choices The specification uses DIDComm v2.0 message formats, passkey authentication through Liquid Auth built on FIDO2 and WebAuthn, and supports real-time voice and text streaming as well as signing delegation. It requires no central message relay and no blockchain to operate, and the reference implementation is available on GitHub alongside an open-source wallet proof-of-concept and an OpenClaw plugin for testing.

“The answer is you don’t hand them the keys, you approve each use of them,” said Marc Vanlerberghe, the foundation’s chief strategy and marketing officer, describing how AC2 grants AI agents authority without the ability to act against a user’s interests.

Where it fits The launch builds on Algorand’s recent security-focused upgrades and lands as how exchanges are opening trading to AI agents becomes a live question across the industry. The foundation cautioned that the release contains forward-looking statements and that the protocol remains subject to change as it seeks design partners. The protocol is blockchain-agnostic, so wallets and agents across networks could adopt it rather than being tied to Algorand.

AUTHOR

Entrepreneur and freelance writer based in Nakuru, Kenya. I cover cryptocurrency, the Blockchain technology, and financial topics. It’s my joy to transform the simplest phrases in a way they reach a reader’s heart to help them discover how crypto is disrupting the world as we have known it. I believe in transforming the world, one word at a time.

Not financial or tax advice. PANews content is strictly educational and informational and is not investment advice, financial advice, tax advice, legal advice, or a solicitation to buy or sell any digital asset, security, or financial product. Do your own research and consult qualified advisers.

Disclosure. PANews may publish sponsored content, partner content, advertisements, affiliate links, event promotions, and market commentary involving Web3 projects, service providers, or financial products. PANews personnel, contributors, or affiliates may hold digital assets or other interests related to covered topics. See our Terms of Service.

This site is protected by reCAPTCHA.

This is Part 3 in a series of posts looking at the wide variety of new capabilities for developers in the Algorand 5.0 upgrade. If you missed "Part 1: Salt - cryptographic capabilities," or "Part 2: Fat - Fatter apps and transactions," you can read them now.

Part 3: Acid - Safety with more flexibility Software engineers who have studied database design will be familiar with the ACID properties of a database: Atomicity, Consistency, Isolation, and Durability. These four properties together provide a guarantee that database transactions are processed reliably, making applications more secure, highly resilient, and easy to reason about.

Algorand has historically been designed to be a particularly safe and elegant distributed database at two different levels. The base level is the global ledger itself, and on top of that is the state maintained by each stateful application.

It is in this second, application-level that the next version of the AVM, v13, relaxes a long-standing isolation measure that only the app that owns a box can read from and write to it. Developers will be able to build apps more flexibly now that boxes can optionally be opened up to direct access from other applications.

New capabilities This upgrade introduces two new application parameters: FamilyBoxAccess and ForeignBoxReads. The first is a parameter that enables an app’s boxes to be read and written by other applications in the same “family,” as defined by having the same creator. The second enables an app’s boxes to be read, and only read, by any other application.

These parameters can be set by calling a new opcode app_params_set that acts on the application executing this opcode. This is a new paradigm insofar as these are opcodes run by an application to modify itself, rather than being performed by a transaction.

This means two things:

The procedure for enabling family box access or foreign box reads involves two steps: first updating the code to include the relevant opcode and then subsequently running that code.

An application that has no way to update its code will not be able to use these operations on itself because it has no way to update its code in the first place to include these opcodes. Intentionally immutable apps can stay that way.

For apps that have enabled this access, a whole set of box access opcodes have been added to the AVM that take both an app ID and box key so that boxes in other applications can be reached. All of this is strictly optional, however, and patterns involving app data that is kept private from other on-chain apps are still possible.

With these new capabilities, applications that previously needed to provide getter and setter methods for other apps to access data in their boxes can forgo a lot of that code by opening up family or foreign box access instead. Combined with the fact that applications can be twice as large, this opens up a lot more bytecode headroom to design protocols that are split across fewer total apps and need less glue code to make them all work together.

One interesting tidbit about family and foreign box access is that these opcodes can be run at any point and it takes effect immediately, so it is now possible to enable and subsequently disable this access within the currently executing application call. This has the potential to unlock “flash” possibilities where this shared state access is enabled, used, and then disabled, all within the same transaction.

New protections The AVM was originally designed with safety in mind, and one deliberate decision was to prevent reentrancy, meaning that smart contract applications are not allowed to call themselves or be called more than once in a given transaction. A single-transaction app execution sequence like A→A is disallowed, as is a sequence like A→B→A.

Forbidding reentrancy eliminates the need for developer discipline around a class of bugs that can occur in program logic, a class of bugs that have at times been footguns for developers when writing EVM smart contracts, which do allow reentrancy. While the ability to do contract reentrancy can enable interesting callback patterns and other capabilities, there is a risk of a contract’s data being in a state that is unexpected or should be impossible because it is only partially done executing. This can lead to, and has contributed to, exploits in escrow contracts holding funds for protocols on other chains.

The AVM allowing apps in the same family to write the same boxes could create the potential for a similar class of bugs, but this risk is mitigated by two new restrictions for apps that have enabled FamilyBoxAccess:

The applications involved must be related in a “family” defined by a shared creator address. It seems safe to assume that multiple applications deployed by the same address have been designed in such a way that this access won’t be abused. That said, it is incumbent upon app developers to ensure family box state is handled properly in a set of applications that use it.

If an application outside the same-creator family sits between two writes to state owned by that family, the AVM will reject the current application call. Stay tuned for Part 4 in this series: “Heat: Cooking with simulate,” coming later this week. What do you want to build on Algorand 5.0? Join our Discord server to meet other developers building PQ solutions, fat apps, box families, and more.

Disclaimer: The content provided in this blog is for informational and educational purposes only. The information is provided by the Algorand Foundation and while we strive to keep it accurate and current, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the blog or the information contained in it for any purpose. Nothing in this blog is legal, financial, tax, or investment advice, nor an endorsement, guarantee, or investment recommendation. Technical descriptions are provided as of the date of publication and may change. Any statements about future plans, features, integrations, protocol or consensus upgrades, fees, or timelines are forward-looking and subject to change, including subject to community adoption, and are not commitments. You should conduct your own research and consult a qualified professional before acting on any information here; any reliance you place on it is strictly at your own risk. All third-party names and trademarks are the property of their respective owners, and their mention does not imply affiliation or endorsement.

This is Part 2 in a series of posts looking at the wide variety of new capabilities for developers in the Algorand 5.0 upgrade. If you missed "Part 1: Salt - cryptographic capabilities," read it now.

Part 2: Fat - Fatter apps and transactions This consensus protocol v42 allows many things to be much fatter: transactions, notes, application arguments, applications themselves, and logic signatures have all been given higher size limits that go far above what Algorand has supported in the seven years since genesis.

Fatter apps We’ve doubled the maximum size of applications. After hearing your feedback about bumping up against the ceiling on the size of application bytecode, we’ve raised that ceiling by two times, from 8 KB to 16 KB. This is implemented by providing four additional program pages beyond the previous limit of three. Now you can add up to seven additional pages for a total of eight 2 KB pages.

This new limit allows both new, bigger applications and existing ones to be updated to add additional pages. As long as the app is updatable, existing ones can be updated to add more pages for more code. If you have an application that was blocked by its app size, that blocker is now removed.

Additionally, when updating an app, developers can now, for the first time, expand an app’s global state schema, which had always been immutable prior to this upgrade.

In both cases, the app updater must take on a new app role, SizeSponsor, that bears the minimum balance requirement (MBR) for the app’s entire extra program pages and global state slots. This role is necessary because the creator account may not be able to cover the increased MBR, so the updater who makes the change to extra program pages or expanded global state must be assessed the whole MBR, if different from the creator. Box MBR is unaffected by this change.

Fatter args In addition to supporting larger application sizes, the protocol will now also allow up to 16 KB total of application arguments in calls, up from 2 KB. This upgrade will make it much easier to get large amounts of data into applications, particularly if you are trying to load data into big boxes. Notably, this limit also enables one application call’s arguments to hold an entire 16 KB program, equivalent to the new limit with all extra pages, if you have an application that implements a design pattern such as a factory or a self-updating application.

Fatter LogicSigs LogicSig programs were previously limited to 1,000 bytes per transaction, pooled across the group, with a grouped maximum of 16,000 bytes. Now the maximum size can be achieved with just one transaction. What was only achievable before by grouping 16 transactions, an approach that can break composability with other applications in the ecosystem that need group space for their own transactions, can be done in a single transaction on 5.0. This new capability means that anything you may have designed that was using extra transactions to achieve a large stateless program can now be rebuilt using a single, large transaction for a more elegant and composable design.

Fatter fees What will all of this cost, you may wonder? Firstly, know that anything that could be done on Algorand before protocol v42 can still be done at the same cost. Existing solutions don’t need to change anything for the transactions they craft because the fee changes provide a free allowance that covers all the capabilities that were previously included in a transaction. This consensus upgrade does not change the minimum fee cost of anything, so it is not a breaking change for transactions that were possible on previous versions.

However, now that expanded capabilities are possible, fees will be charged by a new, dynamic “usage” concept that tallies up protocol resource consumption for an entire transaction group. A group’s usage can be learned by simulating it, which will take into consideration all top-level outer transactions as well as all inner transactions generated by application calls. Because the transactions generated and their exact sizes may vary at runtime, we advise not to try to recreate fee accounting logic in your applications and instead rely on simulate to confirm actual fee costs. I’ll elaborate on this in Part 4 of the blog series.

Stay tuned for Part 3 in this series: “Acid: Safety with more flexibility,” coming later this week. What do you want to build on Algorand 5.0? Join our Discord server to meet other developers building PQ solutions, fat apps, box families, and more.

Disclaimer: The content provided in this blog is for informational and educational purposes only. The information is provided by the Algorand Foundation and while we strive to keep it accurate and current, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the blog or the information contained in it for any purpose. Nothing in this blog is legal, financial, tax, or investment advice, nor an endorsement, guarantee, or investment recommendation. Technical descriptions are provided as of the date of publication and may change. Any statements about future plans, features, integrations, protocol or consensus upgrades, fees, or timelines are forward-looking and subject to change, including subject to community adoption, and are not commitments. You should conduct your own research and consult a qualified professional before acting on any information here; any reliance you place on it is strictly at your own risk. All third-party names and trademarks are the property of their respective owners, and their mention does not imply affiliation or endorsement.

The Algorand protocol engineering team has been cooking up a feast lately, and the Algorand 5.0 upgrade brings a wide variety of new capabilities and raises many of the protocol’s long-standing limits. In this four-part series, we’ll explore some of the most important ones through an extended metaphor using the core components of cooking: salt, fat, acid, and heat. Rather than cooking tasty food, though, we’re enhancing the flavor of the applications that can be built on Algorand.

Part 1 of the series (Salt) is below; stay tuned for parts 2-4 in the coming days. Part 1: Salt - Cryptographic capabilities Post-Quantum Signatures The single biggest addition to Algorand in this 5.0 upgrade is a framework enabling native post-quantum (PQ) signature schemes for transactions, beginning with the addition of Falcon-1024.

While it has been possible since late 2025 to create LogicSig smart contract accounts that will only authorize transactions after verifying a Falcon signature, the way this was achieved required combining multiple transactions together, which impeded DeFi composability with protocols that require using several transaction slots in the atomic group for their own calls. Smart contract accounts are also not the typical approach preferred by most Algorand wallets.

A better approach is to add first-class support for transactions to carry post-quantum signatures, and that’s what we’ve added now:

pqsig: { sch: [2]byte, slt: uint8, pk: []byte, sig: []byte }

The new pqsig framework is a transaction signature envelope that allows arbitrary schemes to be added to the protocol in the future. Here we can indicate the scheme being used, and the first one we support is Falcon-1024, a lattice-based scheme that is suitable for long-lived accounts. In the future, support for additional schemes will be explored. Falcon-512 is already on Algorand’s roadmap as a variant of Falcon with smaller public key and signature sizes that can be suitable in situations where lightness is useful, and security requirements are somewhat less demanding.

Salt to taste Note that this signature object includes slt, an important salt value that is used to ensure that the Algorand address derived from a PQ public key does not correspond to a valid point on Curve Ed25519. If a PQ account address does not lie on the curve, then there is simply no corresponding Ed25519 private key that could ever be found by an attacker with a quantum computer. As a result, PQ accounts can only ever spend by signing with their PQ key.

Generally speaking, the Algorand technical community will consider the canonical salt to be the lowest value that results in an address that is off of Curve Ed25519. This will be the default approach used in our SDKs when handling accounts, in the algod REST API when submitting transactions, and in other tooling.

That said, the protocol itself will not enforce this canonical salting approach, and signatures will verify successfully even if a different salt has been used by a wallet to generate an account.

Astute readers will notice that the salt is only one byte, which provides 256 tries with roughly 50-50 odds each to find a point that isn’t on the Edwards curve. The probability of using all of those tries and failing to find a good address is extremely small, and if that should occur, a new PQ keypair should be generated.

Crypto-agile signing interfaces Alongside this protocol upgrade, we have introduced upgrades in our SDKs around handling and signing for Algorand accounts. This includes support for PQ signature schemes, support for hierarchical-deterministic (HD) accounts, support for integrating with key management systems (KMS), and more secure secret handling.

Throughout the libraries, you will find flexible interfaces for signing transactions that can be wired up to any signer, with the default approach being that this signing occurs somewhere secure rather than handling raw key material directly in the library.

The goal is to make it easier for developers to build secure, production-ready applications and avoid building infrastructure or even helper scripts that involve the use of secrets in cleartext that can fall victim to malware attacks against servers and developer machines.

These new interfaces also open the door to supporting more signature schemes in the future without requiring developers to update their SDK code to leverage new and different approaches to signing transactions.

Stay tuned for Part 2 in this series: “Fat: Fatter apps and transactions,” coming later this week. What do you want to build on Algorand 5.0? Join our Discord server to meet other developers building PQ solutions, fat apps, box families, and more.

Disclaimer: The content provided in this blog is for informational and educational purposes only. The information is provided by the Algorand Foundation and while we strive to keep it accurate and current, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the blog or the information contained in it for any purpose. Nothing in this blog is legal, financial, tax, or investment advice, nor an endorsement, guarantee, or investment recommendation. Technical descriptions are provided as of the date of publication and may change. Any statements about future plans, features, integrations, protocol or consensus upgrades, fees, or timelines are forward-looking and subject to change, including subject to community adoption, and are not commitments. You should conduct your own research and consult a qualified professional before acting on any information here; any reliance you place on it is strictly at your own risk. All third-party names and trademarks are the property of their respective owners, and their mention does not imply affiliation or endorsement.

Validator Count Places Algorand Among the Most Decentralized ChainsAlgorand (@AlgoFoundation) currently operates with 1,537 live validators securing the network, a figure that places $ALGO comfortably within the top tier of decentralized blockchains globally.

The growth represents a meaningful structural shift. That redistribution of stake away from the Foundation and toward independent participants is a key indicator of genuine decentralization, not just raw node counts.

Post-Quantum Upgrade Clears 90% Node SupportThe validator base is also playing a direct role in shaping the network's next major milestone.

The speed with which validators coordinated around v5.0.0 also underscores the practical value of a large, geographically distributed validator set: upgrades can be ratified quickly and without relying on a small group of insiders.

Together, the validator depth and the post-quantum upgrade push Algorand into rare territory among layer-1 blockchains, combining broad network participation with protocol-level security designed for a future where quantum computing poses a credible threat to standard cryptographic methods.

Sources
Blockonomi: Algorand v5.0.0 Clears 90% Support as Post-Quantum Upgrade Nears Mainnet
Algorand Forum: MainNet and TestNet Update Go-Algorand 5.0.0
Algorand Foundation: June 2026 Algo Insights Report

TLDR:

Algorand v5.0.0 reached 90% node support, clearing the upgrade for activation after its cooldown period.
Native Falcon-1024 accounts give Algorand protocol-level support for post-quantum signatures.
AVM v13 expands smart contracts with larger sizes, new opcodes and cross-app box storage support.
A new per-byte fee model targets larger transactions while keeping standard transfer fees unchanged.

Algorand v5.0.0 has reached 90% node support, clearing the upgrade for activation after its cooldown period. 

The protocol change marks Algorand’s largest upgrade since staking rewards launched in January 2025. It introduces native post-quantum accounts alongside expanded smart contract capabilities and a flexible fee model.

The upgrade also moves Algorand closer to a protocol designed to adapt as cryptographic standards evolve.

Algorand v5.0.0 Brings Post-Quantum Accounts to Mainnet
The Algorand team confirmed the 90% support threshold in a post on X. The upgrade will activate once the required cooldown period ends, with mainnet deployment expected soon.

Algorand v5.0.0 has reached 90% support and will now activate after the cooldown period.

This is the biggest upgrade since staking rewards, bringing native post-quantum accounts, more powerful smart contracts, and a more flexible fee model.

Thank you to all the node runners. pic.twitter.com/7hpxpfvJ3b

— Algorand (@Algorand) August 15, 2026

Algorand v5.0.0 introduces native Falcon-1024 accounts for post-quantum signatures. The change moves quantum-resistant account support directly into the protocol rather than limiting it to application-level tools.

The upgrade also introduces AVM v13, expanding smart contract sizes and adding new functionality. New opcodes include poseidon2, while cross-application box storage support expands how applications can manage data.

Algorand has already developed post-quantum infrastructure through earlier network upgrades and account implementations. According to X user Marco Salzmann, v5.0.0 shifts that effort toward broader cryptographic agility across the protocol.

Algorand Upgrade Expands Smart Contracts and Fee Model
The new release adds a per-byte fee model for larger transactions and computationally heavier operations. Standard transfers will not face the same fee changes under the new structure.

The model gives Algorand more flexibility when transactions require greater storage or computational resources. It also creates a mechanism for fees to reflect transaction size  without changing ordinary transfer costs.

Algorand community member Alex, known as france.algo on X, said thousands of node runners upgraded within days. His post described v5.0.0 as one of the network’s largest protocol upgrades.

🚨 Algorand v5.0 has now passed! 🎉

One of the biggest protocol upgrades yet, set to hit mainnet in about a week!

Huge shoutout to the @Algorand protocol team + THOUSANDS of node runners who upgraded in just a few days!

Awesome to see, $ALGO has the BEST community!! pic.twitter.com/yueNMgp6Cj

— Ⱥlex | france.algo 🇫🇷 (@algerstmehn) August 16, 2026

Salzmann also outlined a broader roadmap involving hybrid accounts, post-quantum multisig and additional Falcon research. The roadmap includes further work on post-quantum verifiable random functions and consensus mechanisms.

Algorand just shipped its biggest upgrade since staking rewards launched in January 2025. If you're running a node, here's what's in it, and exactly how to get your setup upgraded.

What's in v5.0.0
Three things landed together in this release.

Quantum-resilient accounts, now native. Falcon-1024 accounts no longer require a LogicSig wrapper. This builds on State Proofs work Algorand shipped back in 2022, the first quantum-resilient mainnet transaction in 2025, and the post-quantum roadmap published in June 2026. This release is the first deliverable off that roadmap.

Resource-based fees. Fees now scale with what a transaction actually needs, larger data, heavier computations, rather than a flat rate for everyone. Regular payments and everyday transfers stay exactly as affordable as they've always been. The extra fees on resource-heavy transactions flow into the fee sink, funding node runner payouts. This is the first concrete step toward a more sustainable network long term, part of the thinking behind the upcoming King Safety paper.

A bigger developer toolkit. Smart contracts can hold twice as much code, share box storage data between each other (opt-in), and existing apps can upgrade in place without a full rebuild. New opcodes add native support for zero-knowledge app development. A new congestion signal previews future network health tooling, no impact on fees today.

How to upgrade
There are three paths depending on your setup.

Running NodeKit
Upgrade with the following command.

./nodekit upgrade

On macOS only, you'll also need to stop and start your node.

./nodekit stop; ./nodekit start

Then launch NodeKit with ./nodekit to confirm your node version. The top right should read something like this.

Node: v5.0.0-stable

Getting a FATA algod is running, please run the stop command error? You need to upgrade NodeKit itself first.

Run the installer command for your OS from nodekit.run
Respond YES to upgrading NodeKit, and NO to fast catch-up
Then run ./nodekit upgrade to upgrade your node

Note, from NodeKit v1.1.0 onward, the nodekit upgrade command upgrades both NodeKit and the node to the latest stable versions in one step.

Running the FUNC Program
If you're on the FUNC Program, this one's simple. An update will be available directly in the FUNC Program. Just download it once it's live, no manual configuration needed.

Running a custom setup
Running something outside NodeKit or FUNC? Reach out to [email protected] and we'll help you get upgraded.

Questions?
If you hit any issues during the upgrade, or you're not sure which path applies to your setup, reach out or join the node runner channel in our Discord and we'll get you sorted.

Algorand v5.0.0 is available now. You can upgrade your node via NodeKit or FUNC. If you need help, reach out via the #node-runners channel in Algorand’s Discord.

Disclaimer: The content provided in this blog is for informational and educational purposes only. The information is provided by the Algorand Foundation and while we strive to keep it accurate and current, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the blog or the information contained in it for any purpose. Nothing in this blog is legal, financial, tax, or investment advice, nor an endorsement, guarantee, or investment recommendation. Technical descriptions are provided as of the date of publication and may change. Any statements about future plans, features, integrations, protocol or consensus upgrades, fees, or timelines are forward-looking and subject to change, including subject to community adoption, and are not commitments. You should conduct your own research and consult a qualified professional before acting on any information here; any reliance you place on it is strictly at your own risk. All third-party names and trademarks are the property of their respective owners, and their mention does not imply affiliation or endorsement.

This guide walks through integrating the x402 payment flow into a service, using the GoPlausible facilitator to handle payment verification and settlement, making that service properly discoverable, and standing up a working demo. It also covers gating a normal Web2 API behind crypto payment instead of API keys or subscriptions.

A note before you start: this guide describes the integration pattern based on the x402 spec and the facilitator's published feature set. Confirm exact endpoint paths, field names, and request formats against GoPlausible's own documentation before shipping, since that's the source of truth.

Before you start Pick your asset. On Algorand, you can price in USDC or ALGO. If you're not sure yet, start on testnet with USDC, since it's the cheapest place to make mistakes. (The facilitator also supports Base and Solana if you ever need to reach those chains, but this guide focuses on Algorand.) Get a wallet and a payTo address. You'll need an Algorand account that is opted into USDC to receive payments. This is also the address your pricing and settlement will be tied to, so treat it as a permanent part of your setup, not something you rotate casually. Decide what you're gating. x402 works per-request, so think in terms of the smallest unit of value you're selling: one API call, one document, one query, one file. Pricing gets easier once you've named that unit.

Step 1: Integrate with the facilitator The facilitator's job is to verify that a payment happened and settle it on-chain, so your service never has to implement signature verification or chain logic itself.

Respond to unpaid requests with HTTP 402. When a request comes in without payment, your server returns a 402 status with the payment requirements: price, asset, network, and your payTo address. Call the facilitator's verify endpoint before fulfilling the request. Once a client resubmits with payment attached, hand that payment to the facilitator to confirm it's valid before you do any work or return any data. Call settle once you've confirmed the request is legitimate. This is what finalizes the payment on-chain. The facilitator is currently covering the transaction fee, so neither you nor your payer needs to hold a balance for fees. This is set by the facilitator and may be subject to change. Test on testnet end-to-end before touching mainnet. Run the full 402 → verify → settle loop against Algorand testnet first. It's free to get wrong there and expensive to debug on Mainnet. Watch your first few settlements land on the GoPlausible dashboard. This is a useful sanity check: if a payment isn't showing up there, something in your integration isn't calling settle correctly, not just a display issue on their end. Best practice: never write your own on-chain verification logic in parallel with the facilitator's. The whole point of using it is that verification and settlement are handled for you. Duplicating that logic yourself is where most integration bugs come from.

Step 2: Make your service discoverable If you want your service to be discoverable, give people and machines a clear way to understand it. A good landing page should explain what the service does and why it is useful, while the Bazaar discovery extension should describe how it works. Both are worth a little care.

Fill out your OpenGraph metadata properly for your landing page. Title, description, logo, and banner. The facilitator's metadata enrichment engine fetches each merchant domain roughly once a day and pulls exactly these fields to build your listing. If they're missing or generic, your entry in the directory will look unfinished no matter how good your API is. Publish an llms.txt file. This follows the llmstxt.org convention and is one of the first things the facilitator checks when it probes your domain, along with any agent well-knowns you support (an A2A agent card, an ai-plugin manifest, an MCP manifest, or an x402 well-known descriptor). If your service is agent-facing at all, this is where that gets communicated. No need to manually register anywhere. There's no form to submit. Once you complete a real, successful transaction, you're cataloged automatically, and your listing pulls from the metadata you've already published. The landing page is the input; the directory entry is the output. Keep it current. Since the enrichment engine refreshes at most once a day, treat your metadata like a small but real part of your API contract, not a one-time task. If you change your pricing or endpoints, update the page and expect the directory to catch up within a day. Add a Bazaar discovery declaration. This gives the GoPlausible facilitator the information it needs to offer your endpoint in the Bazaar catalog, including a description of the endpoint, what it expects as input, and an example of what it returns, declared alongside the payment details in the 402 response you built in Step 1. Keep it clear and specific: “Current weather for any city, returned as JSON” is more useful than “Weather API.” Your payment flow can work without this information, but your endpoint will be harder for developers and agents to find and use. Algorand’s official x402 tutorial includes a working example. Best practice: build your landing page as if it's read by a crawler first and a person second. A short, accurate OpenGraph block and a working llms.txt will do more for your visibility than an elaborate design.

Step 3: Build a working demo A demo proves the whole loop works, from a human clicking connect to money actually landing on-chain. The core flow looks like this regardless of what you're gating:

Connect wallet. A user connects an Algorand wallet to your demo page. Hit the gated endpoint. The demo calls your API without payment and gets back a 402 with the price and payment details. Sign the payment. The wallet signs a transaction for the required amount to your payTo address, on the network you specified. Resubmit with payment attached. The demo calls the endpoint again, this time including proof of payment. Get the resource. Your server verifies through the facilitator, settles, and returns whatever the user paid for, whether that's data, a file, or an API response. A few things worth building into the demo specifically:

Show the price clearly before the wallet prompt appears. Nobody should be surprised by what they're signing. Show the transaction ID and a link to it once settled, so a skeptical user can verify it happened on-chain themselves. Keep the whole loop fast. Algorand settles with instant finality, so a demo that hangs undercuts the pitch. Best practice: build and test the demo on testnet, but keep a mainnet toggle ready. The first thing a new visitor will ask is whether this works with real money, and being able to show that immediately matters.

A use case worth highlighting: gating ordinary APIs with crypto x402 has mostly been pitched as a way for AI agents to pay each other, and that's a real use case. There's a simpler one sitting right underneath it that's easy to miss. This is also a way to sell access to a regular API.

Right now, most APIs gate access with keys, tiers, and subscriptions, because there's never been a cheap way to charge per call. x402 on Algorand removes that constraint. A developer with an existing API doesn't need to be building for agents at all to benefit here. They can gate any endpoint behind a payment priced in cents, collected in USDC, and settled within seconds, with no payment processor, no card minimums, and no subscription tier standing between a user and a single request.

That matters for two different audiences at once:

Developers who already have an API get a way to monetize per-request usage that credit card economics never made viable, and they get it without becoming a crypto company to do it. Developers who aren't thinking about crypto or agents at all get an on-ramp into building on Algorand. For anyone already running an API, per-request payment is a practical option that credit card economics never supported — agent traffic or not. This is also where Algorand's specific design pays off, independent of the agentic-commerce story:

Fixed, sub-cent fees mean the payment doesn't eat the price. Charging half a cent for a call only works if the fee isn't ten times the charge. Instant, deterministic finality means a normal synchronous API call doesn't have to wait around for confirmation, so gating a request with a payment doesn't make the API feel slower. Predictable performance under load means a busy API doesn't need to build congestion-aware retry logic on top of its payment layer. Framed this way, x402 on Algorand isn't just infrastructure for agent economies that don't fully exist yet. It's a payments upgrade available today to anyone who already runs an API and has been living with the tradeoffs of keys and subscriptions because there was no real alternative.

Best practices, quick recap Start on testnet, move to mainnet only once the full loop works end to end. Let the facilitator handle verify and settle. Don't duplicate that logic. Treat your landing page's metadata as part of your integration, not a design afterthought. Price in the smallest sensible unit. The advantage here is that fractional-cent pricing works, so use it. Check the dashboard after your first live settles to confirm everything is wired up correctly. If you already run an API, you don't need an agent use case to justify trying this. Ordinary paid access is a use case on its own. The content provided in this blog is for informational purposes only. The information is provided by the Algorand Foundation and while we strive to keep the information up-to-date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability with respect to the blog or the information, products, services, or related graphics contained in the blog for any purpose. The content of this blog is not intended to be legal, financial, or investment advice nor is it an endorsement, guarantee, or investment recommendation. You should not take any action before conducting your own research or consulting with a qualified professional. Any reliance you place on such information is therefore strictly at your own risk. All companies are independent entities solely responsible for their operations, marketing, and compliance with applicable laws and regulations. In no event will Algorand Foundation nor any affiliates be liable for any loss or damage including without limitation, indirect, or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this blog. Through this blog, you may be able to link to other websites which are not under the control of the Algorand Foundation. We have no control over the nature, content, and availability of those sites. The inclusion of any links does not imply a recommendation nor endorse the views expressed therein.

The partnership delivers 24/7 liquidity to ALGO for institutional counterparties

, /PRNewswire/ -- Algorand Foundation and Flow Traders, a leading global liquidity provider, today announced a partnership to deepen institutional liquidity across the Algorand blockchain. As part of this collaboration, Flow Traders will provide liquidity to support institutional participation in the Algorand ecosystem and make ALGO available to institutional counterparties through its global execution infrastructure, with execution available via FIX, OMS/EMS, ECNs, or high-touch OTC, and settlement in fiat or stablecoins through established workflows.

"This partnership means Algorand's infrastructure now benefits from Flow Traders' continuous, institutional-grade liquidity," said Amar Odedra, Chief Commercial Officer at the Algorand Foundation. "As Algorand's real-world asset ecosystem grows, deep, reliable liquidity in ALGO gives institutional counterparties the confidence to engage with the network at scale."

"We look forward to making ALGO available to institutional counterparties through our global execution infrastructure," said Michael Lie, Global Head of Digital Assets at Flow Traders. "Deep and reliable liquidity is essential to supporting institutional participation in digital asset markets. By expanding our coverage to ALGO, we are improving access to the Algorand ecosystem as it continues to grow across payments, tokenized assets and other on-chain use cases."

Flow Traders brings two decades of ETF expertise to digital assets, operating at the intersection of traditional finance and on-chain infrastructure. As institutional participation in digital asset markets grows, the Algorand Foundation and Flow Traders are committed to expanding liquidity coverage across the Algorand ecosystem.

The Algorand blockchain supports an established RWA ecosystem spanning real estate, commodities, private credit, and stablecoins, with institutional participants including Lofty, Enel, Aberdeen, and Meld. In Q2 2026, the network recorded 23.2 million RWA transactions across 1.2 million monthly active addresses, with $1.61 billion in USDC transacted volume.

About Algorand

Algorand is a public layer-1 blockchain built for financial empowerment. Algorand offers tools to move money across borders, issue and manage assets, verify identity, and develop services that rely on dependable performance and instant settlement. Developers and organizations use Algorand to create practical tools for payments, identity, asset tokenization, public records, and other financial services. Algorand's all-in-one blockchain infrastructure powers financial apps that are easy to build, simple to use, and unlock economic opportunity for users.

Today, the Algorand ecosystem spans startups, developers, governments, and global partners building real-world financial and digital asset solutions. With Algorand, you decide where your money lives, how it moves, and who can access it. To learn more and join the financial empowerment movement, visit algorand.co.

About Flow Traders

Flow Traders is a leading global ETF and digital asset liquidity provider, on a mission to become the liquidity provider of choice in a 24/7 global financial ecosystem. Founded in 2004, Flow Traders has built on its heritage in European equity ETFs to provide liquidity across more than 25,000 products in ETFs, equities, fixed income, commodities, FX and digital assets, on over 150 venues globally. With more than EUR 7 trillion in annual value traded and over 1,600 active counterparties, Flow Traders plays a central role in ensuring markets remain resilient and transparent. The Company is investing in frontier technologies to drive innovation across traditional and digital asset markets. Operating from eight offices across Europe, the Americas and Asia, Flow Traders brings together over 600 professionals representing more than 60 nationalities.

Disclaimer: This press release is provided for informational purposes only. The information is provided by the Algorand Foundation and, while we strive to keep it accurate and current, we make no representations or warranties of any kind, express or implied, as to its completeness, accuracy, reliability, or suitability for any purpose. Nothing in this release constitutes legal, financial, tax, or investment advice, nor an endorsement, guarantee, or investment recommendation. References to third parties, including any organizations, agencies, products, or platforms, are for informational purposes only and do not imply any endorsement, affiliation, or partnership beyond what is expressly stated. All third-party names and trademarks are the property of their respective owners. Operational figures reflect information available as of the date of this release and may be subject to revision. Any statements regarding future plans, integrations, deployments, or timelines are forward-looking and subject to change. The Algorand Foundation undertakes no obligation to update these statements except as required.

SOURCE Algorand Foundation

Five days. That’s all it took for daily x402 settlements on Algorand to leap from 1,300 to 40,600, a roughly 30x increase driven by a developer competition called the Global x402 Challenge. The network has processed more than 177,000 transactions across approximately 800 endpoints, and the contest isn’t even close to finished.

What x402 actually is, and why it matters The “402” in x402 refers to HTTP status code 402, “Payment Required,” a response code that’s existed in the web’s architecture since the early days but was never widely implemented. Coinbase developed x402 as a protocol standard that finally puts that dusty status code to work, enabling pay-per-request transactions between clients and servers.

In English: imagine an AI agent that needs to pull data from an API. Instead of signing up for a monthly subscription or navigating an authentication maze, the agent just pays a tiny amount per request, instantly, on-chain.

Advertisement

Algorand’s architecture makes it a natural fit for this kind of use case. The network offers low transaction fees, instant finality, and native support for stablecoins like USDC. The settlements tracked through the GoPlausible facilitator reflect real USDC transactions happening on Algorand’s Mainnet. These aren’t testnet experiments or simulated volumes. Participants in the challenge must deploy a paid endpoint and generate at least one real USDC settlement to qualify.

Inside the Global x402 Challenge The competition driving this activity comes with a prize pool of $100K USD and 500K ALGO. The challenge was launched around mid-July 2026, following a series of workshops and hackathons designed to onboard developers to the protocol.

Developers deploy endpoints on Algorand’s Mainnet that accept x402 payments, building real services that get paid in real stablecoins every time they’re used. The competition is designed to run until at least November 2026, with finalists scheduled to present at Devcon 8 in Mumbai.

The AI-commerce angle The protocol is purpose-built for high-frequency, low-value payments, exactly the kind of transactions that AI agents generate when they interact with APIs, data feeds, and other digital services. Traditional payment rails can’t handle this. Credit card processors would laugh you out of the room if you tried to settle a fraction-of-a-cent payment through their systems.

Algorand’s support for x402 went live earlier in 2026, and the current challenge is essentially stress-testing whether the network can handle the kind of volume that a mature agentic economy would demand.

What this means for investors Developer competitions are, by their nature, artificial demand generators. The real test comes after November 2026, when the prize pool has been distributed and the hackathon energy fades. If endpoints continue processing x402 payments at elevated levels, it would validate Algorand’s positioning as a settlement layer for agentic commerce.

The 500K ALGO prize pool means tokens are being distributed to active developers building on the network. Coinbase originated the x402 standard, which means Base, its own Layer 2, is a natural competitor for x402 settlement volume. Algorand’s early mover advantage in this niche is real, but maintaining it will require the endpoints deployed during this challenge to evolve into production-grade services that attract organic demand from AI agents and developers who aren’t competing for prize money.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.

Top 3 Altcoins to Watch for the First Week of August 2026

The GRAM (GRAM) token is extending losses on Tuesday as Apple pulled Telegram from its iOS App Store worldwide, while Algorand (ALGO) emerges as the top-performing crypto, extending its 5% gains from the previous day.

Solana (SOL) holds steady amid emerging bullish signs, including BlackRock's filing to issue tokenized fund shares, the Double Disinflation proposal, and renewed demand in its memecoin ecosystem. 

Telegram’s exit from the App Store weighs on GRAMTelegram has been removed from the iOS App Store worldwide, while neither Apple nor Telegram has issued an official statement. The GRAM token is down 3% at press time on Tuesday, after briefly dropping to $1.29 early in the day.

From a technical perspective, GRAM shows a contracting price trend, forming a falling wedge pattern on the daily chart. The Relative Strength Index (RSI) at around 37 indicates firm bearish momentum, with further downside room before reaching oversold conditions.

A decisive close above the overhead trend line near $1.44 could open the path toward the center pivot and R1 pivot levels at $1.53 and $1.71, respectively. 

GRAM/USDT daily price chart.Looking down, a sustained daily close below $1.29 would confirm the bearish breakout. The S1 and S2 pivot levels at $1.23 and $1.05, respectively, serve as crucial support levels.

Bearish momentum eases in Solana amid new bullish catalystsBlackRock filed with the U.S. Securities and Exchange Commission (SEC) to issue tokenized fund shares on the Solana network. BlackRock plans to launch the Daily Reinvestment Stablecoin Reserve Vehicle (BRSRV), which would boost stablecoin reserves on Solana.

In addition, the ongoing Double Disinflation Proposal is live on Solana and aims to reduce long-term sell pressure by doubling the disinflation rate to 30% from the current 15%. The SIMD-0550 proposal requires 10% of active stake to advance to achieve a full governance vote.

Finally, the Solana memecoin ecosystem is heating up, with the Cate memecoin reaching a market cap of $73 million within 8 days of its launch and $40 million in 24-hour trading volume. The memecoin ecosystem reflects a renewed demand and risk appetite in the Solana ecosystem.

SOL maintains a mixed near-term tone, holding steady below the 50-day Exponential Moving Average (EMA) at $75.63 and the 200-day EMA at $91.19. SOL remains under the downward resistance trendline at $75.81, suggesting that recent rebounds are still capped.

The RSI around 46 maintains a broadly neutral tone while the Moving Average Convergence Divergence (MACD) is marginally below its signal and zero lines, hinting at subdued momentum.

For a sustained recovery, SOL must clear above the 50-day EMA at $75.63, which could open the path toward the 200-day EMA at $91.19.

SOL/USDT daily price chart.On the downside, a close below the descending support trendline near $71.50 could extend the decline to the February 6 low at $67.50.

Technical outlook: Will Algorand price reclaim $0.10?Algorand edges higher on Tuesday, extending its rebound from the recent record low of $0.0757. At the time of writing, ALGO trades above the 50-period EMA at $0.0875, which now underpins a constructive near-term bias. The pair remains well below the longer-term 200-period EMA at $0.1096, capping the broader trend.

Momentum shows early signs of recovery as the MACD rises above its signal line, turning the histogram reading positive while the RSI climbs to 63, inching toward the overbought area. Taken together, the indicators hint at firm bullish pressure in the short term.

On the topside, initial resistance aligns with the May 8 high of $0.1000, ahead of the broader structural barrier at the 200-period EMA at $0.1096.

ALGO/USDT daily price chart.On the downside, the immediate pivot is the 50-period EMA at $0.0875, where a pullback toward it could attract buyers as long as the daily close holds above it.

(The technical analysis of this story was written with the help of an AI tool. Know more.)

PANews August 3 news, according to SoSoValue data, crypto market sectors were mixed, with the SocialFi sector standing out, rising 1.18% in 24 hours. Within the sector, Gram (GRAM) and Chiliz (CHZ) rose 1% and 1.03%, respectively. Meanwhile, the Layer1 sector rose 0.94%, Cardano (ADA) gained 5.08%, and Algorand (ALGO) surged 7.84%.

In other sectors, the PayFi sector rose 0.92% in 24 hours, with Ultima (ULTIMA) up 3.09%; the CeFi sector rose 0.91%, with NEXO (NEXO) up 1.25%; the Layer2 sector rose 0.81%, with Starknet (STRK) up 3.90%; the Meme sector rose 0.47%, with MemeCore (M) up 8.71%; the DeFi sector rose 0.20%, with Ethena (ENA) up 8.68%.

Additionally, the NFT sector fell 4.96%, and within the sector, Audiera (BEAT) dropped 6.95%.

Crypto sector indices reflecting historical sector performance showed that the ssiSocialFi, ssiCeFi, and ssiLayer2 indices rose 1.37%, 1.14%, and 1.03%, respectively.

A recent report from CGAP, a think tank associated with the World Bank, has turned the spotlight onto the use of stablecoins in international humanitarian aid. The report, frequently discussed by prominent crypto commentator All In Crypto, features real-world cases where Stellar- and Algorand-based platforms facilitate digital cash transfers in challenging regions.

Stablecoins in humanitarian relief effortsCGAP’s research investigates whether stablecoins can assist non-profit organizations in moving money across borders, particularly when traditional correspondent banks are slow, costly, or outright inaccessible. The analysis identifies a range of technical and regulatory barriers, including high transaction fees, lack of transparency in foreign exchange rates, delays of several days in payments, and the withdrawal of banks from jurisdictions labeled high-risk.

The report notes that stablecoins transact on blockchain networks, with the choice of network directly affecting costs, speed, and service availability. Stellar is highlighted as a blockchain supporting USDC, while both Stellar and Algorand are specifically identified as preferred low-fee networks in humanitarian cash transfer programs.

Field cases: Stellar and Algorand in actionIn Sudan, the Norwegian Refugee Council used KoalaPay, a digital payments platform, to distribute USDC—a major dollar-pegged stablecoin—to local partners handling aid disbursement. According to All In Crypto’s summary, KoalaPay runs on both Stellar and Base networks, with local organizations converting USDC into Sudanese pounds before transferring money to aid recipients.

A separate Ukraine initiative, launched in December 2022, relied on Stellar’s Aid Assist platform, MoneyGram, and self-managed digital wallets. This program delivered $4.6 million to more than 2,500 households during its first two years of operation.

CGAP described how, in Ukraine, digital stablecoin payments on Stellar and integration with major remittance networks enabled fast, traceable transactions to recipients in a highly volatile market.

Meanwhile, Algorand features in the Afghanistan-based case managed by Mercy Corps and HesabPay, a platform that sent a stablecoin denominated in afghani, the local currency, to users’ wallets. HesabPay allows recipients to receive digital funds directly, even in environments with limited banking infrastructure.

Mini dictionary: CGAP (Consultative Group to Assist the Poor) is a global partnership housed at the World Bank, focused on advancing financial inclusion in developing economies by researching digital financial services and innovative technologies.

CountryPlatformBlockchain UtilizedStablecoinImplementation PartnerReported ImpactSudanKoalaPayStellar, BaseUSDCNorwegian Refugee CouncilFunds converted to Sudanese pounds, distributed to local recipientsUkraineAid Assist, MoneyGramStellarUSDC (via wallets)Multiple partners$4.6M to 2,500 householdsAfghanistanHesabPayAlgorandAfghani-denominated stablecoinMercy CorpsDirect-to-recipient stablecoin aid deliveryChallenges remain for digital aid solutionsWhile CGAP affirms that stablecoins can enhance traceability and expand market access for cross-border aid, the report cautions that familiar hurdles remain. Currency exchange, cash withdrawal, and compliance all present continued challenges, even when on-chain transaction costs are negligible. The expense and availability of off-ramps—services that allow recipients to convert digital assets into local currency—still pose operational difficulties.

Another warning from CGAP is that direct-to-recipient models could shift foreign exchange risk, withdrawal fees, and digital literacy requirements to aid recipients. These risks are particularly significant for vulnerable populations in regions with limited access to merchant networks or digital infrastructure.

CGAP emphasizes that while blockchain-based transfers may cut transaction fees, practical access and inclusion barriers can persist in fragile environments where alternatives are scarce.

Stellar is an open-source blockchain designed for fast, low-cost cross-border payments and is widely used by financial institutions and non-profits for currency transfers. Algorand, launched in 2019, offers high-speed and scalable decentralized finance solutions and operates with a unique pure proof-of-stake protocol.

Disclaimer: The information contained in this article does not constitute investment advice. Investors should be aware that cryptocurrencies carry high volatility and therefore risk, and should conduct their own research.

Every time the internet has taken on a new kind of participant, it has exposed a payment rail that wasn't built for it. Card networks were built for a person standing at a register. They were stretched to cover a browser tab, and it worked, barely, with fraud tooling and checkout friction bolted on for decades. Agentic AI is the next participant, and it is not a person with a browser tab. It is software that can decide, in milliseconds, to call a hundred different paid services on someone's behalf, evaluate what came back, and call a hundred more. Nothing about the existing rails was built to carry that. The question worth asking isn't just whether agents can pay at all – x402 already answers that – it's which underlying chain should the payment settle on, because at agent scale, that choice stops being a footnote and starts being the constraint.

What agent-scale volume demands A human making an online purchase generates one transaction and can tolerate a few seconds of uncertainty while it clears. An agent completing one task might generate dozens of transactions, a pricing lookup, a verification check, a compute call, a follow-up, each individually worth a fraction of a cent, each needing to clear before the agent's next decision depends on it. That shift changes what “good enough” looks like for a settlement layer. Three properties stop being nice-to-haves and start being requirements: 

Finality must be immediate and certain, not probable. Cost must stay negligible and predictable at extremely high transaction counts, not just cheap on a good day. And settlement must be independently verifiable, since the party on the other end of an agent-to-agent transaction usually isn't a human who can just call and ask what happened.
Finality: certain, not eventually certain Most blockchains give you a transaction that's provisionally included and then becomes more final as more blocks are added on top of it, which is a reasonable trade-off for a lot of use cases, but it introduces a window where an outcome is probable rather than guaranteed. For an agent economy, that window is a real problem. If an endpoint has to wait for several confirmations before it can be sure a payment is settled, it either releases the paid resource on faith or adds latency back into a system whose whole value proposition was removing latency.

Algorand's Pure Proof-of-Stake consensus produces blocks that are final the moment they're certified, roughly every 2.8 seconds, with no probabilistic settling period and no reorganization risk once a block is confirmed. A transaction is either in a certified block, or it doesn't exist. That's a meaningfully different guarantee than “final after enough confirmations have piled up,” and it's the difference an x402 facilitator needs: an endpoint can release its resource the moment settlement is certified, not the moment it's statistically unlikely to be reversed.

Cost that stays predictable at volume Cheap is easy to claim. Cheap and predictable under load is harder, and it's the property that matters once you're running millions of sub-cent transactions instead of thousands of dollar-sized ones. Many chains price transactions through an auction, gas fees that rise and fall with network demand, which is a fine model when a transaction is worth ten dollars and a fee spike costs you fifty cents. It's a broken model when the transaction itself is worth two cents and the fee occasionally exceeds the payment. Atomic, honestly priced micropayments only work if the cost of moving the money doesn't compete with the price of the thing being sold.

Algorand's fee model is flat rather than auction-based; a fixed fraction of a cent per transaction, with a network built to handle up to 10,000 transactions per second. That combination of fixed cost and high throughput headroom is what lets a builder price a reminder at two cents and a booking at five cents and actually keep the difference, instead of watching network conditions eat the margin on the smallest, most frequent actions, which are exactly the actions an agent economy runs the most of.

Settlement that doesn't require trusting a middle layer The third requirement is easy to overlook because humans rarely need it: when something goes wrong, or when an audit needs to happen, or when a dispute needs resolving, someone needs to be able to independently verify what actually settled, without taking a sequencer's word for it or waiting on a rollup's fraud-proof window to close. Algorand's consensus produces a single, publicly verifiable ledger with deterministic finality by design, not a fast “soft” confirmation followed by a slower “real” one settling elsewhere later. For an agent economy that's going to need real accounting, which endpoint got paid, how much, for what, at what time, that distinction between one settlement and two staggered ones is not academic. It's the difference between a ledger you can point an auditor at and a ledger you have to explain.

What this means for what you build None of the properties above matter in the abstract, they matter because of what they let a developer ship. If finality is instant and fees stay flat and negligible at volume, the right unit to build is not an application, it's an endpoint: one narrow, honestly priced capability that an agent can call, evaluate, and pay for in a single exchange. Four patterns cover most of what's worth building.

Charge for data: sell access to a dataset, a report, a market signal, or a verification result, one request at a time. Charge for compute: let an agent pay only when it runs a model, executes code, or completes an inference call. Charge for actions: let an agent pay to trigger something real, sending a message, booking a resource, generating a file. Charge for verification: sell trust itself, proof, a reputation check, a validation an agent should run before it acts on someone's behalf.
What ties all four together is that they're cheap, frequent, and only worth building if the settlement layer underneath doesn't eat the margin or introduce a delay the agent must wait out. That's the specific reason the finality and fee properties described above aren't a side benefit, they're what makes the endpoint pattern viable at all.

But an endpoint by itself rarely solves anything. A pricing lookup is a fact, not an answer. A single inference call is a capability, not a decision. Real utility, the kind someone actually keeps paying for, almost always comes from orchestration: taking several narrow, atomic endpoints, sometimes several you built yourself, sometimes several built by entirely different teams, and combining them into a response to a question a person or another agent actually had. The endpoint is the unit worth building. The solution is what you get when several of them work together toward a problem someone needs solved.

Poe, Quora's consolidated interface for chatting with several AI models through one product, is a useful case to look at here. This is not because anything about it is done wrong, but because its own published policies show clearly what a team has to build when the models it is bringing together don't have a native way to charge per use and settle right away. That infrastructure is a reasonable, well-built answer to a real constraint, and it is worth going through in some detail because of how differently the same product can look once that constraint is no longer there.

To let users move between models in one place, Poe has users prepay into a points balance, spread across fixed subscription tiers. Poe's own help center says unused points do not carry over between billing periods unless a plan says otherwise, and that points bought ahead of time expire one year after purchase (Poe Purchases FAQs). On the creator side, developers who build bots on the platform are paid on a periodic cycle rather than right away: Poe's Creator Monetization FAQ says earnings become payable once they reach ten dollars, with payment sent thirty to forty-five days after the end of the month they were earned in, routed through Stripe (Poe Creator Monetization FAQs). Building and keeping up that accounting, the points ledger, the subscription tiers, the payout calendar, is a fairly big piece of infrastructure sitting next to the actual product, and it is what any team has to build today when there is no settlement layer underneath that can charge and pay out per use, instantly.

Now picture the same kind of product built the other way around: as an orchestration layer sitting on top of several atomic x402 endpoints, each one a separate model, priced and settled on its own. A client asks one question. The orchestration layer decides which endpoints that question actually needs, calls each of them, pays each one the moment it answers, and puts together what comes back into a single response. This version works out better for everyone involved, not only for the team building it: the aggregator does not need to build or maintain its own financial system on the side, the model providers behind each endpoint get paid the moment their work is used instead of waiting on a monthly cycle and a minimum threshold, and the end user never carries a prepaid balance that can sit there unused or quietly expire. None of that flow needs a points system or a payout calendar, because every leg of it settles by itself, in seconds, at a cost too small to matter. The product is the judgment applied in the middle, not the settlement machinery underneath it, and that is only possible because the settlement layer underneath can be trusted to just work, every time.

Now picture the same kind of product built the other way: as an orchestration layer sitting on top of several atomic x402 endpoints, each one a distinct model, priced and settled on its own. A client asks one question. The orchestration layer decides which endpoints the question needs, calls each one, pays each one individually the moment it responds, and assembles what comes back into a single answer. Nothing about that flow requires a points balance, a subscription tier, or a monthly payout run, because every leg of it settles on its own, in seconds, at a cost too small to matter. The product is the judgment applied in the middle, not the settlement machinery underneath it, and that's only possible because the settlement layer underneath can be trusted to just work.

This is the argument for building endpoints on Algorand: not that a single endpoint is valuable in isolation, but that instant, cheap, verifiable settlement is what makes it worthwhile to build several of them and let something else orchestrate them into a real solution. That's the concrete version of the abstract argument above: the difference between a builder having to construct financial infrastructure from scratch and a builder being able to skip that step entirely and just build the product.

Where this is already running This isn't a hypothetical fit. Algorand added full x402 support on Mainnet in February 2026, with ecosystem startup GoPlausible operating a facilitator that verifies and settles payments natively on the Algorand Virtual Machine. Every one of the properties above, instant finality, flat low fees, single-ledger verifiability, is already what's carrying those settlements today, not a roadmap item.

It's also worth being honest about where the broader x402 ecosystem stands; daily transaction volume across the whole protocol, on every chain, is still small relative to the attention agentic commerce is getting, and a meaningful share of it is still test traffic and early experimentation rather than mature, sustained demand. That's not a weakness in the thesis; it's exactly why the base layer choice matters more right now than it will later. The rails get chosen while the volume is still forming, not after. Builders shipping x402-powered endpoints today, including through the Global x402 Challenge, are making that choice in real time, and the properties that matter at agent scale, certain finality, predictable cost, verifiable settlement, are the ones worth building on.

Disclaimer: The content provided in this blog is for informational purposes only. The information is provided by the Algorand Foundation and while we strive to keep the information up-to-date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability with respect to the blog or the information, products, services, or related graphics contained in the blog for any purpose. The content of this blog is not intended to be legal, financial, or investment advice nor is it an endorsement, guarantee, or investment recommendation. You should not take any action before conducting your own research or consulting with a qualified professional. Any reliance you place on such information is therefore strictly at your own risk. All companies are independent entities solely responsible for their operations, marketing, and compliance with applicable laws and regulations. In no event will Algorand Foundation nor any affiliates be liable for any loss or damage including without limitation, indirect, or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this blog. Through this blog, you may be able to link to other websites which are not under the control of the Algorand Foundation. We have no control over the nature, content, and availability of those sites. The inclusion of any links does not imply a recommendation nor endorse the views expressed therein. Any statements about future plans, integrations, or protocol upgrades are forward-looking and subject to change.

New operational data highlights the Humanitarian Payments Council's momentum ahead of its Washington, D.C. summit.

DOVER, Del., July 15, 2026 /PRNewswire/ -- The Algorand Foundation today shared new progress from its Humanitarian Payments Council, marking a shift from pilot projects to institutional-scale deployments. Convening today in Washington, D.C. to build on the foundations laid during their September meeting in Berlin, Council members are highlighting a major expansion of blockchain-backed aid delivery in high-stakes environments.

Most notably, according to UNHCR, the UN Refugee Agency, it has scaled its use of reloadable cards through HesabPay, the Algorand-powered payments platform, to support more than 625,000 refugee returnees and over 17,500 internally displaced people in Afghanistan, with more than $35 million in assistance. This operational milestone reflects the network's ability to support large-scale aid disbursement in a live deployment and provide secure, immediate financial empowerment in regions where traditional banking infrastructure is absent or limited.

"Blockchain-powered payment infrastructure that is locally connected, globally compliant, and fully traceable has the potential to strengthen trusted aid delivery. The next step is continued collaboration to expand reliable digital financial ecosystems that can help deliver humanitarian assistance more securely, efficiently, and transparently for donors, regulators, and forcibly displaced people and communities alike," said Carmen Hett, Corporate Treasurer at UNHCR.

"The progress achieved since our Berlin meeting is clear evidence that tokenized aid is moving from a novelty to a practical, scalable option for global aid delivery, particularly in economically distressed countries where traditional banking infrastructure is virtually nonexistent," said Matt Keller, Head of Impact at the Algorand Foundation. "By scaling our work with UNHCR and HesabPay to reach over 600,000 returnees in Afghanistan, we are showing the international community that blockchain-based aid can deliver speed, transparency, and cost-efficiency where traditional infrastructure is limited."

This operational progress serves as the backdrop for the Humanitarian Payments Council meeting taking place this week in Washington, D.C. The event convenes international humanitarian agencies, financial institutions, fintech providers, and policymakers to discuss scalable frameworks for global humanitarian stablecoin deployments.

About Algorand

Algorand is a public layer-1 blockchain built for financial empowerment. Algorand offers tools to move money across borders, issue and manage assets, verify identity, and develop services that rely on dependable performance and instant settlement. Developers and organizations use Algorand to create practical tools for payments, identity, asset tokenization, public records, and other financial services. Algorand's all-in-one blockchain infrastructure powers financial apps that are easy to build, simple to use, and unlock economic opportunity for users.

Today, the Algorand ecosystem spans startups, developers, governments, and global partners building real-world financial and digital asset solutions. With Algorand, you decide where your money lives, how it moves, and who can access it. To learn more and join the financial empowerment movement, visit algorand.co.

Disclaimer: This press release is provided for informational purposes only. The information is provided by the Algorand Foundation and, while we strive to keep it accurate and current, we make no representations or warranties of any kind, express or implied, as to its completeness, accuracy, reliability, or suitability for any purpose. Nothing in this release constitutes legal, financial, tax, or investment advice, nor an endorsement, guarantee, or investment recommendation. References to third parties, including any organizations, agencies, products, or platforms, are for informational purposes only and do not imply any endorsement, affiliation, or partnership beyond what is expressly stated. All third-party names and trademarks are the property of their respective owners. Operational figures reflect information available as of the date of this release and may be subject to revision. Any statements regarding future plans, integrations, deployments, or timelines are forward-looking and subject to change. The Algorand Foundation undertakes no obligation to update these statements except as required.

FIFA is deploying an upgraded Video Assistant Referee system with semi-automated offside technology that can detect positional differences as small as 10 centimeters for the 2026 World Cup.

FIFA has also been building out a crypto and blockchain layer around the tournament, with Kraken, Avalanche, and Algorand all playing roles in the event.

Advertisement

AI referees and 10-centimeter precision The new semi-automated offside technology, or SAOT, uses AI-driven 3D player tracking powered by 16 optical cameras alongside standard broadcast feeds. The system fires real-time alerts when a player strays offside by as little as 10 centimeters, a leap from the previous 50-centimeter threshold.

The International Football Association Board, or IFAB, has also confirmed an expanded scope for VAR reviews. Officials can now use video replay to evaluate decisions around corner kicks, second yellow cards, mistaken identity, and set-piece fouls, with the focus remaining on correcting clear and obvious errors.

FIFA’s centralized VAR operation room sits in Dallas, equipped with the tracking technology and broadcast infrastructure needed to support matches across all host venues in the US, Canada, and Mexico.

Kraken leads the crypto charge On June 9, 2026, Kraken was named the Official Crypto Exchange Supporter of the FIFA World Cup 2026.

FIFA has been running FIFA+ Collect, a platform for historical NFT collectibles built in partnership with Algorand. Avalanche technology is being piloted for blockchain-based ticketing solutions during the tournament. The potential use of Chainlink oracles for live match data has also been identified as part of the tournament’s digital infrastructure.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.

Algorand’s native token, ALGO, has maintained its upward momentum in recent days amid renewed buying interest. As trading volume and price action both showed signs of recovery, market watchers started to eye a potential breakout. At the time this article was prepared, ALGO was trading at $0.09086, with a 24-hour trading volume of $26.1 million and a total market capitalization of $813.15 million.

Crypto market analyst Alpha Crypto Signal reported that ALGO continues to build on its bullish momentum, with the price rising by over 6%. According to the analyst, sustained buying pressure could play a decisive role in determining the short-term direction of the market.

Attention is now focused on the $0.1040 resistance level. A successful break above and consolidation at this threshold could further strengthen the bullish trend. Conversely, if ALGO fails to overcome this resistance, the token may enter a sideways pattern with short-term volatility.

Alpha Crypto Signal notes that buying pressure in ALGO remains strong and the token has sustained its upward movement with a gain exceeding 6%.

Lofty AI marks a milestone within the Algorand ecosystemData shared by the Algorand Foundation highlighted a noteworthy development on the network side. For the first time, total value locked (TVL) on Lofty AI, a leading real estate tokenization platform, exceeded $100 million. This signals increased adoption of real-world asset utilization within the Algorand ecosystem.

Lofty AI has tokenized more than 180 properties spread across 21 US states. The platform has also generated over $5 million in cumulative rental income for its community of more than 40,000 investors. These figures point to the growing reach of blockchain-based fractional property ownership.

Glossary: RWA, or real-world assets, refers to representing traditional assets such as real estate as digital tokens on a blockchain. TVL, or total value locked, is a key metric showing the dollar value of assets locked within a protocol.

MetricDataLofty AI TVLOver $100 millionTokenized propertiesMore than 180US states21Generated rental incomeOver $5 millionNumber of investorsMore than 40,000The Algorand Foundation stated that Lofty AI surpassed $100 million in total value locked for the first time, with over 180 properties tokenized across 21 US states on Algorand.

Bitcoin trends impact ALGO’s directionThe recent steady rise in ALGO has been driven by not only network-related developments but also broader market sentiment. The recovery seen in Bitcoin has fueled increased risk appetite among altcoin traders, and Algorand has benefited from this momentum.

Looking ahead, investors will be watching closely to see whether buying interest can push ALGO past the $0.1040 resistance. A breakout above this level could open the door to further gains, while a failure would likely see prices consolidate for some time.

Disclaimer: The information contained in this article does not constitute investment advice. Investors should be aware that cryptocurrencies carry high volatility and therefore risk, and should conduct their own research.

A wave of cryptocurrencies are marketed as “ISO 20022 compliant,” with the promise that banks will adopt them and send prices soaring. This guide explains what the standard actually is, why it matters for global payments, and why the “compliant coin” label is mostly a myth.

Summary

ISO 20022 is a global standard for the messages financial institutions send one another, defining a common, data-rich language for payments and securities, not a rule about cryptocurrencies. Major systems including SWIFT and the United States Fedwire have adopted it, replacing older, simpler message formats with structured data that carries far more information. A group of tokens, including XRP, XLM, ALGO, HBAR, and others, are widely marketed as “ISO 20022 compliant,” fueling a belief that banks will adopt them and lift their prices. That label is largely a myth: there is no certification or registry for compliant coins, and being aligned with the standard does not mean a token is endorsed, validated, or destined for bank adoption. The standard genuinely matters for connecting traditional finance and blockchain, but the investment thesis built on the compliance label rests on a misunderstanding of what ISO 20022 actually is. Table of Contents

The standard that runs the world’s payment messagesWhy the financial world is switching to itA worked example: what richer data actually buysWhere crypto enters the pictureThe “compliant coin” myth, explainedWhat “aligned” actually means for a tokenThe XRP case specificallyWhat ISO 20022 does and does not mean for pricesRed flags and scams to watchFrequently Asked Questions ISO 20022 is an international standard that defines a common, structured language for the electronic messages financial institutions send one another, covering payments, securities trades, and other financial transactions. That is the whole of it: it is a messaging standard, a shared format that lets banks, payment systems, and market infrastructures exchange information in a consistent, data-rich way. It says nothing, in itself, about cryptocurrencies. And yet ISO 20022 has become one of the most hyped terms in certain corners of the crypto market, attached to a list of tokens, XRP, Stellar’s XLM, Algorand’s ALGO, Hedera’s HBAR, and several others, that are marketed as “ISO 20022 compliant,” with the implication that this compliance makes them special, bank-ready, and poised to soar once financial institutions adopt the standard. 

The reality is more mundane and more important to understand, because the gap between what ISO 20022 is and what the hype claims it means is exactly where investors get misled. This guide explains the standard plainly, why the financial world is adopting it, where crypto genuinely fits, and why the “compliant coin” label is largely a marketing myth rather than a meaningful endorsement.

The reason this matters is that ISO 20022 sits at the intersection of a real, significant trend and a layer of misleading marketing, and telling the two apart is essential. The real trend is that the global financial system is upgrading the language it uses to move money, a genuine modernization with real consequences for how payments work and how easily traditional finance can connect to blockchains. The misleading layer is the claim that certain tokens are validated or endorsed by the standard, a claim that has fueled speculative buying based on a misunderstanding. 

This guide covers what ISO 20022 actually is, why institutions are switching to it, what richer messaging buys them, where the crypto angle comes from, why the compliance label is a myth, what alignment truly means, the specific case of XRP, and how to read the whole phenomenon honestly. The goal is to leave you understanding both the substance and the spin.

The standard that runs the world’s payment messages Start with what ISO 20022 fundamentally is, because its name makes it sound more mysterious than it is. When a bank sends money to another bank, no physical cash travels; instead, the banks exchange messages instructing each other to debit one account and credit another. For decades, those messages used older, rigid formats that packed limited information into terse codes, formats designed in an era of expensive bandwidth and simple transactions. ISO 20022 is the modern replacement: a standardized, structured language for these financial messages that can carry far more information in a consistent, machine-readable form. Think of it as a shared grammar that every institution agrees to speak, so that a message sent by a bank in one country can be understood automatically by a system in another without translation or guesswork.

The power of ISO 20022 lies in two qualities: it is standardized, meaning everyone uses the same format, and it is rich, meaning each message can carry detailed, well-organized data rather than cramped codes. A useful way to picture it is the difference between a tightly abbreviated telegram and a properly structured digital form. The old formats were like telegrams, squeezing essential facts into minimal space and leaving much to interpretation. ISO 20022 is like a structured form with clearly labeled fields for every relevant detail: who is paying, who is receiving, the purpose of the payment, the parties involved, and the regulatory information attached. This is not a small upgrade. It changes what financial systems can do with a payment message, because a message that carries clean, structured, comprehensive data can be processed, screened, and reconciled automatically in ways that the old cramped formats never allowed.

Why the financial world is switching to it The migration to ISO 20022 is one of the largest coordinated upgrades in the history of financial infrastructure, and it is happening because the old messaging formats had become a serious bottleneck. The legacy formats carried so little structured data that banks constantly had to deal with incomplete information, manual intervention, and errors, all of which slow payments down and raise costs. When a payment message lacks clear, structured fields, a human often has to step in to interpret it, check it against sanctions lists, or chase missing details, and every such intervention is friction. As global payments grew in volume and as regulatory demands for transparency and screening intensified, the limitations of the old formats became untenable. ISO 20022 solves this by carrying the rich, structured data that lets far more of the process happen automatically and accurately.

The adoption has been sweeping. The global messaging network that connects most of the world’s banks has been migrating its cross-border payments to ISO 20022, phasing out the legacy formats. Major domestic payment systems have moved as well, including the United States’ main real-time settlement system, which adopted ISO 20022 for its operations, joining systems in Europe and elsewhere that had already transitioned. The direction is unmistakable: the world’s core payment rails are converging on this single standard, because the benefits, richer data, better automation, improved compliance, and smoother interoperability between systems, are compelling enough to justify an enormous, multi-year coordinated effort. For the financial industry, ISO 20022 is simply the new common language of money movement, and the migration to it is a genuine, consequential modernization. None of this, it is worth stressing again, has anything inherent to do with cryptocurrencies. It is about how banks and payment systems talk to each other.

A worked example: what richer data actually buys To make the value concrete, picture a single cross-border payment under the old system and under ISO 20022, because the difference shows why institutions care.

Under a legacy format, a bank sending a payment abroad might transmit a message with a sender, a receiver, an amount, and a short, cramped reference field, with much of the contextual detail abbreviated, omitted, or jammed into free-text notes that no automated system can reliably read. When that message arrives, the receiving bank may not have enough structured information to automatically confirm the purpose of the payment, verify the parties against regulatory lists, or match it to the right account, so a staff member has to intervene, slowing the payment and introducing the possibility of error. Multiply that friction across millions of payments and the cost in time, money, and risk is enormous.

Now picture the same payment under ISO 20022. The message arrives with clearly labeled, structured fields: the full identities of the sender and receiver, the precise purpose of the payment, the regulatory and compliance information, and the references needed to match it automatically to the correct account. Because the data is structured and comprehensive, the receiving bank’s systems can process it without human intervention, screen it against sanctions and fraud checks automatically, and reconcile it instantly. The payment moves faster, costs less to handle, and carries less risk of error or of slipping past compliance controls. This is the real, unglamorous value of ISO 20022: it turns payment messages from cramped telegrams that often need human interpretation into structured data that machines can handle end to end. That improvement in automation, compliance, and interoperability is why the entire financial world is undertaking the switch, and it is a truly significant upgrade to the plumbing of global finance. It is also, notably, an upgrade about messages, not about money itself, and certainly not about any particular token.

Where crypto enters the picture So how did a banking messaging standard become a crypto buzzword? The connection runs through the idea of interoperability between traditional finance and blockchain. As ISO 20022 became the language banks use, some blockchain projects, particularly those focused on payments and settlement, positioned themselves as able to work with that language, to structure their own messaging or data in ways compatible with the standard that banks were adopting. The thinking was reasonable on its surface: if banks are standardizing on ISO 20022, then a blockchain that can speak the same data language might integrate more easily into bank workflows, which could be an advantage for a payments-focused crypto network.

From that reasonable starting point grew a much larger and much shakier narrative. A list of tokens came to be labeled “ISO 20022 compliant” across crypto media and social channels, typically including XRP, Stellar’s XLM, Cardano’s ADA, Algorand’s ALGO, Hedera’s HBAR, and a handful of others associated with payments or enterprise use. Around this list formed a popular investment thesis: that because these tokens are ISO 20022 compliant, banks adopting the standard will naturally adopt these tokens, driving massive demand and sending prices soaring. The thesis is seductive because it connects a real, sweeping trend, the global migration to ISO 20022, to a specific set of assets, implying that those assets are uniquely positioned to benefit from the trend. Entire communities and marketing campaigns have been built around the “ISO 20022 coin” label, treating it as a mark of quality and a catalyst for price appreciation. The trouble is that the label means far less than the hype suggests, and in important respects it is simply false.

The “compliant coin” myth, explained Here is the core fact that punctures the hype: there is no such thing as official ISO 20022 certification for a cryptocurrency, because no certification process or registry for compliant coins exists. The standard is a messaging format used by financial institutions, and it has no mechanism for validating, endorsing, or registering tokens. When you see a coin described as “ISO 20022 certified” or “endorsed by ISO,” that language is marketing, and it is misleading or outright false. No authority hands out a compliance badge to cryptocurrencies, no list of approved tokens is maintained by the standards body, and being included on a community-circulated “ISO 20022 coin” list confers no official status whatsoever. The label that has driven so much speculative interest does not correspond to any real certification.

This matters because the entire investment thesis rests on a misreading of what the standard is. ISO 20022 governs how financial institutions format the messages they send each other; it does not validate the assets those messages might reference, and it does not bless particular blockchains as bank-ready. A bank using ISO 20022 messaging to interact with a crypto-related service is using the standard to communicate, which says nothing about whether the underlying token is approved, valuable, or destined for adoption. The conflation of “this token’s project works with ISO 20022 data formats” and “this token is officially compliant and therefore bank-endorsed” is the heart of the myth. The first may be true in a narrow technical sense for some projects; the second is not a real category. An investor buying a token because it appears on an “ISO 20022 compliant” list is buying based on a designation that does not officially exist, which is precisely the kind of misunderstanding that marketing language is designed to exploit.

What “aligned” actually means for a token To be fair and precise, there is a real kernel beneath the myth, and understanding it keeps this guide honest. A blockchain project truly can do engineering work to make its systems compatible with ISO 20022 data, structuring the information its network handles so that it maps cleanly onto the standard’s fields, or building tools that let institutions using ISO 20022 messaging interact with the blockchain more easily. This is real work, and for a project aiming to serve banks and payment providers, being able to speak the same data language as the institutions it wants as customers is a sensible and potentially useful capability. So when a project says it is “aligned with” or “built for” ISO 20022, it may be describing genuine technical compatibility, which is not nothing.

But notice how far that real kernel is from what the hype claims. Technical compatibility with a messaging standard is a feature a project chooses to build, not a certification it receives, and it does not make the project’s token special, validated, or guaranteed adoption. Plenty of capability can be ISO 20022 compatible without any of it translating into demand for a token, because, as with so much in crypto infrastructure, the usefulness of a network to institutions is a separate question from demand for its native asset. A project can do excellent work making its systems speak the standard’s language and still see no particular benefit flow to its token, because banks using that compatibility are using the technology, not buying the coin. So “aligned with ISO 20022” should be read as a modest, real technical claim about a project’s engineering, never as an official stamp of approval or a reason to expect price appreciation. The distance between the honest version of the claim and the hyped version is enormous.

The XRP case specifically Because XRP sits at the center of the ISO 20022 hype, it is worth examining its actual relationship to the standard, which illustrates the whole confusion neatly. Ripple, the company associated with XRP, has genuine ties to the world of financial messaging standards; as a company building payment infrastructure for institutions, Ripple participates in the relevant standards bodies and works with the messaging formats that banks use. That corporate level engagement is real and is part of why XRP appears at the top of most “ISO 20022 coin” lists. But here the crucial distinction between Ripple the company and XRP the token reasserts itself, the same distinction that runs through so much of the XRP story.

Ripple’s involvement with financial messaging standards as a company does not mean that XRP the token is “ISO 20022 compliant” in any meaningful sense. Ripple’s own chief technology officer has stated plainly that XRP has nothing to do with ISO 20022, clarifying that while Ripple as a company may engage with the standards world, that engagement does not translate into the token itself being compliant or endorsed. The standard is about how institutions message each other; XRP is a digital asset that can serve as a bridge in settlement. Those are different things, and a company working with messaging standards does not make its associated token a certified ISO 20022 instrument. The persistence of the XRP ISO 20022 conflation, despite direct clarification from the people who would know, shows how powerful the marketing narrative has become and how readily a real corporate fact, Ripple engages with standards bodies, gets transformed into a false token level claim, XRP is officially ISO 20022 compliant and therefore bank bound. The honest position is that Ripple’s standards work is real and XRP’s “compliance” is a myth, and both can be true at once.

What ISO 20022 does and does not mean for prices Pulling it together, the right way to think about ISO 20022 is to separate its genuine significance from its mythologized one, because both exist and they point in very different directions. Truly, ISO 20022 is a meaningful, long-term tailwind for the convergence of traditional finance and blockchain. 

As the entire financial system standardizes on a rich, structured data language, it becomes technically easier for blockchain networks that can speak that language to integrate with bank workflows, and over a long horizon that interoperability supports the broader adoption of blockchain-based settlement and tokenization. For payments-focused crypto projects, being able to work with the standard banks use is a real and sensible capability that may help them win institutional business over time. That is a slow, structural benefit to the ecosystem, and it is worth understanding.

What ISO 20022 is not is a catalyst that validates specific tokens or that should be expected to pump particular coins. There is no certification, no registry, no official “compliant coin” status, and no mechanism by which the standard endorses or guarantees adoption of any asset. The investment thesis that says “this token is ISO 20022 compliant, so banks will adopt it and the price will soar” rests on a designation that does not officially exist and a causal chain that does not hold, because banks adopting a messaging standard does not mean banks buying tokens. 

The disciplined reading is to treat ISO 20022 as what it is, an important modernization of financial messaging that gently supports long-term blockchain interoperability, and to treat the “compliant coin” label as what it is, a marketing narrative untethered from any official meaning. A project’s genuine technical work with the standard can be a small point in its favor. The compliance badge that crypto marketing waves around is not a reason to buy anything.

Red flags and scams to watch Because the ISO 20022 narrative is so heavily marketed and so widely misunderstood, it has become fertile ground for misleading promotion and outright scams, and knowing the warning signs protects you. The danger is not the standard itself, which is a legitimate piece of financial infrastructure, but the way its name is used to lend false authority to speculative pitches. Treat the following as red flags whenever you encounter ISO 20022 in a crypto context:

• Any claim that a token is “ISO 20022 certified,” “approved by ISO,” or “officially compliant.” No such certification or registry exists for cryptocurrencies, so this language is always misleading, and a project or promoter using it is either confused or deliberately exploiting the confusion.

• Price predictions that treat the standard as a guaranteed catalyst, such as promises that a coin will surge “once ISO 20022 goes live” or “when banks switch.” Banks adopting a messaging standard is not the same as banks buying tokens, and anyone presenting it as a sure path to gains is selling a misunderstanding.

• “ISO 20022 coin list” promotions that bundle a group of tokens as uniquely positioned to benefit, often used to pump lower-quality assets by association with the more credible names on the list. The list has no official status, and inclusion confers nothing.

• Urgency and exclusivity, such as claims that you must buy before a specific adoption date or miss a once-in-a-lifetime window. Genuine infrastructure modernization unfolds over years and does not create the kind of dated price triggers these pitches invent.

• Sources that conflate Ripple’s corporate standards work, or any company’s, with token-level compliance. A company engaging with standards bodies is real; the leap to “therefore the token is endorsed” is the exact sleight of hand to distrust.

The broader risk is financial. People have bought tokens primarily because of the ISO 20022 label, expecting bank adoption to drive prices, and that thesis rests on a designation that does not officially exist. If you are considering an asset associated with the standard, evaluate it on its actual fundamentals, its technology, adoption, team, and tokenomics, exactly as you would any other, and disregard the compliance badge entirely, because it carries no real weight. As with anything in crypto, never invest money you cannot afford to lose, be skeptical of any pitch that promises certainty, and remember that the louder a narrative is marketed, the more carefully it deserves to be checked.

Frequently Asked Questions What is ISO 20022 in simple terms? ISO 20022 is an international standard that defines a common, structured language for the electronic messages financial institutions send one another, covering payments, securities, and other transactions. It replaces older, rigid message formats with richer, machine-readable data, so that a payment message can carry detailed, clearly labeled information that systems can process automatically. It is a messaging standard for banks and payment systems, not a rule about cryptocurrencies, and it has nothing inherent to do with any token.

Why are banks adopting ISO 20022? Because the older message formats carried so little structured data that they created constant friction: incomplete information, manual intervention, errors, and difficulty with automated compliance screening. ISO 20022 carries rich, structured data that lets far more of the payment process happen automatically and accurately, improving speed, cost, fraud and sanctions screening, and reconciliation. The world’s core payment rails, including the main global bank messaging network and major domestic settlement systems like the United States Fedwire, have migrated to it because the benefits justify the enormous coordinated effort.

What are “ISO 20022 coins”? It is a label, circulated across crypto media and social channels, applied to a list of tokens, commonly XRP, XLM, ADA, ALGO, HBAR, and a few others, that are marketed as being compatible with or “compliant” with the standard. Around this label grew an investment thesis claiming that because banks are adopting ISO 20022, they will adopt these tokens, driving prices up. The label has fueled significant speculative interest, but it does not correspond to any official certification or status, which is the central problem with it.

Is the “ISO 20022 compliant” label real? Largely no. There is no certification process or registry for compliant cryptocurrencies, because the standard is a messaging format for institutions and has no mechanism for validating or endorsing tokens. Language like “ISO 20022 certified” or “endorsed by ISO” is marketing and is misleading or false. A project can do genuine engineering to make its systems compatible with ISO 20022 data, which is a real but modest technical capability, but that is very different from an official compliance badge. No authority approves or registers tokens under the standard.

Is XRP actually ISO 20022 compliant? Not in the way the hype implies. Ripple, the company, truly engages with financial messaging standards bodies as part of building institutional payment infrastructure, which is why XRP tops most “ISO 20022 coin” lists. But Ripple’s own chief technology officer has stated plainly that XRP, the token, has nothing to do with ISO 20022. The standard concerns how institutions message each other; XRP is a separate digital asset. A company working with messaging standards does not make its associated token a certified ISO 20022 instrument, so the token level compliance claim is a myth, even though Ripple’s standards work is real.

Should ISO 20022 affect which tokens I buy? Not on the basis of the compliance label, which does not officially exist. ISO 20022 is a genuine, long-term tailwind for connecting traditional finance and blockchain, and a payments project’s real technical compatibility with the standard can be a small point in its favor. But the standard does not validate, endorse, or guarantee adoption of any token, and banks adopting a messaging standard does not mean banks buying coins. Treating an “ISO 20022 compliant” label as a reason to expect price appreciation means relying on a designation that does not exist and a causal chain that does not hold.

This article is educational information, not investment advice. It aims to clarify a widely misunderstood topic, and details reflect reporting available as of June 26, 2026. Verify current information from primary sources, and be especially cautious of marketing language that implies official certification where none exists.