Connect
Cover: A circuit breaker anyone may pull, but only by proving insolvency on-chain

A circuit breaker anyone may pull, but only by proving insolvency on-chain

Who can pause the staking contract, and when?

A pause held by arithmetic rather than a role: any address may halt the staking contract, but only while a solvency breach is readable from chain state, and the operator cannot lift it while the breach holds — a governance question converted into a proof obligation.

Known formally as The proof-gated breaker in the BlazePhoenix whitepaper.

BlazePhoenix Engineering · article updated 2026-08-13 · site dataset through 2026-11-19 · 10 min · written from the deployed bytecode

At a glance
LevelAdvanced
Formal nameThe proof-gated breaker
Reading time10 min
Sections7
Updated2026-08-13

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

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

English — Any address may halt the staking contract — there is no role on the call — but it succeeds only while insolvency is readable from chain state in-frame: the contract's token balance below what it owes, both sides recomputed, nothing accepted from calldata. Outsiders can only push the balance up by donating, so the condition can be prevented but never created; the operator cannot lift the emergency while the breach holds, and the log permanently flags proof-triggered versus discretionary halts.

Português — Qualquer endereço pode travar o contrato de staking — a chamada não tem role — mas ela só sucede enquanto a insolvência for legível do estado da chain no próprio frame: o saldo de tokens do contrato abaixo do que deve, ambos os lados recomputados, nada aceite da calldata. De fora só se pode empurrar o saldo para cima doando, logo a condição pode ser evitada mas nunca criada; o operador não pode levantar a emergência enquanto a violação persistir, e o log marca para sempre as paragens por prova contra as discricionárias.

Español — Cualquier dirección puede detener el contrato de staking — la llamada no tiene rol — pero solo tiene éxito mientras la insolvencia sea legible del estado de la cadena en el propio frame: el saldo de tokens del contrato por debajo de lo que debe, ambos lados recomputados, nada aceptado de la calldata. Desde fuera solo se puede empujar el saldo hacia arriba donando, así que la condición puede prevenirse pero nunca crearse; el operador no puede levantar la emergencia mientras persista la brecha, y el log marca para siempre las paradas por prueba frente a las discrecionales.

Français — N'importe quelle adresse peut arrêter le contrat de staking — l'appel n'a aucun rôle — mais il ne réussit que tant que l'insolvabilité est lisible depuis l'état de la chaîne dans le frame : le solde de tokens du contrat en dessous de ce qu'il doit, les deux côtés recalculés, rien accepté de la calldata. De l'extérieur on ne peut pousser le solde que vers le haut en donnant, donc la condition peut être empêchée mais jamais créée ; l'opérateur ne peut lever l'urgence tant que la brèche tient, et le journal marque à jamais les arrêts prouvés des arrêts discrétionnaires.

Deutsch — Jede Adresse darf den Staking-Contract anhalten — der Aufruf trägt keine Rolle —, aber er gelingt nur, solange die Insolvenz im Frame aus dem Chain-Zustand lesbar ist: der Token-Bestand des Contracts unter dem, was er schuldet, beide Seiten neu berechnet, nichts aus Calldata übernommen. Außenstehende können den Bestand nur durch Spenden nach oben drücken, die Bedingung also verhindern, aber nie erzeugen; der Operator kann den Notfall nicht aufheben, solange der Bruch besteht, und das Log kennzeichnet dauerhaft bewiesene gegenüber diskretionären Halts.

Русский — Любой адрес может остановить стейкинг-контракт — у вызова нет роли, — но он проходит лишь пока неплатёжеспособность читается из состояния цепи в том же фрейме: токен-баланс контракта ниже его обязательств, обе стороны пересчитаны, из calldata не принимается ничего. Извне баланс можно лишь поднять донатом — условие можно предотвратить, но нельзя создать; оператор не может снять аварийный режим, пока пробой держится, а лог навсегда помечает остановки по доказательству против дискреционных.

Türkçe — Herhangi bir adres staking sözleşmesini durdurabilir — çağrıda rol yoktur — ama yalnızca ödeme aczi zincir durumundan çerçeve içinde okunabilirken başarılı olur: sözleşmenin token bakiyesi borçlu olduğunun altında, iki taraf da yeniden hesaplanmış, calldata'dan hiçbir şey kabul edilmemiş. Dışarıdakiler bakiyeyi ancak bağışla yukarı itebilir; yani koşul önlenebilir ama asla yaratılamaz. İhlal sürerken operatör acil durumu kaldıramaz ve kayıt, kanıtla tetiklenen duruşları takdire dayalı olanlardan kalıcı olarak ayırır.

