I tried mining on a pool but my balance goes backwards. it will go up then go back. I don't see anywhere where shares are being rejected, was wondering if this happens to anyone else.
the cpu pool send the mined nxs to the adress written in the command line of the miner. This should be the reason your balance decrease when the payout is done. Check your wallet.
there is no payout, it is 0. I just started, so it went from .23 to .26 then back to .23. it did this a couple of times but the payout is 0 and wallet balance is 0.
This is a result of the last block found being an orphan. When the pool finds a block the current mining "round" ends and the shares that all miners have found are used to work out how much each miner has earned during that round. At this point your balance goes up by that amount (0.03 in your case) and a new round is started (all share counts reset to 0). The pool then has to wait a little while before it knows whether the block it submitted has been orphaned by the network or not. If we find it was orphaned then we essentially reopen the previous round, reinstating the shares everyone submitted, reducing the balance of all miners back to their previous amount, and refunding the balances of those miners who were paid in that block. So this is where you see the balance go back to it's previous state (down by 0.03).
The reason we have to adopt this process is that Nexus is not like other pools that wait for blocks to mature before calculating and making payments. Instead miners payments are part of the mined block's coinbase, so you receive a "mined" block in your wallet for your payout amount and it matures there.
I'm hoping to improve this process slightly though, so that the current round is not closed (balances don't increase) until we can be certain that the last block found was not orphaned. The problem though is that this is not simply a one-time check - the pool can believe that its submitted block was accepted by the network, only to have it orphaned some time later (usually less than a minute though). So we have to keep checking the state of the last few blocks submitted just in case they get orphaned. In fact the pool checks the last 5 found blocks, every 20s, just in case.