reentrancy-attacks VS Smart-Contract-Audits

Compare reentrancy-attacks vs Smart-Contract-Audits and see what are their differences.

reentrancy-attacks

A chronological and (hopefully) complete list of reentrancy attacks to date. (by pcaversaccio)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
reentrancy-attacks Smart-Contract-Audits
1 427
1,184 560
- -
7.7 9.1
28 days ago 6 days ago
GNU Affero General Public License v3.0 -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

reentrancy-attacks

Posts with mentions or reviews of reentrancy-attacks. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-02.
  • A look into formal verification of smart contracts using Certora
    5 projects | dev.to | 2 Dec 2022
    The main challenge is dealing with non-view functions. The default behavior of the prover is to assume that an external call can alter all state on every contract but the caller, noted as HAVOC_ECF. This can lead to state changes in external contracts that are unreachable, making verification more difficult. Furthermore, it assumes that the call is non-reentrant, which in reality is a frequent source of attacks. This last issue can be avoided by indicating that calls can re-enter, noted as HAVOC_ALL, but this means that an external call can mutate any state in any contract, caller included. This leaves the contract being verified in a state where we don't know anything about it after an external call is made. This severely limits what we can prove.

Smart-Contract-Audits

Posts with mentions or reviews of Smart-Contract-Audits. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-10-29.

What are some alternatives?

When comparing reentrancy-attacks and Smart-Contract-Audits you can also consider the following projects:

full-blockchain-solidity-course-py - Ultimate Solidity, Blockchain, and Smart Contract - Beginner to Expert Full Course | Python Edition

golang-tls - Simple Golang HTTPS/TLS Examples

White-Paper

umbra-protocol - πŸŒ•πŸŒ‘ Privacy Preserving Shielded Payments On The Ethereum Blockchain

awesome-security-GRC - Curated list of resources for security Governance, Risk Management, Compliance and Audit professionals and enthusiasts (if they exist).

Smart-Contract-Security-Audits - Certified Smart Contract Audits for Ethereum, Solana, Near, Cardano, Aptos, Sui, Binance Smart Chain, Fantom, EOS, Tezos by Chainsulting

solidity-advanced - Smart Contracts using Advanced Solidity methods.

awesome-solidity - A curated list of awesome Solidity resources

LiquidityPoolExample - Example Certora verification for a simple multi-contract system

assets - A comprehensive, up-to-date collection of information about several thousands (!) of crypto tokens.

publications

the-dao-hack-simulation - A simulation of the infamous DAO hack from 2016