Eternal Upgradeable Pattern in Solidity

Upgradation in smart contract is very important part, to enhance functionality or improve security. But updating a smart contract is different from tradition method. e.g. storage.sol a seperate storage contract to handle storage. and its library. Contract version 1: use the library of storage contract to access the storage contract. Backend contract version 2 Here… Continue reading Eternal Upgradeable Pattern in Solidity

Registry Upgradeable Pattern

Here is the first pattern to upgrade a smart contract via a middle registry contract. Which returns the new version contract. Below is the structure of Registry Upgradeable Smart Contract Pattern. Onwer.sol registry.sol this contract act as a middle man to get the address of upgraded of latest backend contract. BackendContract.sol this is the main… Continue reading Registry Upgradeable Pattern

Self Destruct method of Smart Contract in Solidity

Here is the code example how can we destruct a contract. For destruction we have to set the payable address in selfdestruct method where all ethers of contract can be transferred. After destruct a contract all state variables become null, 0 or false, also we can’t update any state variable. e.g.

Circuit Break Pattern in Solidity

In the live contract there are many chances we find an type of error and we have to stop smart contract to handle malicious activity. here is the sample of Circuit Break Pattern.

State Machine Pattern in Solidity

During developing a smart contract sometime we need to manage the different stages and execute and restrict method according to that state/stage of the smart contract.

Owner Based Restriction in solidity

Authentication is very important in any project to control and give limited access to users for this purpose, in solidity we get this functionality with this pattern.