[ANN][BABY][AIRDROP][EXCHANGE]PoW/PoS+Low-Masternode+[Defense (GPU)ASIC]

[CryptoRobert]

How often would you hit a block with CPU mining now, mining with a good i7 processor? I mean, is it a matter of hours, days or weeks or... years?

I have 1 4core/8thread and 1 8core/16 cpu mining and I get between 2-4 blocks a day between both of these CPUs.  With a single quad core, I would expect 0-1 blocks a day, certainly 3-4 a week.

In order to mine is there anything special you's have to do or is it just sufficient to leave the wallet open? How many of the CPU's resources would the wallet use?

[mo_onster]

Hey. Very good project!
Good luck for team!

[alkaiser]

with current masternode , you need to wait 3 days++ to get first reward

Good morning.I can't figure out why there's no payoff from the masternode.A PC running around the clock, masternode running correctly done the port forwarding....not only that, she blocked the balance is not baby 10000 and 30000, so still no payout to my address...Someone tell me where to look, that would work.Thank you in advance.

I restarted 6 of my masternodes late last week and it took 3-4 days before they started earning money.  It used to only take about 24 hours but with the greater number of nodes, it now seems to take at least 3 days to get any payout.  Just my experience so you may get luckier.

[duchaitp]

There are 2000 masternodes, we have gone one fifth of the way. Looking forward to the development of Baby and towards success.

[darval]

How often would you hit a block with CPU mining now, mining with a good i7 processor? I mean, is it a matter of hours, days or weeks or... years?

I have 1 4core/8thread and 1 8core/16 cpu mining and I get between 2-4 blocks a day between both of these CPUs.  With a single quad core, I would expect 0-1 blocks a day, certainly 3-4 a week.

In order to mine is there anything special you's have to do or is it just sufficient to leave the wallet open? How many of the CPU's resources would the wallet use?

You need to leave the daemon running (it is running when you are using the gui wallet).  You also need to set it to generate.  You can do this with the debug window in the gui and do:

Code: ("debug window")

setgenerate true 

Or if you are using the command line, you can do:

Code: ("command line")

$ ./baby-cli setgenerate true

Assuming you are in the directory with the baby-cli binary and it is executable.

In both cases you can limit the number of cores it uses by adding a third parameter which is the number of cores.  Using 2 cores would be:

Code: ("debug")

setgenerate true 2

Code: ("command line")

$ ./baby-cli setgenerate true 2

[Ethinkin9]

Baby is growing fast, the transaction speed is also very fast. 

[crazyer1976]

Baby is growing fast, the transaction speed is also very fast. 

My wallet worked for several days in a row, but could not catch a single block (I7-4770K, 3 cores). The complexity is very high. Did and truth no one can do pool for this coin!

[CryptoRobert]

How often would you hit a block with CPU mining now, mining with a good i7 processor? I mean, is it a matter of hours, days or weeks or... years?

I have 1 4core/8thread and 1 8core/16 cpu mining and I get between 2-4 blocks a day between both of these CPUs.  With a single quad core, I would expect 0-1 blocks a day, certainly 3-4 a week.

In order to mine is there anything special you's have to do or is it just sufficient to leave the wallet open? How many of the CPU's resources would the wallet use?

You need to leave the daemon running (it is running when you are using the gui wallet).  You also need to set it to generate.  You can do this with the debug window in the gui and do:

Code: ("debug window")

setgenerate true 

Or if you are using the command line, you can do:

Code: ("command line")

$ ./baby-cli setgenerate true

Assuming you are in the directory with the baby-cli binary and it is executable.

In both cases you can limit the number of cores it uses by adding a third parameter which is the number of cores.  Using 2 cores would be:

Code: ("debug")

setgenerate true 2

Code: ("command line")

$ ./baby-cli setgenerate true 2

Thank you, this has been very useful. Especially the command to limit the mining to an X number of cores, I would have not been able to use it otherwise.

[CryptoMiner88]

Very good project! I join!

We can make community so strong! Join Discord baby: https://discord.gg/CxHybbU   

[flexmankz]

I'm in TOP 20... WOAHHHHHH!!!

[BABYCHAIN]

How often would you hit a block with CPU mining now, mining with a good i7 processor? I mean, is it a matter of hours, days or weeks or... years?

I have 1 4core/8thread and 1 8core/16 cpu mining and I get between 2-4 blocks a day between both of these CPUs.  With a single quad core, I would expect 0-1 blocks a day, certainly 3-4 a week.

In order to mine is there anything special you's have to do or is it just sufficient to leave the wallet open? How many of the CPU's resources would the wallet use?

You need to leave the daemon running (it is running when you are using the gui wallet).  You also need to set it to generate.  You can do this with the debug window in the gui and do:

Code: ("debug window")

setgenerate true 

Or if you are using the command line, you can do:

Code: ("command line")

$ ./baby-cli setgenerate true

Assuming you are in the directory with the baby-cli binary and it is executable.

In both cases you can limit the number of cores it uses by adding a third parameter which is the number of cores.  Using 2 cores would be:

Code: ("debug")

setgenerate true 2

Code: ("command line")

$ ./baby-cli setgenerate true 2

Thank you, this has been very useful. Especially the command to limit the mining to an X number of cores, I would have not been able to use it otherwise.

nice job

[kikichou]

I have 10 baby MN,every 1-2 days,i got one MN missing,have no idea with that.

[mtx_demon]

I have 10 baby MN,every 1-2 days,i got one MN missing,have no idea with that.

That's why you are running more than the VPS is capable
Probably it's missing RAM
did you setup a swap in the VPS?
that will not help much but would extend life in couple days maybe

[jujubax]

more than 1300 Masternodes
dammm
One block a day pretty much now!!

[asem]

an adorable project, is there no whitepaper ?? I think you need to add it, good luck.

[BABYCHAIN]

./baby-cli reindex
The abnormal shutdown will cause ZBABY to fail to generate the block which will destroy the integrity of the data, so it needs to be resynchronized.

[GoVanza]

What happens in the network? 7 hours jumps on the hash and crazy swings !!! Connected Asic or Pool!!??
At me the unit was caught at 23:05 it was confirmed 101 till 04:22 hours

[darval]

What happens in the network? 7 hours jumps on the hash and crazy swings !!! Connected Asic or Pool!!??
At me the unit was caught at 23:05 it was confirmed 101 till 04:22 hours

Whatever the issue, it is slowed the generation of blocks down.  More hash would have sped it up.  I am sure it is being investigated.

[darval]

What happens in the network? 7 hours jumps on the hash and crazy swings !!! Connected Asic or Pool!!??
At me the unit was caught at 23:05 it was confirmed 101 till 04:22 hours

Whatever the issue, it is slowed the generation of blocks down.  More hash would have sped it up.  I am sure it is being investigated.

It appears to have gotten back closer to normal now.  Not sure what happened.

[mtx_demon]

Welcome the new exchange for BABY!!