Earn 78000U easily in ten hours with 0.035eth risk-free.
The popular project today is Clips, a project similar to xen, so the gameplay should be similar to xen. However, some people have taken a different approach and are earning transaction fees through batch minting, which is a profitable business without any losses. This article mainly aims to understand the basic logic of batch minting.
Profit Calculation:
The price of CLIPS used to calculate the earnings in this article is shown in the image provided. The GAS cost for the contract author is 0.0352ETH. The author's address can be found at Ethereum Transaction Hash (Txhash) Details | Etherscan.
The profit calculation process: The contract charges a 6% transaction fee, but batch minting helps users save some gas. So users still profit, it's a win-win situation. You can see the details on Twitter in the image provided.
From the contract information, it is known that the beneficiary address of the contract author is the deployment address. The current CLIPS balance of this address is 1374900000. At the time of writing this article, the price of the token was 0.000057, but the liquidity of the pool has not been thoroughly investigated.
Profit Calculation: 1374900000 * 0.000057 = 78369.3U
Contract Interpretation:
This is an Ethereum smart contract written in Solidity. The contract consists of three parts: the Clip interface, the claimer contract, and the BatchMintClips contract. Here is an explanation of these parts:
-
Clip interface:
This interface defines the basic functions of the Clip contract, including mintClips(), transfer(), and balanceOf(). These functions are used to create new Clip tokens, transfer tokens from one address to another, and query the token balance of an address, respectively. -
claimer contract:
This is a simple contract that takes an address as a parameter in its constructor. In the constructor, it first obtains an instance of the Clip contract and then calls the mintClips() function to create new Clip tokens. Finally, it transfers the newly created tokens to the receiver address passed in. -
BatchMintClips contract:
This contract is used to batch create Clip tokens. It has a public owner variable and an onlyOwner modifier to ensure that only the contract creator can execute certain functions.- Constructor: When creating the BatchMintClips contract, the address of the contract creator is set as the owner.
- batchMint() function: This function takes a parameter count, which represents the number of claimer contracts to create. For each claimer contract to be created, it instantiates a new claimer contract and sets the BatchMintClips contract's address as the receiver. This way, when new Clip tokens are created, they will be sent to the address of the BatchMintClips contract. After the batch creation is complete, 94% of the tokens are transferred to the caller's address, and the remaining 6% of the tokens are transferred to the owner's address.
In summary, this contract allows users to batch create Clip tokens. The caller can execute this operation by calling the batchMint() function and providing the desired quantity to create. After the batch creation is complete, the caller will receive 94% of the tokens, and the contract creator will receive the remaining 6%.
Conclusion:
The contract author combines the experience of xen and demonstrates a flexible use of Solidity. The ideas can be very well borrowed. The above contract is very simple, and I believe that anyone who has studied the WTF-Solidity Basics can write it. The implementation of the code is not difficult, but the difficulty lies in the implementation of the ideas. I look forward to everyone's hard work and rewards when the bull market comes.