OJK OFFICIAL monthly txn value (Rp T · regulator aggregates ALL licensed exchanges = the truth line):

our live aggregate vs OJK official (2026-05 = Rp23 T/mo): extrapolating 6 complete days ×30 BRACKETS it, and does not reproduce it: credible-core Rp12.8 T = 0.56× OJK (44% under) → total Rp52.5 T = 2.28× OJK (128% over). More days will not close this. The gap is definitional, not sampling: self-report inflates the total, and the biggest retail players (Pintu/Ajaib/Pluang) are invisible to us so the core under-counts. Also not like-for-like on time: OJK's latest is 2026-05 and this window is live, and the official series fell from Rp37.2T (2025-11) to Rp23.01T over that gap. OJK monthly = the anchor.

DJP crypto tax (tax authority, monthly releases · every row states its BASIS, because the two headline figures are not on the same one):

ONE OF THE TWO TAX COMPONENTS IS A CLOSED BOOK. PMK 50/2025 (effective 2025-08-01) treats crypto transfers as securities-equivalent, so transfers left the PPN base entirely; PPh 22 became 0.21% on domestic licensed venues and 1% on foreign ones. Measured across our snapshots from 2025-09 to 2026-06: PPh 22 grew Rp373.64B while PPN DN grew Rp9.20B, a 41-to-1 ratio, and PPN reads flat to the rupiah across the last two releases. The regulation was read first and predicted exactly this. So the TOTAL stays comparable across the break, since the headline rate is about 0.21% either side, but the PPN line is not a demand signal any more.

OPEN QUESTION, stated because the arithmetic does not close. Tax collected divided by OJK reported volume implies an effective rate that ROSE while the domestic statutory rate did not: 0.0954% in 2024 (Rp620.38B on Rp650.61T) against 0.1652% in 2025 (Rp796.74B on Rp482.23T). Volume fell 25.9% and tax rose 28.4%, a 54-point divergence. Four things could explain it and none is verified here: OJK may count both sides of a trade, so the taxable base is about half the printed figure; collections lag; some volume is exempt; or the new 1% foreign rate is adding collections whose volume never enters a domestic-only denominator. That last reading would make this pair the first window onto offshore flow, which is why it is written as a question and not as a finding.

Indo vs GLOBAL volume trajectory (both indexed to 100 at 2025-07 · tracking or decoupling?):

method: Direct keyless exchange API where verified (Indodax, Luno-ID, Bittime). CoinGecko raw exchange-reported 24h volume (BTC->IDR) for Indo-domiciled exchanges whose direct endpoint is key-gated or geo-blocked. App-only + no-volume-API players excluded.

caveat: Indodax self-reports Rp261B vs CoinGecko Rp206B (self-report vs aggregator gap). Direct-endpoint audit 2026-07-12: Bittime wired DIRECT (openapi.bittime.com, keyless). Tokocrypto market-data is key-gated (code:3701), Bitwyre /public API is dead (404/web-app), Pintu keyless API has price but no volume field -> CoinGecko/excluded. Upbit-ID is Komdigi-blocked at the ISP (Biznet RPZ DNS-sinkhole of id-api.upbit.com -> HTTP 000; a Jakarta/Biznet IP TRIGGERS the block, does not fix it); a DoH bypass returns live data (verified 2026-07-13) but Upbit is kept on CoinGecko per operator call. Ajaib has its own anti-scrape WAF (HTTP 403 even with full browser headers). 2026-07-13: BTSE Indonesia wired DIRECT via api.btse.id (local OJK entity, keyless market_summary IDR-quote vol; global api.btse.com is Komdigi/Biznet DNS-blocked). Reku wired DIRECT via api.reku.id /v2/ticker (its ticker carries IDR-quote vol; was wrongly excluded as market-data-only). 2026-07-17: Mobee wired DIRECT+AUTH via open-api.mobee.io /v1/markets/summary (authenticated, read-only); prior 'app-only, no public API' belief was stale (Mobee shipped an Open API). base_volume on IDR_ pairs = IDR turnover (verified quote_volume*last==base_volume). IDR-QUOTE PAIRS ONLY: Mobee's USDT book is wash-dominated (USDT_AMZNX alone self-reports ~$1.9B/24h = 97pct of its USDT volume, vs ~$160k on every other USDT pair) so USDT/USDC pairs are excluded; IDR-quote sum stays >Indodax so the wash-guard still keeps Mobee out of credible_core. Bittime, BTSE ID, Mobee report volume exceeding Indodax (the market leader), likely wash/incentivized-inflated. total is an UPPER BOUND. credible core (ex-Bittime/BTSE ID/Mobee) = Rp439B.

