Language:
PRODUCTS
SECTORS
MORE
Quantum Security 🔍 Search Request Access →
gateCentralBankReserve — Central Bank Minimum Reserve Gate
// The problem

Minimum reserve was previously a paper principle, checked only after the fact.

The European Central Bank requires commercial banks to hold one percent of their reserve base. gateCentralBankReserve turns this into a cryptographically enforced principle: requirement correctly calculated, average maintained, penalty interest where due, exemption on record. If any one is missing, the money does not move.

No draining the reserve via the released amount
The gate compares the reported balance against the calculated requirement before every transaction. The bank cannot drain the reserve to redirect the released amount elsewhere, the outflow is physically blocked.
// Architecture

Four clusters, checked sequentially.

Every cluster is dispositive (material_block_mode: true), a hit blocks bindingly, not merely for documentation. That is the default at this systemic bottleneck.

CLUSTER 1
Reserve Calculation
Calculates the minimum reserve requirement from the reported reserve base multiplied by the hard-coded reserve ratio of one percent and compares it against the reported balance.
reserve_base_eur · required_ratio_pct · reported_balance_eur
CLUSTER 2
Average Fulfilment
Calculates the genuine average of all daily closing balances over the entire maintenance period under Art. 8 of Regulation (EU) 2021/378, to rule out sham compliance through short-term deposits before period end.
daily_balances_series · average_balance_eur · maintenance_period_days
CLUSTER 3
Penalty Interest
If a shortfall is conceded, checks whether a penalty-interest calculation under Art. 5 of ECB Regulation No. 2531/98 has been performed and produced a positive amount.
shortfall_confirmed · penalty_interest_calculated · penalty_amount_eur
CLUSTER 4
Exemptions
For every exemption (e.g. institutions in resolution under Art. 4(2)), requires proof of Bundesbank recognition. Without proof of exemption, a resolution-bank is not waved through.
exemption_claimed · bundesbank_exemption_proof
Fatal test case: average fulfilment below requirement
A regional bank achieves only €8.9m on a period-average basis against a requirement of €11.2m. BLOCK_R2_AVERAGE_FULFILLMENT_SHORTFALL fires before the payout occurs.
// Test results

Two tested scenarios.

All values on this page are fictional test data and serve only to illustrate the gate logic.

Scenario C1C2C3C4 Verdict Latency
Sparkasse X, €12.4m reserve requirement met over the averaging periodPASSPASSPASSPASSCENTRAL_BANK_RESERVE_SEALED394ms
Regional bank Y, average fulfilment €8.9m below requirement €11.2mPASSFAILnot evaluatednot evaluatedBLOCK_R2_AVERAGE_FULFILLMENT_SHORTFALL441ms
Cryptographic chain continuation
Every test produces a deterministic receipt_id (VAR-RSRV-{TENANT}-{SEQ}), an input_snapshot_hash, an HMAC-SHA256 signature, and a merkle_link to the previous receipt. Timestamps are supplied exclusively by the caller, never derived from the system clock. Sanctions screening runs live via the OpenSanctions API. Any exception to a block requires six-eyes approval. External trust anchors (TSA timestamp, Shamir quorum signature) are attached asynchronously and carry PENDING status until then.
// Clarification

What gateCentralBankReserve is not.

  • Not automatic recognition by the Bundesbank or ECB. The gate delivers a cryptographic proof, not supervisory approval.
  • Not an independent regulatory-reporting system. The gate seals the pre-check, it does not replace an existing Bundesbank reporting procedure.

For commercial banks and central banks that want to make minimum reserve fulfilment provable.

GATE CATALOG · REGULATORY DETERMINATION DOMAIN

gateCentralBankReserve

gateCentralBankReserve determines encoded reserve, liquidity, account, settlement and monetary-infrastructure conditions. The gate contributes a bound regulatory determination state; it creates neither regulatory authority nor Execution Permission.

DOMAIN_DETERMINATION_ONLY = true · EXECUTION_AUTHORITY = false · EXECUTION_PERMISSION = false
gateCentralBankReserve regulatory determination domain
AUTHORITY BOUNDARY

RESERVE STATE IS NOT CENTRAL-BANK AUTHORITY.

CAN

  • deterministically evaluate encoded regulatory conditions
  • bind determinations to source, scope, time and input state
  • surface missing, expired or conflicting regulatory dependencies
  • produce attributable evidence for the concrete determination

CANNOT

  • replace a regulator, supervisor, court or competent institution
  • create legal or regulatory authority through score, consensus, AI or administration
  • turn a gate PASS into an Execution Right on its own
  • mint an ExecutionCapabilityToken on its own
REGULATORY STATE

Regulatory determination is evidence. Not regulatory authority.

SOURCE

Authoritative source

The relevant rule must originate outside the system from a legitimate normative or institutional source.

SCOPE

Defined matter

The determination is limited to the encoded subject, entity, transaction or operation under review.

TIME

Point-in-time state

Effective dates, transition periods, expiry and version state remain explicit.

INPUT

Canonical input

A reproducible determination requires a defined canonical input state.

DEPENDENCY

Dependencies

Missing or contradictory dependencies remain visible rather than being converted into invented permission.

EVIDENCE

Bound evidence

The resulting state can be bound to source, input, scope and time for later verification.

RELATED DETERMINATION DOMAINS

Regulatory domains compose. They do not confer authority on one another.

Only scope-relevant determinations become dependencies in Execution Rights resolution. The links shown are not a universally mandatory sequence.

EXECUTION RIGHTS

Five dimensions. Regulatory state can inform them; no gate replaces them.

AAUTHORITY
RRULE
JJURISDICTION
TTIME
DDEPENDENCY
ALL FIVE REQUIRED DIMENSIONS VALID → VALID EXECUTION RIGHT · ANY REQUIRED DIMENSION ABSENT → NO VALID EXECUTION RIGHT → NO CAPABILITY → NO EXECUTION
INVARIANT

A regulatory PASS is a determination. Never a permission by itself.

AUTHORITY → DETERMINATION → EXECUTION RIGHTS → CAPABILITY OR NONE → EXECUTION OR NONE → EVIDENCE

Request Access →