$2.4M in drain attempts stopped.
Read how 0x prevented drains without changing their contracts.
On integrated networks, protocols define the states they must never reach. The network rejects transactions that would create or spread those risks before they settle.
"For institutional capital to flow into DeFi at scale, we need to move beyond reactive security models. Institutions don't operate in environments where they detect problems after they occur, they require infrastructure that makes certain failure modes impossible. This integration gives institutions the deterministic, auditable controls they need to meet compliance requirements, while also protecting everyday DeFi users who want assurance that protocols won't be exploited."
Read how 0x prevented drains without changing their contracts.
The Credible Layer
The Credible Layer builds circuit breakers into the transaction path without adding a pause committee, trusted signer, or settlement delay.
Set the outcomes your protocol must avoid.
Build checks in the workflow your engineers use.
Invalid transactions are rejected before settlement.
Every policy decision leaves a verifiable record.
For networks & appchains
Integrate the Credible Layer so apps can enforce their own policies as blocks are built.
Policies are evaluated where transactions are accepted or rejected, not after the fact.
The Credible Layer inherits the network’s trust model without adding a pause committee, trusted signer, or settlement delay.
Apps define their own rules; the network enforces them neutrally, no matter who sends the transaction.
Downstream protocols can act on risk signals from the protocols they depend on, containing failures at the boundary.
For apps & protocols
Stop bad debt and unbacked assets with invariant checks, circuit breakers, and anomaly detection on every transaction.
Protect admin keys, owner changes, approvals, modules, and emergency operations after a transaction has been signed.
Enforce outflow limits, share-price checks, NAV bounds, strategy constraints, and collateral safety policies before capital moves.
Prevent borrow, withdrawal, liquidation, oracle, and parameter changes that break account or market-level risk rules.
Reject unsafe swaps, pool manipulation, route settlement failures, and abnormal liquidity movement before LPs inherit bad state.
Block tainted flow exposure, restricted counterparties, unsafe venues, and risk-increasing actions when threat signals are active.
For capital & custody
Public records show which protections are active. Detailed traces stay private. Coverage is something you can verify, not just a claim.
See active policies, curator actions, and outflows to downstream markets.
Make enforcement coverage an eligibility requirement for deposits and distribution, not a nice-to-have.
Use live constraints, changes, and rule-level evidence to decide whether exposure should grow.
Carry enforcement records into diligence, risk, insurance, and IC workflows.
More yield is not worth losing everything. Every protocol also inherits the risk of the systems it relies on. Existing defenses act too late.
A review of the code you shipped last quarter cannot cover every path the protocol may encounter today.
An alert mid-exploit is a post-mortem with better timestamps. Detection is not prevention.
Attacks can finish inside a single block. A human-operated pause key may never get pressed in time.
Blockchains have fast settlement which creates fast losses; prevention is paramount here.
“Audits are necessary, tests are necessary, but there seems to be something missing. We would prefer something preventive, not something that responds after the problem.”
“Current monitoring systems detect malicious patterns only after an action has been taken. Catching a malicious transaction before it is mined would be the holy grail of monitoring.”
Read product updates, case studies, market analysis, and first-hand essays about preventative security.
Inspect the public repositories behind runtime enforcement, assertion tooling, and the wider Phylax stack.
Follow implementation guides for assertions, local workflows, testing, and Credible Layer primitives.
Declare the states your protocol must never reach. Phylax rejects the transactions that would cross them and publishes the evidence auditors, allocators, and insurers can verify.