Connect
Cover: What a conservation guard cannot see: five findings that passed a correct, enforced, tested invariant

What a conservation guard cannot see: five findings that passed a correct, enforced, tested invariant

What can a conservation guard not see?

A measurement: a conservation check applied at thirteen entry points with no exemption for administrators was silent for six of the seven vulnerabilities disclosed against the contract it protected — and five of those are 2-safety properties no single-trace invariant can express.

Known formally as The silence of an invariant in the BlazePhoenix whitepaper.

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

At a glance
LevelAdvanced
Formal nameThe silence of an invariant
Reading time12 min
Sections8
Sources cited5
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 — A measurement, not an argument: a conservation guard that was correctly written, enforced at thirteen entry points including both administrative funding paths, exempt for nobody and covered by tests was nonetheless silent for six of the seven vulnerabilities later disclosed against the staking contract it protected — five of them 2-safety properties no single-trace invariant can express. The procedural content is the contrapositive: the surviving attack always lives inside the guard's silence, so that is where an audit should search.

Português — Uma medição, não um argumento: uma guarda de conservação corretamente escrita, imposta em treze pontos de entrada incluindo ambos os caminhos administrativos de financiamento, sem isenção para ninguém e coberta por testes, ficou mesmo assim em silêncio para seis das sete vulnerabilidades depois divulgadas contra o contrato de staking que protegia — cinco delas propriedades 2-safety que nenhuma invariante de traço único consegue exprimir. O conteúdo procedimental é o contrapositivo: o ataque sobrevivente vive sempre dentro do silêncio da guarda, e é aí que uma auditoria deve procurar.

Español — Una medición, no un argumento: una guarda de conservación correctamente escrita, impuesta en trece puntos de entrada incluidos ambos caminos administrativos de financiación, sin exención para nadie y cubierta por tests, quedó aun así en silencio para seis de las siete vulnerabilidades luego divulgadas contra el contrato de staking que protegía — cinco de ellas propiedades 2-safety que ninguna invariante de traza única puede expresar. El contenido procedimental es el contrapositivo: el ataque superviviente vive siempre dentro del silencio de la guarda, y ahí es donde una auditoría debe buscar.

Français — Une mesure, pas un argument : une garde de conservation correctement écrite, appliquée à treize points d'entrée y compris les deux chemins de financement administratifs, sans exemption pour personne et couverte par des tests, est pourtant restée silencieuse pour six des sept vulnérabilités divulguées ensuite contre le contrat de staking qu'elle protégeait — cinq d'entre elles étant des propriétés 2-safety qu'aucun invariant à trace unique ne peut exprimer. Le contenu procédural est la contraposée : l'attaque survivante vit toujours dans le silence de la garde, et c'est là qu'un audit doit chercher.

Deutsch — Eine Messung, kein Argument: Ein korrekt geschriebener Erhaltungs-Guard, an dreizehn Eintrittspunkten erzwungen — beide administrativen Finanzierungspfade eingeschlossen —, für niemanden ausgenommen und testabgedeckt, blieb dennoch für sechs der sieben später gegen den geschützten Staking-Contract offengelegten Schwachstellen stumm — fünf davon 2-Safety-Eigenschaften, die keine Single-Trace-Invariante ausdrücken kann. Der prozedurale Gehalt ist die Kontraposition: Der überlebende Angriff wohnt immer in der Stille des Guards, also sollte ein Audit dort suchen.

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

Türkçe — Bir ölçüm, bir sav değil: doğru yazılmış, iki idari fonlama yolu dahil on üç giriş noktasında dayatılan, kimseye muafiyet tanımayan ve testlerle örtülen bir korunum bekçisi, koruduğu staking sözleşmesine karşı sonradan açıklanan yedi zafiyetin altısında yine de sessiz kaldı — beşi, hiçbir tek-iz invaryantının ifade edemeyeceği 2-güvenlik özellikleri. Prosedürel içerik, ters-önerme: hayatta kalan saldırı her zaman bekçinin sessizliğinin içinde yaşar; denetimin araması gereken yer orasıdır.

