Call #2730 · BD · Currency depreciation (FX reference rates)

BDT depreciates 0.29% or more against USD at any point within 14 days, from 122.858.

Made 2026-09-19, resolving 2026-10-03 — a 14-day window, fixed before the outcome was known. Every field on this page was frozen when the call was made.

31%
what we said
stated on 2026-09-19, before the window opened
calls table · probability
22%
how often it happens anyway
BD's own base rate at issue — we sit +10pts from it
calls table · base_rate
OPEN
not yet resolved
resolves 2026-10-03
resolver: fx_rates (daily USD reference rates)
The criterion

Frozen at issue

Hit if the currency's peak rate against USD inside the window exceeds the issue-day reference (122.858054) by at least 0.29%. Peak, not endpoint: a devaluation that retraces still happened.

The resolver is external — fx_rates (daily USD reference rates) — and the daily snapshot of this call in ledger-snapshots/ carries GitHub's timestamps. Diff any two dated files to verify nothing above moved after 2026-09-19.

History

Every BD currency call

2026-09-20call #279532% · resolves 2026-10-04 2026-09-18call #266630% · resolves 2026-10-02 2026-09-17call #260129% · resolves 2026-10-01 2026-09-16call #253635% · resolves 2026-09-30 2026-09-15call #247134% · resolves 2026-09-29 2026-09-14call #240634% · resolves 2026-09-28 2026-09-13call #234134% · resolves 2026-09-27 2026-09-12call #227635% · resolves 2026-09-26 2026-09-11call #221236% · resolves 2026-09-25 2026-09-10call #214629% · resolves 2026-09-24 2026-09-09call #208036% · resolves 2026-09-23 2026-09-08call #200035% · resolves 2026-09-22 2026-09-07call #193534% · resolves 2026-09-21 2026-09-06call #1870said 33% · HIT 2026-09-05call #1805said 33% · HIT 2026-09-04call #1741said 31% · HIT 2026-09-03call #1677said 30% · HIT 2026-09-02call #1612said 29% · HIT 2026-09-01call #1547said 34% · MISS 2026-08-31call #1482said 33% · MISS

← The full ledger · the same data as JSON

Daily snapshots of this book are committed to the public repository — ledger-snapshots/ — so the stated probabilities and thresholds carry GitHub's timestamps, not ours. A reader can verify no call moved between issuance and resolution without trusting us.