What premium do Turks pay for a digital dollar? This index measures the gap between what USDT costs in lira on Turkish exchange order books and the global dollar price converted at the reference exchange rate, every trading day. Turkey is one of the world’s heaviest stablecoin markets relative to its economy; with dollar accounts legal onshore the premium sits near zero in calm times and opens in lira stress — this is a stress gauge, not a forecast. Sister indices: India USDT, India USDC, India Bitcoin, Korea USDT, Brazil USDT.
| Exchange | Mid (₺) | Best bid / best ask (₺) | Spread | vs index fix |
|---|---|---|---|---|
| loading… | ||||
Methodology v0.1.0 · DRAFT pending calibration and Owner sign-off. Values marked TO BE SET are filled from calibrate.py after roughly 44 hours of live capture; the version number does not change when they are filled, because filling them does not change how a fix is computed.
The Crypto Times Turkey USDT Premium Index (CTPI-USDT-SPOT-TRY) measures how much more (or less) a dollar stablecoin costs in Turkish lira on Turkish exchange order books than the global dollar price converted at the reference exchange rate, every trading day. Two numbers are published: the raw premium (lira price of USDT versus USD/TRY) and the peg-adjusted premium (the headline), which also divides out USDT’s own small deviation from $1 so that only the Turkey-versus-world gap remains.
What to expect. Turkey has no hard retail foreign-exchange controls — dollar deposit accounts are legal and widely held — so the structural premium is friction-sized, not control-sized: close to zero in calm times, which is itself information. The index earns its keep as a stress gauge: in lira episodes the premium opens as demand for a digital dollar runs ahead of on-ramp capacity, and the daily archive records exactly how far and for how long.
Fix window 11:30–12:30 TRT (12:00 ± 30 minutes), published at 12:31 TRT (09:31 UTC) by a systemd timer with Persistent=true; if the host is off through the window, the timer runs on boot, finds no samples and refuses to publish. No estimate is ever published in place of a missed fix; a missed or late fix is recorded in the corrections log as a publication-timing entry.
The ECB publishes its daily reference rates around 16:00 CET, which is 17:00–18:00 in Turkey, hours after the window closes; the fix therefore always prices against the prior ECB business day’s rate, the family’s deterministic rule, and its date is cited with every fix.
Official fixes are computed every Monday to Friday (TRT). Local public holidays do not pause the index: crypto trades every day, so a Turkish public holiday is an ordinary fix day, priced against the ECB reference rate by the usual rule below. Weekend runs store an indicative point at the same fix time, measured against the last business day’s USD/TRY and marked distinctly on the chart.
The engine that computes this index also computes The Crypto Times India Bitcoin Premium Index, where the global leg moves inside the window; the family rule pairs each venue sample with the reference captured nearest to it in time (within 120 seconds; unpaired samples are counted and dropped, never estimated). For a stablecoin leg the pairing changes nothing materially, but one rule for the whole family is worth more than two.
r = venue_mid_try ÷ usdtusd_ref — the USD/TRY rate implied by that venue’s USDT quote.r across its paired samples is the venue observation; the median two-sided lira depth resting within ±TO BE SET bps of mid (stored bands: 50, 100) is the venue weight.TO BE SET two-sided. Exclusions are recorded in the fix’s provenance with the venue’s would-be value.R. A venue must supply real resting depth, not just a printed price, to move the fix.premium_pct = (R ÷ USDTRY − 1) × 100.raw_premium_pct = (observed_mid_median ÷ USDTRY − 1) × 100.value = R × usdtusd_ref (lira per USDT), where usdtusd_ref is the median of the references actually paired, so that value ÷ (usdtusd_ref × USDTRY) − 1 reproduces the headline premium exactly from the figures on the page.An official fix requires at least TO BE SET eligible venues, a publishable USD/TRY reference within the carry ceiling, at least one paired USDT/USD reference, and no existing official fix for that time. Officials are immutable once written; restatements go only through governance tooling and appear in the corrections log.
two_venue_aggregate; high_venue_dispersion when venue observations differ by more than TO BE SET bps; unpaired_samples(n); insufficient_venues on indicative fixes only.
Candidate venues at launch: BtcTurk and Binance. Paribu publishes no documented public market-data API and its website answers automated requests with a browser challenge; the index does not imitate an app to reach undocumented endpoints, so Paribu is not collected unless it offers public data or data access. Icrypex’s USDT/TRY book was empty and Bitci answers with the same browser challenge (checked 23 September 2026). With two venues the index sits at the family’s two-venue minimum: a day on which either is unavailable at the fix produces no official fix, never a single-venue number. Turkey’s 2024 crypto law brought exchanges under Capital Markets Board licensing; a venue’s regulatory or security history is disclosed beside the fix, never assumed away. Constituent status is set from measured order-book depth during calibration and reviewed against the family venue policy; the venue-status line and the per-exchange table state, every day, which venues the number includes and why any is excluded. Changes appear in the changelog.
Between fixes the page shows a 5-minute indicative reading computed with the same pairing and aggregation, against the USD/TRY rate in force at the sample. Past 15 minutes without a usable sample the live block shows STALE rather than a stale number. Indicative readings are never part of the daily fix series.
Besides the daily fix, the engine records one reading a day at 12:00 UTC — the same moment for every index in the family (15:00 TRT here) — computed exactly as above over 11:55–12:05 UTC (14:55–15:05 TRT), against the latest ECB reference captured before the window closes, which is always the prior business day’s rate. It exists so that a future multi-country composite can combine markets observed at the same instant rather than hours apart. It is not this index’s official value and is never part of its fix series; a day on which it cannot be computed is recorded as INVALID with its reason. Around that window the collector samples every 60 seconds whatever the local hour. The series is published at /v1/sync on the engine host.
The methodology version changes only when the way a fix is computed changes — never for display, documentation or the filling of calibration values above. Package versions are separate.
Methodology text: Local public holidays do not pause the index: a holiday is an ordinary fix day, priced against the ECB reference rate by the usual rule; weekends stay indicative. No change to how the fix is computed. Official fixes remain switched off.
Venue discovery (run 23 September 2026): BtcTurk, Binance and the Kraken and ECB references answered as documented. Paribu is disabled: it publishes no documented public order book and its website answers automated requests with a browser challenge. Icrypex’s USDT/TRY book was empty and Bitci refused automated requests, so both stay disabled. The index runs on two venues, the family minimum. Official fixes remain switched off.
Index created on the CTPI family engine, configured for USDT/TRY: Turkish venues BtcTurk, Binance and Paribu enabled, Icrypex and Bitci shipped as configuration-only candidates pending endpoint confirmation; USDT/USD reference from Kraken paired per sample; ECB USD/TRY denominator; noon-TRT fix published 12:31 TRT; raw and peg-adjusted premiums. Official fixes remain switched off ([fix].official_enabled = false) until calibration values are set from live data and the methodology is signed; the daily timer stores indicative (shadow) fixes meanwhile.
No corrections, restatements or publication-timing entries yet. Entries are added here, inside this document, never on a separate page: a missed or late fix is recorded as a publication-timing entry; a change to a published value is a restatement, with the old value, the new value, the reason and the date.
| Date | Type | Fix date | Detail |
|---|---|---|---|
| none recorded | |||