pool.burst-team.us payout confusion
-
@gpedro sorry for the late night posting which wasn't very clear.
it takes the pool fee percent (plus transaction fee (1 burst)) from the config
then from remainder takes a transaction fee for every item in the array current_shares. it looks like that is all miners that submitted on the block (haven't dug in to find out details of what is stored in array)
then the from that remainder it calculates reward payments according to bot current shares and historical shares
i mention 5% because the previous posts indicating the amount of discrepancy and my napkin maths made me think this might be it. again there is probably more to what is going on but seemed like a place to start. will do some more digging at some point.
-
so @BurstMiner1 has the following shares in the block 331119 (retrieve from the screenshot):
current block: 0.0017% or 0.000017
historical shares: 0.222% or 0.00222-
2146+76 = 2222 (total payment received by pool for the block 331119)
-
2222 *.98 = 2177.56 (less the pool fee of 2%)
-
2177.56 - 334 = 1843.56 (1 burst for the fee of pool transaction + 333 burst for fees of transfers for miners)
-
1843.56 * .6 = 1106.136 (total pool current share percentage)
- 1843.56 * .4 = 737.424 (total pool historic percentage)
- 737.424 * 0.002220 = 1.63708128 (your share of the total current share percentage)
- 1106.136 * 0.000017 = 0.018804312 (your share of the total historic share percentage)
so @BurstMiner1 should have got 0.018804312 + 1.63708128 = 1.65588559 burst (or 165588559 NQT) around block 331123 in his threshold balance...
@haitch sorry to bother you again but can you check this querys?
-
blockID = "331120" and accountID = "18412210141346961862" (just to check)
-
blockID = "331121" and accountID = "18412210141346961862" (just to check)
-
blockID = "331122" and accountID = "18412210141346961862" (just to check)
-
blockID = "331123" and accountID = "18412210141346961862" (if i am correct the payment for block 331119 of him will appear in this block with the this query)
-
blockID = "331124" and accountID = "18412210141346961862" (just to make sure it is not in block 5 ;D)
ATTENTION: this calcs are for the worst case in this block because we are accounting that the pool keep 1 burst per each different account being paid and supposetly from the code only fees from current block winnings are accounted and this number should be smaller so this means that if this number is smaller the payout for miners will be a little higher
-
-
@damncourier i was doing some math but i took into consideration your last reply in my math ;P
Is just 1 more burst relative of what i was saying right?
just to make sure i understood right...@iKnow0 your math was wrong because you were utilizing his burst winnings at that block as a percentage LOL i took the same mystake inumerous times and i was already hitting my head in the wall trying to understand why so big discrepancy then i checked the printscreen HAHAHHAA
-
@gpedro They all return no records. Even though the calc is done on a lter block, it's recorded for the Block it's won on.
-
@haitch Ok then there is something we are still missing from the code... @damncourier if you find out anything more let us know please
-
@gpedro did you mix up the current and historical in your calculations?
current block: 0.0017% or 0.000017
historical shares: 0.222% or 0.002221106.136 * 0.00222 = 2.45562192 (your share of the total current share percentage)
737.424 * 0.000017 = 0.01253620 (your share of the total historic share percentage)should it be ?
1106.136 * 0.000017 = 0.018804312
737.424 * 0.002220 = 1.637081280.018804312 + 1.63708128 = 1.65588559
-
@iKnow0 OH Shout?!?!!?!? Thanks... I made the change! You are right i mix things up ;P
@haitch So with this correction all looks good there is no more variables in play... so the pool charge 2% + 1 burst per each different account in the current block shares list...Let me remember that my calcs were for all the shares paid in the block so if this would be true @BurstMiner1 should received 1.65588559 and he received 1.93734903 so it only charges for the current block shares and not from the historical ones as @damncourier stated. 333 is the amount of accounts with shares in that block (current + historical)...
-
@gpedro should it be .00017 not .000017?
-
@iKnow0 no... 0.0017% is 0.000017
-
@iKnow0 the math is done and now thanks to you is correct the only data we don't know exactly for the math be 100% correct is how many accounts submitted a valid deadline to the pool in that block, this data could be collected if the printscreen @BurstMiner1 was from the complete page because on top of the pool page says the amount of miners that submitted a deadline... If we had this value we would replace it for the 333 and add 1 burst to it like i did in my math ;D
-
@gpedro for block 331119 there were 244 nonces submitted by a total of 151 miners.
-
@haitch ok so @BurstMiner1 has the following shares in the block 331119 (retrieve from the screenshot):
current block: 0.0017% or 0.000017
historical shares: 0.222% or 0.00222-
2146+76 = 2222 (total payment received by pool for the block 331119)
-
2222 *.98 = 2177.56 (less the pool fee of 2%)
-
2177.56 - 152 = 2025.56 (1 burst for the fee of pool transaction + 151 burst for fees of transfers for miners)
-
2025.56 * .6 = 1215.336 (total pool current share percentage)
-
2025.56 * .4 = 810.224 (total pool historic percentage)
-
810.224* 0.002220 = 1.79869728 (your share of the total historical share percentage)
-
1215.336 * 0.000017 = 0.020660712 (your share of the total current share percentage)
so @BurstMiner1 should have got 0.02066071 + 1.79869728 = 1.81935799 burst (or 181935799 NQT)...
He received 1.93734903 so probably some difference in some round decimal somewhere ;DIf i do the same math but only for 151 fees collected before doing the distribution (meaning the pool fee didn't collected extra fee like the remaining payments) the result is 1.82025619 so it collects something even less than 1 burst per address with a submitted nonce in that block ... I'm out of clues right now xD
-
-
@gpedro not all miners will be paid as most goes to deferred payment until the payment threshold is reached.
if you do it with 20 miners getting payed, which seems reasonable its not too far off. See Below.

-
@gpedro I believe the historic value at time of calculation is used, so it may have changed between screenshot of block won, and calc done three blocks later.
-
@iKnow0 As far as i understand it has to be 1 burst from each account that submitted a deadline because all this payments are done to the threshold...
I find more likely that his shares have changed between his screenshot and the end of the block in the case of the current block or his historical shares changed between the screenshot and the calculations 3 blocks later...
-
@gpedro unfortunately the call to "current_shares.count" which determines how much fee is going to be deducted, is in a library file I don't have the source for - so no idea what it's returning.
-
@haitch what language is the whole thing? C/C++?
-
This post is deleted!
-
-
@gpedro I honestly not sure - didn't look like C++ to me, but I'll defer to those that know the languages.



