Is it some using the new DNS Over Https DoH ?
Topic: lolMiner 1.64: Fastest Kaspa miner in market - page 19. (Read 155973 times)
Well, that is easy - just read what the changes are about.
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Ok pretty dev xD
Yes I thank the Chinese firewall, it allowed us to do more blocking solo
Yes we saw the drop in hashrate suddenly after I have been using the devil's DNS since the beginning as we call it in our country because it encrypts all even the illicitly illegal content ...
In hiveos, it's very practical and cloudflare manages that very well
The hashrate has come back quite fast... I think they search for solutions to avoid that.
the solution would be that it would use more fossil fuels but advanced in renewable energies.
Myself my energy comes from solar panel + wind turbine backup.
China = industrial pollution
here is my opinion.
your actions are good but it would have been better to work more on nvidia and consumption on amperes cards than this
China + USA = pollutions see the latest climate summit of Glasgow.
Also of interest https://climate.selectra.com/en/carbon-footprint/most-polluting-countries
Well, that is easy - just read what the changes are about.
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Ok pretty dev xD
Yes I thank the Chinese firewall, it allowed us to do more blocking solo
Yes we saw the drop in hashrate suddenly after I have been using the devil's DNS since the beginning as we call it in our country because it encrypts all even the illicitly illegal content ...
In hiveos, it's very practical and cloudflare manages that very well
The hashrate has come back quite fast... I think they search for solutions to avoid that.
the solution would be that it would use more fossil fuels but advanced in renewable energies.
Myself my energy comes from solar panel + wind turbine backup.
China = industrial pollution
here is my opinion.
your actions are good but it would have been better to work more on nvidia and consumption on amperes cards than this
Well, that is easy - just read what the changes are about.
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Ok pretty dev xD
Yes I thank the Chinese firewall, it allowed us to do more blocking solo
Yes we saw the drop in hashrate suddenly after I have been using the devil's DNS since the beginning as we call it in our country because it encrypts all even the illicitly illegal content ...
In hiveos, it's very practical and cloudflare manages that very well
The hashrate has come back quite fast... I think they search for solutions to avoid that.
Well, that is easy - just read what the changes are about.
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Ok pretty dev xD
Yes I thank the Chinese firewall, it allowed us to do more blocking solo
Yes we saw the drop in hashrate suddenly after I have been using the devil's DNS since the beginning as we call it in our country because it encrypts all even the illicitly illegal content ...
In hiveos, it's very practical and cloudflare manages that very well
Hello. Do you have 1.37 for Windows?
Hello. Do you have 1.37 for Windows?
Also interested in 1.37 for Windows as well too!
1.38 READY in Github :-)
Due to the current circumstances and the focus of this publication, the change logs are bilingual this time.
at the beginning i thought that the github was done hacked so i downloaded nothing besides no valid explanation!
Why use chinese
and english (logic)So you got confused and blame the dev
Seems pretty straight forward to me.
Well, that is easy - just read what the changes are about.
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Last week many PoW networks saw a big loss in hashrate, because the China firewall started blocking dns resolition and mining traffic towards mining pools. This update handles exactly that messy situation by allowing to mine on behind the fw (use tls enabled and --dns-over-https 2). Because the update mainly addresses problems in China I tried to welcome them more by doing the change log in Chinese one single time
Hello. Do you have 1.37 for Windows?
Hello. Do you have 1.37 for Windows?
Also interested in 1.37 for Windows as well too!
1.38 READY in Github :-)
Due to the current circumstances and the focus of this publication, the change logs are bilingual this time.
at the beginning i thought that the github was done hacked so i downloaded nothing besides no valid explanation!
Why use chinese
and english (logic)Hello. Do you have 1.37 for Windows?
Hello. Do you have 1.37 for Windows?
Also interested in 1.37 for Windows as well too!
1.38 READY in Github :-)
Hello. Do you have 1.37 for Windows?
Also interested in 1.37 for Windows as well too!
Hello. Do you have 1.37 for Windows?
gminer cant run a rtx3070fe either so im out of miners for cortex.
problem mining cortex on rtx3070ti fe cards i get opencl init memory allocation failure basically it dont work lol works on other algos i only get probs on cortex sucks./
Cortex was developed for AMD and adapted to NVidia, it is not probably the best miner to be used with Nvidia GPU.
problem mining cortex on rtx3070ti fe cards i get opencl init memory allocation failure basically it dont work lol works on other algos i only get probs on cortex sucks./
So is that to say if you have an AMD card, you're probably never going to see any improvements?
I don't think so... He said he is working on it in the Telegram group!!
So is that to say if you have an AMD card, you're probably never going to see any improvements?
It seems it is not update but 1.36a is giving more Mhs to me in ETH with Nvidia...
Improved Ethash & Etchash performance on all Nvidia Turing & Ampere GPUs by 0.3 to 0.7% depending on card & system.
Decreased rate of stales on Nvidia Turing & Ampere GPUs.
Improved Ethash & Etchash performance on all Nvidia Turing & Ampere GPUs by 0.3 to 0.7% depending on card & system.
Decreased rate of stales on Nvidia Turing & Ampere GPUs.
thanks mate,
all of my cards are 8gb, will it work?
all of my cards are 8gb, will it work?
--dualmode etc --dualpool etc_pool_here --dualuser wallet_etc_here --dualdevices gpu_nummers_than_you_want_to_use
thanks mate,
all of my cards are 8gb, will it work?
all of my cards are 8gb, will it work?
So you HAVE to use --devices and --dualdevices and put the gpus you want on eth on devices and the ones you want to mine etc on dualdevices per the instructions i posted.
Because those instructions state that if you dont specify then cards with 5gb or more will be on eth and cards with 4gb or less will be on etc.
Since yours are all 8gb without specifically assigning them its going to use them all for eth…cause 8gb > 4gb.
If you add a 4gb card then that 4gb would automatically mine etc with your current command line as long as it has
--dualmode etc --dualstratum
added and in your case would need to have the devices and dualdevices added.
thanks mate,
all of my cards are 8gb, will it work?
all of my cards are 8gb, will it work?
Jump to: