openzeppelin-contracts-upgradeable
gambit
openzeppelin-contracts-upgradeable | gambit | |
---|---|---|
10 | 1 | |
940 | 153 | |
1.3% | 2.0% | |
9.4 | 7.4 | |
9 days ago | 11 days ago | |
JavaScript | Rust | |
MIT License | 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.
openzeppelin-contracts-upgradeable
-
Solidity digest / mar 2023
v4.8.2 of OpenZeppelin contracts and contracts-upgradeable bug fix for ERC721Consecutive that could cause a balance overflow when _mintConsecutive was used for batches of size 1 breaking changes to ERC721: the internal function _beforeTokenTransfer will no longer update balances when batchSize is greater than 1
- Issue logging out certain state variables in Hardhat
-
Can a function that implements __Ownable_init by not with the initializable modifier be run more than once?
Yeah. That restriction is coming from a utility. There are options to modify the owner through transfer ownership on the `OwnableUpgradable` contract. You can also use the `reinitializer' modifier to create your own re-init logic.
- Contract inheritance is a reason Open Zeppelin plans to adopt Diamond Storage
-
Nuances of Using Upgradeable Smart Contracts
Most smart contracts developers have used Openzeppelin/contracts. Those developers dabbling in Upgradeable smart contracts use its sister project Openzeppelin/contracts-upgradeable. The two are the same albeit the constructor in the contract is replaced by the initializer.
-
Contract example with best practices?
Here’s a few references: - https://openzeppelin.com/contracts/ - https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable (highly recommended)
- Token
-
It costs $436 to deploy a smartcontract on Ethereum
https://github.com/OpenZeppelin/openzeppelin-contracts-upgra...
For KYC you'll need to implement your own ERC20 compatible token with some checks in the transfer functions. The CMTA is the Swiss contract reference and proposes one:
- https://np.reddit.com/r/solidity/comments/prlgj8/how_do_we_create_an_upgradeable_smart_contract/hdjnhnd/
- How do we create an upgradeable smart contract with a hardhat?
gambit
-
Solidity digest / mar 2023
Certora/gambit - A Solidity Mutation Testing Tool. See also article Gambit: A Solidity Mutation Testing Tool for Formal Verification
What are some alternatives?
openzeppelin-contracts - OpenZeppelin Contracts is a library for secure smart contract development.
smart-contract-best-practices - A guide to smart contract security best practices
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.
cardano-node - The core component that is used to participate in a Cardano decentralised blockchain.
l2beat - L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling solutions.
fe - Emerging smart contract language for the Ethereum blockchain.
openzeppelin-contracts-upgra
CMTA20 - Smart contract to tokenize a Swiss corporation's shares on Ethereum
plutus - The Plutus language implementation and tools