Pages:
Author

Topic: [ANN][BABY][AIRDROP][EXCHANGE]PoW/PoS+Low-Masternode+[Defense (GPU)ASIC] - page 9. (Read 38016 times)

member
Activity: 308
Merit: 10
need more marketing and promote this coin!


who can promote this coin on other forums?  



IF you can help with something, you can msg to dev!!!
member
Activity: 308
Merit: 10
need more marketing and promote this coin!


who can promote this coin on other forums?  
member
Activity: 93
Merit: 10
This coin name is so sweet lol
tell me how i can mine this please
Install the wallet as described on the first post of this thread, then 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 console")
> 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 console")
> setgenerate true 2
Code: ("command line")
$ ./baby-cli setgenerate true 2
member
Activity: 308
Merit: 22
so what's the next thing ?

thousands  masternodes now .... waiting for 10000 + masternodes ?
full member
Activity: 273
Merit: 100
Welcome the new exchange for BABY!!


member
Activity: 93
Merit: 10
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.
member
Activity: 93
Merit: 10
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.
newbie
Activity: 149
Merit: 0
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
copper member
Activity: 70
Merit: 6
./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.
member
Activity: 243
Merit: 10
an adorable project, is there no whitepaper ?? I think you need to add it, good luck.
copper member
Activity: 56
Merit: 0
more than 1300 Masternodes
dammm
One block a day pretty much now!!
full member
Activity: 273
Merit: 100
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
newbie
Activity: 27
Merit: 0
I have 10 baby MN,every 1-2 days,i got one MN missing,have no idea with that.
copper member
Activity: 70
Merit: 6
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
jr. member
Activity: 86
Merit: 1
I'm in TOP 20... WOAHHHHHH!!!
newbie
Activity: 21
Merit: 0
Very good project! I join!

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


sr. member
Activity: 1015
Merit: 289
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.
member
Activity: 434
Merit: 19
Baby is growing fast, the transaction speed is also very fast.  Grin

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!
member
Activity: 253
Merit: 10
Rolling in the Deep
Baby is growing fast, the transaction speed is also very fast.  Grin
member
Activity: 93
Merit: 10
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
Pages:
Jump to: