davout: have you given any thought to the idea of compromising between transparency and stability, by hiding only the dark pool order volume, but not the fact that an order exists?
If the volume is hidden though it discourages me from using the market. If people use the dark pool then the volume on the market always appears low and makes me think there's no trading going on. So I look for a busier market or assume bitcoin is not being traded.
|
|
|
I don't understand what the benefit of a dark pool is. Can you explain why someone would use the dark pool? Or why someone wouldn't use the normal pool and should only use the dark pool?
|
|
|
should I write "huesped.name_of_worker:password" or only my nick without nick of worker?
This first one: "huesped.name_of_worker:password"
|
|
|
So to generate a local time, make the server generate this HTML code: <script language="javascript" type="text/javascript">document.write(new Date(Date.UTC(2011, 1, 6, 18, 24, 0)).toLocaleString())</script> Have your server generate the "real" numbers above. If the server stores times as milliseconds-since-1970 in GMT, you can do it even easier: <script language="javascript" type="text/javascript">document.write(new Date(1297016640000).toLocaleString())</script> Slush's server uses XHTML so document.write won't work. See here: http://www.w3.org/MarkUp/2004/xhtml-faq#docwrite
|
|
|
Did you download it and gunzip it on the phone? I just tried the following steps from the N900 terminal and it worked: $ wget http://www.bluishcoder.co.nz/bitcoin-pool/bitcoind.gz $ gunzip bitcoind.gz $ chmod +x bitcoind.gz $ ./bitcoind
|
|
|
Trying to run the binaries on Windows it gives an error saying that OpenLDAP.DLL is missing. Should that be included in the .zip file?
|
|
|
I guess it's that my system is slow (the 1-2K is the sum of the threads, not the individual ones). I get the "zeroes in hash" message once in a while, but it keeps telling me that it's not the actual result.
I'm pretty sure that cryptopp_asm32 is broken on at least some systems (mine included). It never generates a share. There is some mention of this in the thread about minerd. I stick to the 'C' method or '4way' on compatible hardware.
|
|
|
on the "doublec/puddinpop pool-system", users might "earn" 0.00****btc, but those sub-cents will be lost, not forever, but for you, the generator.
I agree, rounding to 0.01 is the better approach.
|
|
|
Also, do you really have to wait a day for the confirmation? I think 10 new blocks should be more than enough.
He has no choice but to wait. The coins aren't available from the generated block until 120 more blocks have passed. This is enforced by the network and software. He can't send the coins out before this.
|
|
|
I set my threshold to 0.01 and my reward is 0.55 but I don't think its sending it to me. Maybe it doesn't work below 1?
Same here. My reward is over the threshold of 0.01 but nothing sent.
|
|
|
32 is not difficulty,
It might be a good idea not to call it 'difficulty' on the webpage...
|
|
|
Which version ? Did you build it yourself ?
I got the error you got when I had the wrong username/password.
|
|
|
and again, i just had 2 of 3cores @ 2400khash/s each running for about 15minutes and got 2shares/found 2 winning hashes. that's not even close to your 19hrs.
Yes, I guess the difficulty calculator I used must be incorrect. Any idea what the estimate would be?
|
|
|
What's the current difficulty value for miners to get a share?
Found it, '32' according if it's the listed difficulty under each registered miner. So that's about 19 hours for a share using a 2,000 khash/s machine (my estimate of an average dual core laptop).
|
|
|
The instructions say to use one registered miner for each remote miner instance connected. Does this mean multithreaded miners need to be limited to 1 thread only? Will running them with multiple threads confuse the share algorithm?
|
|
|
What's the current difficulty value for miners to get a share?
|
|
|
2010-12-17 08:51:59.737616 Send 7.34 to 1JdEn5LeMREmAjcAi4KWf8EX6zkubqGn55 Send 2.56 to 1A6ru2AYP9gMBpMEw63fwLqXNJ75efaBiY Send 1.61 to 13SecR7EGTXQ4LHGWvYhbAEUbMnFpyMWHG Send 1.22 to 1Eo51LLvhkJhxGR6oga1QkNV9a1KJsbrF7 Send 0.48 to 16yH1S6eJpj8UyLFqMVM35pbf5vXrec2c8 Initial balance: 50.03, sent total 13.21 for 5 people, time 0.4 sec Why so few payouts and they don't add up to 50? Are there a lot of entrants that have a minimum amount to send set so their balance is accumulating?
|
|
|
I had 4.7 installed as it was mentioned in the build-unix.txt . I now installed 4.8 and tried again.
I now get
Edit CMakeCache.txt. Change the line that references libdb.so to libdb_cxx.so.
|
|
|
Is the source for your cooperative miner available?
|
|
|
What the logs say, will the new pool have a site?
I'm keeping my server running until it generates a block so the people who've contributed hashes for the last couple of days haven't wasted their time. Hopefully not too many people will switch before that happens otherwise it'll be forever before it generates. I'll update the bitcoin-pool page with the new IP address and a note that someone else is running it when that happens.
|
|
|
|