Have been getting errors like this one when I try to export metadataError: Source "@openzeppelin/contracts/security/Pausable.sol" not found: File not found. Searched the following locations: "/home/marko/Work/swarm/swarm-si/.". --> src/PostageStamp.sol:5:1: | 5 | import "@openzeppelin/contracts/security/Pausable.sol"; to solve this you need to include a path to node modules like below and then you will get proper output. Bare in mind to use a proper solidity version of the contractssolc --bas...

Have been getting errors like this one when I try to export metadataError: Source "@openzeppelin/contracts/security/Pausable.sol" not found: File not found. Searched the following locations: "/home/marko/Work/swarm/swarm-si/.". --> src/PostageStamp.sol:5:1: | 5 | import "@openzeppelin/contracts/security/Pausable.sol"; to solve this you need to include a path to node modules like below and then you will get proper output. Bare in mind to use a proper solidity version of the contractssolc --bas...

When I want to rewrite requires to custom errors in bigger blocks of solidity code I solve it with chatGPT. I use prompt below to make the solution work out of the box and just c/p code.Prompt, just c/p it and add solidity code below it Rewrite this code in a way that reverts are transformed to custom solidity errors use this pattern of replacement require(success, "Transfer failed"); replace with error TransferFailed(); //Transfer failed if(!success){ revert TransferFailed();} Group all erro...

When I want to rewrite requires to custom errors in bigger blocks of solidity code I solve it with chatGPT. I use prompt below to make the solution work out of the box and just c/p code.Prompt, just c/p it and add solidity code below it Rewrite this code in a way that reverts are transformed to custom solidity errors use this pattern of replacement require(success, "Transfer failed"); replace with error TransferFailed(); //Transfer failed if(!success){ revert TransferFailed();} Group all erro...

