getwork is working fine, and is properly sending to the miner, and I havent received any errors at this point,
also after checking the explorer one again I see POW blocks are coming in just fine....


So im not quite sure what error you may be having, but if you provide more details I would be happy to help any way I can It's possible the long time between POW blocks may be due to a fairly large drop in hashrate ,although I will watch closely in case it happens again.

On a side note, now that this issue has been cleared up, I will be working on the pool again, and will hopefully be up in the next couple days

I am at my day job, but will look into it the second I can...
<edit>
strangely the pools seem to still be running fine.... is there an error you are getting?
Blockmonsta

lpool.name

<edit>
So looking at the explorer it seems the last POW block actually found was 461631, and there may be an issue with GBT [getblocktemplate]. Which is quite strange considering we are well past the 450k mark when all changes kicked in, and a final POW block of 1mil is hardcoded in the codebase... some examples below:

....rpcmining.cpp.....

....main.cpp....

...main.h.....

I am back home from work and am working furiously on a fix for all. I am currently going over all commits and changes to see if it was a mistake made by me during updates, or if it was a bug in the code used as a base, the minute I have new info I will update here.
Thank you for bringing this to my attention. Once fixed and all is known to be well, I will send you 500XGTC from my personal wallet for the bug report

<edit>
Offering a 5000 XGTC bounty to anyone in the community who can locate the issue before I can. Im not asking for fixes, I will do the fixes, but extra eyes make finding a bug much quicker and will allow mining to resume for all much quicker.
It does not seem to be in "getblocktemplate" or "getwork" or "getworkex" functions, as I have already compared these to other coins code, and all matches perfectly.

Still no response..... if some of the community also put in requests for the update, maybe they will see it is important and get to work on it. However, in my experience yobit can be quite slow in these situations...

Thank you all for your support and kind words 😊
As for "whats next".... i will be attempting to add a "Total current supply" stat to the pool after its rebuild. This will allow us to try for a coinmarketcap listing.

On top of that I am still working in the background to complete the 3.0 software which will be of a 9.x codebase with many new features and UI updates.

Following that are plans for Bloom and SPV integration allowing a quick loading android wallet to be built.

And finally, after these important steps, we will be working on market adoption and real world uses such as donations to charities that support and help drive women in tech.

Although if the community has any other ideas I would be happy to hear  them 😊

50 more sent from the pool wallet, 164 - 50 = 114 LOG remaining [need to test the wallet to ensure they make it to you]
http://cryptoguru.tk/Transaction/index.php?Currency=LOG&Transaction=98ef4416022d512f65b9553475105fcd075fe7edeee8261da229275655c70a7a
I have some more hardening to do on the pool, ports are still closed but explorer is currently up.

Small UI change to help separate mined transactions from staked transactions. Will be included in next build.

I will be manually making payouts tonight for any coins mined at L8nit3-Miners.com, and then ports will be blocked for a short time.

I will be pulling down and rebuilding the pool, with much more focus on better DDOS security as we seem to have had some "interesting" traffic over the past few days.
This process will likely take a few days as I will be restarting from a fresh clean server, and using things I have learned since it was first built, hopefully making a nicer stronger pool for all to use, and hopefully with the "coin supply" addition to the explorer.
Once this is finished I will update here and l8nit3-miners should be running happily again :)

Pool/Explorer is intermittent right now, however main seed node is still rocking. Once finished on some small changes to the XGTC code [which I feel is more important as we have 2 other pools right now], I will focus the needed time and energy to get the pool/explorer back up and running.

UPDATE
I have the 2.1.1.3 update currently building while I am at work. This will add the miniupnpc 1.9 support added by inder/redni, some qt icon fixes, some qt pro fixes, and will update the noblocks version to stop recieving info from the old 1.0.8 versions. And lastly it adds 2 more seed nodes for faster syncing.
Also we are getting quite near block 450k when our new POS % and removal of superblocks will kick in.
Once we pass 450k I will add a new checkpoint in the code which will be in the 2.1.1.4 release

UPDATE
2.1.1.3 has been released, building the pi daemon now. Also the bootstrap.dat has been updated to 445k+ blocks.
OP has been updated with new links, and new additions to roadmap. However I am unable to load up virustotal.com right now and as such the virustotal results have not yet been updated.

2.1.1.3 includes:

<edit>
VirusTotal results have been updated in OP for 2.1.1.3 release

<edit2>
Have looked into a CoinsMarketCap listing, however they require a website that displays current total supply for the coin. I am not used to very much PHP but am in the process of adding it as a stat on the pool explorer [which I will share with other yiimp pool owners if it works]. Once this is working we should be ready for a listing on CoinMarketCap which should help the project get some more visibility

