24
loading...
How to test a BEP20 token with Hardhat and not get SCAMmed
The BEP20 token we will be testing today is the $SCAM token.
SCAM is a BEP20 token created on Binance Smart Chain. $SCAM has a 100k marketcap currently (350k at its/BNB’s ATH) and a limited supply of 100 million tokens, a lot of which was distributed through multiple free airdrops on reddit that helped grow the community into 200+ members on telegram and 700+ on reddit.
$SCAM follows a bare-bone ERC20 token implementation deployed on the BSC Mainnet with basically no admin functions or centralized control — no blacklist, burn or freeze functions and also no additional tokens can be minted.
I hope you already have solidity development environment ready at your machine.
Otherwise, please refer to my previous post How to make a fullstack dapp with React, Hardhat and ethers.js with examples.
I came across Safe Crypto and Money ($SCAM) randomly on the dev.to website through the developer’s story about how learning about ERC20 tokens and programming practice on Solidity became a passion project leading to this coin.
I was just restarting blockchain development again and I found the story of the author very interesting.
What started out as a meme token, as can be understood from the name itself, organically evolved into an awesome friendly community where beginners and developers alike could learn more about cryptocurrency and DeFi.
They’ve already launched a website and implemented a fully decentralized liquidity rewards contract, and are currently working on decentralized governance and treasury, as well as a faucet.
The community itself has become a place of healthy conversation, discussion and ideation, and a launching platform for various voluntary projects taken up by members such as a coin-listing site, NFTs, merchandise, and marketing campaigns.
First, I thought it was just a joke but I was intrigued by the post. I found the project funny and wanted to be more involved with the project and found its Telegram group also.
Different from my first expectation, the members of the group were very helpful. I could find a clue to set up and deploy a smart contract code that one of my client wanted to test.
I also inspired myself to write How to make a fullstack dapp with React, Hardhat and ethers.js with example by participating in the group.
I think it helped me a lot in getting further involved with blockchain stuffs and find useful information.
It is important to have someone help you get familiar with cryptocurrency and its relevant technologies. Otherwise, it is very easy to get scammed and lose money.
If you want to know more about SCAM after this post, you can participate in its Telegram group.
Currently, the faucet contract to get SCAM free is also working so you can hold it free. I think it can be a good opportunity to have your first cryptocurrency.
The website for it is also ready at https://faucet.scam-coin.org/ page.
You can use any wallet in the list below.
Then, connect it to the website.
Finally, follow its instruction to get your first $SCAM token.
If you have any doubt, please join the group and ask the members in there for help. They will help you to learn about SCAM, cryptocurrency, smart contracts and DeFi in general and other blockchain relevant stuffs.
Before you start, BEP20 token specification is equal to ERC20 equivalent, so if you are not familiar with that, please read the documentation for it first.
We will inspect each part of it. This will help you find what this contract does and write tests in the next part to confirm that.
1. This is where the owner of the contract can define BEP20 token name, symbol and the decimal for it. It is just following the ERC20 standard.
2. Here, the total supply of the token is defined. There are no mint or burn function for SCAM. You can see that there is a fixed amount of SCAM tokens(100000000).
Then, the owner of the contract will take 20000000 of it and 1000000 will be used with airdropTokens function.
3. These functions until 4. is just some parts of IERC20 standard functions. It was the intention of its author.
4. This is where airdrop of the SCAM token happens, you can see it is sent from the contract to receiver. (100000000–20000000 = 80000000 in the constructor part)
5. This part is not relevant to the SCAM token logic. It is just a fallback function that extracts the BNB balance from the contract.
I spoke with the author and he told me that he included it to receive donation for the contract.
It is not relevant to SCAM token logic. But, we will include the test to see if it affects the balance of a SCAM holders in the next part.
6. These are some functions from SafeMath OpenZeppelin library code.
You can read their documentation for more information.
In the previous part, we inspected the contract code for SCAM and see what each part of it does.
We will write simple tests for it to find that they all work ok.
I will assume you are using the source code link I shared at the beginning of this post.
Before you update your project, please edit your hardhat.config.js and use the solidity compiler version between >=0.4.22 <0.6.0 that you prefer.
module.exports = {
defaultNetwork: "hardhat",
paths: {
artifacts: './src/artifacts',
},
networks: {
// $npx hardhat run scripts/deploy.js --network localhost
// https://hardhat.org/config/
hardhat: {
chainId: 1337,
},
},
solidity: "0.5.6", // This is where you should edit.
};Use $yarn compile (npx hardhat compile) to see if the contract code really compiles and it should show a result similar to this.
Creating Typechain artifacts in directory typechain for target ethers-v5
Successfully generated Typechain artifacts!Use $yarn serve (npx hardhat node) in a console to set up local solidity dev env with hardhat.
Then, verify that everything is ok with your scripts/deploy.js file.
If you could make it to this part, we can finally write tests for the SCAM contract.
You can see the test/scam-test.js file in the repository similar to this.
The smart contract code for SCAM is very simple and we don’t need a lot of lines of code to test it also.
1. There are very big numbers are involved for BEP20 token contract. We need their hex values to test them with hardhat and ethers.js package.
Therefore, I manually included them. For that, you can use your Python console with hex function.
$python
>>> hex(1000000000000000000000000)
'0xd3c21bcecceda1000000'
>>> hex(1000000000000000000000000000000)
'0xc9f2c9cd04674edea40000000'
>>> hex(1000000000000000000000000000000000)
'0x314dc6448d9338c15b0a00000000'
>>> hex(1000000000000000000000000)
'0xd3c21bcecceda1000000'
>>> 10 ** 26
100000000000000000000000000
>>> hex(_)
'0x52b7d2dcc80cd2e4000000'You can also refer to How to use Python in JavaScript with examples post to include that to your JavaScript code.
Otherwise, you can find a JavaScript function to find hex value of the big number also. But, that will be unnecessary if you know how to use Python also.
2. We test here to see contract name, symbol and the decimal is set correctly when the contract is deployed. You can also verify if the total supply of the token is set and preMine amount is correctly saved to the address of the owner of the contract.
3. In this part, we first check if other users (not owners) can call airdropTokens or not.
You can see if the caller were firstComer or secondComer (not owners), the contract shouldn’t allow to use airdropTokens function. In the contract, there is no error message set, so we use unspecified api from @openzeppelin/test-helpers package to test them.
You can also see the receiver have airDropSize amount of token “1000000000000000000000000” after that. This can be confusing comparing to the smart contract part but you can see the decimal value is “18”. If we consider that, the large number will be 1000000 of SCAM token and sent to the receiver.
4. Tests below this will be help you find how some of ERC20 standard functions included for this contract work.
You can see transfer, approve, allowance, transferFrom will work all ok with them.
5. There were fallback function and releaseBNB in the contract code for donation.
function releaseBNB() external {
require(msg.sender == owner_);
owner_.transfer(address(this).balance);
}
// Fallback function
function() external payable {}We can test that calling this function will not have any effect for not owners.
You can see the balance for the firstComer is equal after calling releaseBNB function in the test.
You could write more tests here if you want.
Test all of them really work at your machine with $yarn test (npx hardhat test) and you will see every test passes with the result similar to this.
$yarn test
Creating Typechain artifacts in directory typechain for target ethers-v5
Successfully generated Typechain artifacts!
SCAMToken state and transactions
✓ Should test 'totalSupply' and other default values.
✓ Should test 'airdropTokens' and the contract and receiver balance change.
✓ Should test 'transfer' from the owner to firstComer.
✓ Should test 'approve' and 'allowance' from the owner to firstComer.
✓ Should test 'approve', 'allowance' and 'transferFrom'.
✓ Should test 'releaseBNB' and it shouldn't affect the balance of other users (not owners)Hope you could make all tests pass.
In this post, we learnt how to test a custom BEP20 token with SCAM. I introduced it because I found its community very helpful. Hope the code snippet used here can be a starting point to test other BEP20 or ERC20 tokens also before you buy them.
ERC20 and BEP20 token are almost identical and you will be able to use the code snippet used here for the former as well.
If you liked the post, please share it with others. I am plan to share more blockchain relevant stuffs. I am interested in ETH and POLKADOT.
Thanks.
Join Coinmonks Telegram Channel and learn about crypto trading and investing
24