Smart contract risk is the chance that code running on a blockchain does something its users did not expect, and that the result cannot be undone. The causes fall into four groups: coding bugs, flawed protocol economics, weak operations such as key management, and dependence on outside systems like price feeds. Token supply schedules, including unlocks, add a market-side risk on top of the technical ones.
This guide explains each group with sourced examples, shows what audits can and cannot establish, and then covers how token unlocks change supply. It is educational information, not financial advice.
Cryptela
Assess Crypto Risk With Better Context
Explore cryptocurrency market data, analytics, education, and industry insights to help put digital asset risks in context.
Key Takeaways
- Smart contracts execute exactly as written, and code on Ethereum cannot be changed once created, so a bug can become a permanent loss.
- OWASP’s 2025 Smart Contract Top 10 puts access control, price oracle manipulation and logic errors at the head of the list.
- Many large incidents are chains of design, operational and economic flaws rather than a single coding mistake.
- An audit lowers risk but cannot guarantee security, so check who audited, what was covered and what has changed since.
- A token unlock creates no new tokens. It changes how many can be sold, which is why size relative to circulating supply matters.
Table of Contents
What a Smart Contract Does and Why Its Risk Is Different
A smart contract is a program stored on a blockchain. According to ethereum.org, these programs follow “if this then that” logic and execute according to the rules in their code, which cannot be changed once created.
When you interact with one, you send a transaction. The Solidity documentation describes a transaction as a message that can carry data and Ether. If the target account holds code, that code runs with the data as input inside the Ethereum Virtual Machine (EVM), the runtime that executes contract code.
Two properties explain most of the risk:
- Immutability. A deployed contract is hard to patch. A mistake stays live unless the developers built an upgrade path, and that path is itself something to evaluate.
- Value held in code. Many contracts hold user funds directly. A flaw is not a bug report, it is an open door to a balance.
ethereum.org’s security guide puts the value stolen or lost to smart contract defects at easily over $1 billion. It lists the DAO hack, the Parity multi-sig theft of $30 million and the Parity frozen wallet issue, in which over $300 million in ETH was locked forever.
The Main Types of Smart Contract Vulnerabilities
OWASP’s 2025 Smart Contract Top 10 is a practical checklist of what goes wrong. It names access control vulnerabilities, price oracle manipulation, logic errors, lack of input validation, reentrancy, unchecked external calls, flash loan attacks, integer overflow and underflow, insecure randomness and denial-of-service attacks. Here is what the most common ones mean.
Access control flaws
Some functions should only be callable by an owner or a governance process. If the check is missing or wrong, anyone can call them. In the worst cases that means changing ownership, minting tokens or withdrawing funds.
Reentrancy
Reentrancy happens when a contract sends funds or calls another contract before it finishes updating its own records. The called contract calls back in and repeats the withdrawal against a balance that has not yet been reduced. The DAO exploit of 2016 is the textbook case.
Logic errors and weak input validation
The code compiles and runs, but the rules it encodes do not match what the designers intended. Missing checks on the data passed into a function are a frequent cause, because an attacker controls that data.
Oracle manipulation and flash loans
Many DeFi contracts need a price from outside the chain, supplied by an oracle (a data feed). If an attacker can distort that price for a moment, the contract may lend too much or liquidate the wrong positions. A flash loan is a loan borrowed and repaid inside a single transaction, so it gives an attacker large temporary capital without any collateral. Used together, the two can turn a small weakness into a large payout.
Integer overflow and underflow
When a calculation exceeds the range a number type can hold, it can wrap around to a wrong value. Newer compiler versions have reduced this problem, but it remains on the OWASP list for code that bypasses the built-in checks.
Real Exploits and What They Teach
Past incidents show how these categories play out. The table summarizes cases with a source that states the figures.
| Incident | Date | Loss | Root cause |
|---|---|---|---|
| The DAO | June 2016 | 3.6M ETH stolen | Reentrancy |
| Parity multi-sig | 2017 | $30M stolen, over $300M locked | Wallet library flaws |
| Euler Finance | March 2023 | $197M | Unguarded function, liquidation discount and flash loan combined |
| Prisma Finance | March 2024 | 3,479.24 ETH (about $12M) | Insufficient input validation |
Euler Finance: no classic bug, still a total failure
The Euler exploit on 13 March 2023 created a $197 million deficit in four minutes. The authors of a 2025 academic analysis of severe attacks note that nothing in its Solidity source could be attributed to common smart contract vulnerabilities. Instead, an unguarded auxiliary function, a liquidation discount and a flash loan combined into an unexpected profit engine.
The lesson is that a scanner for the usual bug list is not enough. Economic design needs review as well.
Prisma Finance: one missing check
In March 2024, Prisma Finance lost 3,479.24 ETH, roughly $12 million. The LlamaRisk post-mortem traces it to insufficient input validation in the onFlashloan function of the MigrateTroveZap contract. It is a small gap with a large consequence.
The wider pattern
The same academic study examined 50 severe attacks between 2022 and 2025, with over $1.09 billion in losses. It groups root causes into four tiers: protocol logic design, lifecycle and governance, external dependencies, and classic smart contract vulnerabilities. It also describes “exploit chains,” in which human, operational and economic design flaws link with implementation bugs. For a reader, this means risk lives in more than the Solidity file.
A Practical Way to Assess Smart Contract Risk Before You Use a Protocol
Nobody can prove a contract safe. You can, however, ask structured questions that map to the four root-cause tiers above. Use them as a starting point, not a guarantee.
1. Design: does the economics make sense?
Read how the protocol makes money, what it lends against, and which prices it trusts. If a single price feed or a single pool decides who gets liquidated, oracle and flash loan risk is higher.
2. Code and audits: what was reviewed, and when?
Look for published audit reports and confirm that the audited code is the code deployed. Check whether the scope included every contract that holds funds. An audit of an older version says little about a version with new features.
3. Governance and upgrades: who can change the rules?
Some contracts can be upgraded by an admin key or a multisig wallet (an account that needs several signatures to act). That can fix bugs, but it also concentrates power. Find out who holds the keys, how many signatures are needed and whether there is a time delay before changes take effect.
4. Dependencies: what else does it rely on?
Bridges, oracles and other protocols are all part of the attack surface. A contract can be well written and still be harmed by something it depends on.
5. Your own exposure
Wallet approvals deserve attention. Granting a contract unlimited spending permission means a later flaw can reach your balance. Keep position sizes small relative to your total holdings, and only use funds you can afford to lose.
For context on how new projects present security work, see Cryptela’s coverage of an AI-based smart contract audit firm and of a custody partnership aimed at institutional DeFi security. Both are project announcements, so read them as a project’s own account.
What Audits and Testing Can and Cannot Establish
Audits matter, and it helps to know exactly what they provide. The BSSC Smart Contract Security Standard requires that an audit be conducted by at least two people who did not take part in developing the code. It also states that an audit cannot guarantee security, but one that correctly follows a recognized methodology can ensure certain known vulnerabilities are not present.
The standard also advises combining testing written by the developers with testing from independent parties. Developers know the code well, but they also hold undocumented assumptions that their own tests do not reflect.
On the testing side, ethereum.org says unit testing alone is minimally effective for improving security. It recommends combining it with property-based testing, static analysis and dynamic analysis such as fuzzing. Its testing guide adds that low code coverage can create false confidence, because tests can all pass while untested code paths still hide vulnerabilities. It names audits and bug bounties as two ways to get others to analyze a contract.
What this means for a reader:
- An audit badge is a data point, not a verdict.
- Multiple independent reviews and a running bug bounty give broader coverage than one report.
- Time in production without incident adds some evidence, but not proof.
Token Unlocks: A Supply Risk Beside the Technical Ones
Smart contract risk is not only about hacks. Many tokens release their supply on a schedule written into a vesting contract, and each release changes what holders face in the market.
What a token unlock is
A token unlock is the moment tokens that were locked, often those allocated to teams, investors or the treasury, become transferable. Bitbase explains that an unlock creates no tokens and total supply stays fixed. What changes is the float, the fraction of supply that can actually be sold. It also notes that many launches in the 2023 to 2025 cycle listed with a circulating float of just 5% to 15% of total supply, which is why later unlocks can be large relative to what trades.
A common structure is a cliff followed by gradual release. One vesting guide describes a typical setup of a 12-month cliff with a 36-month total vest, where one third of the allocation unlocks at the first anniversary. Schedules differ by project, so always read the specific one.

