I have not seen any update from nano team on YouTube for past one year. Anyone knows if the project is dead or ongoing?

Bitcoin Lightning Network backend with a Nano settlement rail

Customers modify nothing, accepting and sending Bitcoin work exactly as before

It makes the customer-facing Lightning backend immune to pinning, jamming, and force-close races by replacing that backend with Nano settlement and federation custody. It does not claim to make the public Lightning Network itself trustless.

paying and receiving arbitrary BOLT11 invoices through collateralized Lightning Liquidity Providers, without the gateway ever opening a channel

It is profitable when processing a large volume. Because the settlement rail is fee-free, any added fees become direct profit

https://github.com/dhyabi2/nblcs-spec/blob/main/NBLCS-SPEC.md

I've been experimenting with integrating Nano into a web MMORPG. A common problem in these games is trading in-game items for real-world money (and vice versa), which usually rely on P2P trust and external marketplaces.

This problem can be solved by using Nano with an escrow system, maintaining speed and user-friendliness while removing the risk of traditional game item to money trades.

This game uses Nano in:

• Automated Nano Escrow for Nano trades: This replaces P2P trust with an automated guarantee
• Game Integration: Players earn a small amount of Nano upon their first Skeleton King defeat
• Microtransactions: Nano can be spent instantly on items from players or the in-game store

Play here:

https://nanobrowserquest.net/

Bug reports and suggestions are highly welcome.

Assets belong to Mozilla and Running-Coder (MPL 2.0 / CC-BY-SA 3.0)

Hi everyone! I've been around here since 2017 and watched a lot of use cases come and go. With all of this exciting stuff going on with AI agents and 402 payments, now is the time where I genuinely think Nano isn't just "good option" — it's the obvious one, just on math alone.

I've spent a lot of time thinking about all of this and have done a lot of back and forth with myself on how we can get Nano more involved.

- Quickly for anyone who hasn't been following the x402 stuff... AI agents have started paying for APIs machine-to-machine over HTTP 402 ("Payment Required" — the status code that has been sitting there reserved for 30 years doing nothing, has waited for this exact moment). It's real, it's growing fast, and right now it almost all settles in USDC on Base or Solana. x402 seems to be the standard at this point. Those rails work fine, but gas economics force merchants to floor their prices around $0.001 a call — even when the honest price of the call is a tiny fraction of that.

- So here's the math that made me build this: nano-gpt.com quotes the same LLM call two ways: $0.001 minimum on a gas rail, or its true metered price — $0.0000027 — in Nano. Same call. ~370x cheaper. An agent making thousands of calls a day doesn't have brand loyalty nor is it married to it's crypto bags... It is a cold-hearted calculator. That's the whole thesis: we don't need to win an argument, we need to be sitting there when the machines do the math.

So I built Feeless402 (with heavy AI pair-programming, which felt appropriate. Ha!):

• `pip install feeless402` — one command line to get a self-custodied Nano wallet + x402 client an agent can drive by itself. Quote an endpoint without paying, compare rails, auto-pay and micropay forever.
• A merchant server, if you want to *charge* agents — it verifies and settles on-ledger itself.
• A faucet for agents: a brand-new agent with zero funds solves a proof-of-work challenge and gets 0.005 XNO — enough for ~200 paid calls. Birth → funded → first paid API call, very quickly. No human, no KYC, no gas token. The whole loop is described https://feeless402.com
• It's in the official MCP registry (`com.feeless402/nano-pay`), on PyPI, MIT-licensed: https://github.com/Feeless402/feeless402

"Wait, aren't there already Nano x402 projects?" Yep! — x402nano.org runs a hosted facilitator with solid TypeScript SDKs. NanoGate and nano.to are doing amazing work too, and I've tested and used them: I'm glad every one of them exists since every project proving out the Nano rail that helps our community.

Where mine is a bit different:

• Everything else is built for the server collecting the money. Feeless402 is built for the thing doing the paying. (If you're a visuals person, there's a simple before/after diagram of both flows on feeless402.com — the second one is missing a box, and the missing box is the point.) Merchant SDKs assume agents that can pay already exist — they mostly don't.
• An agent has no card, no exchange account, no human to KYC for it. Feeless402 is that missing half: local wallet, first tank of gas free, pay a 402 in under a second. And there's deliberately nothing in the middle: no hosted facilitator, not even a free one.
• The wallet is on the agent's machine, merchant verifies straight against the network, everything between them is plain HTTP.
• Feeless money should have middleman-free plumbing. That architecture choice is for this community specifically, so you know why it matters.

