reentrancy-attacks VS full-blockchain-solidity-course-py

Compare reentrancy-attacks vs full-blockchain-solidity-course-py and see what are their differences.

reentrancy-attacks

A chronological and (hopefully) complete list of reentrancy attacks to date. (by pcaversaccio)

full-blockchain-solidity-course-py

Ultimate Solidity, Blockchain, and Smart Contract - Beginner to Expert Full Course | Python Edition (by smartcontractkit)
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 full-blockchain-solidity-course-py
1 11
1,197 10,531
- 0.9%
7.7 2.8
about 2 months ago 10 days ago
GNU Affero General Public License v3.0 MIT License
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.

full-blockchain-solidity-course-py

Posts with mentions or reviews of full-blockchain-solidity-course-py. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-05-04.

What are some alternatives?

When comparing reentrancy-attacks and full-blockchain-solidity-course-py you can also consider the following projects:

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

eattheblocks - Source code for Eat The Blocks, a screencast for Ethereum Dapp Developers

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

awesome-zksync - ↔️ A curated list of awesome zkSync resources

Smart-Contract-Audits - Smart Contract security audit reports

DeFi-Developer-Road-Map - DeFi Developer roadmap is a curated Developer handbook which includes a list of the best tools for DApps development, resources and references!

solidity-cheatsheet - Cheat sheet and best practices for solidity. Write smart contracts for Ethereum.

awesome-solidity - ⟠ A curated list of awesome Solidity resources, libraries, tools and more

smart-contract-audits - ContractWolf audited smart contracts

openzeppelin-contracts - OpenZeppelin Contracts is a library for secure smart contract development.

remix-ide - Documentation for Remix IDE

opensea-js - TypeScript SDK for the OpenSea marketplace