العربية — يجوز لأي عنوان إيقاف عقد الرهن — لا دور على الاستدعاء — لكنه لا ينجح إلا ما دام الإعسار مقروءاً من حالة السلسلة داخل الإطار: رصيد العقد من العملة دون ما يدين به، والجانبان محسوبان من جديد، ولا شيء يُقبل من الـcalldata. لا يستطيع الخارجيون إلا دفع الرصيد صعوداً بالتبرع، فالشرط يمكن منعه لكن لا يمكن خلقه أبداً؛ ولا يستطيع المشغّل رفع الطوارئ ما دام الخرق قائماً، والسجل يعلّم للأبد الإيقافات المثبتة مقابل التقديرية.

हिन्दी — कोई भी पता स्टेकिंग कॉन्ट्रैक्ट रोक सकता है — कॉल पर कोई रोल नहीं — पर वह तभी सफल होती है जब दिवालियापन उसी फ़्रेम में चेन-अवस्था से पठनीय हो: कॉन्ट्रैक्ट का टोकन-बैलेंस उसकी देनदारी से नीचे, दोनों पक्ष पुनर्गणित, calldata से कुछ स्वीकार नहीं। बाहरी लोग दान देकर बैलेंस केवल ऊपर धकेल सकते हैं, इसलिए शर्त रोकी जा सकती है पर कभी बनाई नहीं जा सकती; उल्लंघन रहते संचालक आपातकाल नहीं हटा सकता, और लॉग प्रमाण-जनित बनाम विवेकाधीन रोकों को स्थायी रूप से चिह्नित करता है।

日本語 — どのアドレスでもステーキングコントラクトを停止できます。呼び出しに役割は付いていません。しかし成功するのは、支払不能が同一フレーム内でチェーン状態から読み取れる間だけです。コントラクトのトークン残高が債務を下回ること。両辺は再計算され、calldataからは何も受け入れません。外部の者は寄付で残高を押し上げることしかできないため、条件を防ぐことはできても作り出すことは決してできません。違反が続く限り運営者は緊急事態を解除できず、ログは証明による停止と裁量による停止を恒久的に区別して記録します。

中文 — 任何地址都可以叫停质押合约——调用上没有角色——但只有当无力偿付能在同帧内从链上状态读出时才会成功:合约的代币余额低于其欠付,两边都重新计算,不从 calldata 接受任何断言。外人只能通过捐赠把余额推高,因此该条件可以被阻止却永远无法被制造;违约持续期间运营者无法解除紧急状态,日志还永久标记这次叫停是证明触发还是酌情决定。

한국어 — 어떤 주소든 스테이킹 컨트랙트를 정지시킬 수 있습니다 — 호출에는 역할이 없습니다 — 하지만 지급불능이 같은 프레임에서 체인 상태로부터 읽히는 동안만 성공합니다. 컨트랙트의 토큰 잔액이 채무보다 적어야 하고, 양변 모두 재계산되며, calldata에서는 아무것도 받아들이지 않습니다. 외부인은 기부로 잔액을 올릴 수만 있어 조건을 막을 수는 있어도 만들 수는 없습니다. 위반이 지속되는 동안 운영자는 비상사태를 해제할 수 없고, 로그는 증명으로 발동된 정지와 재량에 의한 정지를 영구히 구분해 남깁니다.

Bahasa Indonesia — Alamat mana pun boleh menghentikan kontrak staking — panggilan itu tanpa peran — tetapi hanya berhasil selama insolvensi terbaca dari keadaan chain di dalam bingkai: saldo token kontrak di bawah yang diutanginya, kedua sisi dihitung ulang, tak ada yang diterima dari calldata. Orang luar hanya bisa mendorong saldo naik lewat donasi, jadi kondisinya bisa dicegah tapi tak pernah bisa diciptakan; operator tak bisa mencabut darurat selama pelanggaran bertahan, dan log menandai permanen mana penghentian berbasis bukti dan mana yang diskresioner.

