bytecode-verifier
openzeppelin-contracts
Our great sponsors
bytecode-verifier | openzeppelin-contracts | |
---|---|---|
1 | 233 | |
86 | 24,079 | |
- | 1.6% | |
0.0 | 9.5 | |
almost 1 year ago | 5 days ago | |
JavaScript | JavaScript | |
- | MIT License |
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.
bytecode-verifier
-
How can you check the deployed smart contract matches the solidity code the authors say they've published?
Consensys has a project https://github.com/ConsenSys/bytecode-verifier that allows verifying a contract bytecode if one has the sources available.
openzeppelin-contracts
-
Blockchain transactions decoding: making wallet activity understandable
Lets look the events of Open Zeppelin’s ERC20 token contract:
- Construir e implementar un VAULT (bóveda) ERC20 en Shardeum
-
Are ERC-777 Unsafe?
ERC-777 is difficult to implement properly, due to its susceptibility to different forms of attack(opens in a new tab). It is recommended to use ERC-20 instead. This page remains as a historical archive.
- OpenZeppelin is trying to avoid paying a bounty for a vulnerability that caused $1,1B worth of assets freeze
- Security improvements of the ERC20 token standard
- Ethereums most used token standard ERC20 requires security enhancements
- The most used Ethereums token standard (ERC20) requires a security patch.
-
Best Solidity Vertion
This depends if you're writing a contract from scratch or using existing code. If you're making something new, then yes (recommend not to use THE most recent available, always better to go with tried and tested). For existing projects, never try to override the solidity version. This may be a pain with "@" imports - ideally everyone should specify the library version (e.g. https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v2.5.1/contracts/token/ERC20/ERC20.sol).
What are some alternatives?
remix-ide - Documentation for Remix IDE
solmate - Modern, opinionated, and gas optimized building blocks for smart contract development.
openzeppelin-solidity - OpenZeppelin Contracts is a library for secure smart contract development. [Moved to: https://github.com/OpenZeppelin/openzeppelin-contracts]
hardhat - Hardhat is a development environment to compile, deploy, test, and debug your Ethereum software.
hashed-timelock-contract-ethereum - Hashed Timelock Contracts for ETH, ERC20 and ERC721 on Ethereum
ERC721A - https://ERC721A.org
truffle - :warning: The Truffle Suite is being sunset. For information on ongoing support, migration options and FAQs, visit the Consensys blog. Thank you for all the support over the years.
Safemoon.sol - safemoon contract
Smart-Contract-Security-Audits - Certified Smart Contract Audits for Ethereum, Solana, Near, Cardano, Aptos, Sui, Binance Smart Chain, Fantom, EOS, Tezos by Chainsulting
solidity - Solidity, the Smart Contract Programming Language
remix - This has been moved to https://github.com/ethereum/remix-project