To fork a network in hardhat you need to change config that adds this line to your networks networks: { hardhat: { forking: { enabled: true, url: 'https://rpc.gnosischain.com', blockNumber: 29279000, }, .... With that, when you run hardhat node or hardhat test you will have your local node running at snapshot of whatever chain url rpc you put into config. This will give you different output when running tests it('return data for forked network, async function () { console.log(await getBlockNu...

To fork a network in hardhat you need to change config that adds this line to your networks networks: { hardhat: { forking: { enabled: true, url: 'https://rpc.gnosischain.com', blockNumber: 29279000, }, .... With that, when you run hardhat node or hardhat test you will have your local node running at snapshot of whatever chain url rpc you put into config. This will give you different output when running tests it('return data for forked network, async function () { console.log(await getBlockNu...

To actually get constructor parameters you will need to get transaction details and see what was “data” that was sent or if you are using etherscan you can go to”Input Data” field and see all the bytecode there. So I will take this transaction as example https://goerli.etherscan.io/tx/0xf15cfeb9be64058ba3680a7095ca045bb7cdddc85e318921a297de36f77e48b0 and use its bytecode to dissect constructor parameters. We need to go the end of the code and find this part of codethis 0033 is the last opcode...

To actually get constructor parameters you will need to get transaction details and see what was “data” that was sent or if you are using etherscan you can go to”Input Data” field and see all the bytecode there. So I will take this transaction as example https://goerli.etherscan.io/tx/0xf15cfeb9be64058ba3680a7095ca045bb7cdddc85e318921a297de36f77e48b0 and use its bytecode to dissect constructor parameters. We need to go the end of the code and find this part of codethis 0033 is the last opcode...

So you decided to use gnosis safe and its multisig for your smart contracts. Great decision if you moved from EOA and one private key to more secure setup. With that there are some caveats and experiences you need to prepare for. Strongly recommend that you first do some actions and signings of transactions on testnet, better yet, try to do exact same actions on testnet you plan to do on mainnet. Reason is that you might come into unexpected problems that are better experienced on testnet fir...

So you decided to use gnosis safe and its multisig for your smart contracts. Great decision if you moved from EOA and one private key to more secure setup. With that there are some caveats and experiences you need to prepare for. Strongly recommend that you first do some actions and signings of transactions on testnet, better yet, try to do exact same actions on testnet you plan to do on mainnet. Reason is that you might come into unexpected problems that are better experienced on testnet fir...

Exporting function signatures and especially error signatures which are still not properly showcased on etherscan and others is useful thing to have so you can match your errors or your function calls. To do that I made a custom hardhat task that will do that if you pass it name of the contract. Put this into tasks folderimport { task } from 'hardhat/config'; task('sigs', 'Generate ABI signatures for errors and functions') .addParam('c', 'Name of the contract for which to generate ABI data') ...

Exporting function signatures and especially error signatures which are still not properly showcased on etherscan and others is useful thing to have so you can match your errors or your function calls. To do that I made a custom hardhat task that will do that if you pass it name of the contract. Put this into tasks folderimport { task } from 'hardhat/config'; task('sigs', 'Generate ABI signatures for errors and functions') .addParam('c', 'Name of the contract for which to generate ABI data') ...

Main difference between deployed bytecode or runtime bytecode and bytecode that is shown in deployed transaction is that later has initial code in it and its bigger in size. So what is initial(init) code?A smart contract's constructor is a one-time function not stored on the blockchain but present in the initial code. When creating a contract, users can also send native currency. It's vital to ensure the contract can accept this currency at deployment. If it can't, the creation...

Main difference between deployed bytecode or runtime bytecode and bytecode that is shown in deployed transaction is that later has initial code in it and its bigger in size. So what is initial(init) code?A smart contract's constructor is a one-time function not stored on the blockchain but present in the initial code. When creating a contract, users can also send native currency. It's vital to ensure the contract can accept this currency at deployment. If it can't, the creation...

How to encode function with parameters and execute it within solidity executeCall Lets start with this example for safeTransferFrom function and its parameters. Go to remix and add this code, then compile it// SPDX-License-Identifier: BSD-3-Clause pragma solidity ^0.8.17; contract Encode { address from = 0x55C21585007bC89202Bc7eed9B315c8eaB4190A8; address to = 0xB1620c0547744DeDD30F40a863c09D1964532F8C; uint id = 1; function encodeWithSignature( ) external returns (bytes memory) { return abi....

How to encode function with parameters and execute it within solidity executeCall Lets start with this example for safeTransferFrom function and its parameters. Go to remix and add this code, then compile it// SPDX-License-Identifier: BSD-3-Clause pragma solidity ^0.8.17; contract Encode { address from = 0x55C21585007bC89202Bc7eed9B315c8eaB4190A8; address to = 0xB1620c0547744DeDD30F40a863c09D1964532F8C; uint id = 1; function encodeWithSignature( ) external returns (bytes memory) { return abi....

pragma solidity ^0.8.0; interface IUniswapV2Pair { function getReserves() external view returns (uint112 reserve0, uint112 reserve1, uint32 blockTimestampLast); } contract LiquidityChecker { function getLiquidity(address pairAddress) external view returns (uint112 reserve0, uint112 reserve1) { (reserve0, reserve1, ) = IUniswapV2Pair(pairAddress).getReserves(); } } Use this code in your contract and fetch liquidity of any V2 Pair, just input address of pair you got with methods from previous p...

pragma solidity ^0.8.0; interface IUniswapV2Pair { function getReserves() external view returns (uint112 reserve0, uint112 reserve1, uint32 blockTimestampLast); } contract LiquidityChecker { function getLiquidity(address pairAddress) external view returns (uint112 reserve0, uint112 reserve1) { (reserve0, reserve1, ) = IUniswapV2Pair(pairAddress).getReserves(); } } Use this code in your contract and fetch liquidity of any V2 Pair, just input address of pair you got with methods from previous p...

EIP 4096 has an interesting method of updating your metadata with events, more details here. https://eips.ethereum.org/EIPS/eip-4906 So lets see how to implement it with an example. First you need to create a file with interface that has this code in itpragma solidity ^0.8.0; import "@openzeppelin/contracts/utils/introspection/IERC165.sol"; /// @title EIP-721 Metadata Update Extension interface IERC4906 is IERC165 { /// @dev This event emits when the metadata of a token is changed. /// Third-...

EIP 4096 has an interesting method of updating your metadata with events, more details here. https://eips.ethereum.org/EIPS/eip-4906 So lets see how to implement it with an example. First you need to create a file with interface that has this code in itpragma solidity ^0.8.0; import "@openzeppelin/contracts/utils/introspection/IERC165.sol"; /// @title EIP-721 Metadata Update Extension interface IERC4906 is IERC165 { /// @dev This event emits when the metadata of a token is changed. /// Third-...

You can run this in REMIX IDE to get deterministic value of contract used for uniswap v2 pairpragma solidity ^0.8.17; contract UniswapV2Helper { function findPair() external returns (address){ address factory = 0x5C69bEe701ef814a2B6a3EDD4B1652CB9cc5aA6f; address token0 = 0x2aC3c1d3e24b45c6C310534Bc2Dd84B5ed576335; // change me! address token1 = 0xB4FBF271143F4FBf7B91A5ded31805e42b2208d6; // change me! address pair = address(uint160(uint256(keccak256(abi.encodePacked( hex'ff', factory, keccak2...

You can run this in REMIX IDE to get deterministic value of contract used for uniswap v2 pairpragma solidity ^0.8.17; contract UniswapV2Helper { function findPair() external returns (address){ address factory = 0x5C69bEe701ef814a2B6a3EDD4B1652CB9cc5aA6f; address token0 = 0x2aC3c1d3e24b45c6C310534Bc2Dd84B5ed576335; // change me! address token1 = 0xB4FBF271143F4FBf7B91A5ded31805e42b2208d6; // change me! address pair = address(uint160(uint256(keccak256(abi.encodePacked( hex'ff', factory, keccak2...

Choose your environment on the left side, for localhost use custom and enter endpoint that you have running locally, probably it will be the one on the image which is http://127.0.0.1:8545 and that is also default hardhat local node. Once we have that set, you should import solidity code of the contract you want to use, the reason for this is that you need ABI and to use the ABI of contract you want, this is one of the methods you can use to get it. The other way is just to copy and paste ABI...

Choose your environment on the left side, for localhost use custom and enter endpoint that you have running locally, probably it will be the one on the image which is http://127.0.0.1:8545 and that is also default hardhat local node. Once we have that set, you should import solidity code of the contract you want to use, the reason for this is that you need ABI and to use the ABI of contract you want, this is one of the methods you can use to get it. The other way is just to copy and paste ABI...