UPDATE
Now that 2.1.1.3 is out I will be pulling down and rebuilding the pool, with much more focus on better DDOS security as we seem to have had some "interesting" traffic over the past few days.
This process will likely take a few days as I will be restarting from a fresh clean server, and using things I have learned since it was first built, hopefully making a nicer stronger pool for all to use, and hopefully with the "coin supply" addition to the explorer.
Once this is finished I will update here and l8nit3-miners should be running happily again :)
I thank the other pool owners for continuing to host mining for XGTC at their pools, it is incredibly helpful while I work on the dev pool

Outstanding coins from pool sent manually:
txid=79bebf0b7baf774790e500aa4a1702af4b3b674983d3a4ec4f7ead43ff637913

Yes that is the plan, there is still some minor adjustments I need to make in the backend once all is paid, but the hope is to be up before long and running at full speed again

<edit>
@lyolyalya
You have ~324-160 = 164 LOG outstanding at this point. I am simply putting this here to have a fair, publicly viewable record of this as I will be pulling down and rebuilding the pool, with much more focus on avoiding chain splits as much as possible, aswell as better DDOS security as we seem to have had some "interesting" traffic over the past few days.
This process will likely take a few days as I will be restarting from a fresh clean server, and using things I have learned since it was first built, hopefully making a nicer stringer pool for all to use. Once this is finished I will update here and LOG should be running happily again :)

These were sent directly from my own c-cex account, and as such are not reflected on the pool. I will be resetting the stats manually, but only after you have been fully paid back the missing coins. That way we can both be sure all is fair.

Sent, however c-cex gave a strange txid...

And the rest will be sent ASAP.

Raspi daemon tested and working on raspi3 , at this point unsure about earlier models.
Pi Daemon

Also finally found a working copy of a 10.6.8 vm, so just gotta install all deps and xcode, and build should be ready in a day or so

And lastly, for those that do not know this yet, coinsmarkets.com is an exchange that also allows you to stake POS coins in the wallet. Similar to a POS pool

Listen "Tami" your FUD does not work. You do not read, you are the worst part of crypto.
A transaction on the wrong chan WILL NEVER GO THROUGH. You and the whole community were warned of this.
So here is your answer "Tami", DO SOME ACTUAL WORK and fix your own coin. You have been reported to mod, and are now on ignore.

@Rest of community
Thank you for your assistance in explaining this once again

Awesome
I build 5-6 card rigs for friends and customers, but currently only rock 2 280x's my self..... hydro pricing sucks in my area.
I have good news however, I have a partial payment of approx 50% of your owed coins ready for you, I just want to ensure WkUUHG2zDC4SeRSLzTM9wf9aQxuo3hHhKJ is the correct address before sending, also I am waiting on a few more altcoin orders to go through and will have the rest. At which point I will be resetting the pool stats [only after all owed coins are paid] and making some changes in the backend of the pool that should hopefully prevent this issue in the future

Sadly no, with approximately 1275.32268 LOG created each day, that would have meant nearly all other miners had dropped off and you had pulled nearly a full days worth of blocks alone. Which makes far more sense knowing now that we were mining on our own chain... separate from all other miners. However, you are absolutely still owed ~1/3 of that amount, which is quite good for a day   may I ask what your using to mine with? multi gpu setup?

Ok, so it seems I was incorrect in remembering why the wallet needed to be compiled with 10.7+ as a base. It was not qrcode support, but was libc++11. It would seem that Apple has decided to only officially support libc++ on 10.7... so I will have to add an hdd to my hackintosh [or possibly just a VM] and setup a 10.6.8 build to be able to properly compile for versions 10.7 and under.
All this is to say, I am working on it but may take a bit longer then a simple re-compile as I originally thought.

Ahhh that is the issue there. Due to enabling qrcode support, a minimum of version 10.7 is required. I apologize, and will build a version compatible with older versions as soon as i am off work 9pm est.

what version of mac and what version of the wallet? the 2.1.12 version? also is there an error message by chance?

Ok, so the current status is as such:
I believe we are now on the correct chain, and I am cashing in holdings of some other altcoins to be able to pay the owed coins. Once we had switched to the wrong chain, any coins mined on that chain technically do not exist, which is why they never made it to your wallet. However, while we were on the correct chain you absolutely did mine up a balance that is still owed to you.
Here is a screen shot of the current pool stats [in the admin section] to show the outstanding coins on the correct chain:

Once I have acquired enough BTC from my other holdings, I will use that to buy the LOG you are owed, and it will be sent from an exchange wallet to ensure that there are no issues with you receiving them.
Again I apologize for the lengthy timeframe while I try and work out exactly how this happened, and while I cash out my other holdings. [POT, PI, DASH, etc.]

Wonderful, thank you for your help I am also uploading an updated bootstrap now