ens-contracts
EIPs
ens-contracts | EIPs | |
---|---|---|
7 | 486 | |
531 | 12,560 | |
3.4% | 0.8% | |
8.4 | 9.8 | |
5 days ago | 3 days ago | |
JavaScript | Python | |
MIT License | Creative Commons Zero v1.0 Universal |
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.
ens-contracts
- Implement offchain DNS Registrar support #203
-
ENS DAO Newsletter - The long-awaited NameWrapper is live!
More details can be found in the pull request.
- A beginner's guide to ENS Name Wrapper and It's Functionality
-
Daily General Discussion - March 6, 2023
M3mber: I think this is a way to mint an NFT that represents a membership in something with an expiry date (pitched as a way for DAOs to bring in recurring money like a subscription rather than just the one-off token sale). They use ENS domains, with NameWrapper to accomplish this; is it only because ENS domains already have expiry built in so they don't have to code it from scratch?
-
How to find length of string in Solidity, from the smart contract of ens
// SPDX-License-Identifier: MIT // Source: // https://github.com/ensdomains/ens-contracts/blob/master/contracts/ethregistrar/StringUtils.sol pragma solidity >=0.8.4; library StringUtils { /** * @dev Returns the length of a given string * * @param s The string to measure the length of * @return The length of the input string */ function strlen(string memory s) internal pure returns (uint256) { uint256 len; uint256 i = 0; uint256 bytelength = bytes(s).length; for (len = 0; i < bytelength; len++) { bytes1 b = bytes(s)[i]; if (b < 0x80) { i += 1; } else if (b < 0xE0) { i += 2; } else if (b < 0xF0) { i += 3; } else if (b < 0xF8) { i += 4; } else if (b < 0xFC) { i += 5; } else { i += 6; } } return len; } }
-
string length function explaination
I came across this helper function to find a string length present at https://github.com/ensdomains/ens-contracts/blob/master/contracts/ethregistrar/StringUtils.sol And I couldn't understand what this piece of code is doing uint bytelength = bytes(s).length; for(len = 0; i < bytelength; len++) { bytes1 b = bytes(s)[i]; if(b < 0x80) { i += 1; } else if (b < 0xE0) { i += 2; } else if (b < 0xF0) { i += 3; } else if (b < 0xF8) { i += 4; } else if (b < 0xFC) { i += 5; } else { i += 6; } } return len; Any help is appreciated. Thank you
- ERC1155 "Name Wrapper" is the .eth, and integrated extensions, new unified protocols
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
What are some alternatives?
contracts-v2 - 🐇 Hop Protocol v2 smart contracts
bips - Bitcoin Improvement Proposals
openzeppelin-contracts - OpenZeppelin Contracts is a library for secure smart contract development.
token-allowance-checker - Control ERC20 token approvals
avalanche-wallet - The Avalanche web wallet
rocketpool - Decentralised Ethereum Liquid Staking Protocol.
solidity - Solidity, the Smart Contract Programming Language
ethereum-burn-stats - Website that showcases EIP-1559 Burn
go-ethereum - Go implementation of the Ethereum protocol
l2beat - L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling solutions.
bsc - A BNB Smart Chain client based on the go-ethereum fork
RatioGang.com