Andrew B Coathup
Andrew B Coathup
I agree that the format should be consistent with other OpenZeppelin contracts. Should we wait until https://github.com/OpenZeppelin/ethernaut/issues/117 is done and then update or do it as part of that? I...
Agree on updating the contracts once #123 is done. My preference is consistency with OpenZeppelin contracts linting.
Thanks, I have the same experience with Alien Codex level.
Related to open issue: https://github.com/ethereum/web3.js/issues/1648
Hi @Asamartino, I'm sorry that I haven't gotten back to you on this yet. I like the idea. I am thinking of the best way to upgrade to Solidity 0.6...
I now have a number of levels showing as completed: 10. Re-entrancy ✔ 11. Elevator ✔ 12. Privacy ✔ 13. Gatekeeper One 14. Gatekeeper Two ✔ 15. Naught Coin ✔...
@thelastjosh can you update the PR title to include the EIP #
> 3\. Allow using only "ERC-20" and not "EIP-20". My preference would be to use an ERC prefix for the category to quickly distinguish between core and ERC categories, the...
>Instead of sending the Chinese letters of the Great Wall 长城, two EIP-3754 tokens with ID#38271 and ID#22478 are sent in order to represent the two letters. The receiving end...
A Logographic use case could be implemented using ERC1155, so I don't see the need for a new EIP. The metadata extension is optional in ERC1155. https://eips.ethereum.org/EIPS/eip-1155#metadata-extensions