Pages:
Author

Topic: [BIP] BipCoin. NOW LIVE. Mineable. CryptoNote. BipCot NoGov Licensed. - page 11. (Read 25052 times)

sr. member
Activity: 476
Merit: 250
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.
sr. member
Activity: 476
Merit: 250
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.
sr. member
Activity: 476
Merit: 250
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.
sr. member
Activity: 476
Merit: 250
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. 
newbie
Activity: 14
Merit: 0
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.
newbie
Activity: 6
Merit: 0
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
sr. member
Activity: 476
Merit: 250
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.
newbie
Activity: 6
Merit: 0
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.
sr. member
Activity: 476
Merit: 250
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.
newbie
Activity: 6
Merit: 0
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.  
sr. member
Activity: 476
Merit: 250
We now have set prices in bips for stickers, buttons and drink koozies! https://bipcoin.org/?page_id=82 Spend #BipCoin
sr. member
Activity: 476
Merit: 250
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
newbie
Activity: 6
Merit: 0
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.
sr. member
Activity: 434
Merit: 250
I think it's a little amusing that my Core 2 Duo desktop has found more blocks than my i7-5500U laptop...
sr. member
Activity: 476
Merit: 250
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.
sr. member
Activity: 476
Merit: 250
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.
sr. member
Activity: 434
Merit: 250
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...
sr. member
Activity: 476
Merit: 250
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.
sr. member
Activity: 434
Merit: 250
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.
sr. member
Activity: 476
Merit: 250
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
Pages:
Jump to: