In my opinion, the timestamp of a block doesn't give any information on whether the block was generated and released immediately to the rest of the network or not. Consider the following case: - The current block chain has N blocks at time T0.
- The "cartel" finds a new block "N+1", let's call it block X, at a certain time T1 and decides not to publish it right away.
- Some time later at T2, somebody not inside the cartel finds also a block "N+1" (call it block Y) and releases it immediately to the rest of the network.
- Once one of the cartel nodes see this block Y, the whole cartel releases block X (and doesn't transmit block Y to other nodes).
What does an honest node see at time T3 (seconds later then T2): it gets (at best) two new solutions X and Y and it has to decide which one is "the best" to start working on. If it would rely on the timestamp T1 and T2 of the blocks, block X will win each time, as it was created (well) before block Y ! As the difficulty is adjusted so that blocks are generated in average every 10 minutes, T1 and T2 won't be hours apart either (but probably between 0 to 30 minutes). So the cartel has two advantages: it is already working for the time T2-T1 on block N+2 (and if it has already been found, it can destroy block Y instantly by publishing block N+2 too) and it can prevent transmitting "non-cartel" blocks to other nodes to a certain degree. I believe you hit the nail on the head here. I believe this could be happening right now. Look real closely at some of the stats @ nullvoid, http://nullvoid.org/bitcoin/statistix.php?showallblocksSeveral blocks are found in less than 1-2 minute, some even have been found in negative time (like block 100557 found in -19 seconds). Today it seemed like many of the blocks are being found well underneath the average time. I also noticed that when the mining pool @ bitcoin.cz got a block, my windows Bitcoin client didn't get notified of the block update for 6 minutes! That means the Pool got a 6 minute head start of everyone else @ 5.5 Bhash/s ... that's a good head start. I'm not sure what caused this behavior, but it was interesting to watch happen before your eyes. Go figure, the bitcoin pool got several blocks after that too, then didn't get any for several hours. I'm also curious if the bitcoin pools are being messed with by said "cartels", as slush said his server came under a DDoS attack last week....hrm... |
|
|
|
alright, I followed the instructions on that site... but why do I keep getting this error regardless of whether I open the .bat file or do so manually?
C:\bitcoin\poclbm_py2exe_20101228\poclbm.exe --user=no --pass=no
Traceback (most recent call last):
File "poclbm.py", line 3, in <module>
File "pyopencl\__init__.pyc", line 3, in <module>
File "pyopencl\_cl.pyc", line 12, in <module>
File "pyopencl\_cl.pyc", line 10, in __load
ImportError: DLL load failed: The specified procedure could not be found.
I thought I was just doing something wrong at first, but even when I followed the instruction on the blog, word for word, with a slight variation in version numbering I get this error. I don't get what this means, and the poclbm.py has 0 lines in it, and takes up 0 KB. :/
Just a guess, but do you have the latest drivers for your video card? My friend saw something similar last night and a video card driver update resolved it. |
|
|
|
Edit: False alarm, please ignore. Hi,
I'm seeing several repeat "accepted" hashes. Here's an example.
01/01/2011 18:09, e62d8177, accepted
01/01/2011 18:09, e62d8177, accepted
01/01/2011 18:09, a753edb1, accepted
01/01/2011 18:09, c46b1614, accepted
01/01/2011 18:10, 51ccbc9c, accepted
01/01/2011 18:10, 51ccbc9c, accepted
01/01/2011 18:11, 2b411e8b, accepted
01/01/2011 18:11, 2b411e8b, accepted
01/01/2011 18:11, 2b411e8b, accepted
01/01/2011 18:13, 3ddfdb84, accepted
01/01/2011 18:13, 9e29c06c, accepted
01/01/2011 18:13, bdc65504, accepted
01/01/2011 18:13, bdc65504, accepted
01/01/2011 18:14, f4d73c8f, accepted
01/01/2011 18:14, 7229e2dc, accepted
01/01/2011 18:15, af861f38, accepted
01/01/2011 18:15, c5d3b074, accepted
01/01/2011 18:16, c446c905, accepted
01/01/2011 18:16, 5e9072e6, accepted
01/01/2011 18:16, 5e9072e6, accepted
It seems to be getting more frequent over the last few days too, as in I'm now see 3 to 4 repeat "accepted" hashes.
The number of "shares" I get from bitcoin.cz doesn't increase with repeats either.
What would cause the same hash being accepted more than once?
Is my client computing the same hash more than once? If so, why?
Thanks for the great code. Getting ~150,000 khash/s.....I think. 
|
|
|
|
it be nice to know what block the pool is currently working on.
OK, I added block# to stats page (in next release). Thank you very much! Expect donations soon. |
|
|
|
|
Another question for you. How many hashes are in a "share"?
|
|
|
|
1) Could you update the System statistics page on bitcoin.cz to show the block we're currently working on as a group?
What specific stats about current block are you missing? Block history table is, ehrm, block _history_. Operational stats are above. Btw next block number is in my opinion non-relevant for pool stats. I'm not doubting you, but I noticed a few days ago that *after* the pool got a block, that my bitcoin client didn't get an update that the block was solved for ~4-5 minutes. I'm just wondering if the opposite could also happen, hence, it be nice to know what block the pool is currently working on.
2) If the current block is 100,084 and it is solved by someone else, the next network block would be 100,085. Does that information get updated with the group or are we all still crunching away @ block 100,084?
Of course miners have up to date information. Miners are asking pool approximately every 5 seconds for new job to crunch. I thought so, but I just wanted to be sure. |
|
|
|
|
Slush, got two questions for you.
1) Could you update the System statistics page on bitcoin.cz to show the block we're currently working on as a group?
2) If the current block is 100,084 and it is solved by someone else, the next network block would be 100,085. Does that information get updated with the group or are we all still crunching away @ block 100,084?
I had 3.48 bitcoins when I woke up today! Thanks for the awesome work!
|
|
|
|
Hello. I looked through this thread and can't find the download link for this client. Repost please?  Thank you. |
|
|
|
|
This is a cross thread posting. Sorry in advance.
The amount of bitcoin's being reported since the update from about a week or so ago seems to be cut in half. This was brought up before and it was quickly disregarded. So now I'm asking the other people that are running clients that are contributing to the pool to look at their numbers and see if it's off for you too.
Here we go.
Here's the numbers being reported @ the time of writing this.
Server Status : 96 clients, 203464 khash/s
Address <removed> will receive 8.10162 BTC if this block is solved
I have a total of eight remote mining instances running.
8733+9600+8733+9600+8966+9600+7833+12366 = 75,431 khash/s between my two boxes which is CPU's and GPU's combined.
75,431 khashes (my systems) / 203,464 (server khash/s) = 0.3707338890417961
0.3707338890417961 * 100 = %37.07338890417961
That's about %37.07 (0.3707.. * 100) of the total khash/s that the server is reporting.
Now we show what %37.07 of 50 bitcoins should be.
For every 1% of a block (50 bitcoins) is 0.5 bitcoins.
50(bitcoins/block) / 100(%) = 0.5 (bitcoins/block)
0.5 * 37.07% = 18.535 bitcoins
WHY AM I ONLY GETTING "8.10162 BTC if this block is solved"? I should be getting 18.535, which is about what I saw before the update a week ago. I know there has been talk about distribution methods, but I don't care what you call it when the math is wrong and the amount paid out and is far less than what it should be. If been contributing to the pool non-stop since it started. I even crashed the server a few times because by throwing about 64 CPU's and 3 GPU's at it, but now I'm back to 6 CPU's and 3 GPU's.
It was very obvious when this happened because the amount of BTC I would receive was at least cut in half.
Here's a some tables for others to quickly look up about what range they should be getting back.
To get a percentage use this equation: (your khash/s) divided by (server khash/s) then multiply it by 100.
CPU USERS LOOK HERE
BITCOINS PER PERCENTAGE (%.05 increments) BETWEEN 0.01% and 1.00%
50 * 0.01% = 0.005 bitcoins
50 * 0.05% = 0.025 bitcoins
50 * 0.10% = 0.050 bitcoins
50 * 0.15% = 0.075 bitcoins
50 * 0.20% = 0.100 bitcoins
50 * 0.25% = 0.125 bitcoins
50 * 0.30% = 0.150 bitcoins
50 * 0.35% = 0.175 bitcoins
50 * 0.40% = 0.200 bitcoins
50 * 0.45% = 0.225 bitcoins
50 * 0.50% = 0.250 bitcoins
50 * 0.55% = 0.275 bitcoins
50 * 0.60% = 0.300 bitcoins
50 * 0.65% = 0.325 bitcoins
50 * 0.70% = 0.350 bitcoins
50 * 0.75% = 0.375 bitcoins
50 * 0.80% = 0.400 bitcoins
50 * 0.85% = 0.425 bitcoins
50 * 0.90% = 0.450 bitcoins
50 * 0.95% = 0.475 bitcoins
50 * 1.00% = 0.500 bitcoins
GPU USER'S LOOK HERE
BITCOINS PER PERCENTAGE (%5 increments) BETWEEN 1% and 100%
-------------------------------------------
50 * 1% = 0.5 bitcoins
50 * 5% = 2.5 bitcoins
50 * 10% = 5 bitcoins
50 * 15% = 7.5 bitcoins
50 * 20% = 10 bitcoins
50 * 25% = 12.5 bitcoins
50 * 30% = 15 bitcoins
50 * 35% = 17.5 bitcoins
50 * 40% = 20 bitcoins
50 * 45% = 22.5 bitcoins
50 * 50% = 25 bitcoins
50 * 55% = 27.5 bitcoins
50 * 60% = 30 bitcoins
50 * 65% = 32.5 bitcoins
50 * 70% = 35 bitcoins
50 * 75% = 37.5 bitcoins
50 * 80% = 40 bitcoins
50 * 85% = 42.5 bitcoins
50 * 90% = 45 bitcoins
50 * 95% = 47.5 bitcoins
50 * 100% = 50 bitcoins
IS ANYONE ELSE SEEING THIS, OR HAVING I COMPLETELY LOST MY MIND?
|
|
|
|
WHY AM I ONLY GETTING "8.10162 BTC if this block is solved"? I should be getting 18.535, which is about what I saw before the update a week ago. I know there has been talk about distribution methods, but I don't care what you call it when the math is wrong and the amount paid out and is far less than what it should be.
The server is running the contributed method. This means each user gets a portion based on the actual number of hashes contributed. So if the pool was running for 2 days and your miners have only been running for 12 hours then you haven't contributed anywhere near the number of hashes as your percentage of the current hash value of the pool. You should be seeing the amount of BTC you would earn slowly increasing over time if you joined the pool recently. I've been at it since you put the server up. Hrm...so what happens to the counter that says how much I've contributed after the server crashes and get's restarted? |
|
|
|
I considered doing this but ended up taking the easy path of just distributing puddinpop's binaries directly. Oh really? Thank you for clarifying that. I can't seem to locate the original URL for his binaries. Could you share that please? |
|
|
|
Let me be clear about the following. Doublec, I'm not focusing on you here, and I do thank you for running the first set of servers. I fully understand the cost of running servers, and can appreciate you letting everyone hammer on it while we run this experimental/buggy code. That being said, I know this has been brought this up before, and now it is being brought up again. The amount of bitcoin's being reported since the update from about a week or so ago seems to be cut in half. This was brought up before and it was quickly disregarded. So now I'm asking the other people that are running clients that are contributing to the pool to look at their numbers and see if it's off for you too. Here we go. Here's the numbers being reported @ the time of writing this. Server Status : 96 clients, 203464 khash/s Address <removed> will receive 8.10162 BTC if this block is solved I have a total of eight remote mining instances running. 8733+9600+8733+9600+8966+9600+7833+12366 = 75,431 khash/s between my two boxes which is CPU's and GPU's combined. 75,431 khashes (my systems) / 203,464 (server khash/s) = 0.3707338890417961 0.3707338890417961 * 100 = %37.07338890417961 That's about %37.07 (0.3707.. * 100) of the total khash/s that the server is reporting. Now we show what %37.07 of 50 bitcoins should be. For every 1% of a block (50 bitcoins) is 0.5 bitcoins. 50(bitcoins/block) / 100(%) = 0.5 (bitcoins/block) 0.5 * 37.07% = 18.535 bitcoins WHY AM I ONLY GETTING "8.10162 BTC if this block is solved"? I should be getting 18.535, which is about what I saw before the update a week ago. I know there has been talk about distribution methods, but I don't care what you call it when the math is wrong and the amount paid out and is far less than what it should be. Here's a some tables for other to quickly look up about what range they should be getting back. To get a percentage use this equation: (your khash/s) divided by (server khash/s) then multiply it by 100. CPU USERS LOOK HERE BITCOINS PER PERCENTAGE (%.05 increments) BETWEEN 0.01% and 1.00% 50 * 0.01% = 0.005 bitcoins 50 * 0.05% = 0.025 bitcoins 50 * 0.10% = 0.050 bitcoins 50 * 0.15% = 0.075 bitcoins 50 * 0.20% = 0.100 bitcoins 50 * 0.25% = 0.125 bitcoins 50 * 0.30% = 0.150 bitcoins 50 * 0.35% = 0.175 bitcoins 50 * 0.40% = 0.200 bitcoins 50 * 0.45% = 0.225 bitcoins 50 * 0.50% = 0.250 bitcoins 50 * 0.55% = 0.275 bitcoins 50 * 0.60% = 0.300 bitcoins 50 * 0.65% = 0.325 bitcoins 50 * 0.70% = 0.350 bitcoins 50 * 0.75% = 0.375 bitcoins 50 * 0.80% = 0.400 bitcoins 50 * 0.85% = 0.425 bitcoins 50 * 0.90% = 0.450 bitcoins 50 * 0.95% = 0.475 bitcoins 50 * 1.00% = 0.500 bitcoins GPU USER'S LOOK HERE BITCOINS PER PERCENTAGE (%5 increments) BETWEEN 1% and 100% ------------------------------------------- 50 * 1% = 0.5 bitcoins 50 * 5% = 2.5 bitcoins 50 * 10% = 5 bitcoins 50 * 15% = 7.5 bitcoins 50 * 20% = 10 bitcoins 50 * 25% = 12.5 bitcoins 50 * 30% = 15 bitcoins 50 * 35% = 17.5 bitcoins 50 * 40% = 20 bitcoins 50 * 45% = 22.5 bitcoins 50 * 50% = 25 bitcoins 50 * 55% = 27.5 bitcoins 50 * 60% = 30 bitcoins 50 * 65% = 32.5 bitcoins 50 * 70% = 35 bitcoins 50 * 75% = 37.5 bitcoins 50 * 80% = 40 bitcoins 50 * 85% = 42.5 bitcoins 50 * 90% = 45 bitcoins 50 * 95% = 47.5 bitcoins 50 * 100% = 50 bitcoins IS ANYONE ELSE SEEING THIS, OR HAVING I COMPLETELY LOST MY MIND? |
|
|
|
I got 3 GPU's (two GTX 470 and one GTX 260), 2 CPU's (one AMD Quad-Core and one Intel Dual-Core) throwing a combined total of ~71,000 khash/s into the pool (~35%). I could throw more at it, but last time I did that it crashed the server.....whoops. The pool is running @ ~208037 khash/s while writing this. Yet, since it's inception, this pool has only gotten 1 block while several hundred blocks have been solved? What's going on here?  Really, this is just nuts that all these clients and we still can't get more blocks. I've heard rumor there is someone with 20-30 GPU's crunching away at this, and if that's the case then even a pooled effort is still going to be several 100,000 khash/s behind that guy. Is the server running bitcoind with a CPU or GPU? If it's not running with a GPU, I'm willing to try using one of my my system's as a server and see if having a GPU helps reach more than 208,037 khash/s and/or handle several hundred clients (avoiding the 102 limit). |
|
|
|
Does that also work for running a server on Windows?
Yes, except replace 'bitcoinr' with 'remoteminer-cpu.exe' or 'remoteminer-cuda.exe'. Got it working. Was missing the "-gen" and it didn't want to run. Added "-gen" and it's find now. Thanks! |
|
|
|
To run a server on linux: bitcoind -remoteserver -remotebindaddr=0.0.0.0 -remotebindport=8335 -gen Note the 'remotebindaddr'. This is what makes the server accessible over the internet by other clients. To run clients: bitcoinr -server=ip.addr.of.server -address=bitcoinaddress Does that also work for running a server on Windows? |
|
|
|
Q: How would one go about running their own mining server? I read the readme and tried to setup my own mining server, but it doesn't seem to be acting like a server. I tried the "-remoteserver" flag, but it doesn't take it. Could someone please provide an example of what command and options I would use to start a mining server? Also an example of the what client's would have to run to connect to my server. Thanks! |
|
|
|
|
puddinpop, what's the URL we can get this from?
|
|
|
|
|
You mentioned previously that your server was running 80-100% CPU. Is it possible that there could be too many clients now and the server is just under heavy load?
I saw the number of clients in the 180's earlier with the group doing ~200,000 khash/s.
|
|
|
|
|
Status update: Offline again. Traceroute seems fine though.
|
|
|
|
|
Yeah, I'm starting to see that too. It's jumping between 433 and 1633 for me.
Should be averaging around 833 typically.
Odd indeed.
|
|
|
|
|
Show Posts
