Juno (Bitso)

Juno (Bitso) issues 1 local stablecoin, MXNB (Mexican peso), on 5 chains. Supply is $3.77M, +43.5% in 30 days.

Licensed · CNAD (El Salvador)
Supply
$3.77M
+$1.14M (+43.5%) in 30 days
Trading volume
$3.37M
DEX pools, last 30 days.
Transfer volume
$15.82M
Sep 2026, full month
Active addresses
358
Sep 2026, full month

Monthly supply

Total · USD

$0$2M$4MFEB 26APR 26JUN 26AUG 26OCT 26

Apps and protocols

Not published

We only list named partners with a public source.

Verify and integrate

Juno (Bitso):

Not found: Terms.

Licence: Licensed · CNAD (El Salvador) · Nvío Pagos El Salvador

CNAD lists MXNB (issuer: Nvío Pagos El Salvador) as authorised through its public-offering process, issued 19/5/2025. Nvío is not shown on CNAD's issuers page. The link to FXscan's 'Juno (Bitso)' label rests on the CNAD listing; mxnb.mx is JS-only and was not readable. No Mexican authorisation for MXNB was found.

Source: cnad.gob.sv ↗ · Checked 17 Oct 2026

MXNB contract addresses (5)

As listed on mxnb.mx ↗

Each address opens in that chain's block explorer.

Not confirmed by the issuer yet. Issuers can request a check →

FAQ

How are stablecoins attributed to Juno (Bitso)?
From a curated list built from issuers' own public documents and announcements. When we cannot confirm who issues a stablecoin, it stays Unattributed rather than being guessed.
Are there gaps in Juno's data?

MXNB

  • Trading volume · Arbitrum · before 1 Dec 2025. Trading on Arbitrum from 2 Aug to 30 Nov 2025 is missing from our pool data, so trading volume for those months is understated.

Checked against our coverage audit on 17 Oct 2026. Rules that apply to every stablecoin are on Methodology →

How is supply measured?
We read totalSupply onchain from each chain and leave out wallets the issuer names as not issued yet or waiting to be burned. Bridged copies count once. We compare the total with DefiLlama. If the two differ by more than 10%, the page raises an alert and still shows our read, unless we cannot yet name the unissued or treasury balance behind the gap. Then the alert stays and the figure shown is DefiLlama's. A missing or failed chain read also shows DefiLlama's figure. Methodology →
Are bridged copies counted?
Bridged copies of a stablecoin are left out of supply totals, so the same coins are not counted twice. Their contracts are still listed on the stablecoin's page, marked “Bridged, not counted in supply”. Methodology →
Which chains have no past supply reads?
We read today's supply on Algorand, Noble, Hedera and ICP onchain, but not past supply there. Charts use DefiLlama's series for these chains where it has one; where it doesn't, the chart leaves that chain out or shows it as “Chain unknown”. Contracts on these chains are still listed, with a link to the chain's block explorer. Which stablecoins this affects is in each issuer's FAQ. Methodology →
How are USD values calculated?
Supply valued at each stablecoin's trading price, or at the reference FX rate where none exists. Methodology →
Why are changes shown in the stablecoin's own currency?
A 30-day change compares supply in the stablecoin's own currency, so a move in the dollar exchange rate doesn't show up as growth or decline.
How do I mint or redeem these stablecoins?
It depends on the issuer: some let individuals mint by bank transfer, and some only onboard businesses. Each stablecoin page lists who can mint, how to redeem and the local payment rails, with sources. Example: MXNB →
How often is the data updated?
About once a day, at a time that varies. Each refresh must pass automated checks before it is published. The last update time is in the footer. Methodology →