This is old news, but some threads were updated, some like this one weren't. In case some people are only subscribed to this thread, the SEC got Jon:

https://www.sec.gov/litigation/complaints/2018/comp-pr2018-23.pdf

I just noticed that while the scam accusation thread was updated, this main thread wasn't. In case anyone is not subscribed to the other thread(s), the SEC got Jon:
https://www.sec.gov/litigation/complaints/2018/comp-pr2018-23.pdf

Do you have skype or other method of contact? I got my skype on my profile, preferably get in touch there. I'll see if dev can pull the backup and check which entries got changed and by how much.

@deisik
Also, no, posts getting deleted would not have caused anyone to go into the negatives.

Hello,

I'm not sure if I've announced it before, but created entries were quickly found to just be the forum dropping requests and was fixed by increasing delay between requests. But the attempts so far to get entries fixed have gone wrong.

dev has run a fix for balance. Basically for created entries in november, script kept amount of new posts and kept adding to it in further entries fixed (more or less), resulting in some users getting 0.1 BTC or more overpayment.

Note that negative balance include pending withdrawal (cancelling a withdrawal should increase balance), so balance would not go down further if withdrawals were processed.

I've looked at results of fix and there seems to be a few problems. Notably some days should have posts credited that weren't, but it almost looks right. However some user who should not have received a negative balance (because that user was never credited at all or had signature). But dev has time since college exams are over and we'll keep working on a fix tomorrow. Entries look almost fine, we'll make sure a few new posts get added to credits, and we'll run a script to calculate if the total amount of every credit for accounts, minus withdrawals, indeed match their balance.

We have not yet given out bonus payment for delays. Except for a few users who received very large amount from the bad script, it's likely bonus will cover, and then some, any overpay you might already have withdrawn.

I'm sorry for the trouble. I've seen some great projects done by this dev, but dev is still studying and I believe it is the first time this dev ever messed with batch updating database this large or complex with randomly spread errors throughout (with entries depending on other entries and affecting multiple fields to be updated) and that there's a bit of "hard time wrapping brain around it." I suppose it can be a bit hard to plan ahead all the steps needed for things to work out properly at the end and script for it if you're not used to do that. At this point it might have been best to manually correct entries instead.

So this is how first day of work on fixes went. I don't think it should take more than 1 or 2 more days to get it fixed. If the dev can't manage, I'm sure wao can find the time to fix himself, because at this point he just wants to pay users.

Current plan for today is:
- Revert DB to yesterday's backup
- Possibly pay out withdrawals anyway, even if some users are overpaid, depending if wao is available right after dev can revert DB
- Try to get fix to run properly and figure out how much balance users should have, hopefully fixed by end of the day
- Figure out bonus for delays to be paid that will probably be credited in following days, hopefully everything being done in time for users to withdraw for the 25th's payment

Regards,
Namworld

So far it doesn't seem there is any bug causing this. Dev will have to test but it might just be some trouble loading the forum to actually check signature and post count (perhaps new filters from bitcointalk) or other similar problem. It appears to be very intermittent.

Problem is dev had busy schedule. Some new features are needed. I'll make sure failed entries can be retried automatically if they failed at cron (you will receive the same rate as everyone else as it is calculated for the cron before entries are processed. A reprocessed entry will use that same rate.). Other than this issue to figure out, adding that fix should be good enough for now. Dev should be able to add it in the next few days. Other than that nothing seems wrong with tracker so I'll ask wao to go ahead and make payments.

Thank you for your patience.

Those -1 post entries are normal default entries to avoid mistakes. Since errors from when tracker campaign started, dev added this so at the start of crediting, it starts by making such a created entry before doing anything else for everyone. That way if credits are not processed for only some people it becomes very obvious to user (which might not be obvious to us otherwise, especially if it's only a few people at end of the queue, since without such a default entry, there would just be a few entries missing for that day and unless we counted manually entries for each day, we wouldn't notice a few missing one.) These entries make it easy to spot and easier to correct and reprocess failed credits

Dev added a lot of tracking/debug features since last issues and feature since the last problems. Tracker starting to become a really polished product. I got in touch with dev and issue will be looked into.

I've added two more guidelines under conditions regarding language and avatars.

I've approved monbux as he is a trusted forum user. Other high ranking applicants will be reviewed. Due to high demand, we'll give priority to high rank/high trust feedback members.