العربية — قياسٌ لا حجّة: حارس حفظٍ كُتب صحيحاً، وفُرض عند ثلاث عشرة نقطة دخول بما فيها مسارا التمويل الإداريان، بلا إعفاء لأحد ومغطى بالاختبارات، ظل مع ذلك صامتاً عن ست من الثغرات السبع التي كُشفت لاحقاً ضد عقد الرهن الذي يحميه — خمس منها خصائص أمان-2 لا يستطيع أي ثابت أحادي الأثر التعبير عنها. المضمون الإجرائي هو عكس النقيض: الهجوم الناجي يسكن دوماً داخل صمت الحارس، وهناك ينبغي أن يبحث التدقيق.

हिन्दी — माप, तर्क नहीं: सही लिखी गई संरक्षण-गार्ड, तेरह प्रवेश-बिंदुओं पर लागू — दोनों प्रशासनिक वित्तपोषण-पथ सहित — किसी को छूट नहीं और परीक्षणों से ढकी, फिर भी उस स्टेकिंग कॉन्ट्रैक्ट के विरुद्ध बाद में उजागर सात कमज़ोरियों में से छह पर चुप रही — जिनमें पाँच 2-safety गुण हैं जिन्हें कोई एकल-ट्रेस अपरिवर्तनीय व्यक्त नहीं कर सकता। प्रक्रियागत सार प्रतिधनात्मक है: बचा हुआ हमला हमेशा गार्ड की चुप्पी के भीतर रहता है, इसलिए ऑडिट को वहीं खोजना चाहिए।

日本語 — これは論証ではなく測定です。正しく書かれ、管理者の資金経路二つを含む十三の入口すべてで強制され、誰にも免除がなく、テストにも覆われていた保存則ガードが、それでも、守っていたステーキングコントラクトに対して後に開示された七つの脆弱性のうち六つについて沈黙していました。うち五つは、単一トレースの不変量では表現できない2-safety性質です。手続き上の含意は対偶です。生き残る攻撃は必ずガードの沈黙の中に住んでいる。監査が探すべき場所はそこです。

中文 — 这是一次测量,不是一场论辩:一个写得正确、在十三个入口(含两条管理注资路径)强制执行、对任何人无豁免、且有测试覆盖的守恒卫兵,仍然对后来针对其守护的质押合约披露的七个漏洞中的六个保持沉默——其中五个是任何单轨迹不变量都无法表达的 2-safety 性质。其程序性内涵是逆否命题:幸存的攻击必然住在卫兵的沉默之内,审计应当去那里搜索。

한국어 — 논증이 아니라 측정입니다. 올바르게 작성되고, 두 관리자 자금 경로를 포함한 열세 개 진입점에서 강제되며, 누구도 면제되지 않고, 테스트로 덮인 보존 가드가, 그럼에도 자신이 지키던 스테이킹 컨트랙트에 대해 나중에 공개된 일곱 취약점 중 여섯에 침묵했습니다 — 그중 다섯은 어떤 단일 트레이스 불변식도 표현할 수 없는 2-안전성 속성입니다. 절차적 내용은 대우명제입니다. 살아남는 공격은 언제나 가드의 침묵 속에 살고 있으므로, 감사는 바로 거기를 뒤져야 합니다.

Bahasa Indonesia — Sebuah pengukuran, bukan argumen: penjaga konservasi yang ditulis dengan benar, diberlakukan di tiga belas titik masuk termasuk kedua jalur pendanaan administratif, tanpa pengecualian bagi siapa pun dan tercakup pengujian, tetap saja bisu untuk enam dari tujuh kerentanan yang kemudian diungkap terhadap kontrak staking yang dilindunginya — lima di antaranya properti 2-safety yang tak bisa diungkapkan invarian jejak-tunggal mana pun. Isi proseduralnya adalah kontrapositif: serangan yang selamat selalu hidup di dalam kebisuan penjaga, maka di situlah audit seharusnya mencari.

