|
Over time, the ratio between gw with a solution and gw with no solution on diff > 1 (diff 8 ) is 5% less than same ratio on diff 1. I have 3 workers, 2 at diff 1 with same ratio, one trough proxy which is moved incrementally after connect to diff 8, its ratio is 5% less than diff 1. I want to use stratum to save pool resources and I assume ratio difference its from vardiff alg. It may also be caused by some relationship with network latency, since diff one workers are connected to DE server (Europe). However, I think most likely is from vardiff, so I would like at least to test same worker at diff 1 trough stratum.
|
|
|
|
|
Guys, pls, how to set difficulty client side without hacking the proxy? Higher diff set pool side eats 5% of my hashing power.
|
|
|
|
|
Is there a way client can chose diff instead of proxy/server attempting to guess best diff for client?
|
|
|
|
Mineaza cineva LTC, sau are de gand sa treaca cat de curand pe LTC? Banuiesc ca nu toti ne luam ASIC-uri, nu?  Inca o intrebare: pe deepbit, la ~ 3.1GHash, primesc cam 0.95-1BTC/zi, variaza de la zi la zi. Nu e cam putin, eu ma asteptam sa fie constant min. 1.1 BTC/zi. O sa incerc sa minez LTC cu fpga-urile mele, la fpga-urile mele pot pune si RAM. Deepbit iti ia 10% taxa iar cu 3.1GHs la dificultatea actuala faci 1BTC pe zi fara taxa. In plus, o variatie de +- 5% pe zi e absolut normala. PS: guess what, lucrez sa-mi fac si eu ASIC. Contul pe deepbit e setat pe propotional, nu pe pay-per-share. Comisionul cica e 3%, in fine o sa ma mut pe alt pool pentru ultimele 2 luni pana ies ASIC-urile. Eu sper sa renteze sa ma mut pe LTC dupa ce ies ASIC-urile, ca nou-ul PC cu 5 GPU abia are 2 saptamani de cand mineaza, asa ca mai am mult pana scot ceva. Apropo de ASIC, nu dureaza mult pana iti faci? Cati bani tb. sa bagi in acest proiect, nu e minim 10k Eur? Wow, pai la proportional ai variatiile cele mai mari. Eu m-am invatat minte pe EMC, cand a fost rally pana la 15 USD / BTC si eu stateam ca fraierul si ma uitam cum fac runde de 12 ore in top 5, castigam de cinci ori mai putin.. Mergi pe BTC cu 5%. Sunt si altele cu 3% dar am inteles ca au uneori probleme sa plateasca (poolul plateste variatia). La ASIC poti scoate prototipul mai ieftin de 10k. Costurile mai mari sunt dupa. Timpul din momentul cand ai inceput sa lucrezi pe hdl pana incepi sa produci placi pot fi, daca lucrezi fluid, in jur de patru luni. |
|
|
|
Mineaza cineva LTC, sau are de gand sa treaca cat de curand pe LTC? Banuiesc ca nu toti ne luam ASIC-uri, nu? Inca o intrebare: pe deepbit, la ~ 3.1GHash, primesc cam 0.95-1BTC/zi, variaza de la zi la zi. Nu e cam putin, eu ma asteptam sa fie constant min. 1.1 BTC/zi. O sa incerc sa minez LTC cu fpga-urile mele, la fpga-urile mele pot pune si RAM. Deepbit iti ia 10% taxa iar cu 3.1GHs la dificultatea actuala faci 1BTC pe zi fara taxa. In plus, o variatie de +- 5% pe zi e absolut normala. PS: guess what, lucrez sa-mi fac si eu ASIC. |
|
|
|
..sane military personnel..
oxymoron alert!  |
|
|
|
Reading the article this sounds more like a quantum scale Turing computer building block rather than an actual quantum computer building block. I mean they were only able to achieve two states, 0 and 1. Or did I misunderstand something?
It's rather "Successfully interfacing a qubit using regular ASICs" Not much of quantum computing yet.. |
|
|
|
|
Lol, so whats the relationship between Pirate thing and BLF?
|
|
|
|
|
what? why it isnt public?
|
|
|
|
That should be fixed now as well. It was related to how my averaging window resets when a miner hasn't submitted a share for more than 10 minutes.
Lol, why, it was only lasting for seconds, and the feeling was good, virtually owning the entire network hash power.. |
|
|
|
lol love how my 24 hour earnings shows "3,458,047.50000000" ...now if only it was true beat this:  |
|
|
|
Merge. |
|
|
|
500 units per day ? that's a unit every "less than 3 minutes" just to assemble, what about testing, baking and packing ? unless the machine assembles several units at once.
If the ASIC is carefully packed, they can assemble easy 500 PCBs per day, SMD only, given the number of employees they have and the machines they bought. I do run a similar business, I dont assemble ASICS, but given the trend, I do consider doing my own ASIC, lol.. |
|
|
|
|
I doubt a regular faraday cage will help. Depending how close you are from the EMP source and what sort of source it has, you will need thick metal shield or multiple metal shields. In theory everything protects, depends of the distance and the thickness of protective layer (and material).
|
|
|
|
If an EMP attack plays out as feared, bitcoin would be the least of your worries.
Imagine the power being out for years, maybe decades.
As someone suggested, after difficulty will fall to 1, we will use pen and paper to continue blocks checking and mine coins. |
|
|
|
|
Maybe I am wrong, but did you "sudo python setup.py install" and did it finish ok or it gave you an error??
|
|
|
|
|
Hi,
Any pool supports JSON RPC request batches?
Cheers
|
|
|
|
Tested with 40 GHs (one 10GHs node and one 30Ghs node), unfortunately, for some reason, the 30GHs node bad-performed. I did install proxy but it was not able to upload more than 5-6 results per second (20 - 25Ghs) with alot of shares spending too much time in upload queue to the point where they would become obsolete after new job. This is not happening on direct connection with btc pool, upload queue is almost always empty. Example 1347652578.006 TS, Submitter2, extracted id=0, data=0
1347652578.168 TS, Submitter2, net-looped id=0, data=0
1347652578.213 TS, Submitter2, extracted id=1, data=0
1347652578.374 TS, Submitter2, net-looped id=1, data=0
1347652578.374 TS, Submitter2, extracted id=2, data=0
1347652578.535 TS, Submitter2, net-looped id=2, data=0
1347652578.535 TS, Submitter2, extracted id=3, data=0
1347652578.696 TS, Submitter2, net-looped id=3, data=0
1347652578.696 TS, Submitter2, extracted id=4, data=0
1347652578.857 TS, Submitter2, net-looped id=4, data=0
1347652578.857 TS, Submitter2, extracted id=5, data=0
1347652579.017 TS, Submitter2, net-looped id=5, data=0
1347652579.017 TS, Submitter2, extracted id=6, data=0
1347652579.177 TS, Submitter2, net-looped id=6, data=0
1347652579.177 TS, Submitter2, extracted id=7, data=0
1347652579.338 TS, Submitter2, net-looped id=7, data=0
1347652579.338 TS, Submitter2, extracted id=8, data=0
1347652579.499 TS, Submitter2, net-looped id=8, data=0
1347652579.499 TS, Submitter2, extracted id=9, data=0
1347652579.659 TS, Submitter2, net-looped id=9, data=0
1347652579.660 TS, Submitter2, extracted id=10, data=0
1347652579.820 TS, Submitter2, net-looped id=10, data=0
happens just before httplib conn.request and net-looped happens after httplib conn.getresponse().read(), id is queue id for work result to submit. |
|
|
|
|
Show Posts
