cpu.fusion
Last updated
Last updated
Part of WaxFusion's mechanics for generating revenue is based on staking WAX for CPU, and renting CPU to users for a low cost.
The actual rental logic is in the main dApp contract, but due to the way WAX's system contracts work and the complications with staking/unstaking WAX to different wallets, rented/staked WAX is sent off to 3 different proxy contracts to complete the staking process.
The contract addresses for these 3 contracts are as follows:
cpu1.fusion, cpu2.fusion and cpu3.fusion
All 3 contracts use the same exact code, which can be found on Github at the following link:
Below is a description of each of the actions on the smart contract, their parameters, and how they are designed to behave.
To get a breakdown of the actions and tables on this contract, use the quick links below.
