Oh, god, I cannot stop laughing! And hey, at least I don't hide it, and let everyone know.... unlike the government! haha

We may be able to recover from this and keep our fingers crossed that there's no stuck payouts in the system. If anyone doesn't receive a payout, look for it in the blockchain, then contact me.

I've been working on getting a mac build but having so many problems.. Most VMware images won't work with my system (AMD). Found a 10.6.2 image that works, but deps won't build properly. Updated it to 10.6.8 manually, kernel panic. In the process of trying different kernels until I find one that works.

Unless someone's kind enough to give me root access to a mac server for a while? lol

Nothing fishy about it.. There's coins in the wallet, just not as much as the system thinks SHOULD be, so the liquid asset shows a negative. But yes, it's impossible for the wallet to have an actual negative balance.

Ugh, Tweek, I'd answer that but I've been dealing with so much crap today I don't even remember right now..

I'll tell you guys one thing, though. Dealing with this coin has been a pleasure and a pretty smooth experience. Some other coins, which I will not name, have serious problems and make a pool sysop's life a nightmare. Anyway, my point is that I've been busy so please forgive me for delaying the giveaway until tomorrow!

This has been a pretty slow week so the pot isn't that great, hopefully whatever the devs have in store for us will get the hashrates kicking again! I like to be able to offer up a fat prize, but I can't do that if we're averaging 10MH, so get your butts in here and mine! http://888.fedaykin.us

Also, stratum has been integrated into the main site, 888US.fedaykin.us should point at it too so you shouldn't have to change any miner configs. God, I'm tired. Good night everyone.

I'll definitely have a look at that.. I was actually looking earlier at the setup page on the MPOS Wiki at https://github.com/MPOS/php-mpos/wiki/Config-Setup#payouts

I noticed there's supposed to be a setting for that but is absent in the config file of MPOS, even the latest version which I pulled today for reference. That may be why it's necessary to comment those lines. I don't know if that's an oversight, or what. I need to speak with the devs about it but it's always a madhouse on IRC. We definitely need to bring that to their attention.

Here's a heads up though, if you have more problems with your payouts, and run validate_payouts.php and see missing payouts, verify them before you go paying them manually because I've had issues with one of my wallets not returning TXID's to MPOS but paying out anyway, thereby creating an extremely ugly situation which may ultimately ruin one of my pools. So keep an eye on failed payouts. If they stack up on you, god help you.

I just re-read my post, I hope that made sense to you.

I'm dealing with about a thousand issues right now but I'll do whatever I can to help you out.