excluded: Pintu Pro (keyless api.pintu.co.id has price, no 24h-volume field); Bitwyre (documented /public API dead, host serves a web app); Ajaib Kripto (Cloudflare WAF 403 even w/ browser headers on BOTH the web app AND the documented API host api.ajaib.co.id; the /coin/internal/v1/price endpoint also needs ECDSA-signed auth + Ajaib exposes NO public 24h-volume endpoint. Adding = CF-bypass + API keys + request-signing for price-ONLY/no-volume. Checked 2026-07-13, not worth it); Upbit ID (Komdigi/Biznet DNS-blocked, still nebeng global/KR infra; shown via CG)

Two different quantities, and they are not comparable. The GAP is how far apart venues price the same asset. The SPREAD is the bid-ask width inside one venue. A market can have a wide gap and tight spreads, or the reverse. They were two panels until 2026-07-28, both headed "spread", which is how a reader ended up with two numbers and no way to reconcile them.

green=cheapest, gold=priciest venue per pair; AVG+GAP across live liquid quotes; grey*=stale/thin book, excluded. USDT/IDR ~Rp17,979 across all venues is ~AT PAR with interbank USD/IDR (Rp18,073, -0.52%) = no meaningful stablecoin premium right now (IDR itself is just weak, ~Rp18K/USD).

Top-of-book bid/ask width per venue = what a taker pays to cross the spread right now. This is execution cost, NOT the cross-venue gap in section 1 above. green=tightest, gold=widest live book per pair; grey*=dislocated (quote is real but the ladder is effectively empty, so it is excluded from best/worst ranking). Quotes that are crossed or wider than 25% are dropped as no-book rather than reported. A tight top-of-book here does not prove size can be filled: see the depth panel below, where the tightest quoted venue is not the cheapest to actually trade.

What a market buy actually pays, walked through the live orderbook, versus mid. Sizes are Rp10M / Rp100M / Rp1B because a depth number without the size it was measured at means nothing. green=cheapest at that size, gold>0.25%, red>1% or unfillable. "dust" marks a venue whose quoted spread sits on under Rp1M of size, i.e. a tight-looking price you cannot trade. Mobee publishes no orderbook, so its depth is UNKNOWN and is deliberately left blank rather than estimated from its spread. This is what the VISIBLE LADDER implies, not a guaranteed fill. Venues commonly apply market-order protection or price bands and would reject a large order rather than fill it at the far end of a thin book, and the ladder itself moves between snapshots. Read a large-band figure as a measure of book thinness, not as a price anyone actually paid.

The same order, priced in two places. At Rp1B, about $55k, the median Indonesian venue charges 102x the slippage of the median offshore venue, 0.110% against 0.00108%. In cash on that one order it is $61.34 here versus $0.59 offshore. 0 of 5 Indonesian venues can fill it at top of book, against 3 of 6 offshore. This is the price of the market being local, and it is the only number on this page that says so directly.

the one honest cell: Rp1B converts to about $55k at the rate measured this run, so this is the only cell on the two cards that is a like-for-like read. The $10k, $250k bands are OFFSHORE-ONLY: Rp10M is about $556 and Rp100M about $5.6k, so neither brackets $10k and nothing brackets $250k. The Indonesian ladders are not re-walked here by design, and interpolating between measured bands would invent liquidity, s

quote currencies differ and are NOT assumed at par. Quotes seen: USD, USDC, USDT, of which USDC, USDT are not USD. Each is converted at a measured rate, and the conversion self-checks: the apparent premium on USDT venues collapses from 0.141% to 0.0012% once converted, which is what you would see if the rate is right and not if it is wrong.

No composite score, on purpose. Averaging measured and unmeasured dimensions would produce one confident number whose precision is invented, and would rank venues by which dimensions happen to be observable rather than by which venue is better. Compare WITHIN a column only. SPREAD is per-venue across its own pair basket and is therefore not like-for-like between venues, and not the same measurement as DEPTH (which is BTC/IDR at Rp100M). *=dust top-of-book, ‡=grouped API assessment covering several venues. Still UNMEASURED for every venue: fiat rails, deposit/withdrawal reliability, because no per-venue source exists yet; those are blank rather than assumed fine. UPTIME is derived from 254 archived cycles and only accrues forward, so treat it as "has not missed recently" rather than a reliability record.

This is a FLOOR, not a total. Platform fee is the venue's own pricing. Round trip adds the exchange levy and the tax, and the tax is sell-side only, so a round trip is not twice a one-way fee. Ranked only against like: Rankings compare only venues measured on the same components. Venues with missing components are NOT ranked, because a cost built from fewer parts is mechanically smaller and would win on ignorance. Fully covered and ranked: Reku, Mobee, BTSE-ID, Luno, Bittime, Indodax. Partial coverage, not ranked: none. Fee page unreadable: none. Still excluded for every venue: min_trade, network_fee, time_to_cash. No Indonesian venue publishes a fee endpoint, so every number here was read off a page by hand and carries its own source and date (checked 2026-07-29). The real cost is higher than every figure here, never lower.

Venue-sourced risk notices from Indonesian exchange Telegram groups, where impersonation warnings and rail changes surface first. These are detections, not verdicts. A row means a venue said something about risk, never that we confirmed a risk is real, so every row carries its source link and whether the venue or a member said it. Filtered 57 raw detections down to 8 by requiring an actual assertion of a threat or a state change: support replies explaining what delisting means, member questions and group rules are excluded, because keyword match finds the TOPIC and is silent on whether anything happened. "standing xN" means one notice posted N times, which is diligence by the venue, NOT N separate incidents. 🔒 Public group messages only, no member profiling, no individuals named.

RESEARCH CHECKLIST, NOT LEGAL ADVICE. Utopia sells market-entry advisory, not compliance or legal work. Every row is a QUESTION plus where its primary source lives. Nothing here says which licence binds you or whether you are exempt, because that is legal advice, we are not qualified to give it, and a confident wrong answer costs someone their entry.
10 questions, of which 2 are answerable from live data on this page and the rest point at a primary source or a professional. Each row states what we CAN see versus what someone qualified has to answer, so the boundary is visible per row instead of buried in a footer disclaimer.

One story in two steps, and previously two panels showing the same number twice. Step 1 is whether the stablecoin rate sits off the official rupiah rate, which is the cleanest read available on capital wanting out. Step 2 compounds that with execution cost to give what the Indonesian leg of the corridor actually costs. The full journey always costs more, never less.

USDT/IDR + USDC/IDR spot = avg across the direct CEX; vs official USD/IDR (Yahoo interbank). Positive = stablecoin premium (capital-flight/demand signal), negative = discount. USDC ~Rp17,973 (-0.55% vs official) tracks USDT, same at-par read. Currently ~at par: IDR is weak (~Rp18K/USD) but no stablecoin-premium stress. 30d lines: USDT + USDC (CoinGecko) vs official (Yahoo).

INDONESIAN LEG ONLY. This is IDR to USDT on an Indonesian venue. The destination leg (USDT to SGD/MYR/THB) is NOT measured, so the full journey costs MORE than every figure here, never less. Crypto as a payment instrument is banned in Indonesia (PBI 18/40/2016); this describes asset conversion, not a payments product.
Leg 1 compounds two costs that are normally quoted separately: walking the real orderbook for a given size, and the stablecoin's own deviation from the official USD/IDR rate. They COMPOUND rather than add, because the deviation applies to the price you already paid slippage on. A venue whose book cannot fill the band is reported as unpriced rather than extrapolated. The five unmeasurable legs are listed by name so a one-leg number is never mistaken for a corridor total.
Reference: The comparison is to the INTERBANK mid rate, which is the best price in the market and one no retail buyer is ever quoted. A retail bank or money changer charges a spread on top, so the gap versus what a person actually pays at a counter is WIDER than the number shown, in the stablecoin rail's favour. We do not measure retail bank rates, so that wider gap is asserted in direction only, never in size.
TWO DEVIATION FIGURES, both real: the header and chart show -0.52% (6-CEX avg vs official); the LEG 1 table applies -0.64%, which is fx_deviation.json's single-venue spot. Same quantity, different sample. The multi-venue figure is the better estimate of the market; the leg-1 column is not yet rebased onto it, so treat leg-1 totals as indicative on the FX component.
Not measured (1 of 2 legs): destination conversion, bank wire comparison, remittance operators, payment pilots + ASEAN interop, offshore access / blocking

Delisting notices, official venue announcements only. The withdrawal deadline is the actionable field, so a notice whose deadline could not be parsed still shows, saying so:

What this panel cannot answer yet, and why. The gap is retention, not difficulty: the archive recorded per-pair spreads for a fixed 8 and venue-level volume, never the pair INVENTORY, so listings and delistings left no trace. Capture starts now, which makes these answerable going forward and never retroactively. 127 cycles retained so far.

• Did liquidity persist after a listing? The archive never recorded the pair INVENTORY, only per-pair spreads for a fixed list of 8 plus venue-level volume. Retention starts with this build, so the answer becomes available going forward. 127 cycles captured so far.
• When was a pair first listed? Same cause. A first-seen date only exists from the first cycle we retained.
• Is a token CFX-eligible? The bourse publishes the eligible-asset list and we do not hold it. Inferring eligibility from what venues list would be backwards: a venue listing a token is evidence about the venue, not about eligibility.

Two different measurements, deliberately shown together. OJK counts REGISTRATIONS with licensed exchanges, which is an account count and includes dormant ones. Chainalysis ranks ESTIMATED ON-CHAIN ACTIVITY, which is a different population and a relative position, so it moves when other countries move. Neither is "users". Read the registration line for scale and the rank for momentum.

Chainalysis: Indo highest APAC YoY growth. OJK optimistic path ~26-27M by end-2026.

Indo #7 overall 2025 (was #3 in 2024). Drop is methodology: Chainalysis added an institutional >$1M sub-index favoring ETF-heavy markets (US/India/Brazil). Indo's retail+DeFi is still massive: #4 in the world on DeFi.

* = investment, not an acquisition. The starred party took a stake; it did not buy the licence holder. On a board about acquiring your way in, that is a different route with different control, and reading it as an acquisition overstates what changed hands.

Every foreign exchange in this data entered Indonesia by ACQUIRING a licensed local entity rather than by applying for a licence. The licence is the asset being traded. Stated as an observation about these rows, not as a claim that no other entry route exists.
5 source-backed edges across 13 entities, 3 of them a foreign venue entering via a licensed local shell. No ownership percentages, no inferred relationships, no scraped registry: each row keeps the status word its source gave, and an investment is never flattened into an acquisition. Relationship types we cannot source yet, listed rather than left absent: bank / fiat rail, custody, VC funding, listing agreement, university / talent. A sparse set of relations shown without its gaps reads as a complete map of a small ecosystem instead of a partial map of a larger one.

STALE, AND THIS PANEL CONTRADICTS OUR OWN LATER AUDIT. Table dated 2026-07-10; the volume fetcher re-probed these hosts afterwards and disagrees. Treat the rows below as REPORTED dev-doc coverage, not as verified reachability, and do not scope an integration off them:
· Bitwyre listed "REST + WS + Trade" / conf high but our audit found it documented API dead (404)
· Ajaib Kripto listed "REST + WS + Trade" / conf high but our audit found it WAF 403, no public volume endpoint
· Reku listed "REST (mkt-data only)" but we read its volume DIRECTLY this cycle
· Mobee listed "app-only (no public API)" but we read its volume DIRECTLY this cycle

