Web3 Database Security Considerations That We Should Be Aware Of

Table of Contents
Oracle Smart contracts have revolutionized various industries by enabling decentralized and trustless transactions.However, integrating Oracle into smart contracts comes with its own set of challenges and security vulnerabilities that developers and auditors must be aware of. In this article, we will explore common security vulnerabilities associated with Chainlink oracles and discuss best practices to mitigate these risks.

I. Common Security Vulnerabilities

Oracle projects are crucial components in the world of blockchain and decentralized applications, providing valuable data for smart contracts. However, they introduce a range of security vulnerabilities that must be addressed to ensure the integrity and security of decentralized applications.

A. Stale Pricing Data

1. Failure to Check for Stale Prices
Stale pricing data occurs when smart contracts do not adequately verify the timeliness of the data received from Oracle projects. This can lead to significant financial losses as contracts make decisions based on outdated information. It is crucial for developers to implement mechanisms that check the freshness of pricing data.
Failure to address this vulnerability can result in scenarios where contract executions occur using prices that no longer accurately represent the asset's real value. For example, if a decentralized finance (DeFi) protocol relies on outdated pricing data for collateral, it could lead to liquidations at incorrect prices, causing users to lose assets unfairly.
2. Correcting Stale Price Data
To rectify the issue of stale pricing data, developers should incorporate timestamp checks into their smart contracts. By comparing the timestamp of the data received from the Oracle with the current block's timestamp, contracts can determine whether the data is still fresh. If the data is stale, appropriate actions, such as reverting the transaction or triggering a data update, should be taken.
3. Examples of Stale Pricing Issues
Real-world examples of smart contracts that failed to address stale pricing data will illustrate the potential risks and consequences of neglecting this crucial security consideration. These examples will serve as cautionary tales for developers and auditors.

B. L2 Sequencer Checks

1. The Importance of Checking L2 Sequencer
Layer 2 solutions like Arbitrum have their own sequencing mechanisms, and overlooking checks for the L2 sequencer's status can lead to unreliable pricing data. Developers need to understand the critical role of the L2 sequencer in ensuring data accuracy and integrity.
Neglecting L2 sequencer checks can result in decentralized applications on Layer 2 chains making decisions based on pricing data that appears up-to-date but is actually unreliable due to sequencer inactivity.
2. Implementing L2 Sequencer Checks
This section will outline strategies for implementing effective L2 sequencer checks in smart contracts. Developers must take proactive measures to verify the availability and proper functioning of the L2 sequencer before relying on pricing data.
3. Examples of Missing L2 Sequencer Checks
Case studies of projects that failed to include L2 sequencer checks in their smart contracts will highlight the consequences of overlooking this security consideration. Such examples will emphasize the importance of diligent implementation.

C. Heartbeat Mismatch

1. Understanding Heartbeat Intervals
Different Oracle price feeds may have varying heartbeat intervals, representing how frequently they update their data. Failing to account for these differences can lead to inconsistencies in pricing checks and calculations.
Understanding the heartbeat intervals is essential for ensuring that smart contracts check for updates at appropriate intervals. For instance, a contract using two different price feeds with distinct heartbeats must adapt its checking mechanisms accordingly.
2. Adjusting Heartbeats for Different Feeds
Developers and auditors should explore methods for adjusting heartbeat checks based on the specific feeds they use. We will discuss how to harmonize checks for multiple feeds with varying heartbeat intervals to maintain consistency and accuracy in pricing data.
3. Examples of Heartbeat Mismatch
Real-life scenarios where contracts struggled with heartbeat mismatches will provide insights into the potential risks and issues that can arise when developers do not account for these variations. These examples underscore the importance of addressing heartbeat disparities.
In each subsection, provide detailed explanations of the vulnerability, its potential consequences, and actionable steps for addressing or mitigating the risk. Additionally, include real-world examples where applicable to illustrate the significance of these security considerations and underscore the importance of implementing best practices.

II. Best Practices and Mitigations

In the previous section, we explored various security vulnerabilities associated with Oracle projects. Now, let's delve into best practices and mitigation strategies that smart contract developers and auditors can employ to safeguard their decentralized applications.

A. Selecting Reliable Oracle Price Feeds

