Сделал п2пулы для добычи DGB на алгоримах GROESTL, QUBIT и SHA256D: DGB форум: DigiByte(GROESTL) P2Pool: http://crypto.office-on-the.net:5021 || http://crypto.mine.nu:5021sgminer --algorithm myriadcoin-groestl -o stratum+tcp://crypto.office-on-the.net:5021 -u DigiByteAddress -p x --expiry 1 --scan-time 1 --queue 0 --no-extranonce or sgminer --algorithm myriadcoin-groestl -o stratum+tcp://crypto.mine.nu:5021 -u DigiByteAddress -p x --expiry 1 --scan-time 1 --queue 0 --no-extranonce DGB Форум: DigiByte(QUBIT) P2Pool: http://crypto.office-on-the.net:5023 || http://crypto.mine.nu:5023sgminer --algorithm qubitcoin -o stratum+tcp://crypto.office-on-the.net:5023 -u Your_DGB_address -p x --expiry 1 --scan-time 1 --queue 0 --no-extranonce or sgminer --algorithm qubitcoin -o stratum+tcp://crypto.mine.nu:5023 -u Your_DGB_address -p x --expiry 1 --scan-time 1 --queue 0 --no-extranonce DGB форум: DigiByte(SHA256D) P2Pool: http://crypto.office-on-the.net:5027 || http://crypto.mine.nu:5027cgminer -o stratum+tcp://crypto.office-on-the.net:5027 -u Your_DGB_address -p x --expiry 1 --scan-time 1 --queue 0 or cgminer -o stratum+tcp://crypto.mine.nu:5027 -u Your_DGB_address -p x --expiry 1 --scan-time 1 --queue 0
|
|
|
Добавил ноду для добычи DGB на алгориме QUBIT: DGB Форум: DigiByte(QUBIT) P2Pool: http://crypto.office-on-the.net:5023 || http://crypto.mine.nu:5023sgminer --algorithm qubitcoin -o stratum+tcp://crypto.office-on-the.net:5023 -u Your_DGB_address -p x --expiry 1 --scan-time 1 --queue 0 --no-extranonce or sgminer --algorithm qubitcoin -o stratum+tcp://crypto.mine.nu:5023 -u Your_DGB_address -p x --expiry 1 --scan-time 1 --queue 0 --no-extranonce
|
|
|
Added a pool for mining DGB with the algorithm QUBIT: DGB Forum: DigiByte(QUBIT) P2Pool: http://crypto.office-on-the.net:5023 || http://crypto.mine.nu:5023sgminer --algorithm qubitcoin -o stratum+tcp://crypto.office-on-the.net:5023 -u Your_DGB_address -p x --expiry 1 --scan-time 1 --queue 0 --no-extranonce or sgminer --algorithm qubitcoin -o stratum+tcp://crypto.mine.nu:5023 -u Your_DGB_address -p x --expiry 1 --scan-time 1 --queue 0 --no-extranonce
|
|
|
sawa, I didn't touch any code related to the json-rpc stuff. My guess is that this is a recently introduced bug on the miningrigrentals end. It seems that they're appending an extra parameter on their share submission messages. Have you tried the same rentals on mainnet recently? My guess is that you'd see the same issue.
On any nodes the same error. I tested a DGB node http://crypto.mine.nu:5027 based on the mainnet code. When I got the error, I tried to switch the lease to the mainnet BTC http://crypto.office-on-the.net:9332 and to the fork http://crypto.office-on-the.net:9334. The reaction of the nodes was the same everywhere - they reported an incorrect number of arguments. You could also try packet sniffing (e.g. with tcpdump -X port 9332) to see what parameters they're sending; they might just be using some stratum extension that p2pool doesn't yet support. If we know what extra data they're sending, we might be able to patch p2pool to support it (or, if it's safe, to ignore it).
I sent a tcpdump to your email
|
|
|
I tried renting rigs at https://www.miningrigrentals.comMany devices do not even begin to mining: https://www.miningrigrentals.com/rigs/35897https://www.miningrigrentals.com/rigs/35744https://www.miningrigrentals.com/rigs/35949In the p2pool screen, I see the messages: Squelched JSON error: Traceback (most recent call last): File "/usr/local/lib/pypy2.7/dist-packages/twisted/protocols/basic.py", line 454, in dataReceived self.lineReceived(line) File "/opt/sha256d/p2pool-btc-fork/p2pool/util/jsonrpc.py", line 164, in lineReceived _handle(line, self, response_handler=self._matcher.got_response).addCallback(lambda line2: self.sendLine(line2) if line2 is not None else None) File "/usr/local/lib/pypy2.7/dist-packages/twisted/internet/defer.py", line 1447, in unwindGenerator return _inlineCallbacks(None, gen, Deferred()) File "/usr/local/lib/pypy2.7/dist-packages/twisted/internet/defer.py", line 1301, in _inlineCallbacks result = g.send(result) --- <exception caught here> --- File "/opt/sha256d/p2pool-btc-fork/p2pool/util/jsonrpc.py", line 85, in _handle result = yield method_meth(*list(preargs) + list(params)) exceptions.TypeError: rpc_submit() takes exactly 6 arguments (7 given) I last tried renting rigs on mrr half a year ago. At that time, all leased devices were well mined on the p2pools.
|
|
|
п2пул вряд ли. Хотя бы потому что на нём блоки редкие и владельцы нод задирают планку комиссии.
|
|
|
Probably because the pool will not give shares with difficulty less than pool.hws.ru:9327/difficulty
For testing purposes, i found GC3355, people called this a "hedgehog" Same settings, same device, pool is different: I understand, I edited my message. Read it.
|
|
|
Hello, I have a paroblem with the masternoeds. I founded 2 MN and I started them, they are working. Status is "Masternode is Running", 0.5 EXCL are comming. But about per hour is change status "Not in the Masternode list" and it stops working. I must unlock the wallet and starts MN again. Can you tell me why it's falling?
Thank you.
|
|
|
Чаще чем на классике. Сайта со стратистикой блоков по форку я ещё не видел.
|
|
|
|