8 of the 29 PAKD on OJK's Dec-2025 roster expose full public APIs; 1 market-data-only; app-first players publish none. DENOMINATOR IS DELIBERATELY THE DEC-2025 ROSTER, not OJK's current 26, because the numerator was probed against that roster and we have not checked whether any of the three venues that have since left the roster were among the 8. Re-basing 8 onto 26 would silently invent a measurement nobody made.

defunct: Zipmex wound down (off current OJK list)

This is the inversion as a single number. IDRX moves 20x more transfers per dollar of supply than IDRT (265 against 13 per $1M per 24h). The token with the balance sheet is not the token with the rail. Transfers are a COUNT, not value, so read this as activity per unit of supply and never as value turnover: we do not read transfer amounts. IDRX also has unread chains, which can only push its figure UP.

Counts and aggregate value only. No individual address is recorded, ranked, labelled or returned. The participant figure is a set CARDINALITY and identifies nobody. No nationality is inferred from any wallet.
Each deployment is queried from TWO different providers over the SAME block range and only ships when they agree within 2%. This is not caution for its own sake: one provider 403s a query another answers, and another silently caps eth_getLogs at 50 blocks, which would return a tenth of the true count from an identical request. Disagreement is PUBLISHED as disagreement. A zero is a real observation, not proof a token is unused: activity may live on another chain, in a bridge, or inside an exchange ledger where no on-chain transfer occurs. Deployments outside the measured chains are listed by name, because a silently partial sweep reads as a complete one.
Window: 100 blocks per chain. Not swept: none.
SHORT WINDOWS. Provider range limits force a 100-block window, which is only seconds to a few minutes on fast chains. A zero over a window that short is weak evidence and must not be read as a token being idle. Ethereum is the only chain here whose window spans a meaningful period.
THE 24H FIGURE IS SINGLE-SOURCE, DELIBERATELY. Two-provider agreement is not affordable at this width: the strictest keyed provider caps eth_getLogs at 10 blocks, so a day of BSC would be over 17,000 calls. The window is denominated in TIME and the block count is derived per chain from a MEASURED block time, which is the fix for the previous version: that one used the same 5,000 blocks everywhere, which was 16.7h on Ethereum and 37 minutes on BSC, so the panel compared sixteen hours against half an hour and let the fast chains read as idle. Read this number as a reading, not a confirmed measurement.
WHAT THE SPOT CHECK IS FOR. The two-provider column covers only 100 blocks, where essentially every row is 0. That is a fact about the window, not the token, so it is no longer the headline. It still earns its place: it is the standing check that the single provider behind the 24h figure is not quietly wrong, since both must cover the identical range and agree.
CADENCE. The 24h sweep re-runs only when the stored reading is older than 20.0h, so a dashboard rebuild every 30 minutes reuses it rather than re-reading. Each fresh reading is appended to a local ledger, which is what will make a trend line possible without ever re-querying history.
COVERAGE IS NOT A FINDING. How many rows reach two-provider agreement depends on free-endpoint availability at that moment, not on the tokens. Identical code 2.5 minutes apart returned 7 of 11 and then 1 of 11. Read the per-row states, never the coverage count, and never compare that count across runs.

on-chain read (keyless, multichain): IDRT $5.02M but CoinGecko claims $9.62M = over-stated ~43%. IDRP $3.61M is 99.6% on Kaia. IDRX $1.02M spread thin over 10 chains. XIDR (StraitsX) $117k across Ethereum/Polygon/Zilliqa, ~94% on Ethereum; its Zilliqa leg is a FiatToken proxy, so supply is read off the proxy and not the implementation address the public explorers link to. IDRT near-zero daily volume. The entire rupiah-stablecoin rail is ~$9.76M. NOT FREE FLOAT. Every supply figure here is the contract own totalSupply(), which is minted minus burned. It therefore INCLUDES tokens the issuer still holds in dev or treasury wallets, unissued balance-sheet inventory minted ahead of demand, and balances frozen in banned or blacklisted wallets, because a blacklist freezes a balance without burning it. None of that is in public circulation, and none of it is separable from the outside: splitting it out needs an issuer-published treasury or reserve address list, and none of these four publish one. So read every supply number as a CEILING on the free float, never a measurement of it. The 24h transfer count is the better proxy for what is actually in use, which is why both now sit in one panel. THE TWO BLOCKS DISAGREE, AND THAT IS THE POINT. IDRT leads on supply and is third on movement; IDRX is third on supply and leads on movement, holding about a fifth of IDRT while moving roughly four times as often, so per rupiah outstanding it turns over about twenty times harder. A supply-only panel would have called IDRT the main rupiah stablecoin, which is true of the stock and wrong about the rail. IDRP corroborates itself across both measures: 93% of its supply and its busiest venue are both Kaia. Transfers are SINGLE-PROVIDER readings over ~24h and are a FLOOR wherever a chain is marked unread.