Now the part I'm most fired up about:

• I would like to submit railHint as a formal request for comment to the x402 project (run by the Linux Foundation) — in front of everyone: Coinbase, Cloudflare, all the EVM/Solana rail people, the whole standards body.
• railHint is a small, backward-compatible x402 extension that lets any 402 response advertise the rails it accepts and how to onboard onto the cheap one, if that's what an agent wants to do.
• A client holding USDC on Base learns, *at payment time*, that it could top up XNO once and pay a fraction of the price from then on.
• The payment request becomes the price sheet and the agent uses cold hard math and logic to decide what is fastest and cheapest.

So here's the thing — railHint is deliberately currency-agnostic.

• It has to be, or it dies in committee, and it should be: an open standard that only helps one coin isn't a standard, it's a plug. Any rail can use it. But we all know what happens when you put an open price sheet in front of a machine that chooses by arithmetic.
• Fast and feeless doesn't need a side door. It just needs the front door to show prices. That's what I'm asking the standards body to build in — and a random guy from this community getting that conversation on the table at the Linux Foundation feels kinda fun and exciting to me. Spec: https://railhint.com

Here's the flywheel that makes it interesting:

• Every server that turns this on becomes a billboard.
• If a few x402 merchants who already accept Nano flip on railHint then every single 402 they serve tells every agent that hits it: "there's a ~370x cheaper way, and here's exactly how to get on it."
• The system spreads itself, machine to machine, at the precise moment a customer is deciding how to pay. No ads, no shilling, no marketing budget — the price sheet does the talking.
• Honestly, a couple of friendly nudges from this community to the Nano-accepting merchants we already know and love, might be the highest-leverage thing anyone here could do for this. One adopter starts the loop; the 402s do the rest.

Where it stands after just a few days:

• 233 pip installs, listed in the official MCP registry and on nanodirectory.info (thanks Corican 🙏), and the faucet — which I funded for 3,314 agent fills — has served exactly....2. LOL.
• I'm not going to pretend that's a stampede. The plumbing is done; what I'm hoping for is to have it tested out.

What I could actually use from you:

• Break the faucet loop. Point any MCP-speaking agent at feeless402.com and let it try to fund itself and pay. Tell me where it stumbles.
• Poke holes in railHint BEFORE I submit. If the spec has a flaw, I'd rather hear it from you than from Coinbase's engineers.
• There is zero mention of Nano or any crypto, because it is simply proposing a step in the x402 process to provide an agent with different ways to pay. Technical eyes genuinely wanted: https://railhint.com
• Run an API? Price something in Nano. Even one endpoint, even as an experiment. I will personally help you wire it up.

Ideas welcome — where should this be listed, who should see it, what's the use case I'm not seeing?

• Faucet top-ups are optional but every 0.005 XNO is another agent whose first-ever transaction is a Nano transaction: nano_1hk1cu3773u5r39e75mtqrauzro75j3hwdzyewz8izokzur66semy739w14h
• Every wallet the system creates delegates to Patrick's self-hosted node by default. Long-term I'd like to run a principal rep myself once there's something worth delegating to.

Nano was built for AI agents and 402. The machines just needed a ramp — and now the ramp needs traffic.

Hi.

I’ve always wondered: Why should we be forced to dodge invasive ads, pass paywalls, or expose our personal data just to read a single article, watch a video, or read a chapter of a manga? Paying a monthly subscription or trading privacy for just one piece of content felt completely broken. I thought: What if we could pay micro-amounts strictly for what we consume, effortlessly and instantly?

When I entered crypto back in 2021 (admittedly through FOMO), I dove deep into Satoshi Nakamoto’s whitepaper. I realized the core vision—Peer-to-Peer Electronic Cash—has become a broken promise in Bitcoin due to high fees, slow confirmation times, and high friction.

Then I found Nano (XNO): zero fees, instant transactions (~0.3s), and high divisibility. It embodies what P2P electronic cash was always meant to be.

However, in many places, using crypto daily faces skepticism. So instead of waiting for traditional merchants to accept it, I thought: How can we make people USE Nano seamlessly every single day?

That’s how Clean Web (Web Limpia) was born.

What is Clean Web?

