Knowledge Base · Payments & x402
Enforcing a policy in code: removing an asset balance from a live page
The symptom
An older project page displayed a treasury address plus a live balance fetched from a block explorer. Nobody had looked at that page in weeks; it contradicted the published policy the rest of the company follows.
What was actually wrong
The widget had been added when the project still planned to display its holdings. When the policy changed, the page was simply forgotten, because the rule lived in documentation rather than in any check.
The fix
The entire section was removed from the source together with the explorer request, committed with a message naming the policy, deployed, and verified in the live page — both that the section is gone and that no balance request is made any more.
What we took away
Policies that matter belong in code review and in checks, not in prose — the page that violates them is always one you have stopped looking at. When you find a violation, delete the request too: a section hidden by CSS still calls the network.