ZZ.Money · reserve-backed digital money · one token per currency

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.

Latest observation 16 Nov 2026, 18:55:08 · 30s ago

Reserve ratio · PKR

R(t) / L(t) · must be at least 1.0000

1.049671Above the warning line
Excess reserve (R − L)
250,000.00PKR
Alert ladder
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. 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

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.

1.0500001.00000012:3222:4108:4518:55latest1.049671warn1.005000halt minting1.000500peg breach1.000000
Reserve ratio · 456 observations · hover or focus the chart and use arrow keys to read one

Total reserves against total liabilities

The pair the ratio is derived from, published as levels in their own right. R is every reserve account in ${currency}; L is outstanding claims, read as the larger of on-chain supply and ledger claims plus redemptions in flight.

Total reserves — R(t)
5,283,128.75PKR
block=3160209
Total liabilities — L(t)
5,033,128.75PKR
max(chain 5033128.750000, booked 5033128.750000) at block 3160209; chain leads
Excess reserve — R − L
250,000.00PKR
What backs the peg beyond the claims outstanding. The ratio says whether; this says how much.
250,000.000.0006:5618:5806:5318:55latest250,000.00fully backed0.00
Excess reserve (PKR) · 432 observations · hover or focus the chart and use arrow keys to read one

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

Booked in the ledger and not yet confirmed on chain. One dispatch cycle behind is normal; a figure that keeps growing is the earliest signal that settlement is silently failing.

250,000.000.0017 Oct27 Oct06 Nov16 Novlatest0.00
Pending settlement (ETK) · 479 observations · hover or focus the chart and use arrow keys to read one

Settlement epoch

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.

Open
Epoch
#556
Net, on chain
zero net — a valid, quiet day
Settled on chain
not yet
0 submissions
Opened
16 Nov 2026, 17:00:00

Accepting transactions.

Peg deviation — free funds

|VWAP − 1.00| / 1.00, over free ETK on the P2P book. The line sits at zero when the market prices ETK at par.

P2P VWAP
—
no trades in window

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

not published

There is no restricted series, and there cannot be one. Nothing creates restricted funds: the agent commission is paid on a merchant deposit, out of that merchant's own fee, and nothing is paid at cash-in. So no ETK is restricted and no restricted market price exists.

Absent by construction, not unimplemented. This page shows deviation over free funds, which is every ETK, beside the dormant restriction's size below. A deployment that paid the commission at the counter again would bring restricted funds back, and with them the reason for a second series.

Restricted funds outstanding
0.00ETK
Dormant: nothing creates restricted funds, so this reads zero. Above zero means something restricts funds again.

Hatch headroom

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.

Headroom remaining
100bps

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.

Committed to the live rate cardConfigured hatch 500 bps

The hatch has to cover the most generous active agent commission, the most generous cash-out agent rate, and a 100bps platform margin (I20). The hatch itself is dormant — nothing creates the restricted funds it releases — and I20 is still checked, so a return to paying commission at the counter finds the hatch already priced. 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, and never corrected by raising the hatch automatically: the hatch is a guardrail two people move, as a change of its own.

100017 Oct27 Oct06 Nov16 Novlatest100I20 floor0
Hatch headroom (bps) · 479 observations · hover or focus the chart and use arrow keys to read one

Deployed equity and working-capital lag

Figures of the dormant cash-in commission path. The agent commission is paid on a merchant deposit, out of that merchant's own fee in the same transaction, so nothing is paid at cash-in and nothing waits to be recovered: these read zero and the lag is not published. They stay because a deployment that paid the commission at the counter again would need them.

Deployed equity — commissions paid, not yet recovered
0.00ETK
0 pairing(s) recovered so far
Deployed principal
0.00ETK
Working-capital lag
not published
Median from a commission to the deposit that recovered it, weighted by amount. Withheld entirely when the replay disagrees with the counter it reimplements.
0.0017 Oct27 Oct06 Nov16 Novlatest0.00
Deployed equity (ETK) · 479 observations · hover or focus the chart and use arrow keys to read one

Latest balance commitment

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.

Submitted
Root · epoch 120088
0x6dcd55689e54a6f065d4a26f2d1fae4934bd236e8686e68e9a2a7d726fae4222
22 balance leaves · 0 ruling leaves · chain block 3,160,209

A receipt is not proof.

Root sum
7,288,425.400000 ETK
On-chain supply at that block
7,288,425.400000 ETK
Pending settlement then
0.000000 ETK
Confirmed
not yet

The root is only published when its own sum equals on-chain supply plus pending settlement (I14). These three figures are the check itself, kept on the row so a failure is legible without re-deriving anything.

Rounding residual

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.

Balance
0.000000ETK
Rate of change
0.000000ETK/hour
over 59.27536599999999822330210008658468723297119140625s since the previous observation
0.00000017 Oct27 Oct06 Nov16 Novlatest0.000000
Rounding residual (ETK) · 479 observations · hover or focus the chart and use arrow keys to read one

Every published figure

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.

