Br0ken
I have noticed and confirmed an issue with the Litebar daemon. I have confirmed with another pool owner. Other Pool owners and other solo miners can confirm this if they wish by checking their immature transactions via listtransaction. This doesn't really affect the averager miner with a private wallet.
Litebard getbalance <--- this command shows the CONFIRMED wallet balance
Litebard getbalance "" <---- this command is meant to show CONFIRMED + UNCONFIRMED wallet balance, however for litebard it is only showing CONFIRMED wallet balance.
This is an issue for Pool owners as it means MPOS doesn't work as it should. Liquid Assets is a function we have in MPOS and it should never decrease (unless the pool owner runs a bonus or send money out of the server wallet) however not only is it decreasing its going into negative values and this in turn prevent miners from getting paid.
Please fix the Litebard getbalance "" code to include UNCONFIRMED payments
Thanks
Sta
JRWhite - can you confirm that you have been getting something similar? Do you get the same values for the two above commands? Did find a workaround by any chance? Or have you not noticed an issue on your end?
Hi Br0ken Any update on this pressing issue? Thanks Sta |
|
|
|
|
Br0ken
I have noticed and confirmed an issue with the Litebar daemon. I have confirmed with another pool owner. Other Pool owners and other solo miners can confirm this if they wish by checking their immature transactions via listtransaction. This doesn't really affect the averager miner with a private wallet.
Litebard getbalance <--- this command shows the CONFIRMED wallet balance
Litebard getbalance "" <---- this command is meant to show CONFIRMED + UNCONFIRMED wallet balance, however for litebard it is only showing CONFIRMED wallet balance.
This is an issue for Pool owners as it means MPOS doesn't work as it should. Liquid Assets is a function we have in MPOS and it should never decrease (unless the pool owner runs a bonus or send money out of the server wallet) however not only is it decreasing its going into negative values and this in turn prevent miners from getting paid.
Please fix the Litebard getbalance "" code to include UNCONFIRMED payments
Thanks
Sta
JRWhite - can you confirm that you have been getting something similar? Do you get the same values for the two above commands? Did find a workaround by any chance? Or have you not noticed an issue on your end?
|
|
|
|
http://ltb.lifeforce.infoNot only does our pool charge no fee, you will actually GET PAID to mine with us!
We noticed that the Block Finder Bonus usually only rewards the top hashers. We weren't happy about that. We want a bonus to reward EVERYONE!
And as such, we have decided to increased block rewards by 1%.
This offer starts now and has no end date.
Current Pool Stats (as of this post): Pool Hashrate: 30 MHs Blocks Found: 8 (last hour) Block Reward: 2.02 per block Payout System: Prop Fee: 0%
|
|
|
|
Hi All, I'm pleased to announce our new Litebar webpool @ http://ltb.lifeforce.info - It is currently 0% fee for the forseeable future however the first 20 miners will have 0% fee for life. *** Block Bonus: 50% Extra Block Reward for the first 10 Block Finders - That's one whole extra litebar per block: Get 3 instead of 2! *** Feel free to join us on IRC at #lifeforce on chat.freenode.net. Sta. Just an update - At this time of writing this, we are already on block 14, the extra 10 LTBs Bonus been paid out, the pool hashrate is on around 30Mh/s and we're getting around 5 Blocks per hour. Where as this block bonus was over quickly, I will be giving away more free LTBs in the coming days to try and boost the MH/s as much as possible! If you're interested please mine with us or at the very least add us as your backup. |
|
|
|
Hi All, I'm pleased to announce our new Litebar webpool @ http://ltb.lifeforce.info - It is currently 0% fee for the forseeable future however the first 20 miners will have 0% fee for life. *** 50% Extra Block Bonus for the first 10 Block Finders - That's an extra litebar per block: 3 instead of 2! *** Feel free to join us on IRC at #lifeforce on chat.freenode.net. Sta. I'll throw some hash your way and see if we can get you started. Good luck with the new pool! Thank you, Thrash! It looks like with your crazy amount of MH/s you might end up with most of the bonus!  |
|
|
|
Hi All, I'm pleased to announce our new Litebar webpool @ http://ltb.lifeforce.info - It is currently 0% fee for the forseeable future however the first 20 miners will have 0% fee for life. *** Block Bonus: 50% Extra Block Reward for the first 10 Block Finders - That's one whole extra litebar per block: Get 3 instead of 2! *** Feel free to join us on IRC at #lifeforce on chat.freenode.net. Sta. |
|
|
|
Q1) Can someone let me know how to get the Prefix and the Identifier for a new coin? (specifically litebar)
Added it to my guide..it is also here earlier in this thread. Thank you for that! This is what happens when I run it - I get all Succcesses at the top but then I get this repeatedly: 2014-02-25 19:31:06.817362 P2Pool: 0 shares in chain (0 verified/0 total) Peers: 0 (0 incoming) 2014-02-25 19:31:06.817451 Local: 0H/s in last 0.0 seconds Local dead on arrival:  Expected time to share: Any ideas? EDIT: Its works I think, I just pointed my miner at it. I'm getting a bunch of HW issues but I'll sort that out. When I tried starting a Litecoin p2pool earlier I wasnt getting the above messages that I am getting with Litebar. Not sure why. Right I have this kinda working, finally. I was getting a bunch of hardware issues until I put +16 after my username in my cgminer conf file. However I dont think this is the permanent solution. I think its a setting on the server that needs to be corrected to may be allocate the difficulty better. I think its one (or more) of the settings to do with ~/P2Pool/P2Pool/Network.py I will tweak them, however if anyone has any ideas on which ones I should be fiddling around with, please let me know. Muchos gracias amigos. UPDATE: This is it: New Litebar P2Pool: http://lifeforce.info:24323 - To add to your collection! Use as your main or as a back up - VPS Hosted - London Based - Fee: 0.5% Going to do some more tweaking first. |
|
|
|
Q1) Can someone let me know how to get the Prefix and the Identifier for a new coin? (specifically litebar)
Added it to my guide..it is also here earlier in this thread. Thank you for that! This is what happens when I run it - I get all Succcesses at the top but then I get this repeatedly: 2014-02-25 19:31:06.817362 P2Pool: 0 shares in chain (0 verified/0 total) Peers: 0 (0 incoming) 2014-02-25 19:31:06.817451 Local: 0H/s in last 0.0 seconds Local dead on arrival: Expected time to share: Any ideas? EDIT: Its works I think, I just pointed my miner at it. I'm getting a bunch of HW issues but I'll sort that out. When I tried starting a Litecoin p2pool earlier I wasnt getting the above messages that I am getting with Litebar. Not sure why. |
|
|
|
Q1) Can someone let me know how to get the Prefix and the Identifier for a new coin? (specifically litebar) Q2) I have done the settings (except for prefix and identifier) to the best of my ability with the aid of this thread for Litebar network.py in both P2Pool locations. Can some bright spark actually post the correct settings for Litebar please. I have spent 12 hours trying figuring it out and could use any help. litebar=math.Object(
PARENT=networks.nets['litebar'],
SHARE_PERIOD=15,
CHAIN_LENGTH=24*60*60//10,
REAL_CHAIN_LENGTH=24*60*60//10,
TARGET_LOOKBEHIND=200,
SPREAD=10,
IDENTIFIER=''.decode('hex'),
PREFIX=''.decode('hex'),
P2P_PORT=19065,
MIN_TARGET=0,
MAX_TARGET=2**256//2**20 - 1,
PERSIST=true,
WORKER_PORT=19055,
BOOTSTRAP_ADDRS=''.split(' '),
ANNOUNCE_CHANNEL='',
VERSION_CHECK=lambda v: True,
),
litebar=math.Object(
P2P_PREFIX='fbc0b6db'.decode('hex'),
P2P_PORT=9065,
ADDRESS_VERSION=48,
RPC_PORT=9055,
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
'litebaraddress' in (yield bitcoind.rpc_help()) and
not (yield bitcoind.rpc_getinfo())['testnet']
)),
SUBSIDY_FUNC=lambda height: 2*100000000 >> (height + 1)//438000,
POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
BLOCK_PERIOD=180,
SYMBOL='LTB',
CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'litebar') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/litebar/') if platform.system() == 'Darwin' else os.path.expanduser('~/.litebar'), 'litebar.conf'),
BLOCK_EXPLORER_URL_PREFIX='',
ADDRESS_EXPLORER_URL_PREFIX='',
TX_EXPLORER_URL_PREFIX='',
SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
DUMB_SCRYPT_DIFF=2**16,
DUMB_SCRYPT_DIFF=0.03e8,
), I know some of these settings are ball park figures, and some of these setting might be completely wrong. Any help would be appreciated. Thanks |
|
|
|
|
Show Posts
