EIPs
openzeppelin-contracts
EIPs | openzeppelin-contracts | |
---|---|---|
486 | 235 | |
12,594 | 24,242 | |
1.1% | 1.4% | |
9.8 | 9.5 | |
2 days ago | 3 days ago | |
Python | JavaScript | |
Creative Commons Zero v1.0 Universal | 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.
EIPs
-
Ethereum Foundation removes their canary
Even more relevant would be the Ethereum Improvement Proposal repo (where people submit proposals to change the spec):
https://github.com/ethereum/EIPs
Or the go-ethereum execution client (the most popular execution client):
https://github.com/ethereum/go-ethereum
-
Bridging the Gap: Better Token Standards for Cross-chain Assets
It’s early in the life of the xERC20 standard, but progress is quickly being made. The standard has been audited and is already live with a few projects. The EIP to adopt the standard has been created, and implementation has begun. Alchemix recently announced support for the xERC20 standard. And Defi Wonderland has published a suggested implementation on their GitHub. This implementation has an interface for the xERC20 contract with eight core functions that the token issuer must implement. These are functions related to setting the Lockbox contract (setLockbox), issuance limits for bridges (setLimits, mintingMaxLimitOf, burningMaxLimitOf, etc.), and the core mint and burn functions.
-
Numbers Protocol submitted EIP-7517, Allowing Consent for AI Data Mining on the Blockchain
Check out EIP-7517: Giving Consent for AI Data Mining on the Blockchain
-
Exploring ERC20 Tokens: The Powerhouse Behind Ethereum's Tokenized World4
ERC223 is not widely implemented, and there is some debate in the ERC discussion thread about backward compatibility and trade-offs between implementing changes at the contract interface level versus the user interface.
- EIPs/.github/workflows/post-ci.yml at master · ethereum/EIPs
- EIPs/.github/workflows/ci.yml at master · ethereum/EIPs
-
Process of recalculating the transactionRoot from a block transaction hash
Ethereum Improvement Proposals (EIPs): These are proposals to change various aspects of Ethereum. They often contain detailed technical discussion and can be a good resource for understanding the finer points of how Ethereum works. EIPs can be found here: https://eips.ethereum.org/
-
Burning ETH is great for the price, but may be a risk to decentralization (A critique of the ETH burn model and a recommendation for new economics)
Worth looking at: EIP6968: Contract Secured Revenue on an EVM based L2 https://github.com/ethereum/EIPs/pull/6969/files
-
Calling All Devs and Crypto Enthusiasts: A Community-Driven Anti-Scam Registry on the Blockchain
Additionally, I have made an EIP that can help standardise and maintain official contract registry of each DApp. This can help identify official contracts of a protocol vs scammers using fraud contracts but presenting like official protocol. https://github.com/ethereum/EIPs/pull/6807
openzeppelin-contracts
-
Mode - Comprehensive Starter Guide
// SPDX-License-Identifier: GPL-3.0 pragma solidity ^0.8.20; import "https://github.com/OpenZeppelin/openzeppelin-contracts/blob/v5.0.0/contracts/token/ERC20/ERC20.sol"; interface Sfs { function register(address _recipient) external returns (uint256 tokenId); } contract ModeToken is ERC20 { address feeReceiver = msg.sender; constructor() ERC20("ModeTokenSFSTest", "SFST2") { //Example amount to mint our ERC20 _mint(msg.sender, 1000 10 * 18); // This is the SFS contract address on testnet Sfs sfsContract = Sfs(0xBBd707815a7F7eb6897C7686274AFabd7B579Ff6); //Registers this contract and assigns the NFT //to the deployer of this contract sfsContract.register(msg.sender); } }
-
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.
What are some alternatives?
bips - Bitcoin Improvement Proposals
solmate - Modern, opinionated, and gas optimized building blocks for smart contract development.
token-allowance-checker - Control ERC20 token approvals
hardhat - Hardhat is a development environment to compile, deploy, test, and debug your Ethereum software.
avalanche-wallet - The Avalanche web wallet
ERC721A - https://ERC721A.org
rocketpool - Decentralised Ethereum Liquid Staking Protocol.
Safemoon.sol - safemoon contract
solidity - Solidity, the Smart Contract Programming Language
ethereum-burn-stats - Website that showcases EIP-1559 Burn
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.