I'm sorry I didn't see your post before. I've had that issue with some of my other pools for the same reason, right now my Tesla pool is running in the negative because of "immature" coins. As long as those coins that are setting the wallet back aren't already "locked for users" as in ready to pay out by the system, then it shouldn't hurt anything. It's a flaw in MPOS, well not really a flaw, MPOS is doing what it's supposed to, but some additional handling for coins that "mature" since they behave slightly differently would be helpful. Since you're seeing errors out of it, though, one possible reason could be that you at some point had set confirms below 30, then back up, that can throw it off. If it's in the negative value MORE than the amount of unconfirmed you have, then you have a problem and it's going to be throwing errors. Try making a new "account" under your coin daemon, and use "./coind move "" "newacct" 10" then back again.. where "" is your default account, I'm assuming you know this. Then run ./coind move "newacct" "" 10 and see if it evens out. I've had a couple of pools bug out on me a little bit and moving coins back and forth actually helped, your mileage may vary though. Sending coins to another address and back did not help the problem, but using the "move" feature did, and I cannot even begin to tell you why! If you're still having problems being in the negative, temporarily funnel your personal coins into the pool's wallet until you build up a fee buffer to negate it, but your pool's liquid assets will ALWAYS be missing whatever is in your unconfirmed, so keep that in mind! Example, you have 5000 unconfirmed, and 5000 in your liquid assets, your actual liquid assets is 10000! It doesn't matter how many confirmations you have it set to, it's going to do this until they "mature" because of the way MPOS handles it. I've been meaning to have a chat with them about this, and a few other things. I have one of my pools on the brink of death (not Coin - we're good!) because of misbehaving wallets not passing TXID's along and MPOS not picking up certain things, so I know, lol, I know...

Good luck!

Its possible that the transaction issues are a side effect of the network being small, and screwed up. I've been working a little bit on a backup pool, and the wallet WILL NOT sync. I've added every node I can find, still will not sync. I love birdcoin, very much so, but I'm afraid that there may be more deep seated problems than my screwed up pool.

I'm kinda freakin out here. Anyway, here's a couple of things that I've noticed about the wallet in the last little bit. I was transferring my personal stash back into the pool to make up for some of the double paid stuff, and had to break it into several transactions.. 100k - Transaction too big, 90k - went through, 500k - transaction too big, 500k - went through. I even had one instance where it gave me a message that it was too big, and went through anyway. There's some issues with this wallet. Going back into the payout logs, alot that were flagged as missing were from way back when I opened the pool, I just never noticed because no flags went up until today. This is a reason I didn't enable "sendmany" for my pool, to avoid issues like this. I'm going to keep it running a couple more days to see if it craps out or not. If it keeps running without issues, I pretty much owe the pool everything I can possibly mine for the next few weeks and I'm mining and donating 100% for the wallet, but we need the developer to come in and have a serious look at the wallet's code, if that's possible. I have a feeling this is just a copy/paste job and the issues are carried over from whatever this coin was forked from.

I understand if anyone's pissed. I am too, extremely so. The best I can say is be patient, lets see if this thing irons itself out or not. If you feel you're missing a payment, check http://explorer2.sancrypto.info/chain/birdcoin/ and see if you can find it. If not, please contact me and I'll see what I can do!

Thanks everyone, you guys have been awesome.

Well, our liquid assets are in the hole. You have so much in the wallet, minus what's "locked for users", the difference is the liquid assets. In this case, in the hole. I sent all my personal stash to counter some of it, Still around -24m

How the system got out of whack, I'll probably never know. The problem is, I'm not even sure if the payout discrepancies subtracted what they were supposed to from the "locked" balance. I've seen transactions get stuck before and pay them out manually, then run the validation script on them again and they show the TXID. In this case there's way too many, and the ones I fixed still didn't show up with a TXID, and a lot got double paid. At this point, it's so far out of whack that there's no hope of getting it fixed by hand, either we can let the system even itself out (by accumulating fees, donations, what I mine, etc) and pray there's no more errors and legitimately stuck payouts, or start fresh on a new pool, let people withdraw what they can, and let me slowly pay back whatever we are missing. This is the worst mess I've ever seen.

Lots of double payouts. I still don't know why the wallet didn't give TXID to those tons of payouts, but this is a huge mess. If anyone is kind enough to return extra that they got paid out, or to chip in to help fix the pool's balance, the address is KwgpnEnaNTh53CUvdirEeqmgiyPwDqJoBd (weird that some addresses start with K, some with L)

I'm very frustrated right now, this isn't what I had in mind for this pool.

That's good to hear, but on my pool, things are WAY screwed up.

It started with crons getting stuck, so I ran my payout validation script.. Thousands of missing payouts. I ran a LOT of them manually, come to find out after digging through the block explorer, even though my validator flagged them as missing, some of these payouts did go through, and they're weeks old. Well, ok, so what's going on? Why didn't it assign a TXID to these payments? So, I run some more through, run the validate a few more times, still flagged as missing. And there's a TON of payments in the payout ledger that are all identical, so even if they're missing, running them by hand isn't going to matter. Now the wallet is saying we're near 30m in the hole. This is a real mess and there's many, many millions of BRD on the line. The wallet not assigning TXID's really screwed up things in the database. At this point, I really have no way of telling if anyone did or didn't get their payment, other than checking on a case-by-case basis. My thoughts are to stop the pool, start up a new one and move everyone to that one, since all our unconfirmed blocks are going to take forever to confirm if I just flat shut the pool down. I admittedly was not prepared for this type of scenario so I don't know what the best course of action would be.

If anyone gets shorted or screwed over, I deeply apologize. I guess for now, keep mining in the pool, I adjusted some things and hopefully the discrepancies in the database won't prevent everyone from withdrawing their coins... I'm going to make a backup pool and later on we'll see about getting everyone moved to that, keeping the old one open for people to w/d their coins. I'm deeply sorry about all this.

Ok, things are very screwed up. I'm going to set up a fresh pool, I need everyone to withdraw their coins from the pool, and I'll have to manually fix whatever doesn't get sent. Did the blockchain fork or something? I've never personally experienced that so I wouldn't know.

Everyone will have to stop mining for the moment and give everything time to confirm, just withdraw whatever you can. Once that's done, I'll have a look at what's left over, run validation on it and see where we're at.

I'm very sorry.




Keep an eye on the thread for the new pool and other news.

Oh my god. Something has gone very very wrong.

Thousands of payouts are reflected in the pool's DB as credited, yet there's no TXID and my validation script is saying they're missing. I don't know what's up with that, but after manually crediting like 25 million worth, the pool's wallet tracking is showing us hugely in the negative. There's THOUSANDS of transactions that seem to have not been credited but I really don't know if they have or not. Something is very, very wrong.


If I cannot get a handle on this I may have to shut it down, or just start a fresh pool.

Just had an alert from the pool. A ton of payouts got stuck. I'll fix them, just give me a little while.


Something has gone horribly wrong.

I think I'm going to have to shut down the pool.

Welp, I get home, and my sister's kids have destroyed my VM-on-a-stick.. My SD card USB stick thingie has been snapped off in the plug, and there's something sticky on my keyboard.

I AM LOSING MY MIND

Yes, and thanks

Hey guys, in case anyone's wondering, the payout cronjob got stuck, so I had to manually restart it this morning. I went back and manually checked over payouts, so everyone got paid.

Well, so much for "it just werks". I've been busting my butt trying to get a wallet built for Mac but for some reason cannot get past building the clang-3.3 dependency for boost. I've tried downloading precompiled binaries already and followed instructions on un-tarring them but to no avail. Doesn't mean I'm giving up, though.

edit: trying a more up to date VM. This means I have to start all over, though.. Takes a day to compile deps.

Mac wallet will be here eventually. I'm discovering it's a herculean effort just to configure a build environment on mac. Takes less than 5 minutes on linux.