THE CONTROLLED COMPARISON. StraitsX issues BOTH tokens, so this pair holds the issuer constant and varies only the market. XSGD carries $16.55M against XIDR at $117k, a factor of 142x. XSGD alone is 1.7x the ENTIRE Indonesian rupiah rail across all four tokens. Singapore is roughly 6M people and Indonesia roughly 284M. Population is stated, NOT divided into the supply: a per-capita figure here would invent a second denominator and imply these tokens are retail-held, which nothing on this page establishes.

coverage, against the whole domain and not our own subset: 29 deployments read this cycle, of 29 we have a verified address and a reader for, of 47 that CoinGecko lists for these tokens. The other 18 are named below rather than dropped. The previous version of this line read "23 of 23", which was true and useless: both sides counted only the chains our map recognised, so the ratio was pinned at 100% and could not have shown a gap. Every figure here is therefore a FLOOR over a partial chain set.

two verification strengths, counted separately: 23 EVM deployments passed the strong check, an on-chain symbol() equal to the expected ticker plus decimals() from the same contract. 6 Solana deployments passed a WEAKER one: an SPL mint exposes no symbol(), so all we establish keylessly is that the mint answers getTokenSupply, reports its own decimals and holds a non-zero supply. That excludes a dead or mistyped address but does NOT prove the mint is the token we asked for, and that claim rests on CoinGecko's platforms map alone. Decimals are still read per deployment, which is not academic here: MXNe is 6 on Base and 9 on Solana, so one shared value would have been wrong by 1,000x.

FX: https://www.exchangerate-api.com · Thu, 30 Jul 2026 00:02:31 +0000 · cross-checked against this dashboard's own USD/IDR spot: -0.017% apart, two independent providers

The load-bearing fact, and the only one on this card with a citation strong enough to build on. Crypto is barred as a PAYMENT INSTRUMENT in Indonesia. Bank Indonesia Regulation PBI 18/40/2016 on payment transaction processing prohibits payment system operators from processing virtual currency. ↗ regulation
SCOPE: This bars crypto as a means of PAYMENT. It does NOT bar crypto trading, which is licensed separately under OJK POJK 27/2024 having transitioned from Bappebti. Conflating the two is the most common error made about this jurisdiction, and the dashboard's own regulatory panels keep them apart.

19 of 20 cells are NOT SOURCED, and that is the state of the art here rather than a gap in effort. This is the ONE card on the dashboard that cannot be measured from an API. Venue fee and rail pages here are Cloudflare-protected (recorded under the B2 fee note: help.indodax.com 403s plain urllib AND WebFetch, and headless chromium gets a 'Just a moment' interstitial; defeating that is circumventing an access control and is not on the table). So every figure is a human reading a published page and recording where and when. Until that happens the cells stay null WITH A REASON, because a filled-in guessed

The empty rows are the point. 6 sectors were searched and returned nothing at all (Payments / on-ramp, Custody / wallet, DeFi protocol, DePIN, Identity / KYC, Data / analytics). 1 returned names whose domains no longer resolve (Gaming / metaverse). Those are different findings: the first says nobody built here, the second says somebody did and it is gone or moved. Payments is the sharpest result: the sector is well served and every operator the pass returned was foreign, so it is a gap in local ownership rather than in supply. What this is not: a census. The roster is one round of search on 2026-07-28 plus the venues we already measure, so exchange coverage is strong because that is what this dashboard does, and everything else is thinner by construction. Our own API census puts 26 licensed PAKD in the market (2026-05) against the 30 listed here. Status words are narrow: quiet means we hold no recent evidence of operation, NOT that a company is gone, and wound-down is only ever used with a link. A site that fails our probe becomes unknown, never dead.

