Currently to setup hardhat quickly and with most plugins you will need just install HH toolbox​​​​​​​npm install --save-dev @nomicfoundation/hardhat-toolbox https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-tool… and with that you can remove obsoletes in you HH config . ​​​​​​​After that, I would recommend you also add hardhat deploy and hardhat deploy ethers https://github.com/wighawag/hardhat-deploy#installation (this part is a bit tricky how it works so read instructions c...

Currently to setup hardhat quickly and with most plugins you will need just install HH toolbox​​​​​​​npm install --save-dev @nomicfoundation/hardhat-toolbox https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-tool… and with that you can remove obsoletes in you HH config . ​​​​​​​After that, I would recommend you also add hardhat deploy and hardhat deploy ethers https://github.com/wighawag/hardhat-deploy#installation (this part is a bit tricky how it works so read instructions c...

Calldata stored on chain is a bit diffeent that state stored on chain "It has to do with the way it is stored on disk. Also it has to do with the guarantees made around its future availability. Calldata is stored in an append only DB (essentially), which can (in theory) be put on a large but slow disk like a spinning disk, tape drive, etc. The guarantees that calldata will be available to all clients indefinitely are also much weaker than the guarantees that state will be available indefinite...

Calldata stored on chain is a bit diffeent that state stored on chain "It has to do with the way it is stored on disk. Also it has to do with the guarantees made around its future availability. Calldata is stored in an append only DB (essentially), which can (in theory) be put on a large but slow disk like a spinning disk, tape drive, etc. The guarantees that calldata will be available to all clients indefinitely are also much weaker than the guarantees that state will be available indefinite...

While testing some web3.eth methods on my contract I made a small script that checks for gas and doesnt run the state chaning calls until there is low enough gas, also sets this gas to the recommended level, could be also lower if wanted Not a complete code as but should be enough to implement in your script\ async function sleep(millis) { return new Promise(resolve => setTimeout(resolve, millis)); } ..... gasPriceWei = '10010000000'; //10 gwei gasPriceLimit = '10010000000'; gasHigh = true; t...

While testing some web3.eth methods on my contract I made a small script that checks for gas and doesnt run the state chaning calls until there is low enough gas, also sets this gas to the recommended level, could be also lower if wanted Not a complete code as but should be enough to implement in your script\ async function sleep(millis) { return new Promise(resolve => setTimeout(resolve, millis)); } ..... gasPriceWei = '10010000000'; //10 gwei gasPriceLimit = '10010000000'; gasHigh = true; t...

One of things you might need to do is listen to events on the chain for particular smart contract(probably yours) and do some action in front end. Assuming you are using react/nextjs this snnippet of code will help you do something you need. In example below we are using moralis library and local hardhat provider through sockets. We then make connection to contract we want to track and add ether js provider .on method that listens to certain event (this case WinnerPicked) and fires some actio...

One of things you might need to do is listen to events on the chain for particular smart contract(probably yours) and do some action in front end. Assuming you are using react/nextjs this snnippet of code will help you do something you need. In example below we are using moralis library and local hardhat provider through sockets. We then make connection to contract we want to track and add ether js provider .on method that listens to certain event (this case WinnerPicked) and fires some actio...

This is taken straight from ethereum by example but it's very important to repeat it so delegatecall is a low-level function similar to call.When contract A executes delegatecall to contract B, B's code is executed with contract A's storage, msg.sender and msg.valueso you also need to have storage layout must be the same as contract A. Check the example below. Also a name doesn’t matter, contract A storage names could have been called whatever, they will still be populated as i...

This is taken straight from ethereum by example but it's very important to repeat it so delegatecall is a low-level function similar to call.When contract A executes delegatecall to contract B, B's code is executed with contract A's storage, msg.sender and msg.valueso you also need to have storage layout must be the same as contract A. Check the example below. Also a name doesn’t matter, contract A storage names could have been called whatever, they will still be populated as i...