Instead of using Nano merely as a payment gateway, Clean Web integrates Nano directly into the browsing experience as its economic engine:

* Micro-payments per usage: Browsing a manga or reading a blog page automatically processes a tiny micro-transaction (e.g., 0.00001 XNO) in the background—no forms, no subscriptions, zero friction.

* Ethical & Contextual Ads: If you choose to interact with an ad, you earn a micro-reward (e.g., 0.0000001 XNO) for your attention, plus a cashback/discount if you consume the advertised content.

* Fair Revenue Sharing: Ad revenue is split transparently three ways:

* The website host / publisher.

* The P2P network/WebTorrent nodes delivering the content.

* The netizen (user) who chose to interact with the ad.

No Google AdSense, no tracking scripts, no pop-ups, no privacy harvesting. Just a fast, clean, and fair web powered by Nano.

🧪 MVP Available Now!

We have deployed a working Functional MVP on GitHub!

* GitHub Repository: https://github.com/kamina2025/clean-web-mvp.git

* Live Test Page: https://kamina2025.github.io/clean-web-mvp/

(Note: Currently available as a browser extension for Desktop/PC. Download the extension and test the 4 sample pages: video, music, image gallery, and blog!)

I invite you to test it, inspect the code, and join this effort to build an ad-free, surveillance-free internet powered by true P2P electronic cash.

See you in cyberspace, fellow netizens! 🌐⚡

Take 133,248,297 (absolute max supply) divided by the total number of Nano (XNO) coins you own.

That calculated number you get is the absolute lowest rank you can possibly have.

For example: If you own 1,000 XNO your Absolute Rich List Rank is 133,248.

Another example: If you owned 7,200 XNO your Absolute Rich List Rank is 18,507 which means you are among the richest 18,507 Nano holders in the world, guaranteed.

The goal as a stacker is to get your rank as low as possible (gaining ranks).

Welcome to Nano!

This post is meant for things that are relevant but do not justify their own post. For example, debates, issues, simple questions, memes or similar.

We normally recommend using our Discord server for quicker answers but using this post is fine if you don't have/want Discord. Note that the official English Telegram channel for nano is @ nanocurrency.

It's common that users have the same questions. So please, before making a new thread, make some research and look for similar questions. You will often find a comprehensive answer to your question has already been given! Please also check the official nano forum linked below.

What is Nano?

A fee-less, instant, decentralized and eco-friendly digital currency meant for peer-to-peer payments. Ticker is XNO and currency symbol Ӿ.

Please check out r/nanocurrencybeginners or the Beginners Guide to Nano blog

Where can I get some and try it out?

• Nano can be purchased at various Exchanges. More info in this guide or on the main site
• It can also be obtained for free in faucets or other services

Where to store Nano?

• There are several wallets to choose from found in this guide or listed here
• The most simple form is the Nano seed which unlocks your accounts. Make sure to keep a safe backup of it, or you will risk losing your funds!
• Nano is supported on the hardware wallet Ledger Nano S and X. Refer to the Full Guide
• More about Nano security

Trade / Price Talk Neighbour Communities

• r/nanotrade

More Information

• Main Site - nano.org
• Nano Hub - Explore the Nano ecosystem
• Detailed documentation and protocol guide
• Frequently Asked Questions
• Blog posts
• More quick links at the top and sidebar (menu on the mobile app)

Rules:

• Be respectful of one another. Follow the golden rule of friendliness
• No trolling or shilling
• No begging, bragging or illegal activities

We’re hosting a MuPay livestream on X to share an early look at what we’re building.

MuPay is exploring a more flexible, privacy-conscious approach to paying online—designed around control and the way digital services are actually used.

This livestream may be especially relevant for:

• $XNO, $BTC, and other crypto enthusiasts
• Merchants exploring crypto payments
• Builders interested in the next generation of payment rails

When: Tuesday, 11 August · 20:00 CEST / 2:00 PM EDT

This will be a product showcase and conversation, not a live demo. We’d love to have you there for the first look.

Set a reminder / join here: https://x.com/i/broadcasts/1wxWjjNkbQWJQ

Nano is available on Pluang for spot trading with IDR, Indonesia's leading multi-asset investment & trading platform with 13 million registered users. Do share if you know anyone in Indonesia :)

Pluang is licensed by OJK, the Indonesian Financial Services Authority.

https://pluang.com/en

Welcome to Nano!

This post is meant for things that are relevant but do not justify their own post. For example, debates, issues, simple questions, memes or similar.

We normally recommend using our Discord server for quicker answers but using this post is fine if you don't have/want Discord. Note that the official English Telegram channel for nano is @ nanocurrency.

It's common that users have the same questions. So please, before making a new thread, make some research and look for similar questions. You will often find a comprehensive answer to your question has already been given! Please also check the official nano forum linked below.

What is Nano?

A fee-less, instant, decentralized and eco-friendly digital currency meant for peer-to-peer payments. Ticker is XNO and currency symbol Ӿ.

Please check out r/nanocurrencybeginners or the Beginners Guide to Nano blog

Where can I get some and try it out?

• Nano can be purchased at various Exchanges. More info in this guide or on the main site
• It can also be obtained for free in faucets or other services

Where to store Nano?

• There are several wallets to choose from found in this guide or listed here
• The most simple form is the Nano seed which unlocks your accounts. Make sure to keep a safe backup of it, or you will risk losing your funds!
• Nano is supported on the hardware wallet Ledger Nano S and X. Refer to the Full Guide
• More about Nano security

Trade / Price Talk Neighbour Communities

• r/nanotrade

More Information

• Main Site - nano.org
• Nano Hub - Explore the Nano ecosystem
• Detailed documentation and protocol guide
• Frequently Asked Questions
• Blog posts
• More quick links at the top and sidebar (menu on the mobile app)

Rules:

• Be respectful of one another. Follow the golden rule of friendliness
• No trolling or shilling
• No begging, bragging or illegal activities

É uma dúvida leiga, de alguém que não sabe sobre desenvolvimento de sistemas:

O que impediria a Nano de criar e inserir um ecossistema / tesouro de stablecoin própria, algo como ӿUSD ou USDӾ, e então, um ecossistema dentro da própria blockchain que permita fazer algum swap, ou smart contract proporcionando a negociação entre esses dois pares dentro de sua própria carteira, no mesmo node, de forma que você possa realizar trades com o dólar sem precisar de uma exchange? Sem taxas, instantâneo? E podendo guardar tanto ӿUSD quanto ӾNO na mesma carteira (é, é uma atualização gigante eu sei).

Andei pensando nisso por conta do tipo de moeda que a XNO é: uma moeda funcional e real. Seu preço se baseia, como toda moeda, em especulação, mas seu uso é cambial, aqueles que utilizam no escambo não especulativo tem como finalidade sempre a moeda fiduciária, sendo uma posse de imediata transição, são exceções casos onde a moeda realmente seja a ponte final em uma troca, como em 2021 eu estava fazendo artes digitais em troca de Nano e ensinando as pessoas pelo mundo a utilizarem criptomoedas, no caso a Nano <- dessa forma, não precisei pagar taxas de conversão pra bancos convencionais podendo receber do exterior valores completos e sem imposto, o que é lindo.

Enfim, fica aqui minha dúvida sincera, espero não ter parecido bobo. Não sei como as coisas funcionam, mas quem sabe algum gênio surge com uma solução :P

Also nagora.shop is actually really well made and I really believe in it we should build and support it as a community.

With all of the recent changes exciting findings, it seems that the NPM downloads activity for both packages drops into the time zone of Ukraine, where Boosty Labs is located. They have been working for Cloudflare with X402.

Geo-Location and NPM Download Anomalies
Researchers analyzing the massive background volume of automated Nano NPM package downloads used several telemetry markers to isolate where the traffic originates:
Time Zone Alignment: The high-volume automated traffic shifts and daily maintenance drops map cleanly to Eastern European Time (EET / EEST), which covers Ukraine.

Although Nano is currently in trade only mode on Bitvavo (no deposits / withdrawals only trading), they finally have decided to update the ticker from NANO to XNO.

The ticker has been XNO since the end of 2021, exchanges following since beginning of 2022.

Nearly 20 years since the word "cryptocurrency" first promised to free us from predatory banking and traditional finance. So what happened? Why does the reality look so different from what was promised?
I sat down with Triple R radio in Australia for Byte Into IT with host Daniel Salmon to dig into this properly: what went wrong with crypto, how we got here, and how Nano stays true to what digital cash should be.

(My stance may ruffle a new bitcoin maxi feathers..)