Indonesia does not treat presence as a spectrum. Per the Chambers 2026 Indonesia blockchain guide, authored by SSEK, the OJK position is that a licence is required of any entity providing regulated digital-financial-asset services to consumers IN Indonesia regardless of where it is incorporated, cross-border provision without a local licence is not permitted, and the enforcement mechanism actually used is access-blocking, applied to a significant number of foreign platforms. So the presence form is not a description of ambition, it is a compliance posture. It also explains the pattern below: partnering with an already-licensed Indonesian operator is not one option among many, it is the route the rules leave open.

Not searched, so not a finding about them: Polygon, Aptos and TRON appear in Mastercard's expanded Crypto Partner Program (Mar 2026) alongside Ripple and Solana, but that is a global programme with no Indonesian element we could evidence, so it is not presence here. Chainlink, Sui, Avalanche and TON were not searched in this pass. Their absence is a gap in our coverage, not a finding about them.

Dates only, no forecasts. Every row restates a date the issuing body published; nothing here predicts what a regulator will do. Where a field carried several dates the LAST is used, because the transition or compliance deadline is what bites, not the signing. 3 upcoming, 23 already in force (6 most recent shown), 0 with no machine-readable date, SHOWN not dropped because the messiest entries encode staged or conditional timing and are the ones worth reading. year-only means the source gave no day and the row is sorted at year-end, not that we know the day. approx means the source hedged and that word is preserved.

RECORDKEEPING, NOT TAX ADVICE. This produces records and a gap list. It computes no liability and hard-codes NO tax rates, because rates change, differ by taxpayer and instrument, and a confident wrong rate is worse than a blank field: someone files on it. Where a rate belongs, the primary regulation is named instead. A qualified professional determines liability.
The expensive part of crypto tax is rarely the arithmetic. It is that the records are incomplete and nobody notices until a deadline. So the gap list is produced every run rather than a total resting on silence.
Canonical export columns: ts, venue, side, asset, quote_ccy, asset_amount, quote_amount, fee, fee_ccy, ref

read: Pattern: Indo is EARLY on classification/tax/AML (crypto slotted under financial-sector law, CARF, Travel Rule) but LATE + restrictive on openness (single-bourse gate, 40% foreign cap, no stablecoin framework, payment banned). The world is opening stablecoins (US/HK/SG); Indo is gating them.

This is a research matrix, not a ranking. No score and no best-jurisdiction verdict: the weights would be ours, and the same regime is an opportunity or a wall depending on whether you are a token, an exchange or a payments business. 16 cells are RELAYED from a named secondary and have not been checked against the instrument, so treat them as leads. 21 are blank because nobody has looked, which means unknown and never "no requirement". Peer source: Tiger Research, Retail Investor Landscape Across 9 Asian Markets, 2026-03-31. HTX-funded, zero citations in the document.

Quick reference (the stack at a glance, full text per law below):

26 laws, sourced from Logseq Regulation/ + primer. click any law to expand its full summary. Links are official source locators, not asserted document deep links.

Indonesian coverage comes from regulators, not media. 4 Indonesian item(s) above are primary regulator documents (OJK, Bank Indonesia, Kemenkeu, Komdigi, CFX). The Telegram capture contributed 0 Indonesian items of 15 crypto-relevant across 10 channels, because it holds no Indonesian sources and Indonesian crypto media has no Telegram presence. That is a TRANSPORT gap, not evidence nothing happened locally. Telegram rows below are global context.

The two layers are on DIFFERENT WEEKS. Term rates are 2026-W30, the reviewed semantic layer is 2026-W29. They come from separate aggregation runs, so do not read a term rise and a topic as the same week of evidence. The semantic layer lags because it is reviewed before it ships.

Reviewed semantic layer (meaning-level, sits BESIDE the raw term counts, never replaces them):

method: panel 8/14 INDO groups present in W29 and all baseline weeks; rate, not count. Public redacted chatter only. Human-reviewed static draft; no automatic semantic generation in dashboard refresh.