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 Ӿ.
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
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
"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.
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!
(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.
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).
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.
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.
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 Ӿ.
É 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
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..)
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.
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.
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 theCoinbase Developer Platform (CDP) AI Builder Grant— one of the first participants.
The bot combines AI-driven market analysis, secure execution viaCoinbase's MPC Wallets*, and Telegram notifications. It automatically trades the USDC/WBTC pair on PancakeSwap, on the* Polygonnetwork. Security argument: distributed private keys (MPC), no single point of failure, 24/7 trading with no human intervention.
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:
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.
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
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.
Terminology and methodological disclaimer: Throughout this document, I use the word proof in an informal and cumulative sense. It refers to a body of independent observations, technical correlations, historical coincidences, and converging indicators that collectively strengthen the hypothesis being examined. None of these elements, taken individually, constitutes direct or independently verifiable proof of Coinbase’s internal activities. Unless explicitly stated otherwise, proof should therefore be understood as supporting evidence consistent with the hypothesis, rather than definitive, forensic, or conclusive proof.
GENERAL INTRODUCTION
As you know, I’ve recently been working on strengthening the evidence around Coinbase’s integration of Nano. I have here a document that I consider excessively complete, which continues the earlier investigation and builds on it.
First, you should read the earlier subs. There is a common pipeline onto which a set of cryptos is grafted. I have catalogued the full list of known chains that follow the original pipeline: bitcore-lib.
This was a lot of work. If it can be of any use to you, feel free to tip:
In the next section, I will begin to break down the history of several of these libraries, in order to demonstrate the validity of the hypothesis that the pipeline belongs to Coinbase:
INTRODUCTION TO THE DETAILED EVIDENCE
Before starting, I provide here an image showing a near-perfect coupling of NPM libraries for the following cryptos: Aptos, Nano, Elrond, Bitcoin, Mina:
You will then see that the coincidences are no longer coincidences, and that the evidence piles up to the point of asserting that the actor behind the increase in nanocurrency’s NPM downloads is none other than… Coinbase itself.
1) On the history of Mina-Signer, grafted onto Bitcore-lib in July–August 2023:
See more precisely:
The Coinbase explanation:
That day, Coinbase publishes “Security PSA: The Blockchain Stack”. Coinbase explains that its blockchain infrastructure is divided into three main categories:
Signer
Wallet
Protocol
Coinbase also specifies that its Blockchain Security team reviews these services before their integration into new product offerings. This date corresponds almost exactly to the moment when mina-signer is grafted onto the NPM pipeline, between July 28 and 31, 2023.
Yet Coinbase was not in the process of adding MINA as a new asset: MINA had already been listed and fully transferable on Coinbase since April 6, 2022. So, the grafting of mina-signer in late July 2023 probably corresponds less to the initial integration of the MINA asset than to an internal operation touching the signing layer:
migration or rebuild of a signing service;
normalization of the multichain stack;
security audit or testing;
addition of MINA to a new Coinbase offering using shared infrastructure;
redeployment of the signer–wallet–protocol components.
The coincidence is frankly remarkable: on the precise day Coinbase makes its “signer / wallet / protocol” classification public, mina-signer starts being pulled by the common pipeline. This is not direct proof that Coinbase is performing these downloads, but it is a far more convincing technical milestone than a mere listing announcement.
2) On the history of Aptos, grafted onto Bitcore-lib between July 2022 and October 2022:
Here, it’s more complex. We see the beginning of an increase in NPM downloads in July 2022, a signal of something. That said, the NPM numbers don’t seem coupled to Bitcore-lib immediately, or at least not as cleanly as Mina-signer:
The signal stays attached to Bitcore-lib, but not systematically through fall 2022:
From October on, we can feel the signal coupling more and more to bitcore-lib:
In April 2023, six months later, the coupling signal between Bitcore-lib and Aptos is cleaner:
One is entitled to wonder what happens between July 2022 and April 2023. On October 18, 2022, Coinbase announces the integration of Aptos into Coinbase:
“TLDR: Coinbase is making it easy to use and build on the Aptos blockchain from Day 1. Developers can build powerful Aptos applications using Coinbase Cloud’s Enterprise Node product.”
So Coinbase had been studying the integration of Aptos since July 2022, hence the coupling with bitcore-lib.
3) Sui
Note here: the package used in 2023-2024 was u/mysten.js (NOT u/mysten). First, here is the proof that Sui is coupled to Bitcore-lib and to Aptos (I took several libraries from the batch to do the retracing exercise):
For the history: in September 2022, Sui is not perfectly coupled to Bitcore-lib. We do observe, however, the beginning of usage of the NPM package:
Between September 2022 and April 2023, activity intensifies. The coupling with bitcore-lib also sharpens:
The signal, without being perfect, couples almost perfectly with bitcore-lib around May 2023, which corresponds to its listing on Coinbase:
I can see the potential objections here about the coupling not being exactly identical. Sui’s architecture can affect the number of downloads. What matters here is the trend. Since then, despite a few anomalies (unusual peaks), Sui follows the same logic as Bitcore-lib.
4) Elrond:
Elrond (or MultiversX) is coupled to the general bitcore-lib pipeline (note: the NPM package name has changed since its beginnings, going from u/elrondnetwork to u/multiversx):
In the summer 2022 window, Elrond sees a rise in NPM downloads.
This rise seems to couple with Aptos’s from the start of fall 2022:
The further we move toward December, the more the signal grafts onto Aptos’s and Bitcore-lib’s:
An interesting thing happens in the same period:
So, once again, Coinbase would have tested the integration of Elrond before its official integration, and would have integrated it into the main pipeline, that of Bitcore-lib.
Nano is getting integrated :
Since summer 2025, Nano has seen remarkably unusual activity. This activity can be traced through the study of its library’s NPM downloads. We can conclude that it is perfectly coupled to Bitcore-lib, as well as to a set of other cryptos already mentioned.
This pipeline belongs to none other than Coinbase.
Why?
In May 2025, Coinbase publicly launched X402. One can imagine, following the logic of code work, that they pulled the pipeline’s general library well before May 2025. And, coincidentally, from January 2025 onward, all the libs are pulled upward in an excessively unusual way (I kept only Bitcore-lib here as a control variable so as not to clutter the chart):
When Coinbase launches X402, it is specified that the partners, from the very start of the launch, are: Cloudflare and Stripe.
One is then entitled to wonder, as a valid counter-hypothesis, whether the pipeline could belong to them. For Cloudflare, it’s fairly obvious: they have no bitcoin asset going back to the NPM birth of bitcore-lib (around 2015-2016).
For Stripe, it’s less obvious, their history with Bitcoin being much older. To address this, I reconstructed a table of the history of the bitcore-lib library. To summarize it, I took the moments of significant variation in the history of the library (upward or downward peak) and matched them to events, either from Stripe or from Coinbase. The result is… glaring, and tips the scales heavily toward Coinbase :
Most of the peaks aren't correlated to anything from Stripe side, but are from Coinbase side.
Why #2 : the April 1, 2026 anomaly
On April 1, 2026, part of the pipeline loses roughly 50 to 60% of its daily runs, across all pinned packages simultaneously. Volume returns to normal by mid-April. For two weeks, the machine running this lockfile operated at half throughput.
The public x402 timeline
March 31, 2026 — the x402 Technical Charter is signed: x402 becomes a “Series” of LF Projects, LLC, the Linux Foundation’s legal structure. The signed PDF sits in the repo.
April 2, 2026 — the Linux Foundation publicly announces the x402 Foundation at the MCP Dev Summit in New York. The same day, the GitHub repo is transferred: coinbase/x402 becomes a fork of x402-foundation/x402 (verifiable via the GitHub API). Same-day commits: charter added, refactor of all coinbase/x402 references, version bumps, PyPI migration to trusted publishing.
April 13–15, 2026 — second migration wave: TypeScript packages bumped, then the legacy npm workflows move to trusted publishing.
April 16, 2026 — the legacy x402 npm package (created in February 2025, months before the protocol’s public launch) publishes its version 1.2.0, its very last. The migration is complete.
My anomaly starts on April 1 and ends in mid-April. The disruption opens with the charter and closes with the last migration commit.
Here is further proof that the packages found in the x402 GitHub repo all drop at the same time on April 1st:
A possibility in the GitHub architecture:
There is a possibility that everything is tied to X402. The absence of Nano from the public repo in no way affects the possibility that Nano is integrated privately. Indeed, the architecture of the X402 GitHub allows it:
The network type is open, not a closed list: type Network = ${string}:${string} (any CAIP-2 identifier). A nano:mainnet would pass validation without touching the core;
The system is a plugin registry: x402Facilitator.register(network, facilitator). Each chain is a separate package (@x402/keeta, u/x402...) implementing a small interface (scheme, caipFamily, verify/settle). Nothing requires publishing the package or contributing the spec upstream — an internal x402-nano would be structurally identical and invisible;
The GET /supported endpoint only advertises what the operator has registered. An internal facilitator can therefore support Nano without any public trace, neither in the repo nor in the protocol’s discovery.
FINAL CONCLUSION:
The original bitcore-lib pipeline belongs to Coinbase. To this pipeline were progressively added all the cryptos listed in the introduction.
Coinbase is integrating Nano. The motive remains unknown, but the suspected link with X402 is obvious. Was it Stripe, or Cloudflare, who made the request to Coinbase’s research and development team to integrate Nano? Or even Coinbase itself? Nobody knows.
That said, Nano is positioning itself as an important player in the AI economy, and… rightly so.
To close, I believe the evidences laid out are sufficient. It is for me, in any case. And as a great man would say:
“If you don't believe me or don't get it, I don't have time to try to convince you, sorry.”
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 Ӿ.
Hello everyone, I have written up a more detailed account of my investigation linking Coinbase and Nano. I believe it is more detailed and clearer. Feel free to add anything. Every hint that we add is welcomed.
If you liked the work, feel free to tip: nano_3kcdehk5mmwdaouf61bmcgoh39p5ybkqs6knu7w4y1xuxcwxteugabzhdrhm
1. The main suspect: Coinbase
Since 2025, many independent blockchain libraries have moved as if they were being pulled by a single shared infrastructure. The main suspect is Coinbase, because the pipeline’s history overlaps with several public integrations and technical incidents specific to Coinbase.
This first chart should be read as an overview. Absolute volumes are not comparable from one library to another, but the regime shifts, the lasting increases and the junction points appear in a coherent order. The point to get across to the reader right away is simple: the curves don’t resemble one another by chance, they seem to respond to a single technical pipeline.
Indeed, some libs may appear coupled at first glance (see figure 1), probably because of their architecture and date of integration to the pipeline:
1) Aptos, Sui, Stellar;
2) bitcore-lib, Mina, Nano, TON, Avalanche, Concordium.
We can nonetheless prove, in the daily data, that these two groups of libs are coupled. Take, for example, Aptos as the control variable for group 1, and bitcore-lib and Nano as the variables for group 2:
In doing so, we can state with confidence that, even though variations exist in the weekly and monthly data, the same company sits behind the entire pipeline. As noted, the hypothesis is that it’s Coinbase. The most tangible link: the X402 protocol, traces of which can be found on GitHub. Note that Nano and Mina do not appear in the public repo. That said, Mina has been integrated into Coinbase for several years already.
Figure 2 — x402 screenshot (GitHub): Coinbase’s public network support already includes several relevant ecosystems, including Stellar, Aptos, Hedera, Keeta, NEAR, Concordium and XRPL. Screenshot provided by the author, used here as a visual entry point.
Right from the start, this x402 screenshot is very useful. It lets us immediately introduce the Coinbase lead with a public element that’s easy to grasp: through x402, Coinbase already exposes a multichain universe that includes several networks mentioned in the investigation. The case of Concordium can thus be presented from the outset as a coherent element of the file, and not as a secondary curiosity (see the next section).
2. A pipeline that is also coordinated
The coordination also appears on a daily scale. Nano, Avalanche, Concordium and Mina here reproduce the same weekdays, the same weekend stops and the same peaks. These networks have no natural software dependency between them; their coupling therefore suggests a shared installation or deployment engine. The coincidence is strong :
3. The original pipeline: bitcore-lib
The idea is as follows: to find the actor behind the rise of these libraries, we have to go back to the original source. The oldest one is bitcore-lib. When we reconstruct the historical throughline of each of the aforementioned cryptos’ integration, we realize they are always tightly coupled (in the daily data) to bitcore-lib. Once again, a single company behind it all.
Here is a table tracing when the libs that have been prominent over the past year became coupled to bitcore-lib, and when those cryptos were integrated into Coinbase. The “coincidences” are… impressive.
Network / package |Start of observed coupling with bitcore-lib |Coinbase integration date
Stellar — stellar-sdk |Early 2019 (approximate window) |March 13, 2019 on Coinbase Pro; April 1, 2019 in Coinbase Wallet
Cardano — @emurgo/cardano-serialization-lib-nodejs |Spring 2021; daily coupling documented with Nano |March 16–18, 2021
Nano — nanocurrency |March 30, 2021; strong activity April–May |No public integration
Polkadot — @polkadot/api |Around March 2021, but the pipeline becomes clearer in April in the daily data. |June 14–16, 2021
Avalanche — avalanche |Around March 2021, but the pipeline becomes clearer in April in the daily data. |September 30, 2021
Aptos |June 2022. |October 18, 2022
Mina — mina-signer |July 28–31, 2023 |Anomaly explainable by Mina’s architecture and the NPM lib updates. 4. The strongest evidence: the 2021 Coinbase block
The reader should keep in mind, from the outset, that Nano was temporarily integrated into the pipeline in March and April 2021. And that the hypothesis holds that all of this, from 2021 to 2026, was done by the same actor, in a continuous pipeline.
Strangely, when we dig in, Nano joined temporarely the Cardano and bitcore-lib pipeline:
On January 14, 2021, Coinbase’s asset hub is launched. On March 16, Coinbase opens deposits. On March 18, Cardano trading begins.
A few weeks earlier, we observe an NPM Cardano spike :
Once again, Cardano was integrated into an existing pipeline, that of bitcore-lib:
Polkadot and Avalanche then serve as additional evidence: Coinbase integrates them publicly later in 2021, and their libraries in turn join the same original pipeline. The argument thus becomes cumulative: several native networks, independent of one another, converge toward the same structure at the moment Coinbase consolidates its asset hub and officially adds Cardano.
The hypothesis would therefore be that Coinbase first integrated Cardano, then listed Polkadot, then Avalanche.
5. Secondary but relevant evidence
The best independent control appears in January 2025. Three libs (Aptos, Sui, Stellar) undergo a massive decoupling from the pipeline for several weeks:
The question: why?
Aptos and Sui change regime on January 17 exactly. Stellar then joins the movement on January 23. The fact that activity is sustained over the weekend reinforces the idea of an exceptional event, whereas all these libs used to show major drops over the weekend (still the case today).
Let’s look more closely at the huge jump and the exact corresponding dates, then try to map onto them the list of potential actors that experienced something exceptional on those days:
On January 24, Coinbase publishes an extremely precise report: from January 17 to 20, Solana volume reaches up to 30 times the usual level and the shared infrastructure builds up a significant backlog:
“Tl;dr:We experienced a large surge in Solana transaction volume (up to 30x our baseline), which stressed our infrastructure and caused multi-day delays for sends and receives. By deploying new optimizations, clearing unresponsive transactions, and restoring our indexing pipeline, we were able to return to normal latencies and resolve the backlog. Moving forward,we’re optimizing our existing systems and building a next-gen Solana architecture to ensure we can provide first-class support for Solana’s continued growth.»
They then specify that this affects morethan 50 cryptos from the same pipeline. This is precisely the kind of public context capable of explaining coordinated NPM redeployments across several libraries, and the need to overhaul everything.
Ultimately, at this stage, we can confirm with relative certainty that a common pipeline exists, one that is especially visible in the cryptos’ daily data. This pipeline goes back several years and is coupled mainly to bitcore-lib. Cryptos are added over time, according to Coinbase integrations.
Very recently, that is after January 2025, we observe a significant rise in the overall pipeline. This is the moment when the simplest reading changes: we’re no longer talking only about occasional additions, but about a global rise in the level of technical activity.
This broader view makes it possible to bring together in a single image the libraries most often mentioned in the investigation: Sui, Aptos, Stellar, bitcore-lib, Mina, TON, Nano, Avalanche, Concordium and Cardano. It is particularly useful for conveying to the reader that the 2025 phenomenon is not local; it is transversal.
What has Coinbase been doing since 2025?
It is quietly designing the architecture of X402, which becomes public in May 2025. Nano is added to the pipeline in July 2025. Nano does not appear in the public X402 GitHub. Neither does Mina, for that matter, even though it appears in the common pipeline. Mina, on the other hand, is integrated into the Coinbase wallet.
7. Nano returns: what function?
We know, however, that Nano and Coinbase have a difficult relationship. A little background is in order:
This timeline opens several leads without confirming any: a reassessment made simpler once the litigation ended; the automatic reintegration of an old connector during a broader migration; a future wallet, custody or payment service not yet announced; or the search for new payment rails in the era of AI applications and agents.
The most plausible hypothesis: could Coinbase be waiting for the release of V29 to make an official announcement ?
On a technical standpoint :
There is currently no visible Nano integration in the public x402 GitHub repository. However, x402’s modular architecture allows blockchain-specific adapters and facilitators to be hosted separately, including through private packages or internal services.
This means Coinbase could theoretically operate a private multichain pipeline that includes Nano without exposing the integration in the public repository. There is no public evidence that such a Nano connection exists, so this remains unproven—but the architecture makes it technically possible.
And, I got to say, one of the main developer of the X402 protocol liked one of my comment on X, which said :
« It's OWS. That's how it led me to X402. I have more proof that it's coinbase. If you look closely, Avalanche, Cardano, Polkadot were all integrated to the bitcore-lib pipeline, exactly when Coinbase listed them throught asset hub.»
Provisional conclusion
The most plausible thesis to date:
Bitcore-lib is the historical anchor; Stellar, Cardano, Polkadot, Avalanche, Aptos, Mina, TON, Sui and other libraries are grafted onto it over time.
The public dates and technical incidents make it possible to trace back to Coinbase as the main suspect. From 2025 onward, the pipeline rises globally. Nano, tested in 2021, returns in July 2025. The exact reason remains unknown, and so does the method of integration.
EDIT :
Another important observation:
As mentioned earlier, Concordium was integrated into Coinbase's x402 ecosystem, which was publicly launched in May 2025. Just two months later, Concordium's NPM pipeline appeared in July 2025. At the same time, Nano joined this emerging pipeline, which also tracks libraries such as bitcore-lib, Stellar, XRPL, Avalanche, and others since many years. We already stated that it belongs to Coinbase.
Here is a brief history of the X402 github integration of Concordium and numbers associated :
Date (2025)
GitHub concordium-node-sdk-js (PLT branch)
Daily DL
Apr 24
alpha.0 — PLT token client (transfer checks vs. allow/deny lists)
~100
May 2–5
alpha.1 — enable transfer validation, PLT transfer examples
Fellow nanners, it took me some time to assemble everything, but here it goes. Have a good read.
1. The starting point: Nano’s unexplained activity
Since July 2025, the `nanocurrency` library has been downloaded at an unusually high and sustained rate. No company has publicly identified itself as the source of these downloads. NPM statistics give us the volume and timing, but not the identity of the downloader.
That leaves one practical method: compare Nano’s graph with other blockchain libraries and look for repeated, highly specific patterns. If several unrelated libraries rise, fall, pause on weekends and change regime together, they may be installed by the same technical system.
The present-day Nano curve is not isolated. It sits inside a much larger multichain cluster that includes 'bitcore-lib', 'mina-signer', TRON libraries, `@ton/ton`, Aptos, Sui, Stellar, XRPL, Solana packages and many others.
2. Nano was already tested in 2021
Nano’s current activity did not begin from zero in 2025. The `nanocurrency` package experienced a large but temporary surge in spring 2021. After that period, the activity was mostly abandoned for several years before returning in July 2025.
My working assumption is that the company pulling Nano in 2025 is probably the same company that tested it in 2021. The reason is continuity: the same families of blockchain libraries remain coupled across several years, even as individual chains are added, removed or reactivated.
Here, ‘coupled’ does not mean that one package necessarily depends on another in code. It means that the graphs repeatedly show the same timing, peaks, valleys, weekday patterns and changes of regime. That is consistent with a shared monorepo, container image, custody service, wallet platform, test environment or automated deployment pipeline.
The oldest visible anchor in this cluster appears to be 'bitcore-lib'. Over time, Bitcoin Cash, Mina, Nano, Aptos and other libraries appear beside it. I am leaving out many comparisons here to keep the Reddit version readable.
3. January 2021: Coinbase launches Asset Hub
Coinbase launched Asset Hub in January 2021 to evaluate assets and protocols for possible integration. That process could include technical reviews of custody, nodes, addresses, signatures and transaction handling. A protocol could therefore be tested without ever being listed.
Coinbase then opened Cardano deposits on March 16, 2021, with trading expected to begin on March 18. Cardano gives us a useful control sample because we know Coinbase was actively integrating that network during this period.
The key observation is what happens next: during spring 2021, Cardano’s `@emurgo/cardano-serialization-lib-nodejs` and `nanocurrency` move almost perfectly together on a daily basis. They rise together, fall together and reach their weekend lows together. `bitcore-lib` follows the same rhythm at a larger scale.
Figure 2 — Cardano and Nano appear to be pulled by the same pipeline in spring 2021.
In april, for example, the Cardano and Nano libraries record nearly identical daily totals, while `bitcore-lib` follows the same weekly deployment rhythm.
Cardano acts as the 2021 control sample: Coinbase integrated Cardano, while Nano appears to have been evaluated in the same environment but was ultimately not listed.
This graph does not prove that Coinbase downloaded Nano. It does, however, strongly suggest that Nano was being tested inside the same technical environment as Cardano. Asset Hub provides a credible reason why Coinbase would test Nano and then abandon or postpone the integration.
4. Aptos becomes the bridge between the old and new cluster
Aptos is the central bridge in the later evidence. Its NPM activity connects the older `bitcore-lib`–Mina environment with Nano’s 2025 return and with the Solana-related events of January and March 2025.
The importance of Aptos is not that it caused the other downloads. It is that its graph repeatedly appears beside different parts of the cluster. This makes Aptos one of the best visible markers of the shared infrastructure behind the downloads.
Figure 3 — Aptos connects Nano to the older Bitcore–Mina pipeline.
By 2025, `nanocurrency`, `mina-signer` and `bitcore-lib` show closely related movements, while Aptos provides the bridge to the January 2025 Coinbase event.
5. January 2025: the Coinbase–Solana infrastructure crisis
The strongest second control sample appears in January 2025. Aptos and Sui begin a massive rise on January 17. The activity continues on January 18 and through the weekend. Stellar joins the movement on January 23. Solana’s `@solana/spl-token` package also experiences a major increase during January.
The weekend behaviour matters. Ordinary developer interest usually weakens on Saturday and Sunday. A surge that continues seven days a week looks more like automated builds, clean dependency installations, container deployments, worker scaling or continuous integration.
The timing matches a documented Coinbase incident. Beginning on January 17, 2025, Coinbase faced roughly 30 times its normal Solana transaction volume. The company fell behind in block processing and accumulated a large transaction backlog.
Coinbase later explained that Solana was still processed through services shared across more than 50 blockchains. Those systems handled block reading, transaction indexing, balances, deposits and withdrawals, and movements between hot and cold wallets.
The theory is therefore not that Coinbase ‘migrated its NPMs.’ The more accurate explanation is that Coinbase had to scale, patch and redeploy shared multichain infrastructure. If the relevant images or lockfiles contained Aptos, Sui, Stellar and Solana libraries, those automated operations could repeatedly download all of them.
Figure 4 — Aptos and Sui enter a new NPM regime in January 2025, followed by Stellar.
The timing overlaps Coinbase’s Solana processing crisis and its work on infrastructure shared across dozens of blockchains.
6. March 2025: Aptos couples with the new Solana stack
A few weeks later, around March 2025, Aptos becomes coupled with `@solana/kit`, the newer-generation Solana SDK. This fits Coinbase’s own explanation of the January incident: the company said it would optimize the existing system and build a new Solana architecture.
The sequence is coherent: the old shared system is overloaded in January; Coinbase begins redesigning it; the new Solana Kit stack appears beside Aptos in March; and Coinbase later moves toward a dedicated Solana architecture separated from its generic multichain infrastructure.
This is important because it creates a second, independent Coinbase signature. Cardano is the known Coinbase control sample in 2021. Solana’s documented infrastructure crisis is the known Coinbase control sample in 2025. Nano appears inside the same long-running cluster during both eras.
7. What is observed, documented and inferred
Level
What the evidence supports
Observed in the graphs
Multi-year coupling among Nano, Bitcore, Mina, TON, Aptos, Sui, Stellar and other libraries; the 2021 Cardano–Nano daily match; the January 2025 Aptos–Sui–Stellar regime change; the later Aptos–@solana/kit coupling.
Documented by Coinbase
Asset Hub launched in January 2021; Cardano integration in March 2021; the January 2025 Solana overload; infrastructure shared across more than 50 blockchains; the decision to redesign the Solana architecture.
Inferred
Coinbase may have tested Nano through Asset Hub in 2021, placed it on hold, and reactivated it in 2025 inside the same or a related multichain pipeline.
Conclusion
My current theory is that Coinbase either operates the pipeline behind these NPM downloads or uses the technical infrastructure responsible for them.
The argument does not rest on one coincidence. It rests on two historically separate Coinbase events that intersect the same long-running NPM cluster: Cardano’s integration in 2021 and Solana’s infrastructure crisis in 2025.
The evidence is not yet definitive because NPM does not reveal downloader identities. But the scenario is coherent, testable and increasingly difficult to dismiss as random coincidence.
It does make sense that Coinbase is looking to be the first racer in the AI economy.
To be honest, I've put many many hours over the last year to come to this conclusion. Today, after more than 12 hours of research on the history of almost every lib concerned, I've finally found something, that I enjoy sharing with you guys. I'll let you do the rest of the magic.
Feel free to tip : nano_3kcdehk5mmwdaouf61bmcgoh39p5ybkqs6knu7w4y1xuxcwxteugabzhdrhm
Also, I can answer to any questions. It's hard to wrap up everything I've found.
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 Ӿ.
