[ANN] LiteBar (LTB) - Reborn

[jminer85]

can someone post a copy of there working solo conf I don't know what I am doing wrong. this is not my first time solo mining a coin but I am having some trouble this time.

here is mine:

addnode=mineblocks.no-ip.org:9065
addnode=65.102.140.115
rpcuser=user
rpcpassword=pass
rpcallowip=192.168.1.2  
rpcport=9051                      
daemon=1
server=1
gen=0

but also, I am using CGminer. I never had success using BFGMiner for solo.

Either way, you need the "rpcallowip=" in the .conf so the wallet will allow your miner to connect to it. If the wallet is on a different computer than the miner, then the ip you input into CGminer/BFGminer needs to be that computers ip address.

ok I have tried cgminer with no luck cgminer does not even see the wallet. I have the ip right its on the same rig. what is the name of your conf file litebar.conf right. it seems that the wallet is not going  in to server mode or something

yes litebar.conf

If the software saw the wallet's IP address you WOULD be solo mining right now. Something isn't right, either the port or ip and port. I can't think of another reason why it wouldn't work. i think I'm stumped on this one..

I was going to say that you need the -server flag but I checked my shortcut and I apparently didn't put it in and it's still solo mining. So maybe it's not needed but you could try that. What I do is use a shortcut to start my wallets because I have all the blockchains on NAT but run the clients on my local computer.

So in the properties of the shortcut you would see in my case: Target:      "C:\Program Files (x86)\Litebar\litebar-qt.exe" -datadir=S:\Litebar

try adding -server where i have put -datadir=S:\litebar on your shortcut or in the cmd prompt when you go to start the wallet. That should put it into server mode or not...like i said it seems I didn't have to do this for it to work for me. I always thought you had to put it in the .conf and put the flag for it but I dunno. Good luck.

This might get me to unbox the widow and try to solo mine with it. I really should put it up on ebay...I've been procrastinating.

yes so I gave up. cgminer would see the wallet so would bgfminer it would show when new blocks were found and diff changes. I resynced the wallet and nothing I added -server nothing I am lost on this one so I moved on. and its not just a widow  its a thunder too. i don't know what i did wrong.

[jminer85]

maybe my luck was so bad that at 45-50mhs i still didn't hit a block in 48hrs. who knows

[userpike]

maybe my luck was so bad that at 45-50mhs i still didn't hit a block in 48hrs. who knows

no you should have hit a few i would think...I only have about 72Mh on it now and I'm getting one about every 10 minutes or so. diff is the highest I've seen it so far since the relaunch right now.

sucks you couldn't get it going. I think someone has a pool now but I don't remember where the post is.. you might be able to hop on with them.

[jminer85]

ya there was a mineblocks pool but no matter what coin I mine there they get massive accepts then after 5 min they get rejected. man I sound like a noobie. I don't have problems with other scrypt pools

[mamaspaliLa]

LiteBar POOL:
http://www.coinspool.ru/ltb/public
welcome! 2% fees

[jminer85]

LiteBar POOL:
http://www.coinspool.ru/ltb/public
welcome! 2% fees

thank you a working pool now I can get some litebars. the pool is working fast but it seems to adjust to diff slow its taking my titan forever to spool up

[mamaspaliLa]

one moments

-----
Now Diff up to: 8-32784 Happy mining

[jminer85]

one moments

-----
Now Diff up to: 8-32784 Happy mining

thanks awesome the pool is working great thanks again

[Spidersbox]

WoW !

Net Hashrate 1,274.65 MH/s

Difficulty 23.88808441

Keep an eye on the pool block count -vs- the block explorer: let's catch any chain forks early.

Thanks
(and good luck mining  )

[mamaspaliLa]

E-mail confirmation not work yet. I fix this tomorrow

[mamaspaliLa]

WoW !

Net Hashrate 1,274.65 MH/s

Difficulty 23.88808441

Keep an eye on the pool block count -vs- the block explorer: let's catch any chain forks early.

Thanks
(and good luck mining  )

Add my pool in 1st pots. Thx

[theboccet]

hashrate exploded!!! I'm happy to think that I mined it when it was forgotten 
If this will continue,everyone will be rewarded

[jminer85]

so I don't understand how forks happen or what causes them can someone inform me. or a link to a good read on it.

[jminer85]

now that I have some coins I through 50k dots on the vote. its not much but its what I mined while I couldn't mine litebar

[jminer85]

one moments

-----
Now Diff up to: 8-32784 Happy mining

how many confirms before litebar gets listed as confirmed on your pool. some blocks are 6hrs old and still not confirmed?   

[Spidersbox]

This is from the bitbar thread:

Ok - simply put, a fork in the blockchain (the long ledger of transactions) can happen when two mining pools (as an example) find a bock at the same time.
Each block in the chain is made up of part of the previous block plus the batch of transactions.

