Connect
Cover: Solvency as one inequality: backing minus owed

Solvency as one inequality: backing minus owed

How do you check, without trusting anyone, that the staking contract holds what it owes?

The staking contract answers one question in public: does the BZPX it holds cover what it owes, within a fixed dust? Four free view calls and a five-bit audit mask let any reader redo the check on any node.

Known formally as Whitepaper 2.4, section 25.10: reading solvency yourself in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · article updated 2026-11-16 · site dataset through 2026-11-19 · 6 min · written from the deployed bytecode

By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.

Abstract in 15 languages · resumo · resumen · 摘要 · 要旨 · ملخص

English — Anyone can check that the staking contract holds what it owes by calling four view functions and comparing two numbers: backing() is the BZPX it holds, owed() is every claim on it, and it is solvent when backing() + dust >= owed(), with dust fixed at 1e10 wei. The engine is pre-launch, so this is a procedure to run once the contract exists.

Português — Qualquer pessoa pode verificar que o contrato de staking detém o que deve, chamando quatro funções view e comparando dois números: backing() é o BZPX que detém, owed() é cada reivindicação sobre ele, e é solvente quando backing() + dust >= owed(), com a dust fixada em 1e10 wei. O motor está em pré-lançamento, pelo que isto é um procedimento a executar quando o contrato existir.

Español — Cualquiera puede comprobar que el contrato de staking tiene lo que debe llamando a cuatro funciones view y comparando dos números: backing() es el BZPX que posee, owed() es cada reclamación sobre él, y es solvente cuando backing() + dust >= owed(), con la dust fijada en 1e10 wei. El motor está en prelanzamiento, así que es un procedimiento para ejecutar cuando el contrato exista.

Français — N'importe qui peut vérifier que le contrat de staking détient ce qu'il doit en appelant quatre fonctions view et en comparant deux nombres : backing() est le BZPX qu'il détient, owed() est chaque créance sur lui, et il est solvable quand backing() + dust >= owed(), avec la dust fixée à 1e10 wei. Le moteur est en pré-lancement, c'est donc une procédure à exécuter une fois le contrat déployé.

Deutsch — Jeder kann prüfen, ob der Staking-Vertrag hält, was er schuldet, indem er vier View-Funktionen aufruft und zwei Zahlen vergleicht: backing() ist das gehaltene BZPX, owed() ist jeder Anspruch darauf, und er ist solvent, wenn backing() + dust >= owed() gilt, mit dust fest bei 1e10 wei. Die Engine ist vor dem Start, dies ist also ein Verfahren für die Zeit, wenn der Vertrag existiert.

Русский — Любой может проверить, что контракт стейкинга держит столько, сколько должен: вызвать четыре view-функции и сравнить два числа. backing() — это BZPX на его балансе, owed() — все требования к нему, и он платёжеспособен, когда backing() + dust >= owed(), где dust зафиксирован на 1e10 wei. Движок ещё не запущен, поэтому это процедура на момент, когда контракт появится.

Türkçe — Herkes, dört view fonksiyonunu çağırıp iki sayıyı karşılaştırarak staking kontratının borcunu karşılayıp karşılamadığını kontrol edebilir: backing() elinde tuttuğu BZPX, owed() üzerindeki her talep ve backing() + dust >= owed() olduğunda ödeme gücü vardır; dust 1e10 wei olarak sabittir. Motor lansman öncesindedir, bu yüzden bu, kontrat var olduğunda uygulanacak bir prosedürdür.

العربية — يستطيع أي شخص التحقق من أن عقد الستيكنغ يحتفظ بما عليه بمجرد استدعاء أربع دوال view ومقارنة رقمين: backing() هو الـ BZPX الذي يحتفظ به، وowed() هو كل مطالبة عليه، وهو ملائم مالياً عندما backing() + dust >= owed()، مع تثبيت dust عند 1e10 wei. المحرك في مرحلة ما قبل الإطلاق، لذا هذا إجراء يُنفَّذ عند وجود العقد.

