Could you release linux binaries for those of us on VPS?
No idea how to make those.
Just use wine
Code:
sudo apt-get wine
wine protoshares-qt.exe
wine protoshares-qt.exe
Topic: Solo Miner for ProtoShares - 2.9% fee - Updated (Read 9637 times)
No idea how to make those.
Just use wine
You are driving a hard bargain. Since there are pools with 1% fee or even less.
Don't see how your service is superior.
Don't see how your service is superior.
Freed up now from my obligations to Invictus to get ProtoShares up and running with a basic wallet and miner, I've turned my attention to creating an optimized miner for everyone who is still mining solo.
Contractor.
The very same creator of the coin create a optmized solo miner with fees? wtf? 
What's the calculation for how many collisions/block are estimated at a given difficulty? 
If only there was a pool that functions. ?..
Don't know anything about setting up pools unfortunately. It would be nice if we could make pooled protoshares mining available through an easy to use gui like this.
Anyway, I've made an updated client available - should mean no more messing about with multiple instances.
If only there was a pool that functions. ?..
I'm seeing a big increase in collisions per minute since the difficulty adjustment. From about 120 to 160 on an i7-3700. This is because there are fewer stales and this miner stops working on hashes as soon as new blocks come in.
FreeTrade, can new qt version support for co-solo?
I think there's a danger if you use the same wallet on a number of different machines, it might just be replicating the same hashes. Use different wallets to ensure that doesn't happen.
good tools
FreeTrade, can new qt version support for co-solo?
I'm getting about 48 colissions per min. so how soon can i solve a block. how to know my hashrate?
I think some miners are mistakenly quoting cpm as hpm, so you can compare those figures directly except in old miners.
Difficulty just went up - so you need about 2,000,000 collisions to expect one block at the moment. At 48cpm . . that's 28 days. Ouch.
I think some miners are mistakenly quoting cpm as hpm, so you can compare those figures directly except in old miners.
Difficulty just went up - so you need about 2,000,000 collisions to expect one block at the moment. At 48cpm . . that's 28 days. Ouch.
Difficulty just went up - so you need about 2,000,000 collisions to expect one block at the moment. At 48cpm . . that's 28 days. Ouch.
Okay - try the new version, you should see at least a 100% improvement.
I'm getting about 48 colissions per min. so how soon can i solve a block. how to know my hashrate?
I think some miners are mistakenly quoting cpm as hpm, so you can compare those figures directly except in old miners.
Difficulty just went up - so you need about 2,000,000 collisions to expect one block at the moment. At 48cpm . . that's 28 days. Ouch.
See licenses for resource files (doc/assets-attribution.txt), and for libs that you link (seems like you link openssl staticaly)
Thanks Alexxy, but I'm not of the opinion I'm breaking the terms of any license that I'm using.
I'm getting about 48 colissions per min. so how soon can i solve a block. how to know my hashrate?
My new solo miner is probably faster, open source, no fee. Sorry FreeTrade.
Where can I get it?
http://bitsharestalk.org/index.php?topic=573.0
My new solo miner is probably faster, open source, no fee. Sorry FreeTrade.
Where can I get it?
Hi, trying your miner on one of my dual xeon servers. With the yPool miner I was getting about 320 collisions per minute. Running 16 instances, yes I do have the ram to handle it. I get a total of about 160. Am I comparing apples to oranges here? If this is accurate then you need to update your solo miner with JH00's code.
My new solo miner is probably faster, open source, no fee. Sorry FreeTrade.
Jump to: