Opstan Mining
In Opstan, coins appear only through mining — that’s the foundation of network security. Choose a mode: pool (more stable) or solo (fully independent, but “lottery”).
Confirmations — quick note
A block appears on average once every ~10 minutes. Operations/rewards are considered fully “final” after 7 confirmations (protection from rare short forks).
Pool mining
RecommendedYou submit shares to a pool; the pool finds blocks and distributes rewards among participants.
- More regular payoutsless waiting, less “lottery”
- Easier to startconnect → mine → earn
- Pool feeusually a small percent
Solo mining
For enthusiastsYou mine directly to the network: if your miner finds a block, the entire block reward is yours (but it may take a long time).
- Maximum independenceno pool and no middleman
- High variancenothing for long time, then a big hit
- Requires a synced nodeand stable connection
Pool mining — quick start (via GUI)
Go to a pool website. You can use a partner pool (partner IPs will be added later) or any other pool. Make sure the pool is trustworthy and avoid suspicious websites.
1) Choose a pool on the website
On the pool site, find the IP/host:port (pool address) and payout rules. Don’t use suspicious sites/pools.
2) Open the GUI node and select “Pool mining”
Launch the GUI node app and in the mining section choose Pool mode.
3) Enter pool IP, your address, and power
Enter the pool IP (from the pool website) and make sure your wallet address is correct so rewards go to you. Choose mining power — usually 4–6 threads. Monitor CPU load in Task Manager.
Where to see hashrate and rewards
Check your hashrate and stats on the pool website — usually there are hashrate, shares, and payouts. Everything is tracked by your wallet address.
How payouts work
The pool pays out when you reach the minimum threshold set by the pool. Often payouts happen around every 100 blocks, but it can be less frequent — depends on the pool.
Solo mining — autonomous, but “lottery” (via opstan.exe)
In solo you mine directly to the network, so make sure: your node is synced, the network is reachable, and your PC time/date is correct. Solo mining runs via opstan.exe (command line, not GUI). Use the default node port 1111 (if your build uses a different one — use that).
1) Run the node via opstan.exe
Launch opstan.exe (command line, not GUI). Use port 1111 (or your default port).
2) Log in to a wallet or create one
If you don’t have a wallet — create a new one. If you do — log in. This is required so the block reward goes to you.
3) Check sync status (command 3)
Run command 3 to ensure you are connected to peers and have the latest chain height. If you’re behind — solo mining is pointless.
4) Start mining (command 1) and choose power
Start mining via command 1 and select power (threads). Monitor CPU load in Task Manager and adjust for stability.
5) Where to see hashrate and results
Hashrate, errors, and results are written to log1. It’s convenient for analyzing stability and problems.
Reward maturity: there is a 100-block lock — the reward becomes spendable only after 100 blocks (about ~16 hours).
How to verify the reward
After you find a block, it appears in the chain. Then wait for 7 confirmations. Check Operations and your wallet balance.
Why is pool “better” for beginners?
Because the pool distributes rewards more frequently and more evenly: you earn based on your shares, instead of waiting for a rare solo jackpot.
What are shares and why do rejected happen?
Shares are lower-difficulty proofs of work that your miner submits to the pool. Rejected can happen due to network latency, wrong difficulty, incorrect PC time, or connection drops.
Miner works, but no payouts
Check: your wallet address, accepted shares, the pool’s minimum payout threshold, and that operations have 7 confirmations.
Solo doesn’t find blocks for a long time — is it a bug?
Usually no. Solo is probability. The smaller your hashrate compared to the network, the longer the wait. For steadier earnings, use a pool.
What about fees?
The network supports fees for operations (transaction/message). If the network is not busy, sometimes 0 fee works. Under load, a fee helps speed up processing.