বাংলা — যে-কোনো ঠিকানা স্টেকিং কন্ট্রাক্ট থামাতে পারে — কলে কোনো রোল নেই — কিন্তু তা সফল হয় কেবল যতক্ষণ অস্বচ্ছলতা একই ফ্রেমে চেইন-অবস্থা থেকে পাঠযোগ্য: কন্ট্রাক্টের টোকেন-ব্যালেন্স তার দায়ের নিচে, দুই পক্ষই পুনর্গণিত, calldata থেকে কিছুই গৃহীত নয়। বাইরের কেউ কেবল দান করে ব্যালেন্স ওপরে ঠেলতে পারে, তাই শর্তটি ঠেকানো যায় কিন্তু কখনো তৈরি করা যায় না; লঙ্ঘন বজায় থাকতে অপারেটর জরুরি অবস্থা তুলতে পারে না, আর লগ প্রমাণ-উদ্ভূত বনাম বিবেচনামূলক থামাকে স্থায়ীভাবে চিহ্নিত করে।

Filipino — Maaaring ihinto ng kahit anong address ang staking na kontrata — walang role sa tawag — ngunit nagtatagumpay lamang ito habang nababasa ang insolvency mula sa estado ng chain sa loob ng frame: ang balanse ng token ng kontrata na mas mababa sa inuutang nito, muling kinukuwenta ang dalawang panig, walang tinatanggap mula sa calldata. Ang mga taga-labas ay makapagtutulak lamang ng balanse pataas sa pamamagitan ng donasyon, kaya ang kondisyon ay mapipigilan ngunit hindi kailanman malilikha; hindi maaalis ng operator ang emergency habang nananatili ang paglabag, at permanenteng minamarkahan ng log ang mga paghintong pinatunayan laban sa mga diskresyonaryo.

Every protocol that can be halted faces the same dilemma stated two ways. A pause button held by the team is a trust assumption: the strongest claim the system can make is that the holder will not misuse it. A pause button held by everyone is an attack: griefing costs one transaction. Almost all deployed designs pick the first and describe it as prudence.

The staking contract carries a third option. It can be halted by anybody — there is no role attached to the call — and what gates the call is not who you are but whether a specific condition currently holds on-chain: that the contract's actual token balance has fallen below what it owes. A caller either can prove insolvency or they cannot, and no amount of standing changes that.

Why the gate cannot be spoofed

Both sides of the comparison are read from chain state inside the frame that performs the check. Holdings are the token balance of the contract, read from the token. Obligations are recomputed from storage rather than accepted from calldata. Nothing is asserted by the caller, so there is nothing for the caller to lie about — the call either finds the condition true when it evaluates it, or it reverts.

The asymmetry that makes this safe against griefing is the more interesting half. The only direction an outsider can push the balance is upwards: anyone can donate tokens to the contract, and doing so can prevent the condition from holding but can never create it. There is no public operation that removes value from the contract without a matching reduction in what it owes. So the breaker is not a lever an attacker can pull at a moment of their choosing; it is a statement about the world that either is or is not currently true, and an attacker who could make it true has already done something worse than pause the protocol.

halt()  is callable by any address, and succeeds iff

        balance(token, this)  <  owed(state)          read in-frame, both sides

anyone can push the left side UP  (donation)   -> can prevent, never create
no public path pushes it DOWN without reducing the right side by the same amount

What tripping it does, and what it deliberately does not

When it trips, the breaker moves no funds. It pauses the protocol and opens every user's individual exit — which is the correct pairing, because a halt that locked users in while the contract was known to be short would convert an accounting problem into a confiscation. The exit returns stake minus debt.

And it cannot be quietly undone. The administrative call that lifts an emergency reverts while the breach still holds, so the operators can only cancel it by first making the contract solvent again. That is the property that distinguishes this from a pause with extra steps: the operator can build, but cannot override. The design converts a governance question — should we be paused? — into a proof obligation, and the obligation runs against the operator rather than against the user.

Finally, the two ways an emergency can begin are distinguished permanently in the log: the event carries a flag saying whether it came from the permissionless proof or from the guardian's discretion. Nobody can later describe a discretionary halt as a proven one, and nobody has to take our word for which it was.

The companion power, which is not proof-gated at all

