solidity-flattener
openzeppelin-contracts
solidity-flattener | openzeppelin-contracts | |
---|---|---|
1 | 234 | |
311 | 24,143 | |
0.0% | 1.0% | |
3.5 | 9.5 | |
about 1 year ago | 2 days ago | |
JavaScript | JavaScript | |
Apache License 2.0 | 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.
solidity-flattener
-
Devlog 2: Gotta jot this down, bc I'll definitely forget
But NoooOOOoooOOOoo. you need an ABI since pool's are auto deployed via the factory (hence the name, duh! I knew that, was just telling you guys). Fuck me. Ok, so how do I get an ABI for an auto deployed contract? Uhg, gotta fire up remix. I tried just pulling it down from github but there are too many relative dependancies/imports to deal with. I'm not about that copy paste life, so found this neat little flattener. It's the first thing I've run today that did it's fucking job the first time! Just download the Uniswap source, install the node app and run
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?
openzeppelin-solidity - OpenZeppelin Contracts is a library for secure smart contract development. [Moved to: https://github.com/OpenZeppelin/openzeppelin-contracts]
solmate - Modern, opinionated, and gas optimized building blocks for smart contract development.
remix - This has been moved to https://github.com/ethereum/remix-project
hardhat - Hardhat is a development environment to compile, deploy, test, and debug your Ethereum software.
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!
ERC721A - https://ERC721A.org
eattheblocks - Source code for Eat The Blocks, a screencast for Ethereum Dapp Developers
Safemoon.sol - safemoon contract
solidity - Solidity, the Smart Contract Programming Language
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.
poap-contracts - The Proof of Attendance Protocol Ethereum contracts