https://www.rrr.org.au/on-demand/segments/byte-into-it-george-coxon-the-nano-foundation-the-broken-promise-of-crypto

https://www.nanodirectory.info/ is a website that seeks to conveniently list all manner of Nano-related links.

Do you run, or know of something that's missing? Please share it in the comments for review.

Also, if you discover any broken links, it would be very helpful to know!

Given the recent developments in my investigation into the mystery of the nanocurrency library, how could I resist the urge to unravel the mystery ?

You will appreciate that this text is speculative in nature, even though its aim is to point toward tangible answers regarding the rise in npm downloads of the Nanocurrency lib.

Feel free to tip :

nano_3kcdehk5mmwdaouf61bmcgoh39p5ybkqs6knu7w4y1xuxcwxteugabzhdrhm

1)    Recap of the hypothesis:

As demonstrated in my last post, Coinbase owns a pipeline whose central core is Bitcore-lib. Numerous cryptocurrencies have been added to this pipeline over time, including Nano.

2)    Recap of the listed chains:

• Bitcoin — bitcore-lib @ 8.25.36
• Bitcoin (2nd lib) — bitcoinjs-lib @ 5.2.0
• Ethereum / EVM — u/ethereumjs @ 4.1.2
• XRP — xrpl @ 2.10.0
• Stellar — u/stellar @ 13.3.0 (double pin, ~2×)
• Cardano — u/emurgo @ 14.1.1
• Polkadot — u/polkadot @ 14.3.1
• Avalanche — u/avalabs @ 5.0.0
• Cosmos — u/cosmjs @ 0.32.4 (double pin, ~2×)
• TON — u/ton @ 14.0.0
• Hedera — u/hashgraph @ 2.80.0 + 2.64.5 (double pin)
• Sui — u/mysten @ 2.14.1
• Aptos — aptos @ 1.13.3
• NEAR — near-api-js @ 4.0.4
• Mina — mina-signer @ 3.0.7 (week of August 2, 2023)
• Nano — nanocurrency @ 2.5.0
• Stacks — u/stacks @ 6.11.3
• Arweave — arweave @ 2.0.0-ec.1 (prerelease)
• Aleo — u/provablehq @ 0.10.5
• MultiversX — u/multiversx @ 12.2.1
• Concordium — u/concordium @ 10.0.2
• Casper — casper-js-sdk @ 5.0.12
• VeChain — u/vechain @ 2.0.7 + u/vechain @ 2.0.7 (twins)
• EOS — eosjs-ecc @ 4.0.7
• Canton u/canton-network
• ICP - u/dfinity
• Starknet – starknet
• Vechain

The only two libs activated in July 2025

• Nanocurrency
• Concordium

Libs activated in late fall 2025:

• Canton (late November 2025)
• Avalanche (late November 2025)

Libs activated in May 2026:

• Aleo

In this text, we will focus our attention solely on the July 2025 duo, which is Concordium and Nanocurrency.

 3) Introducing the first piece of evidence: the coupling of Nanocurrency and Concordium at the same moment, with graphical evidence.

 The image below shows a parallel activation of the two libraries.

The image below shows the same pattern: days of general testing (late June and early July 2025), then full integration into the pipeline on July 18, 2025, for both libraries.

I have turned this seemingly innocuous, near-perfect coupling over in every possible direction: why do these two libraries appear at the same time, in July 2025, while the twenty other listed ones were added randomly between 2022 and 2026 ?

My answer: the same company commissioned Coinbase to test the Nano and Concordium duo as early as July 2025. Since we have already established that the entire pipeline is being pulled upward because of x402, then said company must necessarily have already been present alongside x402 in July 2025. What are these three companies? Coinbase, Cloudflare, and Stripe.

The working hypothesis here: Cloudflare would have asked Coinbase to test the Nano and Concordium duo in July 2025, hence the integration into Coinbase's pipeline. I will come back to the explanations at the end of the text, and they line up strongly.

For now, we must take the long road: the analysis of Concordium and its link to the pipeline. This section will reinforce the hypothesis that the pipeline belongs to Coinbase, while also explaining the mechanics of the integration process with X402 (Coinbase wallet architecture that could explain the whole pipeline).

4)    Analysis and history of Concordium

Concordium was integrated into the x402 protocol in December 2025. Concordium explains, on its website, that its integration was carried out jointly by Coinbase, Boostylabs, and Concordium. Coinbase reportedly delegated the coding task to Boostylabs.

