🗂 Directory — the registers behind the numbers
every name a link🪙 LatAm stablecoins
every mint, burn & holderFloat — outstanding supply on-chain reads
Circulating float from direct contract reads (dormant treasury legs excluded — see reconciliation). Δ = net supply change over the trailing 7 days. Distribution: ● distributed · ⚠ concentrated (upper bound) · ◌ not yet verifiable on that chain.
Liquidity & pools — where BRL stablecoins trade refreshed 60s
Public AMM pools per token: venue, price, pooled liquidity and 24-hour traded volume — every row links to the pool itself. Max @1% = largest swap within 1% slippage (constant-product approximation).
Custodians — where stablecoin reserves sit attested · dated
Every institution named in an issuer's latest bank-naming reserve report, summed across tokens. Report dates differ per token and are declared per row — figures are never restated to a common date.
LatAm stablecoins — local currencies tracked · expanding
The BRL methodology, extended currency by currency: MXN, COP, ARS, PEN. Tracker figures are replaced by direct contract reads as coverage grows.
💱 Markets — BRL pairs across venues
snapshotUSDT/BRL across venues — live connecting
Connecting to the stream…
BRL pairs across venues connecting
USDT/BRL spread across venues stream · a point a minute
24h BRL-pair volume by venue
The dollar premium — USDT/BRL vs official
Implied USD/BRL from each venue's USDT/BRL market vs commercial spot. Positive = on-chain dollars trade rich.
BRL pairs by venue — tick archive sealed day
Pairs & reported volumes
measured vs reportedTwo views that argue with each other on purpose: the pair × venue matrix we measure through public tickers, and the volumes venues report about themselves.
Pair × venue matrix — 24h volume
Reported by the venues themselves first-party APIs
Live charts
ours · /v1Candles for everything we measure ourselves — Binance BRL pairs, the commercial dollar, the premium, per-venue mids and on-chain floats. Every bar comes from our own history database; no third-party feed. Pick a series.
Loading charts…
🔁 Transfers — BRL stablecoins on the move
on-chain · censusValue moved — the volume tape on-chain
Every mint, burn and transfer, USD-valued, stacked by token. Dashed markers show where each token's scan begins — left of them is a floor, not zero.
Volume — value moved per token on-chain
Mint + burn + transfer events, USD-valued, scanned per contract. Click a token for its dossier.
Large on-chain events tx-linked
Single mints, burns and transfers big enough to matter — each row links to its transaction on a public explorer.
Legs — token × chain scan
One row per contract leg: value and transfers over the window, mints and burns, unique addresses on the last complete day, and where the scan begins.
Value moved by chain live scan
Where the BRL sits — domicile register registry-joined
One row per player: the Brazilian entity, its BCB segment, SPI participation, who handles client BRL, the PSAV filing and where reserves are held.
Reported, not verified claims
Players whose Brazilian presence is self-reported or announced and matches nothing in the BCB registers by CNPJ root.
Geofenced client BRL — floors from IF.data BCB
Prepaid payment-account balances filed by each player's own payment institution — a floor for client BRL held onshore, never an estimate.
A · Companies with their own stablecoin measurable on-chain
The rail is their token — every transfer is visible on public chains and can be measured independently.
B · Companies moving money on USDT/USDC self-published only
Their transfers look like any other USDT/USDC transfer — activity can't be attributed without their cooperation. "—" means the company publishes nothing; the blank is shown, never filled.
Regulatory considerations — the rules shaping the rails primary sources
🧱 Tokenized LatAm
census v0.12⚖️ Regulation
official publicationsLicense tracker — Brazil (BCB · PSAV) public records
Brazil's whole market must file with the BCB by Oct 30, 2026 — authorizations granted so far: zero. Other jurisdictions' regimes are in the LatAm radar.
The rules in force today — Brazil
Regulation radar — LatAm 15 jurisdictions · sourced
One row per jurisdiction — the regulator, its public registry, whether a crypto/VASP register exists, and the latest consequential rule; every row links to the primary source.
A jurisdiction with no dedicated crypto regime shows its financial-system regulator and registry — the absence of a VASP register is reported as exactly that, never inferred as prohibition.
Regulatory deadlines — Brazil
Timeline — how Brazil got here 2014 → 2026
Every consequential act on one axis — laws, resolutions, consultations, enforcement. Showing the current year; the full record is one click away.
Document shelf — Brazil, primary sources only sourced per row
Portuguese titles kept — that is what you will cite. Every row links to the publishing authority's own page, and names the authority it came from.
🌎 LatAm atlas
live map · interactiveEverything geographical on one live map: where the stablecoins are issued, where the deals happen, where the miners and validators actually sit, and what each regulator has done. Sites pulse when our live feed sees them move. Drag to pan, scroll to zoom; hover a country for its summary, click for the details.
⛏️ Mining & validators in LatAm
researched · sourced per row⏳ Yields — LatAm on-chain
third-party · dated🗺️ Players
one page per player · every name a linkPlayer directory issuers · platforms · custodians · venues
Custodians — where stablecoin reserves sit
Issuers — who stands behind each stablecoin
Platforms — who issues tokenized assets
Chains — the networks LatAm tokenization runs on
📈 Market pulse
Receita · BCB · B3What Brazil actually trades — mandatory reporting
USD stablecoins on Brazilian rails
B3 listed crypto products
Adoption metrics — Brazil
🔔 Signals & alerts
engineThe live alert engine runs inside the always-on service — it watches supply moves, single mint/burn events ≥US$1M between on-chain reads, the dollar premium, peg deviations on the deepest pools, regulatory deadlines and source health, and fires deduped alerts in real time.
Live alert feed from the service
This week's signals
computed from the datasetAuto-derived from the snapshot dataset on every build — deadlines, float moves, premium, attestation staleness, velocity.
🎛️ Operator console
accountsCreate an operator account to save alert preferences and a token watchlist (stored server-side; delivery via e-mail/Telegram is the next infrastructure step — the engine and preferences are live today).
🤝 Advisory
Independence note
Advisory is a separate activity from the data platform. Dashboard numbers are not influenced by client relationships: the methodology is public, the pipeline is open-source, and no advisory client can alter a figure. Rails and issuers can also apply here to have their flows independently verified — verified rails earn a badge; self-reported figures stay labeled "reported" permanently.
Get in touch → Replies within two business days.
📖 Method, audience & data
Methodology contract
Dashboard figures are complete by construction (on-chain: every mint, burn, transfer and holder of enumerated contracts — figures link to public explorers), complete by law (BCB / Receita / CVM mandatory reporting — linked to official publications), or measured (same formula for every token, machine-collected, timestamped). Research modules are curated from primary sources with per-fact links and as-of dates; anything unverifiable is labeled "no public record found." Failed sources render "—". Values are never estimated to fill a gap. The live layer adds its own fetched-at timestamp to every value it refreshes; a degraded source marks itself stale rather than reusing old data as fresh.
Tables, research modules, sources — everything behind this product.
Methodology — per section
Definitions, scope, source ladders and worked notes for every register on the site. Section pages carry the data; this page carries how it is made.
Tokenization
Yields
Transfers — rails
Notes, definitions & attribution
Mining & validators
Stablecoins
Float reconciliation & unmeasured tokens
The float table's per-token reconciliation against CoinGecko and press figures, and the reasons the eight unmeasurable BRL tokens cannot be measured yet, are maintained as versioned methodology documents in the project repository and summarized on each token dossier.
The stack
Snapshot layer: the open BRL Monitor pipeline (Python stdlib collector · GitHub Actions · twice-daily on-chain reads), now auto-ingested hourly by the service — the "collected" stamp above updates itself. Live layer: a zero-dependency Node service with a SQLite history store, polling FX (30s), Binance (15s), order books straight from 7 exchanges (20s rotation), CoinGecko (90s), DEX pools (60s), on-chain supplies & BCB series (5min), pushing over SSE with a server-side alert engine and operator accounts. The page runs in three tiers — service-connected, direct-API, or frozen snapshot — and always says which one you're looking at.
Credits
Charts rendered with TradingView Lightweight Charts™, © TradingView, Inc. — tradingview.com (Apache-2.0, vendored) and Chart.js (MIT, vendored). All chart data is Lastro's own.
Open data API — /v1 public
Stop scraping seven exchanges. We already read their books directly — Binance, Mercado Bitcoin, OKX, Bybit, Bitget, Foxbit, Bitso — normalize every BRL pair to one shape, and re-serve it with venue + timestamp on every row. CORS-open, no key needed, free with attribution. Nothing is estimated: a failed source returns nothing, not a guess. GET /v1 self-documents.
| Endpoint | What you get |
|---|---|
| /v1/best?pair=USDT-BRL | Consolidated best bid/offer across all venues, ±1% depth in BRL, 24h volume, premium vs commercial spot |
| /v1/book?venue=binance&pair=USDT-BRL | Normalized top-20 order book, numeric levels, fetched-at timestamp |
| /v1/tickers | Every venue × BRL pair: bid, ask, mid, spread (bps), 24h volume, book depth |
| /v1/premium | USDT/BRL premium vs commercial spot, per venue — the dollar-demand dial |
| /v1/reference | USD/BRL commercial spot, BCB PTAX, SELIC target, with sources |
| /v1/supplies | BRL-stablecoin on-chain floats — direct contract reads, per-leg provenance |
| /v1/history?series=…&tf=15m|1h|1d|1M | OHLC for any series the service tracks (?series=list enumerates ~100) |
| /v1/snapshot | The deep on-chain census (every mint, burn, holder) — collector output verbatim, provenance headers |
Books refresh on a 20-second venue rotation (full sweep ≈ 2.5 min); history persists in SQLite (15m candles 2 years, hourly/daily forever). Rate limit 300 req/min per IP. SSE push of the full live state at /stream. Full reference with live examples: 12 API.
🔌 API Reference
Normalized BRL market data, straight from the sources. Read-only, GET-only, JSON everywhere, CORS-open, no key. Every row carries a venue and a timestamp — a failed source returns nothing, never an estimate.
Introduction
The Lastro data API serves everything this site shows. Four data planes, one surface:
| Market data | Order books and tickers read directly from 7 exchanges' own public APIs — Binance, Mercado Bitcoin, OKX, Bybit, Bitget, Foxbit, Bitso — 16 verified BRL pairs, normalized to one shape, plus a consolidated best-bid/offer across all of them. |
| Official rates | USD/BRL commercial spot, BCB PTAX and the SELIC target, with sources and reference dates. |
| On-chain | Circulating float of every BRL stablecoin from direct contract reads, and the deep census — every mint, burn, transfer and holder — from the open collector pipeline. |
| Time series | Every number above is stored as a series: raw ticks 90 days, 15-minute candles 2 years, hourly & daily forever. Daily on-chain history back to Aug 2025. |
Base URL: https://lastro.live · machine index at GET /v1.
Quickstart
# consolidated best bid/offer for USDT/BRL across every venue we read curl "$BASE/v1/best?pair=USDT-BRL" # a year of daily on-chain BRL-stablecoin float, OHLC curl "$BASE/v1/history?series=day.total_usd&tf=1d" # thirty daily closes for three floats on one grid — a row of sparklines in one call curl "$BASE/v1/spark?series=supply.BRZ,supply.BRLV,supply.BRLA&tf=1d&points=30" # a live top-20 order book, normalized, straight from the venue curl "$BASE/v1/book?venue=binance&pair=USDT-BRL"
Auth & rate limits
No authentication. No key, no signup — the API is public and CORS-open (Access-Control-Allow-Origin: *), callable from servers, scripts and browsers alike.
Rate limit: 300 requests per minute per IP. Exceeding it returns 429 with a JSON error. For streaming use cases prefer SSE /stream — one connection, no polling.
Terms: free for any use with attribution to Lastro.Live. The service is in beta — no SLA yet; keep a fallback for anything critical. Higher limits or feeds we don't carry yet: talk to us.
Errors & honesty semantics
| Status | Meaning |
|---|---|
| 200 | OK — body is JSON (or verbatim collector JSON on /v1/snapshot) |
| 400 | Bad parameter — e.g. an unknown tf; body: {"error": "…"} |
| 404 | Unknown route, venue/pair not covered, or no data ingested yet |
| 429 | Rate limit exceeded — back off for a minute |
The honesty contract, as API semantics: a value that could not be verified is absent or null — never interpolated. A degraded source keeps its last value and flags itself stale instead of pretending to be fresh. Partial coverage says so (partial legs are floors, ≥). /v1/snapshot ships the collector's output verbatim with x-origin provenance headers.
Versioning
Everything lives under /v1. Additive changes (new fields, new series, new venues) land silently — parse defensively. Breaking changes get a new prefix (/v2) with /v1 kept alive through a deprecation window announced in the changelog.
Series catalog catalog
Every series below is queryable via /v1/history?series=<name>&tf=… — and ?series=list enumerates what exists right now.
| Family | What it measures | Cadence | Live series |
|---|
Data dictionary
| Field | Meaning |
|---|---|
| bid · ask · mid | Best bid, best ask, midpoint — computed from the venue's own top-of-book, numeric |
| spread_bps | (ask − bid) ÷ mid × 10,000 |
| vol24_brl | 24h traded volume in BRL — venue-reported quote volume, or base × mid when only base volume exists |
| depth_bid_brl_1pct · depth_ask_brl_1pct | BRL resting within ±1% of mid — what the book actually absorbs |
| stale · partial | A failed read keeps its last value and FLAGS it; a partial leg is a floor (≥) — never a guess |
| candle rows | [bucket_start_ms_utc, open, high, low, close, n_ticks] — buckets are UTC-aligned |
| ts · fetched_at | ISO-8601 UTC timestamp of when that specific value was read from its source |
Changelog
| v1 · 2026-08-19 | Initial public release: direct books from 7 venues (16 BRL pairs), consolidated BBO, per-venue premium, official rates, on-chain supplies, SQLite-backed history API (15m/1h/1d/1M), deep census pass-through, SSE stream, alerts feed. |
Self-report a project
Report your product for inclusion in the register.
Glossary & documentation
education · plain languageEverything Lastro measures uses these words. Plain-language explanations of the Brazilian rates, the fixed-income alphabet, the crypto mechanics, and what our API actually gives you. Linked from dotted terms across the site.