1. Importance of Frequent Updates
One fundamental consideration is the selection of reliable oracle price feeds. Smart contract creators should prioritize using oracle price feeds that are updated frequently. Timely updates ensure that the reported prices closely reflect the real-time value of assets, reducing the risk of incorrect calculations.
2. Considering Heartbeat and Deviation Thresholds
It's essential to consider the heartbeat and deviation thresholds of oracle price feeds. Different price feeds may have varying heartbeat intervals and deviation thresholds. A shorter heartbeat and lower deviation threshold lead to more accurate pricing data. Developers and auditors should ensure that price feeds with these characteristics are chosen to maintain accuracy.
3. Ensuring Accuracy of Reported Prices
To ensure the accuracy of reported prices, developers and auditors can perform regular checks on the selected oracle price feeds. By cross-referencing the reported prices with other reputable sources, such as centralized exchanges or liquid indexes, discrepancies can be detected and addressed promptly.

B. Setting Request Confirmations

1. Determining Suitable REQUEST_CONFIRMATIONS
The REQUEST_CONFIRMATIONS parameter plays a crucial role when requesting randomness from Oracle projects. Developers should carefully evaluate the depth of common chain re-organizations on the target chain(s) where their smart contracts will be deployed. The value of REQUEST_CONFIRMATIONS should exceed the depth of potential re-organizations to prevent the re-ordering of blocks and transactions that could affect the randomness results.
2. Adapting to Different Blockchains
For projects that span multiple blockchains, developers should be flexible in adapting the REQUEST_CONFIRMATIONS parameter to the characteristics of each blockchain. Different chains may experience varying degrees of re-organizations, necessitating adjustments to ensure the security and fairness of random outcomes.

C. Handling Price Precision

1. Accounting for Decimal Precision
Oracle price feeds may report prices with different decimal precisions. It is a critical error to assume uniform precision across all price feeds. Developers should account for these variations by dynamically adjusting calculations based on the specific precision of each price feed.
2. Using AggregatorV3Interface.decimals()
To determine the exact number of decimals for a particular price feed, developers can utilize the AggregatorV3Interface.decimals() function. This method provides a reliable way to ensure that calculations involving different assets maintain precision and accuracy.

D. Correctly Configuring Oracle Price Feed Addresses

1. Avoiding Incorrect Hard-Coding
One common pitfall is hard-coding oracle price feed addresses into smart contracts. To mitigate this risk, developers should refrain from hard-coding addresses and instead implement dynamic mechanisms for setting or updating these addresses during contract deployment.
2. Verifying Price Feed Addresses
Auditors play a critical role in verifying that the selected price feed addresses match the intended feeds. Referring to official lists of oracle price feeds and confirming the addresses for projects on various chains is essential to prevent vulnerabilities stemming from incorrect addresses.

E. Preventing Front-Running of Oracle Updates

1. Addressing Slow Updates
Some stablecoin protocols are susceptible to front-running attacks due to slow oracle updates. Developers can consider implementing a small fee for minting and burning operations, making frequent arbitrage less profitable for attackers.
2. Implementing Delay Mechanisms
To thwart front-running attempts, developers can introduce delay mechanisms that prevent users from immediately withdrawing
 funds after making deposits. This delay provides a buffer against rapid price movements and potential attacks.

F. Handling Oracle Reverts

1. Implementing Error Handling
Smart contracts should wrap calls to oracles in try/catch blocks to handle potential reverts gracefully. Error-handling mechanisms can prevent complete Denial-of-Service situations in smart contracts that depend on oracle data.
2. Providing Update Mechanisms
In the event of an oracle malfunction or cessation of operation, smart contracts should offer mechanisms to replace or update oracle feeds. This flexibility ensures the contract remains functional and users can access their assets even if the original oracle feed becomes unavailable.


Incorporating Oracle projects into smart contracts enhances their capabilities but also introduces potential security vulnerabilities. By adhering to best practices and employing effective mitigation strategies, developers and auditors can fortify the security of decentralized applications. It is essential to strike a balance between leveraging powerful data feeds and safeguarding smart contracts against potential risks. As the blockchain ecosystem evolves, staying vigilant and implementing robust security measures remains paramount to ensure the reliability and integrity of decentralized systems.

About Orochi Network

Orochi Network is a cutting-edge zkOS (An operating system based on zero-knowledge proof) designed to tackle the challenges of computation limitation, data correctness, and data availability in the Web3 industry. With the well-rounded solutions for Web3 Applications, Orochi Network omits the current performance-related barriers and makes ways for more comprehensive dApps hence, becoming the backbone of Web3's infrastructure landscape.
Event Recap
Monthly Report
Verifiable Random Function
Zero-Knowledge Proofs
Top Posts
Partnership Announcement
Layer 2
Event Recap
Immutable Ledger
Verifiable Random Function
Zero-Knowledge Proofs
Multisignature Wallet

Orosign Wallet

Manage all digital assets safely and securely from your mobile devices

zkDatabaseDownload Orosign Wallet
Coming soon

zkOS for Web3

© 2021 Orochi