Spoetnik, the issue here unfortunately is related to the share bug in mmcfe-ng. I was able to retroactively fix all the transactions on the pool, but if you made any payouts out of the pool to your personal wallet prior to the fix, I have no easy way to grant you the difference.
This is why your transactions credited amount is much higher than what your personal out-of-pool wallet received, because the numbers were fixed after your payouts were marked as "Paid out to wallet" in the database.
You can see my submitted bug to the mmcfe-ng project here:
https://github.com/TheSerapher/php-mmcfe-ng/issues/611i never took 1 coin out.
any coins i received were entirely random and from the pool and also did not respect the pay out limit i had chose in options.
no offense but all i hear over and over is bullshit excuses why i've been raped with fee's and screwed out of what i earned from the first minute
before AND after you said your fixed things.
I'm out i won't be mining this anymore that's for sure..
its kinda funny how when i complained earlier that i was paying 50% fee's the fee's magically got normal too..
look at pic #1
I made 14.7 million coins and i was given automatically to my wallet 625,117 coins and charged a fee of 294,047 coins
WHAT THE FUCK MAN !? that is damn near 50% !
AND it was like that exactly before you guys said it was being fixed and what was fixed is i received a random 1 time deposit of 1 million coins est.
and after that i've made like 40,000 coins in a 24 hr period waiting for the rest and thinking im doin 1.5 per 24 hrs like everyone else such as the guy i mentioned..
Well congrats and thanks for nothing this is gay !
Sad if your telling me you can't make this right.. i KNOW how much you guys are taking in.. hit the trillion coin mark yet ?
my coins were lost by the pool (that charges me 50% fee's) and i'm told over and over no matter what its normal.
and once i pull a screenshot out of my hat.. i hear oh oh oh oh well uhhh yeah i guess your screwed sorry
fuck this
select sum(amount) from transactions where account_id=8 and type="Credit";
+--------------------+
| sum(amount) |
+--------------------+
| 15353398.818970772 |
+--------------------+
select sum(amount) from transactions where account_id=8 and type="Fee";
+-------------------+
| sum(amount) |
+-------------------+
| 307067.9763796694 |
+-------------------+
select sum(amount) from transactions where account_id=8 and type="Donation";
+-------------+
| sum(amount) |
+-------------+
| NULL |
+-------------+
15353398.818970772 * 2% Fees = 307067.9763796694--------------------------------------------
select sum(amount) from transactions where account_id=8 and type="Debit_AP"; (autopay at threshold out to wallet address)
+------------------+
| sum(amount) |
+------------------+
| 1276993.34379885 |
+------------------+
select sum(amount) from transactions where account_id=8 and type="Debit_MP"; (manual out to wallet address)
+-------------+
| sum(amount) |
+-------------+
| NULL |
+-------------+
select sum(amount*1000) from transactions where account_id=8 and type="Debit_AP" and id<6238; (this is the amount of autopays you did OUT of the pool before the fix was retroactively done, thus screwing yourself and what I was talking about in my post, you idiot.) Multiplied by 1,000 (which was the decimal place fix).
+------------------+
| sum(amount*1000) |
+------------------+
| 14759335.08554 |
+------------------+
Look familiar?
(total corrected) - (paid out already) (unaccounted for)
14759335.08554 - 1276993.34379885 =
13482341.74171115This is a side-effect of a
previously unknown bug to the mmcfe-ng frontend project itself. It was entirely and wholly out of my control. I combed through the code
myself, found the bug
myself, submit it to the project's issue tracker and applied a retroactive fix in < 2 hours since the pool went up. I provided an explanation of the adverse effects of the bug and what it would mean, of which you clearly could not comprehend.
From that point on, because of how manual the steps would be to fix and how small the timeframe of error was on the pools lifetime it was decided I was not going to waste my time calculating the losses of every person who rushed to setup an out of pool wallet and extract their coins within literal 2 hours of coin launch. Its unfortunate, yes, but unforeseen by all parties.
Trust me when I tell you that your whining / flailing / making a scene / acting like a toddler throughout the last few pages of this thread weighed very heavily towards me NOT spending my personal time making you happy for what was a result of your own doing, and inability to understand the consequences despite being told it repeatedly.
Wallet: 29vULP4VnTaD5JnUkME15xyaQjPPaXCdFV
Amount: 13482341.74171115
Txid: 01c7435f36d0ce0967700eef103d0c262ac9e98c85f77740b76a64ef3dddcd4d
To address your inane post quoted above:
"i never took 1 coin out."
yes you did, as seen in the transaction logs for payout to 29vULP4VnTaD5JnUkME15xyaQjPPaXCdFV every 1,000+ coins for hours."any coins i received were entirely random and from the pool and also did not respect the pay out limit i had chose in options."
see above: payouts happen at your clearly set 1,000 coin threshold, above or exact. Have you been on a pool before? If the next round put you from 938 -> 1013 coins, you'll get paid 1013."no offense but all i hear over and over is bullshit excuses why i've been raped with fee's and screwed out of what i earned from the first minute
before AND after you said your fixed things."
offense, but this is actually you ignoring and/or not comprehending the situation, explanation, and actions taken to rectify it. Complete with links. "raped with fees" really made me laugh though."I'm out i won't be mining this anymore that's for sure.."
Good. See below.Now that that's finally at rest, I'd like to let you know you are no longer welcome at my pool. Go find another or solo-mine. I don't tolerate children.
---------------
Pr0d1gy, you also sent an autopay prior to the fix, and are missing 5,056,790 coins.
Wallet: 245wswkjcxmAFjvYo1phFHVbiZCHG6w1ds
Amount: 5056790
Txid: 0d432e1aca628148536f079c58afcb75d86dcba6f2cc88be1b5a1fed301072c7