for instance, the current block being 'mined' is #13550. this current block or records has three transactions in it. Let's say pool A and Pool B both find it to be a bonus block at the same time:

  Pool 'A' takes some information from that block (#13550) and adds the new transaction it just made - for finding a bonus block - smashes it together to make a new block - we will call that block #13551

  At the same time, Pool 'B' does the same thing - some stuff from block #13550 plus the transaction it just made for the block it found - smashes it together and puts it out as block #13551

these new blocks have to be verified (confirmed) several times. That's what the miners do, the crunch the numbers, make sure it all adds up - plus record checking stuff -  then passes it along.

So far, pool A being on the west coast doesn't know about transaction from pool B (maybe it's on the east coast?) and we now have two chains.

more in the next post

[Spidersbox]

part 2 from the bitbar thread:

This happens from time to time, but generally it gets fixed down the line in a block or two. the blocks in the chain get passed around like a 'hot - new mp3 of your favorite group" and eventually get handed to a mining rig to work on.

This is where I am still a little fuzzy on how the mining rigs find out about both transactions - but they do, and in most cases, the early bird get the worm, so to speak, and the looser becomes an orphan - if you have done any mining - you have undoubtedly ran into these.

On rare occasions, pool A sticks with it's fork, and pool B sticks with it's fork, and they just keep going until a transfer fails and all heck breaks loose.
-----------------------------------
The is another instance in which a blockchain becomes forked, and that's referred to as a 51% attack (although I don't think it always happens on purpose)

if pool A has 49% of the total hashing power, and pool B has 51%, pool B will, on average find more blocks - hence create more blocks, and pool A will simply fall behind.

I'm sure there are other circumstances that can cause a fork in the road, but once you have a punctured tire - who cares about the cause at the moment ?  that's for the dev team to work on so it doesn't happen again  Wink

now it's time for questions and corrections, feel free to add both!

[mamaspaliLa]

This is from the bitbar thread:

Ok - simply put, a fork in the blockchain (the long ledger of transactions) can happen when two mining pools (as an example) find a bock at the same time.
Each block in the chain is made up of part of the previous block plus the batch of transactions.

for instance, the current block being 'mined' is #13550. this current block or records has three transactions in it. Let's say pool A and Pool B both find it to be a bonus block at the same time:

  Pool 'A' takes some information from that block (#13550) and adds the new transaction it just made - for finding a bonus block - smashes it together to make a new block - we will call that block #13551

  At the same time, Pool 'B' does the same thing - some stuff from block #13550 plus the transaction it just made for the block it found - smashes it together and puts it out as block #13551

these new blocks have to be verified (confirmed) several times. That's what the miners do, the crunch the numbers, make sure it all adds up - plus record checking stuff -  then passes it along.

So far, pool A being on the west coast doesn't know about transaction from pool B (maybe it's on the east coast?) and we now have two chains.

more in the next post

need 120 confirmation

[jminer85]

part 2 from the bitbar thread:

This happens from time to time, but generally it gets fixed down the line in a block or two. the blocks in the chain get passed around like a 'hot - new mp3 of your favorite group" and eventually get handed to a mining rig to work on.

This is where I am still a little fuzzy on how the mining rigs find out about both transactions - but they do, and in most cases, the early bird get the worm, so to speak, and the looser becomes an orphan - if you have done any mining - you have undoubtedly ran into these.

On rare occasions, pool A sticks with it's fork, and pool B sticks with it's fork, and they just keep going until a transfer fails and all heck breaks loose.
-----------------------------------
The is another instance in which a blockchain becomes forked, and that's referred to as a 51% attack (although I don't think it always happens on purpose)

if pool A has 49% of the total hashing power, and pool B has 51%, pool B will, on average find more blocks - hence create more blocks, and pool A will simply fall behind.

I'm sure there are other circumstances that can cause a fork in the road, but once you have a punctured tire - who cares about the cause at the moment ?  that's for the dev team to work on so it doesn't happen again  Wink

now it's time for questions and corrections, feel free to add both!

thanks for the info

[jminer85]

This is from the bitbar thread:

Ok - simply put, a fork in the blockchain (the long ledger of transactions) can happen when two mining pools (as an example) find a bock at the same time.
Each block in the chain is made up of part of the previous block plus the batch of transactions.

for instance, the current block being 'mined' is #13550. this current block or records has three transactions in it. Let's say pool A and Pool B both find it to be a bonus block at the same time:

  Pool 'A' takes some information from that block (#13550) and adds the new transaction it just made - for finding a bonus block - smashes it together to make a new block - we will call that block #13551

  At the same time, Pool 'B' does the same thing - some stuff from block #13550 plus the transaction it just made for the block it found - smashes it together and puts it out as block #13551

these new blocks have to be verified (confirmed) several times. That's what the miners do, the crunch the numbers, make sure it all adds up - plus record checking stuff -  then passes it along.

So far, pool A being on the west coast doesn't know about transaction from pool B (maybe it's on the east coast?) and we now have two chains.

more in the next post

need 120 confirmation

pool is down last submitted share was 5:52an