How unlocks can affect price
More sellable supply does not automatically mean a price drop, because demand matters too. Analyses of past events nonetheless point to size as the key variable. In a review of over 5,000 unlock events, 6th Man Ventures reported no meaningful relationship to price for small unlocks, those adding up to 1% to circulating supply. Larger unlocks showed a noticeable negative relationship, with prices lower as unlock size rose. The same review found tokens with more than 70% of supply vested had lower volatility than those early in vesting.

Bitbase adds that the schedule is public months or years ahead, so the date is rarely news. It cites a large-sample study by Keyrock in which most unlocks were followed by negative price pressure, with weakness often starting about 30 days before the date. These are market studies from commercial research teams, so treat them as indications of past behavior, not forecasts.
A simple unlock checklist
- Find the schedule. Look for the vesting contract or the project’s published tokenomics.
- Measure the size. Divide the amount unlocking by current circulating supply. Under 1% is a small event by the measure above, and larger percentages deserve more attention.
- Identify the recipients. Team and early investor tokens may be sold differently from ecosystem or community allocations.
- Check the float and valuation. A low float with a high fully diluted valuation means more of the supply is still to come.
- Look at market conditions. Liquidity, trading volume and overall sentiment change how much new supply the market can absorb.
- Consider timing. If weakness tends to arrive before the date, watching only the unlock day can miss the move.
You can follow circulating supply, volume and price history for individual assets on Cryptela, which tracks more than 30,000 cryptocurrencies. Always note the date and time of any figure you rely on, since all of these numbers change.
Reducing Your Exposure as a User
No step removes smart contract risk. These habits reduce it:
- Prefer contracts with a track record, several independent reviews and clear documentation.
- Limit token approvals to the amount you need, and review them periodically.
- Split funds across wallets and protocols rather than concentrating them in one contract.
- Understand upgrade rights. An admin key is a trust assumption.
- Beware of too-good yields. High returns often compensate for higher contract, oracle or liquidity risk.
- Never promise yourself an outcome. Digital assets can lose value, and lost funds on a blockchain are usually unrecoverable.
For Projects: Publishing Your Security Work
Projects that have completed audits, launched bug bounties or published vesting schedules can reach Cryptela’s readers by submitting an article, which costs 99 USD one-off. Cryptela also offers sponsored articles, press releases and other promotional formats on its advertising page. Submitted and sponsored content is promotional material and is kept distinct from Cryptela’s independent editorial coverage.
FAQ
What are the biggest smart contract risks?
OWASP’s 2025 list names access control vulnerabilities, price oracle manipulation and logic errors at the top. Reentrancy, unchecked external calls, flash loan attacks and denial of service follow. Research on recent attacks also shows that design, governance and operational weaknesses contribute alongside code bugs.
Can a smart contract be changed after deployment?
By default, no. Ethereum.org states that a contract’s code cannot be changed once created. Some projects add upgrade mechanisms controlled by an admin key or multisig, which can fix problems but add a trust assumption you should understand.
Does an audit make a smart contract safe?
No. The BSSC standard says an audit cannot guarantee security, though a correctly followed methodology can ensure certain known vulnerabilities are absent. Independent reviews, testing and a bug bounty together give a fuller picture.
How does a token unlock affect price?
An unlock adds no new tokens but increases how many can be sold. One review of over 5,000 events found small unlocks, up to 1% of circulating supply, showed no meaningful link to price, while larger ones correlated with lower prices. Past patterns do not predict future results.
Can I recover funds lost to a smart contract exploit?
Usually not. Blockchain transactions are irreversible, and recovery depends on the specific case. The Parity wallet incident, with over $300 million in ETH locked forever, shows that some losses are permanent.