Every metric recorded into metrics_snapshot, at full stored precision.
MetricNameStored valueUnitObserved (Bangladesh time)
Deployed equity
0 pairing(s) recovered so far
equity.deployed0.000000ETK16 Nov 2026, 18:55:08
30s ago
Deployed principalequity.deployed_principal0.000000ETK16 Nov 2026, 18:55:08
30s ago
fees.revenue_variancefees.revenue_variance0.000000—16 Nov 2026, 01:00:00
18h ago
fees.revenue_variance.arsfees.revenue_variance.ars0.000000—16 Nov 2026, 01:00:00
18h ago
fees.revenue_variance.inrfees.revenue_variance.inr0.000000—16 Nov 2026, 01:00:00
18h ago
fees.revenue_variance.pkrfees.revenue_variance.pkr0.000000—16 Nov 2026, 01:00:00
18h ago
fees.revenue_variance.usdfees.revenue_variance.usd0.000000—16 Nov 2026, 01:00:00
18h ago
Hatch headroom
hatch 500bps against 400bps required
hatch.headroom_bps100.000000bps16 Nov 2026, 18:55:08
30s ago
Total liabilities (L)
max(chain 7288425.400000, booked 7288425.400000) at block 3160209; chain leads
liabilities.outstanding7,288,425.400000BDT16 Nov 2026, 18:55:08
30s ago
Total liabilities (L), ARS
max(chain 80000000.000000, booked 80000000.000000) at block 3160209; chain leads
liabilities.outstanding.ars80,000,000.000000ARS16 Nov 2026, 18:55:08
30s ago
Total liabilities (L), INR
max(chain 5016544.000000, booked 5016544.000000) at block 3160209; chain leads
liabilities.outstanding.inr5,016,544.000000INR16 Nov 2026, 18:55:08
30s ago
Total liabilities (L), PKR
max(chain 5033128.750000, booked 5033128.750000) at block 3160209; chain leads
liabilities.outstanding.pkr5,033,128.750000PKR16 Nov 2026, 18:55:08
30s ago
Total liabilities (L), USD
max(chain 51190.000000, booked 51190.000000) at block 3160209; chain leads
liabilities.outstanding.usd51,190.000000USD16 Nov 2026, 18:55:08
30s ago
Excess reservereserve.excess1,000,000.000000BDT16 Nov 2026, 18:55:08
30s ago
Excess reserve, ARSreserve.excess.ars1,500,000.000000ARS16 Nov 2026, 18:55:08
30s ago
Excess reserve, INRreserve.excess.inr100,000.000000INR16 Nov 2026, 18:55:08
30s ago
Excess reserve, PKRreserve.excess.pkr250,000.000000PKR16 Nov 2026, 18:55:08
30s ago
Excess reserve, USDreserve.excess.usd1,000.000000USD16 Nov 2026, 18:55:08
30s ago
Reserve ratio
R=8288425.400000 L=7288425.400000 booked=7288425.400000 block=3160209
reserve.ratio1.137204—16 Nov 2026, 18:55:08
30s ago
Reserve ratio, ARS
R=81500000.000000 L=80000000.000000 booked=80000000.000000 block=3160209
reserve.ratio.ars1.018750—16 Nov 2026, 18:55:08
30s ago
Reserve ratio, INR
R=5116544.000000 L=5016544.000000 booked=5016544.000000 block=3160209
reserve.ratio.inr1.019934—16 Nov 2026, 18:55:08
30s ago
Reserve ratio, PKR
R=5283128.750000 L=5033128.750000 booked=5033128.750000 block=3160209
reserve.ratio.pkr1.049671—16 Nov 2026, 18:55:08
30s ago
Reserve ratio, USD
R=52190.000000 L=51190.000000 booked=51190.000000 block=3160209
reserve.ratio.usd1.019535—16 Nov 2026, 18:55:08
30s ago
Total reserves (R)
block=3160209
reserve.total8,288,425.400000BDT16 Nov 2026, 18:55:08
30s ago
Total reserves (R), ARS
block=3160209
reserve.total.ars81,500,000.000000ARS16 Nov 2026, 18:55:08
30s ago
Total reserves (R), INR
block=3160209
reserve.total.inr5,116,544.000000INR16 Nov 2026, 18:55:08
30s ago
Total reserves (R), PKR
block=3160209
reserve.total.pkr5,283,128.750000PKR16 Nov 2026, 18:55:08
30s ago
Total reserves (R), USD
block=3160209
reserve.total.usd52,190.000000USD16 Nov 2026, 18:55:08
30s ago
Restricted funds outstandingrestricted.outstanding0.000000ETK16 Nov 2026, 18:55:08
30s ago
Rounding residualrounding_residual.balance0.000000ETK16 Nov 2026, 18:55:08
30s ago
Residual rate of change
over 59.27536599999999822330210008658468723297119140625s since the previous observation
rounding_residual.per_hour0.000000ETK/hour16 Nov 2026, 18:55:08
30s ago
Pending settlementsettlement.pending0.000000ETK16 Nov 2026, 18:55:08
30s 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 — a metric the job failed to compute is listed here, not rendered as an empty tile.

  • commitment.rebuild_mismatch
  • equity.working_capital_lag_days
  • peg.deviation.free
  • peg.vwap