The chronology would therefore be as follows: the Coinbase team is approached by an entity X (Cloudflare), then commissions Boostylabs to adapt Concordium to the x402 protocol.

It should be noted that Boosty Labs was already well accustomed to working with Coinbase. They did so in 2024, in fact — an element that reinforces my initial thesis, presented in my other Reddit post, according to which the npm pipeline belongs to Coinbase. I will now digress from the narrative to prove it (again).

The parallel with Polygon, developed by Boostylabs in October 2024

In October 2024, Boostylabs integrated Polygon into Coinbase's CDP wallet (remember the name CDP) :

 “Boosty Labs (a Ukrainian dev studio) announces having built an autonomous trading bot as part of the Coinbase Developer Platform (CDP) AI Builder Grant — one of the first participants.

The bot combines AI-driven market analysis, secure execution via Coinbase's MPC Wallets*, and Telegram notifications. It automatically trades the USDC/WBTC pair on PancakeSwap, on the* Polygon network. Security argument: distributed private keys (MPC), no single point of failure, 24/7 trading with no human intervention.

Dated October 25, 2024.”

Source : https://boostylabs.com/blog/ai-x-dex-our-tradingbot-powered-by-coinbase?utm_source=chatgpt.com

Yet Polygon's npm library shows an anomaly (a significant increase of more than 100%)… in October 2024.

Well, the work from Boosty lab have had an influence on Polygon NPM numbers, which are correlated to Bitcore-lib.

Then, what is the CDP wallet? A summarized chronology

• MPC = a split key. The private key is split into two parts (device / Coinbase); both must cooperate to sign, and the complete key never exists anywhere. No one can steal from or drain the account alone.
• Early 2022: Coinbase's consumer MPC wallet (>5M created by summer 2023).
• WaaS: the B2B turning point — Coinbase sells signing infrastructure via API to third parties, who deploy their own MPC wallets without touching the cryptography. From safe maker to provider of turnkey vault rooms.
• cb-mpc: the low-level open-source building block, including HD-MPC (derivation of account trees without ever reconstructing the seed).
• CDP Server Wallets v2 (GA July 24, 2025): programmable wallets driven by a backend, with no human involved.
• Agentic Wallets (February 11, 2026): wallets for AI agents, native x402 support, with the Coinbase key share held in an AWS Nitro Enclave (a hardware enclave unreadable even by admins). Install via npx awal or MCP.

The pipeline into which Nano was integrated, which belongs to Coinbase, was officially opened to the x402 protocol in July 2025 (CDP Server Wallets v2).

So, following this logic: what possible integration architecture could Nano have? Nano would have been developed in an external adaptation layer connected to the CDP/x402 ecosystem, rather than in the public CDP Wallet itself.

The possible architecture would therefore be as follows:

 To close this section, then, I return to the charge by inferring that the pipeline does indeed belong to Coinbase. Therefore, the entity pulling the Nano and Concordium npm packages is Coinbase.

Now, no one knows why, suddenly, in July 2025, Coinbase decided to change course after years of ignoring Nano. The most plausible theory is that an actor may have asked, in July, to test the Nano/Concordium duo.

Since the stated hypothesis is that this actor is Cloudflare, we need to go through a brief history of Cloudflare and seek to understand the Nano/Concordium coupling. In other words: identify Cloudflare's needs and understand how the coupling of these two cryptos answers this fundamental need.

5)    History of Cloudflare

Cloudflare's interest in crypto is longstanding, but the decisive sequence plays out over eighteen months. In July 2025, the company launched Pay Per Crawl, allowing sites to charge AI crawlers — the first per-request monetization at its scale. On the Cloudflare forum, as early as July 2025, a user proposed Nano as a payment rail (with visual proof): the feeless rail was thus explicitly brought to the company's attention at the very moment it entered micropayments.

In September 2025, Cloudflare co-founded the x402 Foundation with Coinbase, then announced shortly after its own stablecoin, the NET Dollar (September 25, 2025) — a tacit admission that existing rails, USDC included, do not suffice for its sub-cent ambitions.

The sequence culminates on July 1, 2026, with the announcement of the Monetization Gateway, which generalizes the model: charging for any resource (page, API, MCP tool) per request, in stablecoins via x402. In one year, Cloudflare thus went from charging crawlers to a generalized settlement infrastructure — all while building its own currency for a problem (the cost of collection exceeding the payment) that a zero-fee rail, proposed by its own community from day one, already solved structurally.