Calling some other contract function can be achieved with .call notation on contract address and passing in calldata info which is in bytes format.contract CallFunction { address public s_other_contract_address; constructor(address addy) { s_other_contract_address = addy; } // you could use this to change state function callFunctionDirectly(bytes calldata callData) public returns (bytes4, bool) { (bool success, bytes memory returnData) = s_other_contract_address.call(callData); return (bytes4...

Calling some other contract function can be achieved with .call notation on contract address and passing in calldata info which is in bytes format.contract CallFunction { address public s_other_contract_address; constructor(address addy) { s_other_contract_address = addy; } // you could use this to change state function callFunctionDirectly(bytes calldata callData) public returns (bytes4, bool) { (bool success, bytes memory returnData) = s_other_contract_address.call(callData); return (bytes4...

Can we do that, actually you can if you use this keyword, you will be able to call the function inside the same contract that is external. contract TryExternal { string name = "Nero"; function accessExternal() public view returns (string memory) { return this.result(name); } function result(string calldata _a) external pure returns (string calldata) { return _a; } }

Can we do that, actually you can if you use this keyword, you will be able to call the function inside the same contract that is external. contract TryExternal { string name = "Nero"; function accessExternal() public view returns (string memory) { return this.result(name); } function result(string calldata _a) external pure returns (string calldata) { return _a; } }

To make airdrop you need to have a list of addresses that are eligible for that as well as put them into Merkle tree get hashes of them, store them into a smart contract, and then check if they are on the list. For the node JS part we can use this code to install libraries quicklyconst { MerkleTree } = require("merkletreejs"); const keccak256 = require("keccak256"); let whitelistAddress = [ "0x6271217bE872a0F65Bcd8C90d3D0A80B305B8906", "0xB1620c0542744DeDD30F30a863c09D1964532F8C", "0x139Fb399...

To make airdrop you need to have a list of addresses that are eligible for that as well as put them into Merkle tree get hashes of them, store them into a smart contract, and then check if they are on the list. For the node JS part we can use this code to install libraries quicklyconst { MerkleTree } = require("merkletreejs"); const keccak256 = require("keccak256"); let whitelistAddress = [ "0x6271217bE872a0F65Bcd8C90d3D0A80B305B8906", "0xB1620c0542744DeDD30F30a863c09D1964532F8C", "0x139Fb399...

To use chainlink random number generator you need to import 2 contracts localyimport "@chainlink/contracts/src/v0.8/interfaces/VRFCoordinatorV2Interface.sol"; import "@chainlink/contracts/src/v0.8/VRFConsumerBaseV2.sol"; and then you need to have function to request random word(number) function requestRandomFunction() external { uint256 requestId = i_vrfCoordinator.requestRandomWords( i_gasLane, i_subscriptionId, REQUEST_CONFIRMATIONS, i_callBackGasLimit, NUM_WORDS ); } which when called will...

To use chainlink random number generator you need to import 2 contracts localyimport "@chainlink/contracts/src/v0.8/interfaces/VRFCoordinatorV2Interface.sol"; import "@chainlink/contracts/src/v0.8/VRFConsumerBaseV2.sol"; and then you need to have function to request random word(number) function requestRandomFunction() external { uint256 requestId = i_vrfCoordinator.requestRandomWords( i_gasLane, i_subscriptionId, REQUEST_CONFIRMATIONS, i_callBackGasLimit, NUM_WORDS ); } which when called will...

This standard is still not used in much places but its a right step in direction to enforce royalties for NFTs https://eips.ethereum.org/EIPS/eip-2981 to use Open Zeppelin version this is what to do (npm install openzeppelin/contracts ofcourse)​​​​​​​import "@openzeppelin/contracts/token/common/ERC2981.sol"; in your smart contract and in the constructor you can add something like _setDefaultRoyalty(0xc8A5552031f92dEbeA5D9e61a396944Ee01BB2ca, 500); which sets where royalties should go and in w...

This standard is still not used in much places but its a right step in direction to enforce royalties for NFTs https://eips.ethereum.org/EIPS/eip-2981 to use Open Zeppelin version this is what to do (npm install openzeppelin/contracts ofcourse)​​​​​​​import "@openzeppelin/contracts/token/common/ERC2981.sol"; in your smart contract and in the constructor you can add something like _setDefaultRoyalty(0xc8A5552031f92dEbeA5D9e61a396944Ee01BB2ca, 500); which sets where royalties should go and in w...

As frontend needs to have the current Abi of a deployed smart contract as well as SC addresses it is a tedious process to do this manually. So there is a way to make this automatic when deploying contracts. This is for hardhat setup using hardhat ethers deploy plugin as this makes deployments more streamlined. All you need here is change name of the contract constant and for multiple contracts you would need some looping and arrays.vCode below will make (if they don't exsist) .json file ...

As frontend needs to have the current Abi of a deployed smart contract as well as SC addresses it is a tedious process to do this manually. So there is a way to make this automatic when deploying contracts. This is for hardhat setup using hardhat ethers deploy plugin as this makes deployments more streamlined. All you need here is change name of the contract constant and for multiple contracts you would need some looping and arrays.vCode below will make (if they don't exsist) .json file ...

To better understand solidity and EVM you should read all of these articles, preferably few times https://betterprogramming.pub/solidity-tutorial-all-about-stack-c1ec6070fe60 https://blog.openzeppelin.com/deconstructing-a-solidity-contract-part-i-introduction-832efd2d7737/ https://noxx.substack.com/p/evm-deep-dives-the-path-to-shadowy?utm_source=url&s=r and try all the tools inside that are recommended and step through them, will give you great insights in magic behind all the code.

To better understand solidity and EVM you should read all of these articles, preferably few times https://betterprogramming.pub/solidity-tutorial-all-about-stack-c1ec6070fe60 https://blog.openzeppelin.com/deconstructing-a-solidity-contract-part-i-introduction-832efd2d7737/ https://noxx.substack.com/p/evm-deep-dives-the-path-to-shadowy?utm_source=url&s=r and try all the tools inside that are recommended and step through them, will give you great insights in magic behind all the code.