How does Pool Mining work with Burst, and why do it at all?



  • Can someone explain to me how Pool mining in Burst works?
    Both technically as well as on the allocation side of things?

    Just to be clear: I am well aware what Pool Mining in general is. I come from ETH Mining and I am used to mine using mining pools. However I was a bit suprised when looking at my first 24h Mining results at http://burst.lexitoshi.uk

    Although I am mining with 32TB the pool only payed out: 35.82 BURST after 24 hours...
    I found this suprisingly low and I thought the entire pool must had been very unlucky.

    Few minutes later I was lucky enough to mine my first block and to my suprise I got 1914.50 BURST for my efforts, although the block according to the blockchain explorer was only worth 1853 BURST.

    Here my mining balance and the Block in Question:
    http://burstcoin.biz/address/2330812927884415672
    http://burstcoin.biz/block/12879097186606044125

    Here are the rules of the Pool:
    http://burst.lexitoshi.uk/howitwork.html

    I had expected something like a 50/50 share between rewards I get from mining a block myself and what I share with the Mining Pool, but thats obviously not what is happening...

    Can someone explain that to me?
    And how is this any different to what I would see if I did solo mine?



  • the differance betwen what you got and what the reward for that block would of been standard block reward + any transaction fees payed on transactions contained in that block so not every block pay's the same amount only a minimum amount. not sure what the split is on Lex pool current historic , however with a large payout like that chances are good that no one else on lex pool was even close to your submited deadline for that round so you took most all of the current split for your self, also you may have been fairly high in the historic "all rounds shares" list so could of also taken a larger chunk of that portion of the split as well. that all would be deferred to your account but the pool has a thresh hold that you have to meet befor paying out if you also happen to be close to that threshold with previous deferred payment's pending you can end up with a vary large single payout like this .. it has happend to me a few times. ... as for pool mining in Burst the way the pools work .. not all pools are = as some have settings set differently .. but there is a payout threshold you have to cross befor you receive a payment this is to cut down on transaction fees for most pools it is set at 300 but you will need to check with them to be sure. also you earn burst in two ways wile pool mining from the current block round being forged and from your historic average submited to the pool normaly averaged over the last 50 block's submited the # of blocks the average is based on can varry from pool to pool. most pools are a 60/40 split 60% payed to people that submited for the current round to be devided based on submited deadline times from each miner... 40% payed to the historic shares also based on submited deadline times but is an average of times submited over the last 50 blocks.



  • @TheTiny Each block has fees associated, which can vary widely, 13 Burst in your block, also you would have had other Burst due to you for your deadlines on other blocks that the pool won, as it builds up to 300Burst before a pool pays out. It is usually 60/40 split between current shares and historic shares. Your deadline for the block was 25 seconds which is a fast deadline, ie you would get the majority of the current share.

    If you solo mine you get all the block+fees, but you could be waiting days for a block.

    I think Lex's pool calculates the historic share slightly differently, might be best to ask him to explain the payment.



  • Re: [How does Pool Mining work with Burst](and why do it at all?)

    Ah... I think I just solved the mistory by myself.

    I thought the 35.82 BURST payment was from the lexicon pool, which would had implied that my pool earnings would had been quite empty before I hit the block, but that wasn't that case. The 38 BURST are from the previous pool I was mining on and therefor I do not know how much of I had on my lexicon pool collection before I hit the block.

    Is there anyway to know that?
    I am used to have quite precise mining statistics when mining ETH on ethermine.org
    How come none of the BURST mining pools seem to offer individual mining statistics?

    If you solo mine you get all the block+fees, but you could be waiting days for a block.

    What is an recomanded TB size to consider solo mining?
    And how to choose the right pool depending on your current TB stack?



  • @TheTiny 110+ TB for solo mining, due to rising difficulty maybe 150 and higher :D
    too bad you can't view mining stats, only how much you mine and how much you have in historical shares :/



  • Since I use practically the same pool code I will tell you why you got 1914 instead of a lesser amount. More than likely you won a block win after a block win. You dl was sooooo good and nobody was really close so you got a big chunk. It dont happen this way often so feel lucky!
    Now apparently you had around 200 burst pending and it got add to your block reward. Our pools pay is comparable to Ninja code. There are other variables that plays a role too like how long have you be mining this pool.



  • @HiDevin @tross Thank you!
    Makes sense.

    Is 600 BURST per month and TB a reasonable expectation?
    I am considering to increase my stack by 10-40 TB per Month if that assumption holds.



  • @TheTiny Here you have a calculator, do not notice what it puts per day since that is more a average, that one day you could take 300 and another day 1000
    http://burstcoin.biz/calculator



  • @Energy thank you. I know that calculator. What I do not know is if it's numbers are proofen by experience. After all I am considering to invest 370-1480€ per month into burst coin mining. ;)


Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.