Search content
Sort by
Showing 20 of 82 results by peoples
Re: GMiner v2.76 Ethash(LHR unlock)/KAWPOW/Equihash/CuckooCycle
@Zminer777
on Rigs with RTXA5000 or RTXA6000 cards -> the first card (index 0) is always around 6 MH/s slower then the rest.
But this only seems to occur on >= 8 GPUs.
Any idea ?
Thanks
on Rigs with RTXA5000 or RTXA6000 cards -> the first card (index 0) is always around 6 MH/s slower then the rest.
But this only seems to occur on >= 8 GPUs.
Any idea ?
Thanks
Re: GMiner v2.75 Ethash(LHR unlock)/KAWPOW/Equihash/CuckooCycle
Hey Gentleman,
are you planing to implement a proper API beside http website ?
Something like JSON that can be easily parsed electronically.
Think that will help for mass adoption and bigger farm implementations.
Thanks
are you planing to implement a proper API beside http website ?
Something like JSON that can be easily parsed electronically.
Think that will help for mass adoption and bigger farm implementations.
Thanks
Re: [ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.0
(16.4.0 / 16.4.1) and Ubuntu 16 = stop working?
...under Ubuntu 18 works ok.
Can you recompile using same libraries than before 16.4.0 or trully stop support Ubuntu16 since 16.4.0?
...under Ubuntu 18 works ok.
Can you recompile using same libraries than before 16.4.0 or trully stop support Ubuntu16 since 16.4.0?
Code:
# lsb_release -r
Release: 16.04
# ldd bminer-v16.4.1/bminer
bminer-v16.4.1/bminer: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.11' not found (required by bminer-v16.4.1/bminer)
bminer-v16.4.1/bminer: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by bminer-v16.4.1/bminer)
bminer-v16.4.1/bminer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by bminer-v16.4.1/bminer)
Release: 16.04
# ldd bminer-v16.4.1/bminer
bminer-v16.4.1/bminer: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.11' not found (required by bminer-v16.4.1/bminer)
bminer-v16.4.1/bminer: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by bminer-v16.4.1/bminer)
bminer-v16.4.1/bminer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by bminer-v16.4.1/bminer)
Code:
# dpkg -l | grep libc
ii libc-bin 2.23-0ubuntu11.2 amd64 GNU C Library: Binaries
ii libc-dev-bin 2.23-0ubuntu11.2 amd64 GNU C Library: Development binaries
ii libc6:amd64 2.23-0ubuntu11.2 amd64 GNU C Library: Shared libraries
ii libc6-dev:amd64 2.23-0ubuntu11.2 amd64 GNU C Library: Development Libraries and Header Files
ii libc-bin 2.23-0ubuntu11.2 amd64 GNU C Library: Binaries
ii libc-dev-bin 2.23-0ubuntu11.2 amd64 GNU C Library: Development binaries
ii libc6:amd64 2.23-0ubuntu11.2 amd64 GNU C Library: Shared libraries
ii libc6-dev:amd64 2.23-0ubuntu11.2 amd64 GNU C Library: Development Libraries and Header Files
any info on that one @realbminer ?
Hey guys,
does someone know if its possible to change the ratio of how much power a card is drawing from the PCIe slot vs the additional 6 or 8 Pin power connector ?
Talking about Polaris (470 / 580 / ...) and Navi platform (5700)
und linux.
Thanks in advance .
cheers
does someone know if its possible to change the ratio of how much power a card is drawing from the PCIe slot vs the additional 6 or 8 Pin power connector ?
Talking about Polaris (470 / 580 / ...) and Navi platform (5700)
und linux.
Thanks in advance .
cheers
Re: PhoenixMiner 4.8c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
@PhoenixMiner
tested v 4.8c on some of my rigs.
Receiving the follwoing error after a few minutes:
any idea?
Thanks
tested v 4.8c on some of my rigs.
Receiving the follwoing error after a few minutes:
Quote
terminate called after throwing an instance of 'R1IgD9eDOLARi3qceHb'
what(): Value is not convertible to Int.
Aborted (core dumped)
what(): Value is not convertible to Int.
Aborted (core dumped)
any idea?
Thanks
no one else seeing this error ?
Re: PhoenixMiner 4.8c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
@PhoenixMiner
tested v 4.8c on some of my rigs.
Receiving the follwoing error after a few minutes:
any idea?
Thanks
tested v 4.8c on some of my rigs.
Receiving the follwoing error after a few minutes:
Quote
terminate called after throwing an instance of 'R1IgD9eDOLARi3qceHb'
what(): Value is not convertible to Int.
Aborted (core dumped)
what(): Value is not convertible to Int.
Aborted (core dumped)
any idea?
Thanks
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.6 (Windows/Linux)
ok thanks. Is working with command line.
Is
Is
Code:
ALLCOINS: 1,
recognised by epools.txt ? It is set in my epools.txt on that pool but seems to be ignored.-allcoins is global option so you cannot set it per pool in epools.txt, it must be used only in command line or in config.txt.
alright .. thanks!
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.6 (Windows/Linux)
@Claymore
i'm trying to run v14.6 against my testpool ( ropsten network ) but doesn't work
i'm trying to run v14.6 against my testpool ( ropsten network ) but doesn't work
Code:
...
15:16:38:510 a9ff3700 Probably you are trying to mine Ethereum fork. Please specify "-allcoins 1" or "-allpools 1" option. Check "Readme" file for details.
...
15:16:38:510 a9ff3700 Probably you are trying to mine Ethereum fork. Please specify "-allcoins 1" or "-allpools 1" option. Check "Readme" file for details.
...
If you want to mine some ETH fork, always specify "-allcoins 1", it will work in all versions. If you don't do it, it may work in some old versions and won't work in recent versions.
ok thanks. Is working with command line.
Is
Code:
ALLCOINS: 1,
recognised by epools.txt ? It is set in my epools.txt on that pool but seems to be ignored.Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.6 (Windows/Linux)
@Claymore
i'm trying to run v14.6 against my testpool ( ropsten network ) but doesn't work
v12 version works without a problem on same testpool
i'm trying to run v14.6 against my testpool ( ropsten network ) but doesn't work
Code:
15:16:38:498 a9ff3700 ETH: Stratum - connecting to '10.0.0.26' <10.0.0.26> port 3073 (unsecure)
15:16:38:499 a9ff3700 sent: {"id": 1, "method": "mining.subscribe", "params": ["MinerName/1.0.0", "EthereumStratum/1.0.0"]}
15:16:38:499 a9ff3700 sent: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
15:16:38:499 a9ff3700 sent: {"id": 2, "method": "mining.authorize", "params": ["0x95BceE412F075A528x46767F8aA5A9e28D7AEd25","x"]}
15:16:38:499 a9ff3700 ETH: Stratum - Connected (10.0.0.26:3073) (unsecure)
15:16:38:509 a9ff3700 buf: {"result":[["mining.notify","0HLN9MS76RPEB","EthereumStratum/1.0.0"],"5e6e"],"error":null,"id":1}
{"result":false,"error":{"code":20,"message":"not supported","data":null},"id":5}
{"result":true,"error":null,"id":2}
{"jsonrpc":"2.0","method":"mining.set_difficulty","params":[0.93],"id":null}
{"jsonrpc":"2.0","method":"mining.notify","params":["0000002c","c906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","6d3e225102950af7638fec08410662faf16e2534c1d611cb5f9e390728cbc10b",true],"id":null}
15:16:38:509 a9ff3700 remove first packet 408
15:16:38:510 a9ff3700 remove first packet 327
15:16:38:510 a9ff3700 ETH: Authorized
15:16:38:510 a9ff3700 remove first packet 291
15:16:38:510 a9ff3700 remove first packet 214
15:16:38:510 a9ff3700 epoch #191
15:16:38:510 a9ff3700 Probably you are trying to mine Ethereum fork. Please specify "-allcoins 1" or "-allpools 1" option. Check "Readme" file for details.
15:16:38:510 a9ff3700 Pool sent wrong data, cannot set epoch, disconnect
15:16:38:510 a9ff3700 ETH: Connection lost, retry in 20 sec...
15:16:38:598 1fd7740 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
15:16:38:598 1fd7740 ETH: nicehash stratum mode
15:16:38:499 a9ff3700 sent: {"id": 1, "method": "mining.subscribe", "params": ["MinerName/1.0.0", "EthereumStratum/1.0.0"]}
15:16:38:499 a9ff3700 sent: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
15:16:38:499 a9ff3700 sent: {"id": 2, "method": "mining.authorize", "params": ["0x95BceE412F075A528x46767F8aA5A9e28D7AEd25","x"]}
15:16:38:499 a9ff3700 ETH: Stratum - Connected (10.0.0.26:3073) (unsecure)
15:16:38:509 a9ff3700 buf: {"result":[["mining.notify","0HLN9MS76RPEB","EthereumStratum/1.0.0"],"5e6e"],"error":null,"id":1}
{"result":false,"error":{"code":20,"message":"not supported","data":null},"id":5}
{"result":true,"error":null,"id":2}
{"jsonrpc":"2.0","method":"mining.set_difficulty","params":[0.93],"id":null}
{"jsonrpc":"2.0","method":"mining.notify","params":["0000002c","c906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","6d3e225102950af7638fec08410662faf16e2534c1d611cb5f9e390728cbc10b",true],"id":null}
15:16:38:509 a9ff3700 remove first packet 408
15:16:38:510 a9ff3700 remove first packet 327
15:16:38:510 a9ff3700 ETH: Authorized
15:16:38:510 a9ff3700 remove first packet 291
15:16:38:510 a9ff3700 remove first packet 214
15:16:38:510 a9ff3700 epoch #191
15:16:38:510 a9ff3700 Probably you are trying to mine Ethereum fork. Please specify "-allcoins 1" or "-allpools 1" option. Check "Readme" file for details.
15:16:38:510 a9ff3700 Pool sent wrong data, cannot set epoch, disconnect
15:16:38:510 a9ff3700 ETH: Connection lost, retry in 20 sec...
15:16:38:598 1fd7740 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
15:16:38:598 1fd7740 ETH: nicehash stratum mode
v12 version works without a problem on same testpool
Code:
15:09:34:985 78ff9700 ETH: Stratum - connecting to '10.0.0.26' <10.0.0.26> port 3073 (unsecure)
15:09:34:986 78ff9700 sent: {"id": 1, "method": "mining.subscribe", "params": ["MinerName/1.0.0", "EthereumStratum/1.0.0"]}
15:09:34:986 78ff9700 sent: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
15:09:34:986 78ff9700 sent: {"id": 2, "method": "mining.authorize", "params": ["0x95BceE412F075A528x46767F8aA5A9e28D7AEd25","x"]}
15:09:34:986 78ff9700 ETH: Stratum - Connected (10.0.0.26:3073) (unsecure)
15:09:35:129 78ff9700 buf: {"result":[["mining.notify","0HLN9MS76RPEA","EthereumStratum/1.0.0"],"5e6d"],"error":null,"id":1}
15:09:35:140 78ff9700 buf: {"result":false,"error":{"code":20,"message":"not supported","data":null},"id":5}
{"result":true,"error":null,"id":2}
15:09:35:140 78ff9700 remove first packet 36
15:09:35:140 78ff9700 ETH: Authorized
15:09:35:150 78ff9700 buf: {"jsonrpc":"2.0","method":"mining.set_difficulty","params":[0.93],"id":null}
{"jsonrpc":"2.0","method":"mining.notify","params":["00000001","c906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","becb7a52c410c81ad506d3fcedd1b45b7022cd68466ab8c1f5c990860d90b12f",true],"id":null}
15:09:35:150 78ff9700 remove first packet 214
15:09:35:153 a115d700 Setting DAG epoch #191...
15:09:37:810 a115d700 Setting DAG epoch #191 for GPU0
15:09:42:934 78ff9700 buf: {"jsonrpc":"2.0","method":"mining.notify","params":["00000002","c906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","3379398437be2c6ce263844f86288b00a740af551488edbc84b79ce7f3a7bca7",true],"id":null}
15:09:42:934 78ff9700 ETH: 06/05/19-15:09:42 - New job from 10.0.0.26:3073
15:09:42:936 78ff9700 target: 0x000000011343bdef (diff: 3994MH), epoch 191(2.49GB)
15:09:42:936 78ff9700 gpu #2 dt 3.14 (1%, good)
15:09:42:936 78ff9700 ETH - Total Speed: 0.000 Mh/s, Total Shares: 17, Rejected: 0, Time: 00:05
15:09:42:936 78ff9700 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s, GPU7 0.000 Mh/s
15:09:48:923 78ff9700 buf: {"jsonrpc":"2.0","method":"mining.notify","params":["00000003","c906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","b210d4586d3fe34f0a0fa6472fe3995838e2129541341b3dbbc10a758ea47f77",true],"id":null}
15:09:48:925 78ff9700 ETH: 06/05/19-15:09:48 - New job from 10.0.0.26:3073
15:09:48:925 78ff9700 target: 0x000000011343bdef (diff: 3994MH), epoch 191(2.49GB)
15:09:34:986 78ff9700 sent: {"id": 1, "method": "mining.subscribe", "params": ["MinerName/1.0.0", "EthereumStratum/1.0.0"]}
15:09:34:986 78ff9700 sent: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}
15:09:34:986 78ff9700 sent: {"id": 2, "method": "mining.authorize", "params": ["0x95BceE412F075A528x46767F8aA5A9e28D7AEd25","x"]}
15:09:34:986 78ff9700 ETH: Stratum - Connected (10.0.0.26:3073) (unsecure)
15:09:35:129 78ff9700 buf: {"result":[["mining.notify","0HLN9MS76RPEA","EthereumStratum/1.0.0"],"5e6d"],"error":null,"id":1}
15:09:35:140 78ff9700 buf: {"result":false,"error":{"code":20,"message":"not supported","data":null},"id":5}
{"result":true,"error":null,"id":2}
15:09:35:140 78ff9700 remove first packet 36
15:09:35:140 78ff9700 ETH: Authorized
15:09:35:150 78ff9700 buf: {"jsonrpc":"2.0","method":"mining.set_difficulty","params":[0.93],"id":null}
{"jsonrpc":"2.0","method":"mining.notify","params":["00000001","c906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","becb7a52c410c81ad506d3fcedd1b45b7022cd68466ab8c1f5c990860d90b12f",true],"id":null}
15:09:35:150 78ff9700 remove first packet 214
15:09:35:153 a115d700 Setting DAG epoch #191...
15:09:37:810 a115d700 Setting DAG epoch #191 for GPU0
15:09:42:934 78ff9700 buf: {"jsonrpc":"2.0","method":"mining.notify","params":["00000002","c906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","3379398437be2c6ce263844f86288b00a740af551488edbc84b79ce7f3a7bca7",true],"id":null}
15:09:42:934 78ff9700 ETH: 06/05/19-15:09:42 - New job from 10.0.0.26:3073
15:09:42:936 78ff9700 target: 0x000000011343bdef (diff: 3994MH), epoch 191(2.49GB)
15:09:42:936 78ff9700 gpu #2 dt 3.14 (1%, good)
15:09:42:936 78ff9700 ETH - Total Speed: 0.000 Mh/s, Total Shares: 17, Rejected: 0, Time: 00:05
15:09:42:936 78ff9700 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s, GPU7 0.000 Mh/s
15:09:48:923 78ff9700 buf: {"jsonrpc":"2.0","method":"mining.notify","params":["00000003","c906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","b210d4586d3fe34f0a0fa6472fe3995838e2129541341b3dbbc10a758ea47f77",true],"id":null}
15:09:48:925 78ff9700 ETH: 06/05/19-15:09:48 - New job from 10.0.0.26:3073
15:09:48:925 78ff9700 target: 0x000000011343bdef (diff: 3994MH), epoch 191(2.49GB)
could be yes.
But from a pool operator point of view it sill makes sense to run vardiff. Simply to lower or even out server / network load.
With my knowledge so far i don't see any security issue with vardiff on ethereum. But the big pools out there like ethermine / nanopool and dwarfpool don't use vardiff. So i'm curious to know if there is a reason behind it.
But from a pool operator point of view it sill makes sense to run vardiff. Simply to lower or even out server / network load.
With my knowledge so far i don't see any security issue with vardiff on ethereum. But the big pools out there like ethermine / nanopool and dwarfpool don't use vardiff. So i'm curious to know if there is a reason behind it.
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.0 (Windows/Linux)
v14.0 Beta:
- Windows only: added ability to apply optimized memory timings (straps) on-the-fly, without flashing VBIOS, up to 20% speedup compared to stock BIOS. Currently only Polaris cards are supported, other cards will be added later.
Drivers 18.x or newer are required. Best straps for Ethereum are included. Check "-strap" and "-driver" options for details.
- Windows only: added temperature/fan/clocks management for Radeon VII.
- a few minor bug fixes and improvements.
- Windows only: added ability to apply optimized memory timings (straps) on-the-fly, without flashing VBIOS, up to 20% speedup compared to stock BIOS. Currently only Polaris cards are supported, other cards will be added later.
Drivers 18.x or newer are required. Best straps for Ethereum are included. Check "-strap" and "-driver" options for details.
- Windows only: added temperature/fan/clocks management for Radeon VII.
- a few minor bug fixes and improvements.
Any plans to implement this feature for linux version ? (as far as its possible)
Hey,
wondering why all big ethereum pools don't use vardiff ?
I stumbled accross sammy007 comment here: https://github.com/sammy007/open-ethereum-pool/issues/10
Can someone explain me why vardiff on ethereum is a security issue ?
Thanks
regards
wondering why all big ethereum pools don't use vardiff ?
I stumbled accross sammy007 comment here: https://github.com/sammy007/open-ethereum-pool/issues/10
Can someone explain me why vardiff on ethereum is a security issue ?
Thanks
regards
Re: Pool Question: Hashrate distribution and chance to find a Block
alright. Thanks
So as a pool operator/developer one of the most important things is to make sure that every single miner connected to the pool gets different work. ?
Which is controlled by the nonce/extranonce each miner gets, right ?
For my understanding , nonce itself is to small for modern miners anyway and overflows under a second. So miner starts changeing extranonce, which is also just a number that will be incremented?
Question: How is guaranteed that every single miner realy does unique work. ? How is secured that each miner changes nonce and extranonce values differently to make sure no duplicated shares are created.
So as a pool operator/developer one of the most important things is to make sure that every single miner connected to the pool gets different work. ?
Which is controlled by the nonce/extranonce each miner gets, right ?
For my understanding , nonce itself is to small for modern miners anyway and overflows under a second. So miner starts changeing extranonce, which is also just a number that will be incremented?
Question: How is guaranteed that every single miner realy does unique work. ? How is secured that each miner changes nonce and extranonce values differently to make sure no duplicated shares are created.
Pool Question: Hashrate distribution and chance to find a Block
Hey guys,
lets face the following scenarios:
Scenario 1:
* 3 miners each 10 TH/s connect to one Pool Node.
* One work template for all connected miners. (Work template = mining.notify in stratum -> Merkle branch, Coinbase 1/2, ...)
* 3 different nonce for the given work template
10T ---------> | |
10T ---------> |POOL Node 1|
10T ---------> | |
Scenario 2:
* 3 miners each 10 TH/s connect to different Pool Nodes.
* Three different work templates for three miners. ( 3x different Merkle branch )
10T ---------> |POOL Node 1|
10T ---------> |POOL Node 2|
10T ---------> |POOL Node 3|
In both Scenarios the pool nodes belong to the same pool operator and the miners to one customer.
The question: Is the chance to find a block in both scenarios equal or not ?
Short: 30THs hashing on one work templates vs 30THs - 3x 10THs hashing on three different work templates.
lets face the following scenarios:
Scenario 1:
* 3 miners each 10 TH/s connect to one Pool Node.
* One work template for all connected miners. (Work template = mining.notify in stratum -> Merkle branch, Coinbase 1/2, ...)
* 3 different nonce for the given work template
10T ---------> | |
10T ---------> |POOL Node 1|
10T ---------> | |
Scenario 2:
* 3 miners each 10 TH/s connect to different Pool Nodes.
* Three different work templates for three miners. ( 3x different Merkle branch )
10T ---------> |POOL Node 1|
10T ---------> |POOL Node 2|
10T ---------> |POOL Node 3|
In both Scenarios the pool nodes belong to the same pool operator and the miners to one customer.
The question: Is the chance to find a block in both scenarios equal or not ?
Short: 30THs hashing on one work templates vs 30THs - 3x 10THs hashing on three different work templates.
Re: CKPOOL - Open source pool/proxy/passthrough/redirector/library in c for Linux
Does ckpool also adjusts diff down, or in general, is that something that pools do ?
For example miner hashrate drops by 50% in a current session because a hasboard died.
Yes.For example miner hashrate drops by 50% in a current session because a hasboard died.
Great, thanks
Re: CKPOOL - Open source pool/proxy/passthrough/redirector/library in c for Linux
Hey -ck
thanks for your work and sharing of this great piece of pool software.
I played around with your ckpool to learn and better understand mining process.
Now one question (so far) comes up, why does the pool re-adjust the vardiff from scratch for every known client after reconnects / instance takeover (with your -H option) / ...
Doesn't it put alot of stress on a pool server with thousands of clients connected if , for example , you make a instance takeover and all thousand clients start to re-djust vardiff with x shares per second ?
Since you already have per worker information stored, isn't it better to store also last vardiff information and start from there on the next connection of the same worker ?
Thanks
That's a lot of data to hand over, the handover only hands over sockets, not the state of vardiff etc., and all of them will have to reconnect so all the previous connections will be invalid so you won't know who's on which socket after reconnect anyway. Worker names does not equal which socket they're connected to.thanks for your work and sharing of this great piece of pool software.
I played around with your ckpool to learn and better understand mining process.
Now one question (so far) comes up, why does the pool re-adjust the vardiff from scratch for every known client after reconnects / instance takeover (with your -H option) / ...
Doesn't it put alot of stress on a pool server with thousands of clients connected if , for example , you make a instance takeover and all thousand clients start to re-djust vardiff with x shares per second ?
Since you already have per worker information stored, isn't it better to store also last vardiff information and start from there on the next connection of the same worker ?
Thanks
ok got it, thats for handover.
But why not serving previous difficulty after reconnect ?
Example:
1) Miner A with wokerName: MinerA connected and mined for a while on stable diff.
2) pool stores this diff information per worker
3) Miner A disconnects and reconnects after few minutes
4) pool identifies miner by workerName -> gets old diff value from log and serves the stored diff instead of starting new vardiff ramping ?
Very likely that i oversee a detail, like i said -> Learning phase .. so thanks for your answers
Amen ... of course makes sense, worker name is no unique identifier. Thanks for that.
Does ckpool also adjusts diff down, or in general, is that something that pools do ?
For example miner hashrate drops by 50% in a current session because a hasboard died.
Re: CKPOOL - Open source pool/proxy/passthrough/redirector/library in c for Linux
Hey -ck
thanks for your work and sharing of this great piece of pool software.
I played around with your ckpool to learn and better understand mining process.
Now one question (so far) comes up, why does the pool re-adjust the vardiff from scratch for every known client after reconnects / instance takeover (with your -H option) / ...
Doesn't it put alot of stress on a pool server with thousands of clients connected if , for example , you make a instance takeover and all thousand clients start to re-djust vardiff with x shares per second ?
Since you already have per worker information stored, isn't it better to store also last vardiff information and start from there on the next connection of the same worker ?
Thanks
That's a lot of data to hand over, the handover only hands over sockets, not the state of vardiff etc., and all of them will have to reconnect so all the previous connections will be invalid so you won't know who's on which socket after reconnect anyway. Worker names does not equal which socket they're connected to.thanks for your work and sharing of this great piece of pool software.
I played around with your ckpool to learn and better understand mining process.
Now one question (so far) comes up, why does the pool re-adjust the vardiff from scratch for every known client after reconnects / instance takeover (with your -H option) / ...
Doesn't it put alot of stress on a pool server with thousands of clients connected if , for example , you make a instance takeover and all thousand clients start to re-djust vardiff with x shares per second ?
Since you already have per worker information stored, isn't it better to store also last vardiff information and start from there on the next connection of the same worker ?
Thanks
ok got it, thats for handover.
But why not serving previous difficulty after reconnect ?
Example:
1) Miner A with wokerName: MinerA connected and mined for a while on stable diff.
2) pool stores this diff information per worker
3) Miner A disconnects and reconnects after few minutes
4) pool identifies miner by workerName -> gets old diff value from log and serves the stored diff instead of starting new vardiff ramping ?
Very likely that i oversee a detail, like i said -> Learning phase .. so thanks for your answers
Re: CKPOOL - Open source pool/proxy/passthrough/redirector/library in c for Linux
⭐ Merited by vapourminer (1)
Hey -ck
thanks for your work and sharing of this great piece of pool software.
I played around with your ckpool to learn and better understand mining process.
Now one question (so far) comes up, why does the pool re-adjust the vardiff from scratch for every known client after reconnects / instance takeover (with your -H option) / ...
Doesn't it put alot of stress on a pool server with thousands of clients connected if , for example , you make a instance takeover and all thousand clients start to re-djust vardiff with x shares per second ?
Since you already have per worker information stored, isn't it better to store also last vardiff information and start from there on the next connection of the same worker ?
Thanks
thanks for your work and sharing of this great piece of pool software.
I played around with your ckpool to learn and better understand mining process.
Now one question (so far) comes up, why does the pool re-adjust the vardiff from scratch for every known client after reconnects / instance takeover (with your -H option) / ...
Doesn't it put alot of stress on a pool server with thousands of clients connected if , for example , you make a instance takeover and all thousand clients start to re-djust vardiff with x shares per second ?
Since you already have per worker information stored, isn't it better to store also last vardiff information and start from there on the next connection of the same worker ?
Thanks
Re: Braiins OS: open-source mining firmware [S9, T1]. New release includes AsicBoost
Flashed the braiins-os on some S9 for testing. First quick questions:
1) No Fan information available ?
2) Does braiins-os has emergency power off by overheat or broken fan detection ?
3) how to write braiin os to nand when already booted with sdcard ?
Thanks
1) No Fan information available ?
2) Does braiins-os has emergency power off by overheat or broken fan detection ?
3) how to write braiin os to nand when already booted with sdcard ?
Thanks