[CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers

[twmz]

3) I will test the defective unit when it arrives.  If it does not work, I will not reimburse for return shipping, but will ship another brand new unit back.

Typo above?

[1713874168]

1713874168

[1713874168]

1713874168

[1713874168]

1713874168

[eleuthria]

3) I will test the defective unit when it arrives.  If it does not work, I will not reimburse for return shipping, but will ship another brand new unit back.

Typo above?

Corrected.  Thank you.

[centove]

Update to USB Block Erupter Policy

1) Units will be shipped out untested until orders slow down enough to where testing individual units is not going to slow down shipping.  This will speed up clearing out the backlog significantly.

Next year sometime??

[os2sam]

50Ths Pool??  Would anyone had thunk it a couple years ago?

[eleuthria]

50Ths Pool??  Would anyone had thunk it a couple years ago?

Funny enough, I learned about Bitcoin from the Security Now podcast.  While testing chips I was going crazy, so I've been listening to podcasts and audio books.  For fun yesterday, I turned on the old Security Now podcast that goes over Bitcoin.  Steve mentioned in the video (sounding quite amazed) that the network speed was estimated to be 186 GIGA hashes per second at the time.  Amazing how far it's come in 2 and a half years.  Each of the top 50 users of the pool are now faster than the entire network was back then.

[Miner-TE]

That is funny.  I also learned about Bitcoin from Security Now and immediately pointed a CPU at Slush...

Those were the days .... February 9Th 2011   

http://twit.tv/sn287

[SolarSilver]

Each of the 50 users of the pool are now faster than the entire network was back then.

Please tell use that is "Each of the top 50 users of the pool" :-)

[eleuthria]

Each of the 50 users of the pool are now faster than the entire network was back then.

Please tell use that is "Each of the top 50 users of the pool" :-)

It's been a LONG couple of days!  Fixed .

[os2sam]

That is funny.  I also learned about Bitcoin from Security Now and immediately pointed a CPU at Slush...

Those were the days .... February 9Th 2011   

http://twit.tv/sn287

That's when I learned of Bitcoin as well.  I'm still kicking myself for procrastinating for 3 or 4 months before getting started.

[razorfishsl]

The great thing about Crypto currencies is that.... There is a new one every day....

Still plenty of time to jump under that band wagon....

[eleuthria]

Updates to the store.  Shipping queue position now updates every time an order is shipped, rather than in batches when I manually update the queue.  Additionally, the backorder queue is doing the same, so you can see the backorder queue continue to drop as orders move out .

[Trongersoll]

I've got a question that i probably shouldn't ask, depending on the answer.  Proof of Work. does the pool software verify that every returned hash from the individual miners is a valid response and not just some made up number? Considering the high hash rates it seems to me that this would require quite a bit of computing power, but on the other hand it wouldn't be hard to modify a mining program to spoof the results providing a much higher appearing hash rate.

[wtfvanity]

I've got a question that i probably shouldn't ask, depending on the answer.  Proof of Work. does the pool software verify that every returned hash from the individual miners is a valid response and not just some made up number? Considering the high hash rates it seems to me that this would require quite a bit of computing power, but on the other hand it wouldn't be hard to modify a mining program to spoof the results providing a much higher appearing hash rate.

Yes they are checked. Verification time is orders of magnitude quicker than finding the proof of work.

[eleuthria]

I've got a question that i probably shouldn't ask, depending on the answer.  Proof of Work. does the pool software verify that every returned hash from the individual miners is a valid response and not just some made up number? Considering the high hash rates it seems to me that this would require quite a bit of computing power, but on the other hand it wouldn't be hard to modify a mining program to spoof the results providing a much higher appearing hash rate.

Yes they are checked. Verification time is orders of magnitude quicker than finding the proof of work.

Expanding upon this:  A 1 GH/s miner is doing 1,000,000 Double-SHA256 hashes per second.  It will submit work every 4 seconds (assuming diff=1).  The server does *one* Double-SHA256 hash to verify the work.  Of course, the server is doing that over CPU, but even a CPU (server-grade) is capable of doing a couple million per second.

[Trongersoll]

I've got a question that i probably shouldn't ask, depending on the answer.  Proof of Work. does the pool software verify that every returned hash from the individual miners is a valid response and not just some made up number? Considering the high hash rates it seems to me that this would require quite a bit of computing power, but on the other hand it wouldn't be hard to modify a mining program to spoof the results providing a much higher appearing hash rate.

Yes they are checked. Verification time is orders of magnitude quicker than finding the proof of work.

Expanding upon this:  A 1 GH/s miner is doing 1,000,000 Double-SHA256 hashes per second.  It will submit work every 4 seconds (assuming diff=1).  The server does *one* Double-SHA256 hash to verify the work.  Of course, the server is doing that over CPU, but even a CPU (server-grade) is capable of doing a couple million per second.

Thanks for the answer, i hoped that this was the case. Just noticed on another pool that when a large percentage of hashing was added all at once, instead of the number of blocks found during a day going up, the luck went down instead. I was just contemplating how one could make that happen and i came up with spoofing the pool.

[wtfvanity]

I've got a question that i probably shouldn't ask, depending on the answer.  Proof of Work. does the pool software verify that every returned hash from the individual miners is a valid response and not just some made up number? Considering the high hash rates it seems to me that this would require quite a bit of computing power, but on the other hand it wouldn't be hard to modify a mining program to spoof the results providing a much higher appearing hash rate.

Yes they are checked. Verification time is orders of magnitude quicker than finding the proof of work.

Expanding upon this:  A 1 GH/s miner is doing 1,000,000 Double-SHA256 hashes per second.  It will submit work every 4 seconds (assuming diff=1).  The server does *one* Double-SHA256 hash to verify the work.  Of course, the server is doing that over CPU, but even a CPU (server-grade) is capable of doing a couple million per second.

Thanks for the answer, i hoped that this was the case. Just noticed on another pool that when a large percentage of hashing was added all at once, instead of the number of blocks found during a day going up, the luck went down instead. I was just contemplating how one could make that happen and i came up with spoofing the pool.

Search the forums for a little bit. Something that has been discussed is where a miner adds a bunch of hashing power with a modified miner, and instead of submitting all shares, they just submit shares that are > than the minimum, but less than a full block. So if they add say a terahash of mining, they should be finding blocks every so often. But instead of actually submitting those shares, they withhold them.

Most pools have mechanisms in place for identifying such situations, but a lot of smaller ones or pop up alt coins ones probably haven't even considered it.

[eleuthria]

A whole bunch of orders just got picked up by USPS, over 100 if I counted correctly.  Check your Order Status to get tracking information.  If you see weird tracking information, check the date.  If it's 2012, it's due to USPS recycling tracking numbers.  Apparently something went wrong in October and a bunch of tracking information wasn't deleted before the number was recycled.  It should get corrected the next time it is scanned in by the post office.

[os2sam]

it's due to USPS recycling tracking numbers.

Why is it everyone in the world can have multiple bitcoin addresses without recycling them but the post office has to recycle a number that is about the same length every year?

[Trongersoll]

it's due to USPS recycling tracking numbers.

Why is it everyone in the world can have multiple bitcoin addresses without recycling them but the post office has to recycle a number that is about the same length every year?

They can't afford ASICminers? 

[eleuthria]

The ISP for US based Stratum had a few hiccups earlier (packet loss).  Everything seems to be back to normal now.  Logs aren't showing any signs of hostile activity, so right now I'm blaming it on the DC.

Work is still being done to relocate all the US based servers to a DC that has historically had 100% uptime for the pool in the past.  More information on that hopefully next week.