বাংলা — একটি পরিমাপ, যুক্তি নয়: সঠিকভাবে লেখা, দুটি প্রশাসনিক তহবিল-পথসহ তেরোটি প্রবেশবিন্দুতে বলবৎ, কারও জন্য ছাড় নেই ও পরীক্ষায় আচ্ছাদিত একটি সংরক্ষণ-প্রহরী তবু নীরব ছিল সেই স্টেকিং কন্ট্রাক্টের বিরুদ্ধে পরে প্রকাশিত সাতটি দুর্বলতার ছয়টিতে — যার পাঁচটি 2-safety বৈশিষ্ট্য, যা কোনো একক-ট্রেস ইনভ্যারিয়েন্ট প্রকাশ করতে পারে না। প্রক্রিয়াগত সারমর্ম প্রতিলোম: টিকে থাকা আক্রমণ সবসময় প্রহরীর নীরবতার ভেতরে বাস করে, তাই নিরীক্ষার খোঁজা উচিত সেখানেই।

Filipino — Isang sukat, hindi argumento: ang conservation guard na wastong nakasulat, ipinatupad sa labintatlong entry point kabilang ang dalawang administratibong daan ng pondo, walang exempted at saklaw ng mga pagsusulit, ay nanatiling tahimik pa rin sa anim sa pitong kahinaang isiniwalat kalaunan laban sa staking na kontratang binabantayan nito — lima sa mga ito ay 2-safety na katangiang hindi maipapahayag ng anumang single-trace na invariant. Ang praktikal na nilalaman ay ang contrapositive: ang nakaligtas na atake ay laging nakatira sa loob ng katahimikan ng guard, kaya doon dapat maghanap ang audit.

The useful artefact in this article is not a theory. It is a ratio. A conservation guard that was correctly written, enforced at thirteen entry points including both administrative funding paths, exempt for nobody, and covered by a dedicated test, was nonetheless silent for six of the seven vulnerabilities subsequently disclosed against the staking contract it protected. The seventh moved the residual quantity the guard does observe, and surfaced against a different check.

That partition is publicly verifiable — the findings have identifiers, external reporters and commits — and it is a concrete instance of a claim usually argued in the abstract: that single-trace verification, done properly and taken seriously, can still leave the majority of a real system's defects structurally out of reach. Nothing below is offered as evidence that invariant-driven design fails. It is one honest measurement of what one good invariant could not see.

The guard, and why it is a good one

The check compares, across every value-moving transaction, the change in what the contract actually holds against the change in what it claims to owe, and reverts if those two deltas diverge by more than a dust tolerance. Both sides are recomputed from state rather than read from calldata, so there is no attested quantity anywhere in it. It is applied structurally at every entry point that can move value, administrators included. Violation reverts.

It is also deliberately differential rather than absolute, and that choice is better engineering than the stronger-looking alternative. An absolute form — holdings must always cover obligations — would have turned a few wei of rounding drift into a permanent denial of service for every user. The differential form fails only the transaction that actually leaks. An invariant costs the liveness it forecloses, and the stronger predicate here would have been a denial of service dressed as rigour.

Dimension and silence

An invariant is usually discussed as a predicate. That framing hides half of it. An invariant is two objects: a map from system state onto some observable value, and a relation that must hold over that value. Conventional practice argues about the relation. The map is where the design decision actually sits. In the formal-methods literature the map is an abstraction function, the states it cannot separate are its concretisation, and what it discards is precision loss; none of that vocabulary is ours, and using the established names is what makes the measurement checkable rather than folkloric.

Call the set of state changes the observable cannot distinguish its silence. The one statement that does the work is a contrapositive and therefore trivial — and trivial in the way a change of variables is trivial. If the guard is enforced everywhere it could be violated, then any harmful transition that the guard did not fire on lies inside the silence. Its content is procedural: the surviving attack is never outside the silence, so search there. An audit that re-examines the guard is looking in the one place the attack provably is not.

