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

[MWD64]

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.

hey BipGoat (great name.)

We're taking the pool down for a few days as a test of something, so solo mining should be better now. And if you ever empty your appdata folder, only remove the files ending in .dat, and MAKE SURE YOU BACK THEM UP FIRST!

Woprm,s/
MWD

[1714880503]

1714880503

[1714880503]

1714880503

[1714880503]

1714880503

[1714880503]

1714880503

[1714880503]

1714880503

[1714880503]

1714880503

[MWD64]

We now have set prices in bips for stickers, buttons and drink koozies! https://bipcoin.org/?page_id=82 Spend #BipCoin

[BadAudioisaHateCrime]

New to mining/cryptocoins/etc but I've been solo mining for two days now and I had a big gap from block 5137 to 5726.  Things seem to be churning along like earlier now.  Hopefully the solo mining continues to be good for awhile.  

[MWD64]

New to mining/cryptocoins/etc but I've been solo mining for two days now and I had a big gap from block 5137 to 5726.  Things seem to be churning along like earlier now.  Hopefully the solo mining continues to be good for awhile.  

how many bips have you caught, and when was the last one?

Nice user name.

[BadAudioisaHateCrime]

Worms,
Last block was 5753.  I've got a few today so far, things seem to be speeding up. I've probably got 4 locked right now.

Right now I'm trying to figure out how the whole hashing rate works out.  I was running 7 out of 8 cores for awhile and seeing 150 and I just changed it to 4 to cool down a bit and I'm seeing 165. is there a sweet spot somewhere in the number of cores running or is a based on the individual computer?

I'll be hitting you up for some stickers soon.  I need to figure out how to transfer next.

[MWD64]

Worms,
Last block was 5753.  I've got a few today so far, things seem to be speeding up. I've probably got 4 locked right now.

Right now I'm trying to figure out how the whole hashing rate works out.  I was running 7 out of 8 cores for awhile and seeing 150 and I just changed it to 4 to cool down a bit and I'm seeing 165. is there a sweet spot somewhere in the number of cores running or is a based on the individual computer?

I'll be hitting you up for some stickers soon.  I need to figure out how to transfer next.

yeah, mining with CryptoNote-based coins isn't like Bitcoin-based coins, where more GPU is god. More CPU is supposed to be God with us but not even always that.

To try transacting, send me some dust amount, like .001 bips.

 to this address:
bip1km1DyPMBT1XAZytjJ7VeQw9LAgXgCaixw1jBCHKYCEWw76KvzLLHRTGZhM7x6dR5Y7rQATYQ1ag dicHcWNRn2Wis8RgyMm

and let me know when it's sent.

[BadAudioisaHateCrime]

Worms,
Last block was 5753.  I've got a few today so far, things seem to be speeding up. I've probably got 4 locked right now.

Right now I'm trying to figure out how the whole hashing rate works out.  I was running 7 out of 8 cores for awhile and seeing 150 and I just changed it to 4 to cool down a bit and I'm seeing 165. is there a sweet spot somewhere in the number of cores running or is a based on the individual computer?

I'll be hitting you up for some stickers soon.  I need to figure out how to transfer next.

yeah, mining with CryptoNote-based coins isn't like Bitcoin-based coins, where more GPU is god. More CPU is supposed to be God with us but not even always that.

To try transacting, send me some dust amount, like .001 bips.

 to this address:
bip1km1DyPMBT1XAZytjJ7VeQw9LAgXgCaixw1jBCHKYCEWw76KvzLLHRTGZhM7x6dR5Y7rQATYQ1ag dicHcWNRn2Wis8RgyMm

and let me know when it's sent.

sent.

BTW, when I copied/pasted your address it added a space between lag and dic in your address that gave an error.
 transfer 1 bip1km1DyPMBT1XAZytjJ7VeQw9LAgXgCaixw1jBCHKYCEWw76KvzLLHRTGZhM7x6dR5Y7rQATYQ1ag dicHcWNRn2Wis8RgyMm .001

[ir57]