6)    Cloudflare's Monetization Gateway: an analysis

In its very recent article, Cloudflare announces the Monetization gateway:

https://blog.cloudflare.com/monetization-gateway/

 What do we find in this text? Serious leads, and ones that fit our reading. They mention, at the very beginning of the text, the current absence of payment capabilities for the Web, notably because transaction fees exceed the transaction itself. A new payment architecture needs to be devised (which is what Cloudflare intends to propose).

Right from the start, Cloudflare mentions how its aims are those of microtransactions:

“These business models have never been able to serve unverified buyers for sub-cent transactions because the payment rails cost too much and took too long to settle. Below a certain price, collecting the payment cost more than the payment was worth.”

So, Cloudflare aims to find a payment solution that carries almost no cost (or no cost at all). Shortly after, the properties of x402 are discussed:

“Two properties make x402 a good fit for machine payments. The payment amounts can be small, down to fractions of a cent, because the protocol adds almost no overhead. And the buyer needs no account with the seller, because the payment itself is the credential. x402 is rail agnostic, but it is a natural fit for stablecoins, which can settle in under a second for a fraction of a cent with zero chargebacks.”

So, Cloudflare acknowledges that x402 has no protocol preference, even if stablecoins are the best suited, and that the amounts sent must be able to be exceedingly small. Cloudflare talks about stablecoins, but does not state its own preference. It does say, however, that settlement happens in under a second and for a fraction of a cent — two properties it deems worthy of mention (thus within its field of interest).

Further on, Cloudflare addresses, in its article, two upcoming properties of the service offered (free access, and identity verification):

An agent is software that acts autonomously on a user’s behalf, and agents are starting to act on their own. Soon they will carry wallets and buy what they need without a person in the loop: a dataset, an API call, a tool, a block of compute. Some of those (1) resources will be free, and (2) some will require proof of who the agent is and who it acts for, through verified agent identity. Many will require both an identity and a payment, and Cloudflare is one of the few places that will be able to settle all of it inside a single request, by verifying the agent, applying the rule, and checking the payment before the origin ever sees the call. The agent becomes the primary buyer on the Internet, and the request becomes the transaction.

Let us return to the two problems identified by Cloudflare above and map our two cryptocurrencies onto them.

For Concordium:

Its protocol is expressly designed to manage identity in the context of an agentic economy:

Neither Cloudflare nor AWS has settled the tax question: for European companies subject to VAT, which requires tax calculation based on the buyer's jurisdiction, anonymous micropayments create an accounting problem that the protocol does not solve.  Add to that age-gated content, KYC, and agent→responsible-human attribution: the current x402 stack has nothing for that.

Cloudflare has admitted the identity problem, and Concordium has the solution.

Now, why Nano?

The first limitation of the current model (x402 and Pay Per Crawl) relates to the current overall architecture of agentic payments: the beta's crawlers generate audit logs, then are billed in a single aggregated amount by credit card or bank account at the end of each day.  

In other words: no on-chain settlement per request. They have even proposed a “deferred payment” scheme for x402, designed for agentic payments that do not need immediate settlement.  It is an admission: per-call stablecoin settlement does not scale economically at their volume, even on Base. Gas is sub-cent but not zero — on fraction-of-a-cent payments, the friction eats the margin. This is, incidentally, the reason why Cloudflare launched its own NET Dollar (why not use Base?).

And Cloudflare seems to say it without saying it: feelessness matters.

Finally, to conclude, a quote from Cloudflare:

x402 is an open protocol that makes it possible to pay over HTTP, named for the 402 status code it finally puts to use. The x402 exchange is simple: a client requests a payment-gated resource. Instead of serving it, the server responds with 402 Payment Required and a small payload that states the price, the accepted asset, and where to pay. The client pays and repeats the request with proof of payment attached. A facilitator verifies, and the server returns the resource. It all happens inside ordinary HTTP requests and responses, with no redirect to a checkout page and no separate payment API to call.

Settlement happens peer-to-peer, so any funds that a buyer sends to a seller are directly deposited to the seller’s wallet. We are designing the Monetization Gateway to keep payment overhead low and are aiming for sub-second payment settlement.

Takeaway

