I'm a ridiculously ignorant noob. In the daemon I keep seeing in red "Block reorganized as orphaned and rejected..." A few lines later I see "Alternative blockchain size: 2 with cum_difficulty...." It does end up saying that my sync is ok and returns to showing my absolutely amazing hash rate of 36. This happens every few minutes. Can anyone explain to me what is happening here. Or at least point me in the right direction to learn this stuff myself. So I can cease being a ridiculously ignorant noob.
I used to get that red warning about orphaned whenever I mined a block that ended up being rejected. Have you mined any?
close wallewt and daemon, try deleting everything from %appdata%\bipcoin and restart daemon to sync from scratch. The blockchain is still very small so no problems
Then start wallet, give it the "reset" command to look again for transactions from the beginning.
list_transfers afterwards for more detail
Chances are you will find your latest mined block missing but the problems should stop. You will still be getting some wrong transactions errors but nothing you can do about that.
@MWD64 (or anyone who has a clue)
When the chain forks how come all these problems arise instead of everyone just adopting the longer chain automatically?
That's the case with "common" bitcoin clones (yeah, bip is a monero clone, I know) isn't it?
Thanks for the tips. I had previously solo mined and received 2 blocks (current avail balance 17.55...). I had mined one block while at work but it was never confirmed and was lost when I deleted the appdata folder, resynced the blockchain and reset my wallet. Oh well. I'm learning and I have my very first crypto coins. So this adventure is successful so far.