Worms,
Last block was 5753.  I've got a few today so far, things seem to be speeding up. I've probably got 4 locked right now.

Right now I'm trying to figure out how the whole hashing rate works out.  I was running 7 out of 8 cores for awhile and seeing 150 and I just changed it to 4 to cool down a bit and I'm seeing 165. is there a sweet spot somewhere in the number of cores running or is a based on the individual computer?

I'll be hitting you up for some stickers soon.  I need to figure out how to transfer next.

Some processors throttle themselves when they reach a certain temperature for safety.  Could be you actually get better performance with fewer threads because you are not running hot enough to throttle.

[MWD64]

Worms,
Last block was 5753.  I've got a few today so far, things seem to be speeding up. I've probably got 4 locked right now.

Right now I'm trying to figure out how the whole hashing rate works out.  I was running 7 out of 8 cores for awhile and seeing 150 and I just changed it to 4 to cool down a bit and I'm seeing 165. is there a sweet spot somewhere in the number of cores running or is a based on the individual computer?

I'll be hitting you up for some stickers soon.  I need to figure out how to transfer next.

Some processors throttle themselves when they reach a certain temperature for safety.  Could be you actually get better performance with fewer threads because you are not running hot enough to throttle.

Make sure you put a fan on the computers while mining so they don't burn out. With laptops, prop them up with blocks so air gets under and over. With desktops I put an extra fan inside. Pix of both about 3/4 way down this page:
https://bipcoin.org/?page_id=93

Did you specify a number when you started mining?

start_mining 2

for instance. If you don't specify, it puts in 1. The number should be one less than the number of cores your processor has. More is better. If you have a quad core and type 3, it will mine faster than if you have two cores and type 1.

If you didn't specify a number and you have a quad core or 8 cores, type
stop_mining
then start mining again, specifying a number.

If the number is too high, you'll get a error message in red, and can go down 1 number at a time until it works. 

[MWD64]

Worms,
Last block was 5753.  I've got a few today so far, things seem to be speeding up. I've probably got 4 locked right now.

Right now I'm trying to figure out how the whole hashing rate works out.  I was running 7 out of 8 cores for awhile and seeing 150 and I just changed it to 4 to cool down a bit and I'm seeing 165. is there a sweet spot somewhere in the number of cores running or is a based on the individual computer?

I'll be hitting you up for some stickers soon.  I need to figure out how to transfer next.

yeah, mining with CryptoNote-based coins isn't like Bitcoin-based coins, where more GPU is god. More CPU is supposed to be God with us but not even always that.

To try transacting, send me some dust amount, like .001 bips.

 to this address:
bip1km1DyPMBT1XAZytjJ7VeQw9LAgXgCaixw1jBCHKYCEWw76KvzLLHRTGZhM7x6dR5Y7rQATYQ1ag dicHcWNRn2Wis8RgyMm

and let me know when it's sent.

sent.

BTW, when I copied/pasted your address it added a space between lag and dic in your address that gave an error.
 transfer 1 bip1km1DyPMBT1XAZytjJ7VeQw9LAgXgCaixw1jBCHKYCEWw76KvzLLHRTGZhM7x6dR5Y7rQATYQ1ag dicHcWNRn2Wis8RgyMm .001

yeah, that happens.
got the squittens.
worms.

[MWD64]

Would be nice if the pool could still show network hashrate and difficulty even when it's off.
Right now I can only see the difficulty when I actually find a block.

they will keep running the block explorer, but they're having a DDos attack now though.

[MWD64]

Would be nice if the pool could still show network hashrate and difficulty even when it's off.
Right now I can only see the difficulty when I actually find a block.

from a previous post on this thread:
-=-=-=-=-=-
The commands are a bit ugly. lol. In bipcoind:
set_log 3
print_bc 3600

Each block contains its difficulty. (remember, changes with CryptoNote coins each block)

Difficulty of the last block when I checked a bunch of minutes ago and forgot to post to you:

