Staking is “lock a token, earn rewards”. Running your own pool means settling three things first: what gets staked, what gets paid out, and how long the rewards last. All three are written into the contract at deployment.
- Prepare the reward tokenThe reward tokens need to be in your wallet, and the pool contract needs an approval for enough of them. Insufficient approval is the most common reason a live pool pays nothing.
- Fill in the pool parametersStart time, duration in days, staked token, reward token, owner address, daily rewards, min and max stake, referral rewards (%) and lock-up. Total rewards = daily rewards × days, so enter a real budget.
- Deploy and seed the rewardsDeployment approves the reward token to the pool. Rewards are paid out of that budget and stop when it runs dry — there is no top-up later, so a long pool has to be funded generously up front.
- What participants doParticipants find the pool in the staking list, open it, approve the staked token and stake, then claim whenever they like. Pending rewards on that page are a snapshot of the chain read rather than a live counter, and the page labels when it was read.
- What the management page can changeStaking console only edits project info (project name, site link, description, website) and lock-up, counted from a user’s last stake — 0 means no lock. Total rewards, duration and the reward token cannot change, and there is no “end pool” button.
Careful · Change the lock-up and it only applies from the next stake
Lock-up counts from a user’s last stake, so what is already staked is unaffected by your edit; the moment that user adds more, the new lock-up applies. Explain the change in your community before you make it.
Careful · Rewards are budgeted up front and stop when they run out
Once the pool’s reward balance empties it stops paying. Work out the total and the duration against a real budget before you deploy — there is no mid-run top-up. A long pool that under-funds rewards will watch emissions stop and stakers start pulling out.