[BIP] BipCoin. NOW LIVE. Mineable. CryptoNote. BipCot NoGov Licensed.

[pwpwpw]

everytime I have this fork issue I just delete all from appdata and redownload the chain, then its ok for about a day again, but I'm doing this almost daily.

[MWD64]

everytime I have this fork issue I just delete all from appdata and redownload the chain, then its ok for about a day again, but I'm doing this almost daily.

all the .dat data? or all the data?
and you DO back it up, right?

[MWD64]

everytime I have this fork issue I just delete all from appdata and redownload the chain, then its ok for about a day again, but I'm doing this almost daily.

all the .dat data? or all the data?
and you DO back it up, right?

Sorry for the dumb question, but why do you need to back it up?
If it is only the blockchain, you should be able to redownload it at any time, right?

It's good computing practice to ALWAYS BACK UP ANY FILES YOU INTEND TO DELETE. In case you're wrong, or I'm wrong, and it makes thing not work, then you can revert back to when things were only messed up, but sort of working, and try something else. lol.

And you should always close the associated program before backing up, because sometimes files won't properly back up when in use. 

[MWD64]

everytime I have this fork issue I just delete all from appdata and redownload the chain, then its ok for about a day again, but I'm doing this almost daily.

all the .dat data? or all the data?
and you DO back it up, right?

Sorry for the dumb question, but why do you need to back it up?
If it is only the blockchain, you should be able to redownload it at any time, right?

It's good computing practice to ALWAYS BACK UP ANY FILES YOU INTEND TO DELETE. In case you're wrong, or I'm wrong, and it makes thing not work, then you can revert back to when things were only messed up, but sort of working, and try something else. lol.

And you should always close the associated program before backing up, because sometimes files won't properly back up when in use. 

Have you CPU mined on the pool? I just can't get it to work for me.

no. My friend Jim Jesus (who helped make our logo) did successfully yesterday though.

I'm basically too busy trying to work on getting rid of these nightly problems to mine right now.

[MWD64]

everytime I have this fork issue I just delete all from appdata and redownload the chain, then its ok for about a day again, but I'm doing this almost daily.

all the .dat data? or all the data?
and you DO back it up, right?

Sorry for the dumb question, but why do you need to back it up?
If it is only the blockchain, you should be able to redownload it at any time, right?

It's good computing practice to ALWAYS BACK UP ANY FILES YOU INTEND TO DELETE. In case you're wrong, or I'm wrong, and it makes thing not work, then you can revert back to when things were only messed up, but sort of working, and try something else. lol.

And you should always close the associated program before backing up, because sometimes files won't properly back up when in use. 

Have you CPU mined on the pool? I just can't get it to work for me.

no. My friend Jim Jesus (who helped make our logo) did successfully yesterday though.

I'm basically too busy trying to work on getting rid of these nightly problems to mine right now.

Alright. I'll continue to solo mine for now, but if your friend comes on the forums, it would be nice if he could help me.
You're doing great work on the coin, dev. I'm sure you'll have fixed the errors in no time.

Thanks man.

Jim doesn't like forums. lol.

Since you can't pool mine now, can you try solo mining for a while and let me know if you get blocks? Thanks!

[pwpwpw]

I delete the entire folder every time, right now I can't sync up.

23:47:47.261566 INFO [45.32.31.49:47325 INC] Sync data returned unknown top block: 5629 -> 5636 [7 blocks (0 days) behind]
23:47:47.261566 INFO SYNCHRONIZATION started
23:47:47.458578 INFO [67.173.185.36:18870 OUT] Sync data returned unknown top block: 5629 -> 5636 [7 blocks (0 days) behind]
23:47:47.458578 INFO SYNCHRONIZATION started
23:47:47.694591 INFO [161.53.40.94:18870 OUT] Sync data returned unknown top block: 5629 -> 5636 [7 blocks (0 days) behind]
23:47:47.694591 INFO SYNCHRONIZATION started
23:47:47.927604 WARNING [24.240.49.21:18870 OUT] Exception in connectionHandler: vector<T> too long
23:47:48.306626 INFO [67.87.107.147:18870 OUT] Sync data returned unknown top block: 5629 -> 5636 [7 blocks (0 days) behind]

[MWD64]

I delete the entire folder every time, right now I can't sync up.

23:47:47.261566 INFO [45.32.31.49:47325 INC] Sync data returned unknown top block: 5629 -> 5636 [7 blocks (0 days) behind]
23:47:47.261566 INFO SYNCHRONIZATION started
23:47:47.458578 INFO [67.173.185.36:18870 OUT] Sync data returned unknown top block: 5629 -> 5636 [7 blocks (0 days) behind]
23:47:47.458578 INFO SYNCHRONIZATION started
23:47:47.694591 INFO [161.53.40.94:18870 OUT] Sync data returned unknown top block: 5629 -> 5636 [7 blocks (0 days) behind]
23:47:47.694591 INFO SYNCHRONIZATION started
23:47:47.927604 WARNING [24.240.49.21:18870 OUT] Exception in connectionHandler: vector<T> too long
23:47:48.306626 INFO [67.87.107.147:18870 OUT] Sync data returned unknown top block: 5629 -> 5636 [7 blocks (0 days) behind]

might take a while.

did you back up files like I suggested before deleting? and are you deleting all files in appdata, or just ones ending in .dat? should be the latter.

[pwpwpw]

I did backup now but that chain couldn't even sync up to the last block so its kinda useless and yeah I delete all, will try only .dat but I still can't understand how does solo mining with 80h can split into my own chain.

[MWD64]

I did backup now but that chain couldn't even sync up to the last block so its kinda useless and yeah I delete all, will try only .dat but I still can't understand how does solo mining with 80h can split into my own chain.

I'm not sure you did, since you can't sync.

are your deleted files still in your recycling bin?

[MurderDawg]

[wallet bip1cG]: Height 5445, transaction c399e64e1262ca709101cfa9fffc7ea0096cdbe305c8d71605a15b47a02200c0, received 8.774284946701
Height 5472, transaction eb81bfb4009b08c512a87f6204457acc07e03e4a29c47c484c435a86beb63371, received 8.774171994838
Height 5472 of 5472
[wallet bip1cG]: balance
available balance: 15.000000000000, locked amount: 0.000000000000




Okay.  So i jut checked in on my laptop and it says i FINALLY mined some Bips (Woohoo!)  but it doesn't show up in the locked amount balance.  Does this take awhile, or was I just duped into being happy for a minute? 

did stuff turn around y'all? lots of oddness overnight, but has all worked out on my end, , wallet blocks even with explorer (and explorer back up), and all transfers finall came through. I didn't mine over night, but all sent/received from all wallets, Including CLI and GUI) worked.

No.  Just checked and now there are 3 blocks that say they have been mined, but don't show up in the locked or available balances. 

[ir57]

[wallet bip1cG]: Height 5445, transaction c399e64e1262ca709101cfa9fffc7ea0096cdbe305c8d71605a15b47a02200c0, received 8.774284946701
Height 5472, transaction eb81bfb4009b08c512a87f6204457acc07e03e4a29c47c484c435a86beb63371, received 8.774171994838
Height 5472 of 5472
[wallet bip1cG]: balance
available balance: 15.000000000000, locked amount: 0.000000000000




Okay.  So i jut checked in on my laptop and it says i FINALLY mined some Bips (Woohoo!)  but it doesn't show up in the locked amount balance.  Does this take awhile, or was I just duped into being happy for a minute? 

did stuff turn around y'all? lots of oddness overnight, but has all worked out on my end, , wallet blocks even with explorer (and explorer back up), and all transfers finall came through. I didn't mine over night, but all sent/received from all wallets, Including CLI and GUI) worked.

No.  Just checked and now there are 3 blocks that say they have been mined, but don't show up in the locked or available balances. 

MurderDawg, I've had a couple that failed verification for one reason or another.  You could check for this by searching your bipcoind.log for the phrase "failed verification".

In Windows, from a dos prompt: find /i "failed verification" bipcoind.log

In Linux: grep -i 'failed verification' bipcoind.log

[rancemo]

Looks like the pool is down again.

[MWD64]

Looks like the pool is down again.

We're gonna have them take it down for a few days, and only solo mining.

We have a theory that mining pools with slightly different software from ours are causing all the clusterflucks overnight. And it's overnight because more people in US time zones (where we seem to have most users, because of my radio show) are, and therefore at night when people sleep, all the pool mining messes things up.

We will fix that but the first step is no pool for a few days.

Thank you for your patience.

MWD

[thebaron]

I was wondering how people had modified the pool software, since your wallet client doesn't appear to respond to standard JSON RPC commands like other CryptoNote variants.

[MWD64]

I was wondering how people had modified the pool software, since your wallet client doesn't appear to respond to standard JSON RPC commands like other CryptoNote variants.

yup.

[thebaron]

I think a problem might be that there may not be enough active peers to propagate data across the P2P network fast enough at this point. Consider setting up a few AWS cloud instances of the Daemon to help that...

[MWD64]

I think a problem might be that there may not be enough active peers to propagate data across the P2P network fast enough at this point. Consider setting up a few AWS cloud instances of the Daemon to help that...

Thank you.

I really don't think that's it, We have 4 strong servers 2, in north america, one each in Germany and Japan, that should be enough so far.

We're going to try one thing at a time, but will keep more servers in mind as something to try.

[MWD64]

I think a problem might be that there may not be enough active peers to propagate data across the P2P network fast enough at this point. Consider setting up a few AWS cloud instances of the Daemon to help that...

The JSON comment is probably far closer to the problem.

[thebaron]

I think it's a little amusing that my Core 2 Duo desktop has found more blocks than my i7-5500U laptop...

[BipGoat]

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.