Kosh · digital taka · 1 ETK = 1 BDT
Reserve transparency
Every figure below is an observation the platform recorded into metrics_snapshot once a minute, published without authentication. Nothing here is computed by this page: where a number is not recorded, the page says so instead of deriving one.
Reserve ratio §4.3
R(t) / L(t) · must be at least 1.0000
- 1.0050
- warn
- 1.0005
- halt minting
- 1.0000
- pause and incident
Read the ratio as an interim measure. A 150,000 buffer is RR 1.15 at L=1M and RR 1.0015 at L=100M — identical protection, unrecognisably different numbers. The threshold that means something is coverage: excess reserve against p99 daily clawback exposure (§7.11). L is also read conservatively — the larger of on-chain supply and ledger claims plus redemptions in flight — so this ratio can only read lower than a chain-only denominator would, never higher.
Reserve ratio over time§4.3
The three alert lines are drawn where they actually sit. Below 1.005 is a warning; below 1.0005 minting halts; below 1.0 is a peg breach and a full pause.
Not enough observations in this window to draw a line. The snapshot job writes one row a minute; two are needed.
Total reserves against total liabilities§4.3
The pair the ratio is derived from, published as levels in their own right. R is every reserve account in BDT; L is outstanding claims, read as the larger of on-chain supply and ledger claims plus redemptions in flight.
Not enough observations in this window to draw a line. The snapshot job writes one row a minute; two are needed.
Why the gap is charted and not the pair. R and L differ by a fraction of a percent, so two lines would be one line. The excess is the same comparison at a scale where it can be read, and it is a figure the platform publishes rather than one this page computed. All three — R, L and their difference — are recorded observations; nothing here is derived in the browser.
Pending settlement§7.12
Booked in the ledger, not yet netted on chain. The earliest signal that settlement is silently failing.
Settlement epoch§7.2
Epochs are a state machine, not a cron job: epoch N+1 cannot seal until epoch N is CLOSED (I11). The pending figure above cannot be read without this — the same number is healthy under an OPEN epoch and an incident under a FAILED one.
- Epoch
- #3
- Net, on chain
- zero net — a valid, quiet day
- Settled on chain
- not yet
- 0 submissions
- Opened
- 23 Sept 2026, 15:00:00 UTC
Accepting transactions.
Peg deviation — free funds§4.3
|VWAP − 1.00| / 1.00, over free ETK on the P2P book. The line sits at zero when the market prices ETK at par.
Not enough observations in this window to draw a line. The snapshot job writes one row a minute; two are needed.
Peg deviation — restricted funds§4.3, §5.5b
not publishedThere is no restricted series, and there cannot be one. An earlier draft of §4.3 asked for peg deviation split by fund class, reasoning that restricted ETK would trade at a discount. It cannot: §5.5b forbids selling restricted funds and the P2P order path enforces it, so restricted ETK never reaches the book and no restricted market price exists. The split was solving a problem the restriction already prevented.
Absent by construction, not unimplemented. §4.3 now asks for deviation over free funds — the only ETK with a market — beside the size of the population that has none, which is the figure below. If restricted P2P sales are ever allowed, that change is the reason to add a second series.
- Restricted funds outstanding §5.5b
- 0.00ETK
- The size of the population with no market — it may leave only through a merchant deposit or the hatch (I17).
Hatch headroomI20
Visible here so the margin can be watched before a fee proposal breaches it. A number checked only at approval time is invisible until someone trips it.
The hatch is configured above what the live rates require. That gap is deliberate negotiating room: a rate rise may consume it, and once it is gone the next proposal is rejected until the hatch itself is raised.
The hatch has to cover the most generous active cash-in commission, the most generous cash-out agent rate, and a 100bps platform margin — that margin is what makes a faked cash-in loss-making rather than merely break-even. The headroom is what a new fee rule may consume before the approval path must reject it. It is checked at startup and at every fee-rule approval — never auto-corrected by raising the hatch, which would reprice everyone already holding restricted funds.
Deployed equity and working-capital lag§0.5
The agent commission is paid at cash-in and recovered only when the funds reach a merchant. The platform carries that gap as working capital, and neither figure is derivable from the ledger alone — a commission is recovered by a deposit days later that carries no reference back to it.
Latest balance commitment§13.3
A Merkle sum root over off-chain balances, published each epoch so a transfer is provable without a chain write per transfer. Any holder can demand a proof against this root.
No balance commitment has been built yet.
Rounding residual§4.4
Sub-poisha dust, booked to its own account so every transaction still sums to zero (I2, I9) rather than being discarded. It is meant to drift slowly; fast movement is a bug.
Every published figure§4.4
At the precision it was stored. Nothing on this page is reachable only by hovering, and no rounding above hides a digit that is not printed here.
| Metric | Name | Stored value | Unit | Observed |
|---|---|---|---|---|
| Deployed equity§0.5 0 pairing(s) recovered so far | equity.deployed | 0.000000 | ETK | 23 Sept 2026, 15:22:15 UTC 0s ago |
| Deployed principal§0.5 | equity.deployed_principal | 0.000000 | ETK | 23 Sept 2026, 15:22:15 UTC 0s ago |
| Hatch headroomI20 hatch 500bps against 400bps required | hatch.headroom_bps | 100.000000 | bps | 23 Sept 2026, 15:22:15 UTC 0s ago |
| Restricted funds outstanding§5.5b | restricted.outstanding | 0.000000 | ETK | 23 Sept 2026, 15:22:15 UTC 0s ago |
| Rounding residual§4.4 | rounding_residual.balance | 0.000000 | ETK | 23 Sept 2026, 15:22:15 UTC 0s ago |
| Residual rate of change§4.4 over 59.912519000000003188688424415886402130126953125s since the previous observation | rounding_residual.per_hour | 0.000000 | ETK/hour | 23 Sept 2026, 15:22:15 UTC 0s ago |
| Pending settlement§7.12 | settlement.pending | 220,000.000000 | ETK | 23 Sept 2026, 15:22:15 UTC 0s ago |
Recorded by this system, but not observed yet
Named rather than left blank. “Nothing happened” and “I could not tell” must not look the same (§7.4a) — a metric the job failed to compute is listed here, not rendered as an empty tile.
- commitment.rebuild_mismatch
- equity.working_capital_lag_days
- fees.revenue_variance
- liabilities.outstanding
- peg.deviation.free
- peg.vwap
- reserve.excess
- reserve.ratio
- reserve.total