
Non-circular definition is a design principle stating that key variables within a system must not reference each other in a self-reinforcing loop. In other words, you should not define variable A using B and simultaneously define B using A, as this creates a logical cycle.
In Web3, this concept often applies to scenarios involving price, collateral ratio, and liquidation rules. For example, if a protocol generates its own price and then uses that price to determine liquidation and issuance, it essentially “self-prices.” When market volatility strikes, such self-referential logic can accelerate risk propagation.
You can think of it like building with blocks: each block should stand independently. If the upper and lower layers depend on each other for support, the entire structure becomes unstable.
Non-circular definition is crucial because circular structures amplify “self-reinforcement.” A decline in one variable can impact another through the feedback loop, which then further suppresses the original variable, triggering a chain reaction.
Historically, the algorithmic stablecoin crisis of May 2022 exposed this vulnerability: stablecoin price anchors depended on the market cap and mint-burn relationship of a related token, creating mutual influence and feedback loops. When the market came under pressure, the mechanism entered a “death spiral.”
In lending protocols, if the price of collateral assets is determined by internal metrics held by borrowers, sharp market swings can trigger mass liquidations and concentrated risk events.
The core principle is to design system dependencies as an acyclic graph. Simply put: list all key inputs by source and ensure these sources do not form cycles.
Implementation includes:
This approach makes protocols easier to audit—auditors can trace unidirectional dependency paths without worrying about ending up back at the starting point.
Stablecoins aim to maintain price stability and are usually pegged to fiat currencies or a basket of assets. Applying non-circular definition means ensuring “value backing” does not depend on the stablecoin itself.
Typical practices include:
On the trading layer—such as Gate’s stablecoin pairs—prices are determined by actual order matching and market depth, not by “internal pricing” from issuer contracts. This allows users to see transparent market-driven pricing.
In lending protocols, users pledge assets as collateral to borrow other assets, with the collateral ratio defined as “collateral value ÷ loan value.”
Key implementation points:
For example, when using ETH as collateral to borrow a stablecoin, ETH’s price should come from independent markets and multi-source oracles. Liquidation rules should follow predefined parameters rather than being dynamically rewritten by the stablecoin’s contract during operation.
Oracles bring off-chain data onto the blockchain, functioning like “reliable thermometers” for real-time external readings. Non-circular definition requires oracle sources to be independent from the system being measured.
In practice, using multi-source data and time-weighted average prices helps minimize manipulation risks. Additional safeguards like anomaly detection and circuit breakers can pause critical operations if prices deviate sharply.
For users, checking whether a project uses decentralized, multi-source oracles provides more trust than relying on self-reported data. In trading scenarios, reference actual market transactions and depth rather than just project-provided indicators.
A quick check involves creating a “dependency diagram”: identify a project’s key inputs (such as price, collateral ratio, liquidation parameters, issuance rules) and see if they reference each other.
Steps:
Non-circular definition helps mitigate self-reinforcing risks and reduces “run-on-the-bank” scenarios caused by feedback loops. It improves predictability for liquidation and issuance events and supports easier auditing and regulatory compliance.
Limitations include reliance on external data networks—potentially affecting availability and latency—and sometimes lower capital efficiency due to higher collateral ratios or more conservative parameters.
For regular users, this means a tradeoff: more stability but potentially less aggressive returns. When using Gate for investment or lending, focus on price sources, liquidation rules, anomaly handling, manage positions prudently, and be aware of fund risks.
Steps:
Common mistakes include:
Non-circular definition requires structuring key system inputs as independent and acyclic sources. It is especially critical in stablecoin, lending, and oracle contexts—reducing self-reinforcement and chain reaction risks. Best practices include using multi-source external data, layered risk management, circuit breakers, dependency diagram reviews, and stress testing. For users, focusing on the independence of price and rule sources helps clarify risk boundaries; in volatile markets, robust designs ensure more predictable protocol behavior.
Non-circular definition emphasizes asset value independence and traceability, whereas traditional finance often accepts credit-based collateralization. In Web3, non-circular definition requires collateral assets not rely on unverified value promises of other assets—ensuring a clear and credible value chain. This makes DeFi lending more transparent but limits eligible collateral types.
Projects are exposed to value cycle risks—where multiple assets mutually depend on each other. If any link fails, it triggers cascading failures. Historically, several projects collapsed due to circular dependencies (such as synthetic asset protocols failing during sharp market downturns). Strict non-circular definition significantly reduces systemic risk and user losses.
Check three aspects:
It has an indirect but important effect. Projects adhering to non-circular definition have lower overall risk—reducing the chance your assets are locked in unstable protocols. While risks cannot be entirely eliminated, choosing platforms that strictly implement non-circular definition (like Gate’s reviewed listings) substantially increases fund safety.
New projects can build trust by establishing transparent non-circular value foundations—such as real asset collateralization, publicly auditable reserves, independent third-party verification—demonstrating resilience under stress tests. These projects often attract more risk-averse users and perform more steadily in long-term markets.