invariant  =  I : S -> V        (the observable — the dimension)
           +  R subset of V x V (the relation — the predicate)

Sil(I,R)   =  { transitions the code admits that R accepts }

H(s, t(s)) AND the guard never fired   =>   t is in Sil(I,R)

Where this guard's silence comes from

The guard reads only one combination of its two components, so its effective dimension is a single scalar: the residual between holdings and obligations, bounded per transaction. The state it ranges over contains one record per position — principal, debt, boost multiplier, lock end, index snapshots — plus the emission clock. The guard compresses that entire space onto a line, and there are five independent families of change that move along the line by zero.

The first is the fibre of a sum. Obligations are computed from totals, so for any aggregate distributed over positions, every reallocation of that aggregate is invisible. With a thousand positions the guard observes one direction and is blind along nine hundred and ninety-nine. The second is temporal attribution: when value was earned, who was present while it accrued, and which interval is being priced appear nowhere in the observable. The third is the fibre of a delta — common-mode change and all accumulated historical drift, deliberately, since the absolute form would brick the contract. The fourth is the dust tolerance, which is per transaction and therefore composes: N transactions carry N times the tolerance even though each is individually inside it. The fifth is created by the arithmetic rather than by the statement: a saturating subtraction inside the obligations computation collapses an entire inverted region onto zero.

Silence is created by arithmetic, not only by omission, and that is the part engineers routinely miss. A sum is blind to how it was split. A difference is blind to common-mode change. A tolerance is blind below the tolerance, and blind to N of itself over N transactions. A saturating subtraction collapses a whole region of state onto one value, and the region it collapses is usually the pathological one. Adding a second guard narrows nothing unless its own silence is different — coverage is set intersection, not a count.

The five findings, and why they are the same finding

Five of the seven disclosed staking findings are one error wearing different clothes, and recognising that is more useful than any individual description. Each computes a quantity that accrues continuously — interest, emission weight, a stake's share — by sampling it at the moment someone happens to interact, and then applying that sample to the whole elapsed interval. In the language of integration, they evaluate a path integral by taking the value at the right endpoint and multiplying by the width of the interval.

When nothing changed during the interval, that is exact, which is why it survives review. When the rate moved, it silently attributes the final rate to the entire period, and the difference is taken from one participant and given to another. With a rate that rises linearly from 0.4 to 1.0 across an interval, the true accrual is 0.70 and the amount charged is 1.00 — an over-attribution of more than forty per cent, produced by arithmetic that looks correct on every single line.

Each non-constant factor sampled at the right endpoint generates one member of the family. Sampling the rate at the endpoint produces retroactive repricing of an elapsed interval. Sampling the total weight at the endpoint produces just-in-time capture, where a participant absent for the whole window takes a share of it by being present at the instant of realisation. A stale stored multiplier produces an unearned boost applied to newly added principal. All of them are redistributions: the residual the guard observes does not move, by construction, so the guard is delta-neutral on both sides and never fires.

V_i(t0 -> t1)  =  INTEGRAL_{t0}^{t1}  rate(s) * w_i(s)/W(s)  ds        (owed)

lazy form      ~=  rate(t1) * (t1 - t0) * w_i(t1)/W(t1)                  (charged)

exact only if every factor is constant across the interval.
rate(t1) sampled  -> retroactive repricing
W(t1)    sampled  -> just-in-time capture
stale w_i         -> unearned multiplier

The sharpest available statement: these are 2-safety properties

The reason no better predicate over the same observable would have caught them is not that the guard was weak. It is that the properties violated are not single-execution properties at all. "The interest charged to a position does not depend on which transaction drove the sweep" is a relation between two executions. So is "two positions identical in principal, debt and unlock time receive an identical multiplier". So is time-additivity. In the Clarkson and Schneider classification these are 2-safety properties, and a 2-safety property is not expressible as a predicate over any single execution, at any level of effort.

So the guard did not fail. It could not have succeeded. That is a structural impossibility result available off the shelf, and it upgrades the observation from a war story into a categorical statement — at the cost of a citation and of not claiming it as ours. The theory is not ours: abstraction and its precision loss, the hyperproperty classification, vacuous satisfaction, metamorphic relations, coverage by mutation. All of it is established work with established names. The measurement is the contribution.

The control case, and the boundary of the claim

The sixth finding inside the silence and the seventh outside it form the honest edges. One member of a second, smaller family advances a clock without writing its dual: an emission window closes with nobody eligible and the value is stranded, owed to no one — the purest instance of the sum fibre, since the aggregate is merely recategorised. The other member of that family is the control case: an underwater exit that removes a debt without recording the bad debt it leaves behind. That one is not a redistribution. It changes the relation between what is held and what is claimed, and it surfaced on the absolute solvency axis, which is a different dimension enforced by a different check. The partition falls exactly where the method says it must.

One boundary must be stated rather than glossed. That the control case lies outside the redistribution class is recorded in the findings register. Whether the differential guard would additionally have fired in the offending frame has not been verified against a re-execution, so the claim we publish is the one that is checked: the control case is visible on the absolute axis, and the other six are not visible on either.

And the epistemic point, which is the reason any of this matters. For the entire period those defects were live, the guard was green — not weakly green, but structurally enforced, tested and honest. A correct invariant over the wrong observable produces false confidence, and false confidence is worse than no invariant, because it stops the search.

What replaces it, and what that costs

The answer is not a stronger conservation law, because by the classification above there cannot be one. The observable that would have seen these is per-principal attribution, and enforcing it takes two mechanisms, neither of which is a second modifier. At test time, metamorphic relations supply the oracle: driver-invariance (the cost charged to a position may not depend on which transaction drove the sweep), time-additivity (accrual over a whole interval equals the sum over any partition of it), history-independence of price, and continuity of any throttle that would otherwise be a cliff. Each is a relation between two executions and needs no hard-coded expected value.

On-chain, the discharge is structural: advance the accumulator before any write that changes its inputs, which forces the integrand constant across each settled interval and makes the right-endpoint rectangle coincide with the path integral. That costs nothing per position and is satisfied by construction rather than by a runtime check — and that is exactly why its epistemic status is lower than the guard's. It will not revert if a future edit breaks it. The honest closing sentence is not "we closed the dimension"; it is "we named the dimension, discharged it structurally, and pinned it with two-execution tests".

The practice we would ask a reader to take away is smaller and cheaper than any of it: write the guard as an expression over named state, then write the list of things that can change while that expression does not, and publish the second list beside the guarantee. That deliverable has a fixed shape — this guarantees X; it permits Y and Z — and almost nobody writes the second clause.

Do not trust this page — reproduce it

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

the partition is checkable without us: read the disclosure record and the regression tests in the staking repository, and for each finding ask whether the transformation changes the difference between what the contract holds and what it claims to owe. Six answers are "no".
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). What a conservation guard cannot see: five findings that passed a correct, enforced, tested invariant. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/what-a-conservation-guard-cannot-see/
@misc{blazephoenix_what_a_conservation_guard_cannot_see,
  title  = {What a conservation guard cannot see: five findings that passed a correct, enforced, tested invariant},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/what-a-conservation-guard-cannot-see/},
  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). Sources cited: Clarkson, Schneider — Hyperproperties (2-safety) · Cousot, Cousot — Abstract interpretation (1977) · Jacob; Roscoe — the refinement paradox · Chen, Cheung, Yiu — Metamorphic testing (1998) · Beer, Ben-David, Eisner, Rodeh — Vacuous satisfaction (1997)

Related engineering

Next in Limits of verification · 4 / 4
This was the last one in Limits of verification — back to the library ›

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

Go to APP