I'm not sure what could be causing this. I tried from a test account to input Mediator's address and it worked for me. I'll ask dev about it.

Yep. Withdrawals should have been processed for a while.

Certainly not yahoo's fault. There was simply no method to ban users other than manually updating database to remove users (and then if registrations were to be reopened, they would have been able to sign up again. Only warnings were going out.

I'm happy to report however that we can now ban users, as well as whitelist certain forum accounts. We'll reopen registration in a private fashion. Due to demand, it will be restricted to Hero/Legendary members. We'll continue adding features and hopefully open publicly eventually. As for bans, Yahoo already warned some users and bans will start soon. They've had ample time to clean up their act.

If you have any issues with manager or the campaign, feel free to contact me on Skype. I haven't been active on forum for more than a year and don't check in that often. However I tend to reply to Skype requests within 1-2 days.

The problem with this is if we open publicly and have such instant payment, you know some people would make accounts up to minimum requirements, posting bad quality posts, then bot spamming hundreds of posts with randomly generated after joining campaign, right before a CRON, to then immediately withdraw.

I can ask dev about such a button.

I'll ask owner if he can make payments tomorrow instead of Sunday. Should leave time for everyone to put a withdrawal in.

Because dev was moving on the 1st. But it was done quickly once I got hold. Will still be looking into why some users didn't get credited on certain days, but from now on, before any credits even gets paid, cron will generate an entry for every users with status "Created" before it even start processing them and giving a final status. That way, if it crash before all entries are created, well no one was paid for that day and it will be very obvious. If it only crashes further down the road, then it will be easy for users/us to spot the missed days by the "Created" entries. This should make all daily payments more accountable for if we ever encounter other issues down the road.

I started running the manual cron. Seems it was deployed fine. I accidentally put the first crediting on the 19th august instead of july. I was talking about rate prior to the time of writing. That's a pretty big dip. I'll run crons at 550 for now. I will have to ask owners about paying extra. Considering at most it would be about 20% more on a few hundred dollars, I don't think that would be a problem to pay some extra but I still have to ask. If prices drop further before payments are out, I can personally guarantee that would be compensated too.

Well yahoo received access to start working.

As for me, I tried the manual cron on dev server. The cron actually process, but I can't seem to make settings work (exchange rate, timestamp, etc.) There's no UI yet for that part, it's console command. I'm not sure if I'm doing something wrong or if those settings aren't implemented yet. So bad news, more delays if you needed some funds soon. Good news is more days with better exchange rate.

Dev was moving for the 1st but should have some time. I'll try to get in touch and see if I can get this working or if dev can complete UI quickly for me.

It is indeed yahoo. No I'm not really being replaced per se, but I'm not paid to review users/quality. We had been looking for someone for this work. Yahoo will be reviewing accounts trust ratings and post quality for any changes/bad behavior.

I will be gone tomorrow. I asked owner to delay payments since probably no one has balance. Looks like I'll be able to do missed crons on Monday and owner will probably be able to pay Monday or Tuesday. Again, really sorry for the delays.

There will be no new openings for the time being. If there is, post count per user would have to be limited. Monday a new campaign manager should be able to start working and review post quality.So there might be a FEW openings later.

Sorry, been having a bad week. I'm back.

I had a message from dev they were looking into occasional missing payment for some, intermittently. So hopefully that can be fixed soon.

I'm trying to get a hold of my dev. Seem some new features were pushed live, but it disabled the cron option. As usual, you will be compensated for delays. I will ask for creditings at lowest rate over that period. I'll wait to re-enable it to make sure all new posts are credited in a manual cron at lower rate than today's rate.

Regards

Time shows local time I believe. So It's likely everyone having an issue is for the same day. Normally it's set to log failed crediting due to unexpected data/forum not loading/etc. So server might just have crashed in the middle of run or there's a bug in one of the logging portion.

Dev has been sick, but it's been some days already so hopefully better soon. So I hope that can be checked soon.

As for opening to lower members, as it says in the OP, we probably got enough participants for months to come. It's likely not going to open for any rank at all. If something changes, it will be in the OP.

There's no posting/activity requirement. We might have one after we complete new features/get out of beta.

As for deleted posts, I do not believe we'll be able to compensate for that. I understand it might not always be because of spam/poor post quality, but we cannot check constantly/know about this.

It's caused by server crashing. Missed days are caused by server being down at time of crediting. Those days will be fixed afterward.