Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 153. (Read 458255 times)
March 17, 2012, 01:45:47 PM
Finally got around to removing the old debug info ("fee"), so now Eligius is completely fee-free (as of midnight UTC tonight).
March 05, 2012, 09:28:12 PM
CPU usage was hardly being touched when I looked at top. This was an Ubuntu guest on an ESXi host (HP DL380 G5).
Sure thing. I'll make one in a bit.
Sure thing. I'll make one in a bit.
March 05, 2012, 05:38:20 PM
I tried this yesterday (which is why I was asking). I changed the listener IP in the python script and connected my rigs. One rig worked just fine, but when I added more machines, cgminer couldn't get work quickly enough and kept disconnecting/reconnecting from/to the proxy. I only tested it for a short time though before going to bed.
Hmm, not sure what might cause that. How's it look on CPU usage? Can you create me a pcap file?Code:
tcpdump -i any -s0 -w pcap port 8337 or port 9332
March 05, 2012, 05:15:56 PM
I tried this yesterday (which is why I was asking). I changed the listener IP in the python script and connected my rigs. One rig worked just fine, but when I added more machines, cgminer couldn't get work quickly enough and kept disconnecting/reconnecting from/to the proxy. I only tested it for a short time though before going to bed.
March 05, 2012, 11:41:12 AM
Sure enough, 3.1.4 works. Weird.
Is this proxy meant to run an individual copy on each miner? In other words, it's not meant to run one instance with multiple miners?
It should be fine with multiple miners, but it only supports one upstream username. Is this proxy meant to run an individual copy on each miner? In other words, it's not meant to run one instance with multiple miners?
March 05, 2012, 01:05:41 AM
Sure enough, 3.1.4 works. Weird.
Is this proxy meant to run an individual copy on each miner? In other words, it's not meant to run one instance with multiple miners?
Is this proxy meant to run an individual copy on each miner? In other words, it's not meant to run one instance with multiple miners?
March 04, 2012, 09:22:14 PM
Hmmm... I was using 3.2.2. Perhaps I should try an earlier version?
I'm not sure what version introduced the bug. Just that 3.1.4 is bug-free. March 04, 2012, 09:21:38 PM
Hmmm... I was using 3.2.2. Perhaps I should try an earlier version?
March 04, 2012, 08:53:30 PM
Hey Luke. I was giving gmp-proxy a try and ran into a snag. The server starts fine, but as soon as a mining client connects, I get an error regarding string conversion. I'm fairly certain I have everything configured correctly (unless the newest git isn't supposed to be used against Eligius yet?):
This is a bug in CPython. It's fixed in git, and at least in 3.1.4. Code:
ERROR:JSONRPCHandler:Error during JSON-RPC call: doJSON_getwork[]
Traceback (most recent call last):
File "/tmp/eloipool/jsonrpcserver.py", line 156, in _doJSON_i
rv = getattr(self, method)(*params)
File "/tmp/eloipool/jsonrpc_getwork.py", line 40, in doJSON_getwork
hdr = self.server.getBlockHeader(self.Username)
File "gmp-proxy.py", line 67, in MakeWork
MRD = getMRD()
File "gmp-proxy.py", line 47, in getMRD
MRD = makeMRD(mp)
File "gmp-proxy.py", line 26, in makeMRD
coinbase = a2b_hex(mp['coinbasetxn'])
TypeError: 'str' does not support the buffer interface
Traceback (most recent call last):
File "/tmp/eloipool/jsonrpcserver.py", line 156, in _doJSON_i
rv = getattr(self, method)(*params)
File "/tmp/eloipool/jsonrpc_getwork.py", line 40, in doJSON_getwork
hdr = self.server.getBlockHeader(self.Username)
File "gmp-proxy.py", line 67, in MakeWork
MRD = getMRD()
File "gmp-proxy.py", line 47, in getMRD
MRD = makeMRD(mp)
File "gmp-proxy.py", line 26, in makeMRD
coinbase = a2b_hex(mp['coinbasetxn'])
TypeError: 'str' does not support the buffer interface
March 04, 2012, 08:02:28 PM
Hey Luke. I was giving gmp-proxy a try and ran into a snag. The server starts fine, but as soon as a mining client connects, I get an error regarding string conversion. I'm fairly certain I have everything configured correctly (unless the newest git isn't supposed to be used against Eligius yet?):
Code:
ERROR:JSONRPCHandler:Error during JSON-RPC call: doJSON_getwork[]
Traceback (most recent call last):
File "/tmp/eloipool/jsonrpcserver.py", line 156, in _doJSON_i
rv = getattr(self, method)(*params)
File "/tmp/eloipool/jsonrpc_getwork.py", line 40, in doJSON_getwork
hdr = self.server.getBlockHeader(self.Username)
File "gmp-proxy.py", line 67, in MakeWork
MRD = getMRD()
File "gmp-proxy.py", line 47, in getMRD
MRD = makeMRD(mp)
File "gmp-proxy.py", line 26, in makeMRD
coinbase = a2b_hex(mp['coinbasetxn'])
TypeError: 'str' does not support the buffer interface
Traceback (most recent call last):
File "/tmp/eloipool/jsonrpcserver.py", line 156, in _doJSON_i
rv = getattr(self, method)(*params)
File "/tmp/eloipool/jsonrpc_getwork.py", line 40, in doJSON_getwork
hdr = self.server.getBlockHeader(self.Username)
File "gmp-proxy.py", line 67, in MakeWork
MRD = getMRD()
File "gmp-proxy.py", line 47, in getMRD
MRD = makeMRD(mp)
File "gmp-proxy.py", line 26, in makeMRD
coinbase = a2b_hex(mp['coinbasetxn'])
TypeError: 'str' does not support the buffer interface
February 28, 2012, 10:12:35 PM
This is interesting but I don't understand the low level details. Does this imply that mining this way with the proxy achieves the same independence as p2p or solo regarding 51% attacks and/or voting?
51% attacks, yes, provided enough users choose to audit the blocks."voting": in theory, but supporting it on Eligius would be a lot of work for effectively nothing (BIP 16 sucks, and it'll probably be over within a month anyway)
February 28, 2012, 10:02:44 PM
This is interesting but I don't understand the low level details. Does this imply that mining this way with the proxy achieves the same independence as p2p or solo regarding 51% attacks and/or voting?
February 28, 2012, 09:44:00 PM
Also, Eligius now supports longpolling for getmemorypool, and I have posted an initial draft-draft of a BIP for getmemorypool on the Bitcoin Wiki.
Correct me if I am wrong, but what this means to the miners is that they now have a way to verify that the work they have done is being reflected in the blocks that the pool produces. This is a good improvement if implemented widely, but for now needs somewhat manual checking.
February 28, 2012, 09:40:36 PM
Also, Eligius now supports longpolling for getmemorypool, and I have posted an initial draft-draft of a BIP for getmemorypool on the Bitcoin Wiki.
Correct me if I am wrong, but what this means to the miners is that they now have a way to verify that the work they have done is being reflected in the blocks that the pool produces. This is a good improvement if implemented widely, but for now needs somewhat manual checking. February 28, 2012, 09:03:49 PM
Also, Eligius now supports longpolling for getmemorypool, and I have posted an initial draft-draft of a BIP for getmemorypool on the Bitcoin Wiki.
February 28, 2012, 08:56:18 PM
What do you mean by DECENTRALIZED?
The same way as p2pool: miners can make their own work. February 28, 2012, 08:50:38 PM
What do you mean by DECENTRALIZED?
Is this a lie ? Eligius can't be decnetralized,seriously.
Is this a lie ? Eligius can't be decnetralized,seriously.
February 28, 2012, 11:16:53 AM
I am satisfied that getmemorypool is working, so it has been promoted to non-testing. Here are some simple setup instructions for Linux. Note that this does not support longpolling yet, so there may be high stales.
February 24, 2012, 03:26:02 PM
I have written a short (57 line) one-user proof-of-concept getmemorypool proxy, and included it in Eloipool's serve_getmemorypool branch. By using this locally, you can add code to audit the blocks in any way you want. Due to Eligius currently requiring the "test_" prefix, you will need to add it to the gmp-proxy.py file (prepend "getmemorypool" and "submitblock"). Please contact me on IRC if you would like to help take this to the next level.
To use (after the edits just mentioned), just runThen connect your miner to localhost on port 9332
Edit: Note that this uses Eloipool's JSONRPCServer class, which I optimized to handle heavy loads. Unfortunately, there is no way to do this in a Windows-compatible manner, so this gmp-proxy.py will not work on Windows yet. It might be possible to grab an old thread-based JSONRPCServer from earlier Eloipool versions, but I haven't tried it.
To use (after the edits just mentioned), just run
Code:
./gmp-proxy.py http://youraddress:[email protected]:8337
Edit: Note that this uses Eloipool's JSONRPCServer class, which I optimized to handle heavy loads. Unfortunately, there is no way to do this in a Windows-compatible manner, so this gmp-proxy.py will not work on Windows yet. It might be possible to grab an old thread-based JSONRPCServer from earlier Eloipool versions, but I haven't tried it.
February 23, 2012, 03:57:50 PM
For testing purposes only (ie, I don't guarantee this works yet), Eligius now supports getmemorypool-based mining. Currently, miners are not allowed to modify anything except nonce/ntime, but it does at least enable auditing what goes into the blocks you're working on in realtime (and possibly switching to another pool if anything looks awry).
Since this is untested, and not supported by any miner (as far as I know), I have renamed the JSON-RPC method to "test_getmemorypool" for now; please get in touch with me on IRC if you want to work on a miner/proxy implementing this. Probably the best starting points for implementing a proxy are either the p2pool client (Python2/Twisted) or the BitPenny client (C++).
See also for technical details: Alternative to getwork for miners/proxies
Since this is untested, and not supported by any miner (as far as I know), I have renamed the JSON-RPC method to "test_getmemorypool" for now; please get in touch with me on IRC if you want to work on a miner/proxy implementing this. Probably the best starting points for implementing a proxy are either the p2pool client (Python2/Twisted) or the BitPenny client (C++).
See also for technical details: Alternative to getwork for miners/proxies
Jump to: