OK, I understand. All values are net. So essentially I "donate" some percent of the shares, don't I? In other words, you get the donation when the block is found. And If I change the donation percentage, it will not change the rewards for the blocks already found, only the future ones. Correct?
Exactly. |
|
|
|
From what value is this donation is calculated? From unconfirmed reward, confirmed reward or reward sent? I've just got a bunch of rewards and nothing was subtracted.
All displayed rewards are already displayed without donated amount. |
|
|
|
|
I just enabled automatic pool donations and email notifications on payouts. Reporting worker crashes will be soon.
Also thanks to all who set up some donation on profile page :-).
|
|
|
|
In practice, for your own statistics, it turns out that many weak miners more often do a getwork request, it means that they solve a larger number of blocks, is not it?
Because slow miners are not crunching whole 32bit nonce space. They must ask more frequently to work on up-to-date jobs. For example, jgarzik's miner is iterating only over 24 bits from nonce and GPU miners are using 32bits, but they also have x second timeouts. |
|
|
|
I think IP changes are prevention for botnets than for class rooms. If you use proxy, you have additional network overhead and maybe you lost anonymity because your proxy have to run somewhere. It's little harder (for script kiddie) to setup fast anonymous proxy correctly. I agree it is mainly security by obscurity, but this should not affect regular users with two three miners... What is the difference (for performance) is plugged into a worker one powerful or many weak miners?
The difference is extreme. Miners need fresh getwork every few seconds to crunching actual block. So typically miners download job every 5-6 seconds. From current pool stats you see, that getwork rate is at 85 getworks per second. Diablo miner for ATI 5970 download ~6 getworks per 5 seconds for 600mhash/s (so approx. 1 getwork per second), but 300khash/s CPU miner call getwork once per 5 seconds (0.2 getwork per second). Situation 1) All miners are using ATI 5970. For 85 getworks/s the pool performance is 85*600 = 51000 mhash per second Situation 2) All miners are using CPUs @ 300khash/s, the pool performance is 85/0.2*0.3 = 128 mhash per second Both for the same server load. See the difference? Another view can be total getworks per found block. When miner have rate 1 getwork/s and average time for block is 27 hours, it is 97000 getworks/block. When CPU miner has average time 1 year, you need 6300000 getworks/block. You spend much more resources on network overhead and server capacity than 50 BTCs have current value (not counting power needed for miner itself). So mining with such poor CPU miners is completely worthless. Supporting CPU miners in pool is charity from all GPU donators, because pool with CPU miners will never pay itself for server hosting. I'm happy for CPU pools miners crunching blocks on their personal netbooks for their first bitcoin, but I definitely don't want botnet of 10year old crap computers from computer labs. |
|
|
|
Wait a second, I thought this is about a full implementation of Bitcoin on top of Android and not some remoting. I'm implementing the whole stack in Java for a native Bitcoin app.
Personally I prefer remote solution because I don't want to have my coins on mobile phone for security reasons. So handling wallet + QR codes are enough for me and I want to support this solution. This does not mean I won't pay you for full Android stack, too. |
|
|
|
SSL works in theory. In practice, there's either a bug in browsers or bitcoind that prevents a reliable connection. I hope to resolve that within the next days.
Great, then I send you the rest of my bounty. |
|
|
|
Does this qualify for the bounty?
I like your solution (but didn't tested it on phone yet). Unfortunately current version is still unusable because nobody will open own bitcoind RPC to internet and send plain username/password over it. I don't know how difficult is to add SSL layer, but once this will be solved somehow, my 50BTC is yours. |
|
|
|
well, I got my 1btc finally... after three weeks of collaborative mining. I think I'm out, doesn't seem worth it to burn my cpus that hard.  I think pool is useful to get first newcomer's Bitcoin quite easily even when he has only poor CPU. But it is definitely economic nonsense to mine with CPU to make money. So congrats for you first mined bitcoin, but I believe you can obtain more bitcoins much cheaper on #bitcoin-otc IRC channel :-). |
|
|
|
- Sorting the worker stat by the worker name
Done on dev. - batch create workers (or after create the worker, go back to profile page )
Actually I'm thinking about make it _harder_ to create botnets. Adding captcha for user and worker registration and limit worker count to something like 10 per account, not allow frequent IP changes of workers and so. Connecting botnet of poor workers to pool is my nightmare for both performance and legal troubles. Why? Because I am trying to build a big cluster of workers (~30 hosts)..... (I may will give more details later)
I made pool to help standalone miners smooth their income, not to help people with stealing CPU power from university computer lab. |
|
|
|
HTTP request failed: The requested URL returned error: 400
json_rpc_call failed, retry after 30 seconds HTTP 40x server returns when JSON response is different that miner should expect. That means bad login, bad password, malformed request and so on. Typically the JSON response tell you what wrong happen. I don't know why miner does not display this message to user... HTTP 50x is returned when pool has outage. |
|
|
|
|
Hi, I just tested your miners and it works nicely with my pool, so I added link to pool's homepage.
|
|
|
|
|
I just finished migration of server. Old IP should expire in one hour, then I will shut down reverse proxy on old server, so old IP will not work. If you are using host name 'mining.bitcoin.cz', change is transparent for you and you don't need to change anything on your side.
|
|
|
|
|
I'm going to move application to new server now. There will be some service outage.
|
|
|
|
i just activated my account but the website is telling me user/pass credentials don't match. can you perhaps send me a password reset or reminder?
i think this is weird as i just registered. i usually remember my passwords at least for a few minutes...
I tested registration few times today and I didn't get any troubles here. I deleted your account, please register again... |
|
|
|
|
Thanks for your advices. I think I can handle this 'problem' :-).
|
|
|
|
are having troubles? my gpu and cpu are share constantly and nothing happens, no have loans :S
Interesting. What's your command line? Pool is OK, I don't know why you have troubles... |
|
|
|
I assume dates in the server are stored as GMT. I actually came here to ask about this. I didn't want to make assumptions. Yes, all data on site are in UTC. Thanks to Essjay, I'll add some javascript to enable local times soon. |
|
|
|
Quick question, I was wondering what ratio of invalid or stale to accepted is normal? The past couple days I've been getting 100% accepted, woke up this morning to probably 20%.
You are using m0mchil's, right? Please upgrade to latest version, it fix this issue. |
|
|
|
|
All users of m0mchil's miner, please update to his newest version.
|
|
|
|
|
Show Posts