height 3617, timestamp 1471798573, cumul_dif 447249453, cumul_size 208
id              <8ff004b8695969ade481d7830ca83bb6588d89a2d80e55319d0b2c45130728ce>
difficulty              1233230, nonce 1431655851, tx_count 0


difficulty is 1.2 million.

[MWD64]

Would be nice if the pool could still show network hashrate and difficulty even when it's off.
Right now I can only see the difficulty when I actually find a block.

they will keep running the block explorer, but they're having a DDos attack now though.

Oh, my bad. Thought they just turned off the pool because you said it might be the culprit of the issues we've all been having.

both. the pool and explorer are down due to DDoS. When they get out of the DDos (it's been on and off for a week), they'll leave the pool off but turn the explorer back on.

Pool will stay off until we solve the bad tx issues. all the junk text flooding bitcoind. We have ideas, but need to pool of to check to see what to fix in the wallets.

[MWD64]

Would be nice if the pool could still show network hashrate and difficulty even when it's off.
Right now I can only see the difficulty when I actually find a block.

from a previous post on this thread:
-=-=-=-=-=-
The commands are a bit ugly. lol. In bipcoind:
set_log 3
print_bc 3600

Each block contains its difficulty. (remember, changes with CryptoNote coins each block)

Difficulty of the last block when I checked a bunch of minutes ago and forgot to post to you:

height 3617, timestamp 1471798573, cumul_dif 447249453, cumul_size 208
id              <8ff004b8695969ade481d7830ca83bb6588d89a2d80e55319d0b2c45130728ce>
difficulty              1233230, nonce 1431655851, tx_count 0


difficulty is 1.2 million.

Found a block as I was reading this
Difficulty is about 430k rn, was >500k yesterday

cool and cool.

Are you seeing less errors tonight than the past few nights?

[bspus]

from a previous post on this thread:
-=-=-=-=-=-
The commands are a bit ugly. lol. In bipcoind:
set_log 3
print_bc 3600

Actually, set_log 3 is enough. It reports on every block found by the network, along with the diff. You just need to wait a few mins for a block to be found

print_bc xxxx prints a bunch on the specific block but I don't see the difficulty

[MWD64]

from a previous post on this thread:
-=-=-=-=-=-
The commands are a bit ugly. lol. In bipcoind:
set_log 3
print_bc 3600

Actually, set_log 3 is enough. It reports on every block found by the network, along with the diff. You just need to wait a few mins for a block to be found

print_bc xxxx prints a bunch on the specific block but I don't see the difficulty

Thank you for your service!

[MWD64]

I have only been mining for about 20 minutes now and I have only had 1 connection error, not related to the ones I got before (I still had some yesterday)
https://i.gyazo.com/24699e5fa28c171c2be0a180717ce5cb.png

nice hashrate.

you've only mined 20 minutes tonight, or ever? Did you see more errors other days?
I was seeing them more even when not mining last night.

[MWD64]

For me it is 8:30 AM. Today, I started mining 20 min ago.
Yesterday (12+ hours ago) I still saw some errors but it didn't seem as bad as before.

so there are less errors now?

[MWD64]

For me it is 8:30 AM. Today, I started mining 20 min ago.
Yesterday (12+ hours ago) I still saw some errors but it didn't seem as bad as before.

so there are less errors now?

Yes. What's the default log level btw?
I set it to 0 (after setting it to 3) but it seems the miner doesn't tell me when it found a block.

Not sure.

I just leave it and type
balance
about every 8 hours.

"A watched pot never boils." lol.

[MWD64]

For me it is 8:30 AM. Today, I started mining 20 min ago.
Yesterday (12+ hours ago) I still saw some errors but it didn't seem as bad as before.

so there are less errors now?

Yes. What's the default log level btw?
I set it to 0 (after setting it to 3) but it seems the miner doesn't tell me when it found a block.

Not sure.

I just leave it and type
balance
about every 8 hours.

"A watched pot never boils." lol.

My pot boils when I don't expect it. Got 4 blocks in <1 hour today, was waiting for >1 hour yesterday for one block.

Nice.

I will probably be away for the night. Things are working well and I could use some time away from the screen.