हिन्दी — कोई भी जाँच सकता है कि स्टेकिंग कॉन्ट्रैक्ट के पास उतना है जितना उस पर बकाया है: चार view फ़ंक्शन कॉल करें और दो संख्याओं की तुलना करें। backing() उसके पास मौजूद BZPX है, owed() उस पर हर दावा है, और वह सॉल्वेंट है जब backing() + dust >= owed() हो, जहाँ dust 1e10 wei पर तय है। इंजन लॉन्च-पूर्व है, इसलिए यह कॉन्ट्रैक्ट मौजूद होने पर चलाने की प्रक्रिया है।

日本語 — 誰でも、四つの view 関数を呼び出して二つの数値を比べることで、ステーキングコントラクトが負債に見合う額を保有しているか確かめられます。backing() は保有する BZPX、owed() はそれに対するすべての請求で、backing() + dust >= owed() のとき支払能力があります。dust は 1e10 wei に固定です。エンジンはローンチ前なので、これはコントラクトが存在してから実行する手順です。

中文 — 任何人都可以通过调用四个 view 函数并比较两个数字,来检查质押合约是否持有它所欠的数额:backing() 是它持有的 BZPX,owed() 是对它的全部债权,当 backing() + dust >= owed() 时即为有偿付能力,其中 dust 固定为 1e10 wei。该引擎尚未上线,因此这是合约存在之后再执行的步骤。

한국어 — 누구나 view 함수 네 개를 호출해 두 숫자를 비교함으로써 스테이킹 컨트랙트가 갚아야 할 만큼을 보유하는지 확인할 수 있습니다. backing()은 보유한 BZPX, owed()는 그에 대한 모든 청구이며, backing() + dust >= owed()이면 지급 능력이 있고 dust는 1e10 wei로 고정됩니다. 엔진은 출시 전이므로 컨트랙트가 존재한 뒤 실행할 절차입니다.

Bahasa Indonesia — Siapa pun dapat memeriksa bahwa kontrak staking memegang sebanyak yang menjadi kewajibannya dengan memanggil empat fungsi view dan membandingkan dua angka: backing() adalah BZPX yang dipegangnya, owed() adalah semua klaim atasnya, dan kontrak solven ketika backing() + dust >= owed(), dengan dust tetap 1e10 wei. Mesin ini pra-peluncuran, jadi ini prosedur yang dijalankan setelah kontrak ada.

বাংলা — যে কেউ চারটি view ফাংশন কল করে দুটি সংখ্যা তুলনা করে যাচাই করতে পারে যে স্টেকিং কন্ট্র্যাক্টের কাছে তার দেনা মেটানোর মতো আছে কি না: backing() হলো তার হাতে থাকা BZPX, owed() হলো তার ওপর সব দাবি, এবং backing() + dust >= owed() হলে সে সলভেন্ট, যেখানে dust 1e10 wei-তে স্থির। ইঞ্জিনটি চালুর আগের পর্যায়ে, তাই এটি কন্ট্র্যাক্ট থাকলে চালানোর একটি পদ্ধতি।

Filipino — Masusuri ng sinuman kung hawak ng staking contract ang inuutang nito sa pamamagitan ng pagtawag sa apat na view function at paghahambing ng dalawang numero: ang backing() ay ang BZPX na hawak nito, ang owed() ay lahat ng claim dito, at solvent ito kapag backing() + dust >= owed(), na may dust na nakapirmi sa 1e10 wei. Pre-launch pa ang engine, kaya ito ay pamamaraang gagawin kapag umiiral na ang contract.

Short answer: call four view functions and compare two numbers. `backing()` is the BZPX the contract physically holds. `owed()` is every claim on it, recorded bad debt included and never netted against anything. The contract is solvent when `backing() + dust >= owed()`, with the dust fixed at `CONSERVATION_DUST` = 1e10 wei. That one inequality is `isSolvent()`.

The point of the design is that a reader does not have to trust a dashboard. The staking engine is pre-launch, so this is a procedure to run once the contract exists, not a reading anyone can take today.

Four functions, in increasing detail

`owed()` and `backing()` give the two sides. `isSolvent()` is exactly `!_hardBreach()`, the same condition that lets anyone trip the circuit breaker: `isSolvent()` is false exactly when `tripBreaker` would succeed outside an emergency. `solvency()` returns a report with a collateralisation ratio in WAD, `backing * 1e18 / owed` floored, where 1e18 means exactly covered. That ratio is published by a single producer, and `solvency()` reports that reading rather than a second copy of it (the rule in the article on one question and one producer).

The five bits of auditInvariants

`auditInvariants()` returns a bitmask with one bit per check. Zero means every check holds. Only bit 0 gates the breaker. Bit 1 is a signal, not a guard, because a position can be briefly unhealthy before a liquidation closes it.

BitName in the sourceMeaningGates tripBreaker
0Conservationbalance + dust < owed (a hard breach)yes
1Solvencydebt above 95 % of stake, or stake 0 with debt outstandingno, a signal
2EmissionCaprewardReserve above TOTAL_REWARDSno
3Monotonicityan accumulator fell below its snapshotno
4BoostBoundedweights exceed the stake they were built onno

Source: Whitepaper 2.4, TAB-25.10. Bit 3 is raised by the permissionless touchAuditSnapshot, which moves no value.

Where the inequality is enforced

The modifier `conserves` wraps every value-moving transaction. It compares the change on the two sides of the master identity, balance + total debt + total bad debt + stakedOverdraw on one side, total staked + reward reserve + protocol reserve + pending distribution on the other, within dust, and reverts if the transaction leaks value. The identity is checked on the change across the call, so rounding drift from the past cancels and only a transaction that itself leaks value fails. `emergencyWithdraw` and `syncEquity` sit outside the modifier so they stay callable in a breach. The identity itself is the subject of the article on the master conservation identity.

Two tests keep the inequality honest between releases: `invariant_solvent` and `invariant_backingCoversOwed`, stateful invariants that run a randomised sequence of calls and then check the inequality.

How to read a true

A view that returns true means solvent on what has been recorded. A loss that has not yet been written down, such as a borrower whose accrued debt has passed the stake, is read in part until a sweep, a liquidation or the borrower's own emergency exit records it. The paper says so in section 25.10, and the repository documents the same reading. Reading `owed()` therefore as a lower bound until the next sweep is the careful way to read it.

  1. With any RPC of your choice, pick a block and note its number.
  2. Call `owed()`, `backing()`, `isSolvent()` and `auditInvariants()` at that block.
  3. Add 1e10 to `backing()` and compare the sum with `owed()` yourself. The answer must match `isSolvent()`.
  4. Read `auditInvariants()` as bits: 0 means all five checks hold, and any set bit names its check in the table above.

What this does not claim

It does not say a shortfall cannot happen: it says how a shortfall is made visible and what the contract does about it. It publishes no reading, because there is no deployed contract to read yet. And it takes nothing from our servers: the four values and the block number are all you need.

Do not trust this page — reproduce it

Every claim above is checkable against the chain. Start here:

Before launch, run the stateful tests invariant_solvent and invariant_backingCoversOwed in BlazePhoenixStaking.t.sol (and the same check in InvariantsFullSurface.t.sol) at commit c0366cf of the staking repository. After launch, call owed(), backing(), isSolvent() and auditInvariants() at a block of your choice and compare backing() + 1e10 with owed(). Reading: section 25.10 of the 2.4 whitepaper.
Cite this article

Licensed CC BY-NC-ND 4.0: quote and cite it with attribution and a link. Commercial use and derivative versions need written permission from BlazePhoenix; translations are made by BlazePhoenix. Copy a ready-made citation:

BlazePhoenix (2026). Solvency as one inequality: backing minus owed. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/solvency-as-one-inequality/
@misc{blazephoenix_solvency_as_one_inequality,
  title  = {Solvency as one inequality: backing minus owed},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/solvency-as-one-inequality/},
  note   = {Accessed: reproduce the claim with the command above}
}

Writing an answer, a wiki entry or a paper? The claim above is reproducible against the chain before you quote it — which is the only sound basis for citing a technical source at all.

Contracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF).

Related engineering

Next in Foundations · 6 / 33
Screening Uniswap V4 hooks by arithmetic: why BlazePhoenix never asks a hook anything ›A V4 hook is arbitrary code inside your settlement. BlazePhoenix refuses delta-altering hooks with a bit test on the hook address — before any token moves and without calling it — backed by a codehash-pinned allow-list and the projector Ξ.7 min

Questions, a partnership or a bug to report? Contact us or email contact@blazephoenix.xyz

Go to APP