Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 1151. (Read 4382755 times)

the treshold says how much BTC you have to earn before it will be send to your wallet.

I'm testing this out with one of my miners. It seems to be working OK, but one question: does anyone know how much bandwidth this consumes? The miner is connecting via RPC to the server several times per minute, isn't it?

Also, what’s the 'send threshold' setting on the profile page?

DiabloMiner-XXX -u . -p -o mining.bitcoin.cz -r 8332

Please paste here your command line (replace password with some characters).

which miner do you use?

m0mchil's:
poclbm --host=mining.bitcoin.cz --port=8332 --user= --pass= --device=N

jgarzik's:
minerd --url=http://mining.bitcoin.cz:8332 --userpass= --algo=<4way> --threads=N


not sure about Diablos, something similar i guess.  

Worker's login is assembled by two parts - your login to administration and worker's suffix, dot betweet them: .
When you register worker, system will show you complete login/password on profile page. This is because you can run worker on not fully trusted computer. Nobody with access to this computer can access your web profile (and change wallet address, ...).

Please use exactly one worker login for one miner instance. Otherwise it will break counting of your worker's shares.

Soo... How do i actualy connect the miner?

I'm using DiabloMiner on windows i tried using --host=mining.bitcoin.cz and --port=8332 arguments to connect to the server but it gives me a NullPointerException

Am I just dumb or something ?

How to connect ? (registered account adn worker already)

Yes, we found second block at 16:10, see http://blk.bitcoinwatch.com/b?h=97886. First one from 07:16 is http://blk.bitcoinwatch.com/b?h=97834.

"Blocks' in worker details are only valid block found by this worker. So currently only two workers have  '1' in Block column. All stats are realtime.

yay, seems like we already solved our 2nd block.

are worker-stats updated when generations are matured?
cuz they still show 0 found blocks.

Well, it doesn't even need to be voluntary...

If you release the server code, many people will compete to offer servers. Some people may charge a mandatory 2% fee to cover costs; perhaps some people will charge 1%. It will be competition, and we can choose based on fee, how much we trust them, etc.

:-) No, it isn't. I will make more stats on Statistics page, so everybody will be able to count, if declared cluster power corresponds with finding frequency and if user's share corresponds with his reward.

I was already thinking about how get paid for server resources and I like proposed idea of voluntary continuous donations.

That's already in the code, you're just not aware of it

You might like to code this feature:

When we find a block and you pay out bitcoins, allow us to donate a percentage of the reward to you.

For example, I would be happy to donate 5% or 10% of all my bitcoins earned, to compensate you.

First block found at 8:16 CET! (It reminds me I have to add timezone calculating or at least UTC times to statistics). Once bitcoins will be in the wallet, the first bitcoins will be sent :-). But you already see yours calculated reward on profile page. 4898 shares was needed to find the block.

Cool I'm in Australia, on wi-fi.  my connection isn't the best thing.

Oh, it is really bad connection. I have <40ms and 0%loss (cable connection and in Europe). I expect you are in America (large pings) and over wifi (packet loss)?

I plan to make 'miner proxy' application, which should pre-load work on your computer and act as local bitcoin installation (you connect miner locally to this app). It should help a lot in this case.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Cameron Garnham>ping mining.bitcoin.cz

Pinging mining.bitcoin.cz [109.74.195.190] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 109.74.195.190: bytes=32 time=417ms TTL=49
Reply from 109.74.195.190: bytes=32 time=415ms TTL=49

Ping statistics for 109.74.195.190:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 415ms, Maximum = 417ms, Average = 416ms

C:\Users\Cameron Garnham>ping mining.bitcoin.cz

Pinging mining.bitcoin.cz [109.74.195.190] with 32 bytes of data:
Reply from 109.74.195.190: bytes=32 time=414ms TTL=49
Reply from 109.74.195.190: bytes=32 time=414ms TTL=49
Reply from 109.74.195.190: bytes=32 time=414ms TTL=49
Reply from 109.74.195.190: bytes=32 time=414ms TTL=49

Ping statistics for 109.74.195.190:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 414ms, Maximum = 414ms, Average = 414ms

C:\Users\Cameron Garnham>ping mining.bitcoin.cz

Pinging mining.bitcoin.cz [109.74.195.190] with 32 bytes of data:
Reply from 109.74.195.190: bytes=32 time=414ms TTL=49
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 109.74.195.190:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 414ms, Maximum = 414ms, Average = 414ms

C:\Users\Cameron Garnham>

Interesting. I have running m0mchil's here too and have no one error... Which is your ping to mining.bitcoin.cz? Server is located in London.

Not yet. It need cleanup and optimization, which I'm planning. But I expect that I will open codes at least for security review in future.