Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 329. (Read 903150 times)

The scheduled database maintenance is under way.  This shouldn't be very visible, I was able to make a few tweaks that vastly sped up the site performance.  Most of what is going on now is testing some new queries in order to summarize PPLNS raw data once per minute, to avoid the need to delete 6m+ rows from a table that is have new rows inserted into every few seconds.

The expected result is there should be no noticeable slowdown when a shift is closed going forward.  What will happen is shifts will no longer be a sharp cutoff at shares, but a slightly fuzzy number.  Instead of 6,000,000 shares, it might be 6,005,412, and the next one might be 6,012,983.  A slight variance in shares per shift.  However, the calculations for rewards already allow for shifts to be different sizes, and it weights the distribution of the block reward appropriately so that 'N' is the total shares in the last 10 shifts, and each one of those shares is paid equally when a block is distributed among them.


Small Update:  Sorry the website got so slow at times for the last few days.  I noticed it early this week but due to a cold I was afraid to start doing too much work.  I already lost a lot of my BTC from working while too tired, didn't want to lose share information because I made a mistake with SQL queries while sick.

My getwork code is extremely old and unsupported (PoolServerJ).  I'm not risking changing difficulty in that only to find out it will let diff-1 shares pass through under certain circumstances.  Getwork will be killed off soon enough as it is.

Oh? Vardiff works with getwork also.
Or is it an issue with some other miner programs don't support it?

Unfortunately I can't do that until I can completely phase out getwork, which is not an option just yet.

Time to set a minimum difficulty? ... 2, or 4?

PPLNS shifts temporarily reduced back to 3 million shares until a fix can be made to the closing out of shifts.  The DB just can't handle moving such large amounts of data all at once every 20-30 minutes, and the faster the pool gets, the more it locks up as a result.

Some minor updates done earlier related to DB Schema of a PPLNS table.  It should prevent the big slowdowns of the site when a block is being applied to shifts.  Not completely solved yet, but it's helping.

I keep the pool speed updated pretty regularly (up OR down), but I only use the 24 hour averages found on Pool Stats.  If it changes by more than 1 TH/s the topic tends to be updated within the next day.

^ points to header...perhaps 16000 GH? 

I'm putting LTC testing on hold (I did verify my stratum code works with it and makes blocks!) for the week.  I will be preparing the servers to upgrade to the 0.8.1 branch late tonight/tomorrow.  This should consist of a single stratum server having a minute or two of downtime to restart with a new bitcoind, waiting an hour to make sure it went well, then bringing another one down in the same fashion.

0.8.1 is expected to be available in the next 24 hours for users to download.  This puts in a temporary limit on block processing that enforces the BDB limits in 0.7 that caused the hard fork.  On May 15th (2 months), this limit will be lifted, so users who do not upgrade after 2 months will be at risk of another fork.  Alerts will be pushed to users running old versions.  Patches will also be made available for users who do not want to upgrade to the 0.8 branch, but do not want to be at risk of hard forking from the rest of the network.


Other project for the week is working on PPLNS Shift scripts to split the load of closing a shift into smaller chunks.  The lag most people see on the website is when the pool is closing up a shift.  It's fairly fast in most cases, but once every 30 minutes it does get quite slow due to moving a significant amount of data within the database.



3) Right now miners can set a minimum difficulty.  What I was referring to is eventually moving the entire pool to a higher minimum difficulty (probably 4 to start).  This probably won't happen until I can remove getwork from the pool.

Seems to be working for me..though there are moments of lag...(suppose its updating).


Would like to say hello to everyone as well. Just joined the Pool and Bitcoin in general. I was mining over at another pool but would like to try here for awhile. I like the ui much better.

I am sorry to hear about the above mentioned fiasco. Public shaming and perhaps linking up with other pool operators to ban them is the best option.

I have hard times loading pool webpage and connecting to api? Is the pool still working or it experience issues too?

couple things eleuthria;

1) I support your decision to post the thieves' info. we should all shame them into returning the coins, or make their lives uncomfortable (short of any actual physical harm. tonyroyisathief.com available?)

2) Litecoin mining added to the pool: resounding YES!

3) you mentioned earlier something about raising difficulty, or setting minimum difficuty to accomodate new ASIC technology. Would that exclude the low power, old GPU miners?(me!)

Well only 2 of them were stupid enough to use email addresses that are clearly not anonymous

And one of them leads to:

http://electron.stemacbg.com/

http://www.cards.stemacbg.com/blog/
http://svatba.stemacbg.com/
http://www.facebook.com/pages/STEMAC-%D0%A1%D0%B2%D0%B0%D1%82%D0%B1%D0%B5%D0%BD%D0%B8-%D0%BF%D0%BE%D0%BA%D0%B0%D0%BD%D0%B8-%D0%B8-%D0%B0%D0%BA%D1%81%D0%B5%D1%81%D0%BE%D0%B0%D1%80%D0%B8/185654011467953

Then of course stemacbg.com is administered by:
whois stemacbg.com
That lists a certain Mr. Totev and his phone number ...


Oh and the other one

http://megatron.wcksoft.com/
https://www.facebook.com/WickedSoftware

LOL at that one - his name address and phone number are listed in the
whois wcksoft.com
... and it clearly is as the email address says ... Tony Roy

Eleuthria, if you need me to translate your email into Chinese for some of those in the shame list, please let me know.

You get some results if you put some of those into google ...

splinter1338: there is an ebay account of the same name

QQ421860256 has quite a lot of hits ...

as does lll622root1 ...

... and of course the other qq accounts ...

5 days since emails went out, only one user responding positively, one user responding negatively.  I said I would hold off on the name & shame, but as pointed out in previous posts, there's really no other recourse.  There's no specific legal agreement, and even if there was, most of these users are in a country that wouldn't enforce it, so the best I can do is expose the pseudonyms they used on BTC Guild.

Username	Email	Overpaid
uuhym	[email protected]	356 BTC
bigbomb	[email protected]	142 BTC
xxx123	[email protected]	95 BTC
heley	[email protected]	94 BTC
splinter1338	[email protected]	94 BTC
vinest	[email protected]	94 BTC
QQ421860256	none	47 BTC
hq	[email protected]	47 BTC
NightAss	[email protected]	47 BTC
n17r0	[email protected]	46 BTC
cwetalin	[email protected]	45 BTC
cyco	[email protected]	23 BTC
classic729	[email protected]	23 BTC
youdamushi	[email protected]	23 BTC
goodlivin	[email protected]	23 BTC

Updated after the post:  For the record, the jerk that sent the email I posted on pastebin was NightAss ([email protected]).

No worries, the hot wallet wasn't bled out again.  Bitcoind crashed on the payout server (damn old versions!).  Restarting it and pushing through any payouts that got stuck.

I just hope he didn't allow them to continue to mine here... Seems like a slap in the face.

Exactly. In a situation where there is no legal framework, social and moral judgements are all that can be applied. Ostracism is the only recourse to show the community at large that such actions are not welcome.