You mean mining in 2 pools with a single GPU?
Yes, GPUs are heavily multithreaded anyways and miners don't really use much memory, so there is no problem in running more than one mining program on a GPU. If you tune down priority of one pool, it will "failover" to that one, should the main pool have problems.
|
|
|
Investing in Bitcoin in something that pays out in NOT-Bitcoin is at the current deflation rate not very advisable... just saying...
As the OP wants to play in Bitcoin poker rooms though (and assuming they are Bitcoin ONLY, so not bound to USD exchange rates) GLBSE might be a very good option.
|
|
|
You can only cash out if someone else buys it for that price - there are still 8 shares for sale for less than the initial 75 Bitcent!
If people were willing to pay 1.25 BTC they could buy it for far less currently. It seems however that they are either afraid or want to wait for further info from Tawsix until they invest.
|
|
|
I just wonder how you realized your pool hopping method (manual might be interesting for a short time, but is not really feasible). Also how to decide in reality to which pool to jump - imagine mining still in the 43% margin of pool 1 but then pool 2 finds a share. Should you then jump to pool 2 or mine until 43% on pool 1 and risk not having a pool to immediately jump to? So in the end: Is it smarter to hop off as early as possible or as late as possible? Could/should it be weighted somewhere in between? I bet you get also tons of PMs now! ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
I still don't get why people mine in only a single pool anyways...
Just fire up 2 miners and you're golden! Usually it even gives a little higher hashrate too.
|
|
|
Phoenix 1.48 shows in slow mining mode (~9 MH/s) also a LOT of stale/"rejected" shares (15 out of 16 currently). My guess is, that with more than 1 phoenix instance long polling does only work for a single instance...
If this happens with only a single miner too though, the error must be somewhere else.
|
|
|
15 school computers accounting for 1.5 TH/s? We can be lucky he didn't vring all 60 online then... ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif)
|
|
|
Well, currently 466 shares have been sold. (Edit: Sorry, that should have been 1465!)
Out of these, 161 are for sale for less than 1 BTC, 8 even for 70 Bitcents (meaning this investor looses 40 Bitcents).
Interestingly Tawsix got lucky and even solved a block (in the pool though...)
Currently he mined 1.55787272 BTC, meaning he "owns" one of his own shares now (only 3999 to go!!!11) (Edit: 5000 to go!!!11) and each share would get a whopping 0.00038947 satoshis as dividend! (Edit: less...)
|
|
|
Noch ein bisschen warten bis MTGox auch in Euros auszahlt + handelt (sollte Anfang Juni der Fall sein) oder über eine Seite wie bitmarket.eu verticken.
|
|
|
When is "phase 2" expected to happen?
|
|
|
I don't have proof, but you will just have to trust me, I promise I bought it and its legit though.
Show the receipt then. ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
Looks like more tahn just a short down-spike atm! ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) Currently, we're below 3,5 TH/s. Looks like we scared the noobs away! ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
|
|
|
Some implementation details left out.
Especially protection against malicious nodes + share verification, the main reason why servers are used for pools despite being single points of failure in the first place (as you just have to trust the server operator, not everyone in the pool) ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) We should stop hijacking this thread though... a distributed pool actually sounds kinda nice!
|
|
|
Note:I've attempted PPA installation with little luck
Quote from that page (under "Technical details about this PPA "): This PPA can be added to your system manually by copying the lines below and adding them to your system's software sources. Selecting your Ubuntu version from a dropdown and doing copy-paste of 2 lines shouldn't be too hard, I hope. Also there is a help function on how to add repositories, conveniently linked with the words "(Read about installing)". Where exactly did you fail in this process?
|
|
|
Now here's an idea: build a peer-to-peer pool using cryptography, so is no central pool host to attack.
This would require miners to install software additionally to the mining software. P2P applications also very often require forwarded ports (current mining software just does some [imho highly inefficient] HTTP requests as far as I've understood) and it would also require bandwidth as well as introducing latency issues. In the end, light takes half a second to travel around the globe, you can't transmit data faster than that. I'm btw. also VERY interested how transaction fees are being handled!
|
|
|
Well, sometimes they also might have to learn it the hard way...
In the end the method is known + documented for some months now, as well as counter measures (however one may view them).
|
|
|
I'd rather see a pushpool implementation, so you would point your own miners to a locally operated pool that does all the "magic" for you. To the pools itself you would just look like a normal (single) miner.
This also has the advantage that you could then even distribute work between pools and keep some minimal hash rate running all the time. Also you could then offer this "metapool" to others, creating the ultimate automatic pool hopping tool!
|
|
|
|