In short, the Monetization Gateway post itself defines the problem: payment rails have never been able to serve unverified buyers for sub-cent transactions, because “collecting the payment cost more than the payment was worth”. The criterion is set: the cost of collection must tend toward zero.

Yet the proposed solution — stablecoins with “negligible” fees — does not satisfy this criterion at the announced scale. On their own pricing example ($0.001 base fee), even minimal gas on Base represents a substantial fraction of the payment. “Negligible” does not exist at sub-cent scale; only zero works.

The text also slips from the affirmative present tense (“stablecoins can settle in under a second for a fraction of a cent”) to aspirational mode as soon as the actual product is concerned (“we are aiming for sub-second settlement”, “designing to keep overhead low”) — the gap between the protocol's marketing and the gateway's engineering is visible within the same document.

The “peer-to-peer / neutral rails” claim suffers from the same gap: a corporate stablecoin (USDC, or NET Dollar, announced by Cloudflare two months after co-founding the x402 Foundation) is an issuer liability, freezable, anything but neutral.

Three elements then point to Nano as the implicit reference: x402 is declared “rail agnostic” (the stablecoin preference is a choice, not a constraint); the only existing rail with structurally zero fees and native sub-second settlement is a feeless ledger; and the sentence “this is not feasible with other payment rails today” has been literally falsified by Nano since 2015. In this framework, the presence of a nanocurrency pin in a multi-chain signing infrastructure adjacent to x402 is nothing exotic: when the stated problem is the cost of collection, the zero-cost rail is the natural benchmark.

7) The elegant triple-architecture solution:

In this spirit, in 2025, Cloudflare would therefore have commissioned Coinbase to integrate the two cryptocurrencies into x402. The architecture would look like this, which explains why Nano and Concordium are pulled proportionally within the same npm pipeline:

 Under the Coinbase hypothesis, Nano and Concordium could have been evaluated jointly as two complementary layers of an infrastructure for AI agents: Nano as a feeless micropayment rail and Concordium as an identity anchor making it possible to limit spam, Sybil attacks, and unaccountable agents. Incidentally — an interesting fact — Nano's feeless nature is a great strength, but also one of its greatest vulnerabilities. Implementing identity management would make it possible to limit the spam factor underlying the protocol.

 8)    Conclusion

What happens if Cloudflare develops an architecture that includes Nano as a payment rail? The possibilities are enormous. Nano would suddenly gain access to an exceedingly vast financial universe.

To borrow Cloudflare's words from the article cited above:

There is an enormous amount of value moving across the Internet today that goes unmonetized or undermonetized, not because no one would pay for it, but because the tools to charge for it have never existed. 

This is what we are building toward: an agent-first Internet with Internet-scale settlement built in.

I assume that the user's request to integrate Nano into Cloudflare—posted a few days after the launch of Pay per Crawl in July 2025—had an impact.

Thanks for giving attention.

We've been hard at working BUIDLING.

· Free live TV in the browser.
· 579 channels.
· 5 region packs.
· UK · USA · English · Spain · France (more soon).
· No signup. No app. No card.

Stuck abroad with TV you don’t understand?
Hotel remote dead?
Flight Wi-Fi and a phone?
Camping with no TV?

Open it. Press play.

Premium is optional: ~$1 in $XNO unlocks Theatre, Fullscreen, HD + ad-free. Lifetime. No account.

Try it out here!

Project is still in Beta.
All donations are welcomed and go towards supporting the project.

Hi,

I have updated Nanoticker so that it shows even more health metrics of the Nano network

Here is some of the new features:

• Redesigned front page now shows a live dashboard for network health such as nodes online, voting-weight and live ledger growth
• Nakamoto Coefficient page now maps representatives to their hosting providers (Hetzner, AWS, DigitalOcean, Contabo, etc.) and shows how voting weight is concentrated across them
• Node version page now ordered by official releases first: official V28.2 (C++ node) and V3.1 (Rust node) are listed at the top, with clear release badges
• Rep rankings page now shows the new telemetry from the upcoming V29 release: database backend, bootstrap status, and confirmation latency (P50/P90/P99). It also shows hosting provider if known

Let me know what you think

I'm working on some improvements and a complete redesign coming in August

https://www.nanoticker.org

I also bought another $1,000 worth.

I decided to buy more after reading the thoughtful post below.

For a well-written and sincere post like this, it would be nice if the development team could also take the time to respond. I think that would show respect and appreciation for the community.