pool.burst-team.us payout confusion
-
@BurstMiner1 I'm not a coder - if you want a copy of the pool source code so you can definitively let us all know, I can send it to you.
Data below - note that from my observation of the last couple of blocks, the historic amount added to the payment appears to be the value at the time of the calculation - four blocks after the winning block, not at the time of the block.
| 331144 | 18412210141346961862 | 6097204355 |
| 331147 | 18412210141346961862 | 359859275 |
| 331148 | 18412210141346961862 | 378787450 |
| 331151 | 18412210141346961862 | 368309519 |
| 331179 | 18412210141346961862 | 295771001 |
| 331214 | 18412210141346961862 | 68196850 |
| 331215 | 18412210141346961862 | 63576230 |
| 331217 | 18412210141346961862 | 73401998 |
| 331223 | 18412210141346961862 | 394579565 |
| 331235 | 18412210141346961862 | 280477720 |
| 331242 | 18412210141346961862 | 481053186 |
| 331244 | 18412210141346961862 | 290190633 |
| 331253 | 18412210141346961862 | 328204304 |
| 331261 | 18412210141346961862 | 324042198 |
| 331270 | 18412210141346961862 | 154361410 |
| 331272 | 18412210141346961862 | 188285944 |
| 331288 | 18412210141346961862 | 383278732 |
| 331292 | 18412210141346961862 | 462750876 |
| 331302 | 18412210141346961862 | 420289961 |
| 331323 | 18412210141346961862 | 403291305 |
| 331324 | 18412210141346961862 | 393186401 |
| 331341 | 18412210141346961862 | 1573288116 |
| 331344 | 18412210141346961862 | 1580526093 |
| 331370 | 18412210141346961862 | 2035563068 |
| 331374 | 18412210141346961862 | 1964674823 |
| 331383 | 18412210141346961862 | 1978366329 |
| 331395 | 18412210141346961862 | 683327721 |
| 331397 | 18412210141346961862 | 201426716 |
| 331399 | 18412210141346961862 | 235212068 |
| 331403 | 18412210141346961862 | 260380017 |
| 331422 | 18412210141346961862 | 187525535 |
| 331452 | 18412210141346961862 | 1281779246 |
| 331461 | 18412210141346961862 | 1505618400 |
| 331476 | 18412210141346961862 | 1184693975 |
| 331482 | 18412210141346961862 | 1083226521 |
+---------+----------------------+--------------+
3564 rows in set (0.92 sec)
-
@haitch Can you observe whether block 331148 calculated historical shares 4 blocks afterwards or at the time of completion?
-
@BurstMiner1 No, I can only observe them at the time of calculation based on what I would have been paid based on the historic share at time of calculation vs time of winning the block.
-
@haitch Well I've done the calculations, however due to the story changing in this circus time after time I can't really use it as evidence. That being said, the results I have are still out. Sorry if you are taking this personally, but I find it amusing that BURST literally has no accountability and thus transparency. How can I ever work it out? I don't think it's ever going to be possible.
Even if I was to prove my point who is going to do anything about it? Where would I take the issue? I suppose no one really knows. Funny that.
-
@BurstMiner1 @Catbref wrote the pool - I really don't know how it pays out, I only know what I have been able to see for my self.
On an earlier block i had, the deferred reward increased by my earnings on the current block + historic shares on the current block when the calculation was done.
I'm not taking it personally, but these pools have been in place for years - and if the pool operators were stealing from the clients, someone would have noticed by now. I personally earn nothing directly from the pools - all the fees go to the BurstTeam asset. In actuality, when the pools mine orphan blocks, the coin that recompenses them comes out of my own personal wallet - I'm losing money to keep the pools honest. This is not a lack of transparency - it's the person that can provide the transparency and answer your questions just doesn't seem to be part of the community anymore.
-
@haitch I don't want any arguments but it shouldn't be a case of "someone" is missing so no one knows what's going on. If you can't see exactly what's happening in your own pools' accountability then I obviously have a twisted idea of what transparency really is. I look forward to @catbref returning, if it ever happens.
-
@BurstMiner1 said in pool.burst-team.us payout confusion:
@haitch Well I've done the calculations, however due to the story changing in this circus time after time I can't really use it as evidence. That being said, the results I have are still out. Sorry if you are taking this personally, but I find it amusing that BURST literally has no accountability and thus transparency. How can I ever work it out? I don't think it's ever going to be possible.
Even if I was to prove my point who is going to do anything about it? Where would I take the issue? I suppose no one really knows. Funny that.
With a pool you have to trust the owner/operator. When people open a new pool, I'm surprised by the miners that just flock over to try the new "restaurant" in town to see what's on the menu. The owner.operator rarely, if ever mentions where the block transaction fees go or what the big miner "skew" is. They just clone an existing pool, possibly change the code for the 60/40 split and the big miner skew, open doors for business.
To eliminate some of these unknowns, you can always go solo. You will definitely see your wallet balance increase by exactly the block reward and the total transaction fees for the block when you forge a block.
Remember that in the long run, pool or solo, regardless of the size of your mining farm, you will get your share of the block reward and fees proportional to your farm size divided by the average net difficulty over the time you are mining. The only difference is that solo, you don't pay a pool fee and you definitely get the block transaction fees.
-
@BurstMiner1 okay - all pool owners that cant exactly explain how your pool pays out - please shut it down.
The pools payouts have been reviewed repeatedly, and have found to be honest. If you don't believe the pools - go solo, theoretically you'll earn (mining pool fee percentage) more - you might just go days/weeks/months without a payment.
I cannot verify how the pool pays - therefore we need to shutdown ? I can't answer some specific questions about the pool. If that's not satisfactory to you, vote with your feet and mine solo or elsewhere.
-
@haitch send me a copy of the source i will see if i can figure it out.
-
@haitch You are jumping to conclusions. I never said that pools should shut down. That's something you have come up with. I did however say that I find it amusing, and still do.
@rds Thanks for the input. The reason I am chasing my suspicions up is that it has been a concern of mine before jumping in with a bunch more drives. Perhaps you are right, I should go solo once this happens, or just join ninja, something like that would probably work I will fit the criteria without issue.
-
@BurstMiner1 i believe the payouts to be fair, they might not be perfect, they maybe perfect, but one thing is for sure they are not that far off from perfect in my experience.
-
-
@iKnow0 I appreciate your thoughts and help with my concerns.
-
@BurstMiner1 No, you never explicitly said that the pools should shutdown, but have repeatedly called me out for the "lack of transparency" on the pools. I've repeatedly told you that others have evaluated the pool and found it to be fair. And that I operate the pools, don't program them. I don't have the capability to change the code that others have found to be fair - so, basically, I fundamentally fail to understand your obsession with the fairness when your perceived loss is 16 Burst - 0.016 cents. This much effort for less than 2 one hundredths of a penny cents ?
You've made this massive thread over two one hundreths of a penny, while I've paid out over $1,000 in Burst to keep the pools honest.
Why am I dealing with this ?
-
@haitch I'm a strong believer in the saying "Believe none of what you hear, and half of what you see". The perceived loss is a matter of perspective. If my suspicions are correct and has been going on since I started mining then no, it's not penny cents. It's a matter ~5% of my total ROI. But whatever, you can twist it however you want. I said I don't want any arguments but you persist. I must reiterate, I no longer want to discuss this. The state accountability and transparency make it a fools errand. So there you go. End of story. Cheers.
-
@BurstMiner1 The source is available - anyone can check for themselves. But if the pool forks again, for transparency - you'll pay the difference this time instead of expecting me to do it?
-
been looking at the source for about an hour now, think i have it tracked down
Block.cpp line 188 starts
uint64_t transaction_fees = current_shares.count() * PAYMENT_SEND_FEE; reward_to_share -= transaction_fees; std::cout << "[rewards] pool fee: " << pool_fee << ", max transaction fees: " << transaction_fees << ", reward leftover: " << reward_to_share << std::endl;in context after pool fee (plus a transaction fee for it) is subtracted (prior to this snippet) then a transaction fee is subtracted for every miner that has a share, before the miner rewards are calculated.
roughly running the math 5 percent of block reward is about 100 miner transaction fees. i doesn't look like the info is stored with the account (ie transaction fee taken from every block one), this make since assuming larger rewards and less division (so rewards sent more often) at the time it was coded.
there maybe more to this but this is the best explanation i got right now. it is late and i'm going to bed (hoping i didn't just add fuel to these flames).
-
@damncourier First of all thanks for looking at the code ;D
ok so basically the pool takes 5% of the total block reward (block reward + fees collected in the block) plus it takes 1 burst per each miner with a reward in the current block, then do the division 60/40 and pay the miners to the threshold balance...
so @haitch can you please query the db to know how many addresses were paid by the pool in the block 331119 ?
-
@gpedro There were 333 miners rewarded:
mysql> select count() from Rewards where blockID = 331119;
+----------+
| count() |
+----------+
| 333 |
+----------+
1 row in set (0.00 sec)
-
@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.