The article would be marketing if it stopped there, because the same contract carries the strongest privileged power in either codebase, and it sits right beside the breaker. A guardian role may declare an emergency at its own discretion, with no on-chain condition required. While it stands it disables staking, withdrawing, claiming, borrowing and repaying, and only the same key can lift it.

What that power cannot do is take principal: the emergency exit path remains open throughout and pays out stake minus debt, and the protocol's own reserve withdrawal is bounded and hard-wired to a treasury address fixed at construction. So the guardian holds a power that punishes its own holder — it strands the protocol and frees the users — but it is a power, and it is the reason a staker's lock is not unconditional. Locks run from ninety days to seven years; in front of a commitment that long, a discretionary door that opens for everyone at once is a material trust assumption, and describing the lock as structural would misstate the guarantee a staker actually receives.

One further edge belongs in the same paragraph rather than a footnote. The emergency exit does not settle outstanding rewards first, so unclaimed rewards are forfeited by taking it. Liquidation, by contrast, settles rewards before it acts. A user leaving through the emergency path should claim first if claiming is available.

Role separation is a deployment-time property, not a code property

Both the administrative role and the guardian role are granted to the deployer. Unless they are separated at deployment time, the account that can declare an emergency is the same account that can do everything else, and the intended two-key design collapses into one. That is a configuration property rather than a code defect — which is precisely why it belongs in a threat model rather than a bug list, and why a reader evaluating a live deployment should check the two role holders on-chain rather than reading this article.

The generalisation is worth stating because it applies far beyond us: a separation-of-powers argument that depends on a deployment transaction is only as strong as the record of that transaction. If the two addresses are not independently verifiable, the design is a description of intent.

Why the breaker's own gate has a blind spot

A proof-gated mechanism is only as good as the expression it proves, and this one has a documented weakness that we would rather state than have found. The obligations side of the comparison is computed with saturating subtractions. Saturating arithmetic collapses an entire region of state onto a single value, and the region it collapses here is the inverted one: if obligations exceed what is recorded against them, the computation floors at zero rather than going negative.

The consequence is exact and unpleasant. In precisely the state the breaker exists to detect — deep insolvency of a particular shape — the obligations term can read zero, and a comparison against zero passes trivially. One of the disclosed findings has this signature: an underwater exit that reduced total debt without recording the bad debt it left behind, creating a phantom liability that both locks a hard breach and makes the cancellation path unreachable. That is a vacuity failure rather than a silence failure — the guard is invoked, evaluates, and is satisfied for a reason unrelated to the property — and it is a distinct category worth keeping separate in any audit vocabulary.

The finding is fixed and pinned by a regression test that fails against the vulnerable contract rather than merely passing against the fixed one. The structural lesson is not fixed and probably cannot be: an invariant expressed with saturating arithmetic carries a fibre it did not intend, and the fibre is usually over the pathology.

What remains trusted after all of this

A trustless claim from someone who cannot enumerate their exceptions is worth nothing, so: the guardian's discretionary emergency remains, as does the pause under which repayment and withdrawal stay open, the curated venue registry on the routing side, the curated list of intermediate tokens, the treasury destination fixed at construction, and the token itself. Powers can be permanently surrendered — the flag is written true at exactly one site, never written false, with no proxy and no selfdestruct through which the code could be replaced — and even then the surrender is not total: on the routing side the ability to add a venue or an intermediate survives renunciation while the ability to remove one does not, so anything added afterwards is permanent.

What a user need not trust is anyone to keep the protocol solvent, or to let them out. Those two are held by arithmetic. The distinction this article is about is the difference between that sentence and the much commoner one it resembles, which is that a team promises to be watching.

Do not trust this page — reproduce it

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

check the two role holders on the live deployment before relying on the separation, and confirm for yourself that the cancellation path reverts while a breach holds — the halt condition itself is a pure read of chain state, so you can evaluate it with an eth_call at any block
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). A circuit breaker anyone may pull, but only by proving insolvency on-chain. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/permissionless-circuit-breaker/
@misc{blazephoenix_permissionless_circuit_breaker,
  title  = {A circuit breaker anyone may pull, but only by proving insolvency on-chain},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/permissionless-circuit-breaker/},
  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 Safety mechanisms · 1 / 1
This was the last one in Safety mechanisms — back to the library ›

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

Go to APP