The  new  version  is  finally  ready.  You  can  download  PhoenixMiner  5.8c  from  here:

PhoenixMiner_5.8c_Windows.zip Github
PhoenixMiner_5.8c_Linux.tar.gz Github


Changes in version 5.8c :

• Full LHR disable mode -lhrdis <n>  1 - yes (default), 0 - no
• Added lock core clock
• Fixed an issue causing crashing with some RTX 3060/3080/3090 cards
• Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will
  provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused
• Increased the maximum supported DAG epoch to 600 (i.e. until about Sep 2023)
• Implemented full hardware control for AMD RX6900/6800/6700 cards under Linux. Note that with these cards under Linux you need to specify relative core voltage: e.g. -
  cclock -50 will set the core voltage to be 50 mV under the default value
• Added ROCr kernels for Vega, Radeon VII and Navi cards. With these kernels you will be able to run these cards with Linux drivers 20.45 and later but the performance will
  be lower than with the older PAL drivers and kernels. We recommend using AMD Linux driver 20.30 for all cards except RX6900/6800/6700
• Fixed an issue causing crashing with some RX6900/6800/6700 cards under Linux (there is no need to run these cards with -clkernel 0 anymore)
• Added support for AMD Windows drivers up to 21.8.1. Note that Radeon VII cards will not work with drivers 21.6.1 or higher - you need to use older drivers for proper
  operation of these cards
• Added support for AMD Linux drivers up to 21.20 (use older drivers for Vega or Radeon VII cards as they will not work with 21.20). Note that the latest 21.30 drivers are
  not supported (and the initial testing shows that even the older Polars cards are not working properly with them, so avoid 21.30 for now)
• Numerous other fixes and small improvements

Please let us know if you have any problems or questions related to PhoenixMiner 5.8c

osoese will you keep your promise to reanimate a coin? 

The coin is alive, but news from the developers has been going on for a very long time ...

I can not find ... how to specify backup pools in TPM?

I join the question: VDS on vega does not start! ... Vega is also amd ... 

https://bitcointalk.org/index.php?topic=4832535.new#new

.....
The main developer of Kodiak stopped working on the coin shortly after listing on the Stex exchange. Let everyone decide for himself why this happened ... Who this Kodiak is is unclear, the bitcointalk account is made only for posts in this thread, so there are options ...
There is one developer who has never written in this thread, but is known for other coins. This is osoese (bitcointalk, twitter). He is involved in the development of several coins (EGEM, SFRX, ELLA, LMO, XBI, maybe more ...), I think we should demand an answer from him and remind about responsibility to users.
And wasn’t the LMO originally conceived as a scam to finance other projects (perhaps even more scam))) Huh
In any case, osoese said he would continue work on the LMO. Smiley
.....

https://bitcointalk.org/index.php?topic=4832535.new#new

.....
The main developer of Kodiak stopped working on the coin shortly after listing on the Stex exchange. Let everyone decide for himself why this happened ... Who this Kodiak is is unclear, the bitcointalk account is made only for posts in this thread, so there are options ...
There is one developer who has never written in this thread, but is known for other coins. This is osoese (bitcointalk, twitter). He is involved in the development of several coins (EGEM, SFRX, ELLA, LMO, XBI, maybe more ...), I think we should demand an answer from him and remind about responsibility to users.
And wasn’t the LMO originally conceived as a scam to finance other projects (perhaps even more scam))) Huh
In any case, osoese said he would continue work on the LMO. Smiley
.....

deal with XCY or return the coins!

The main developer of Kodiak stopped working on the coin shortly after listing on the Stex exchange. Let everyone decide for himself why this happened ... Who this Kodiak is is unclear, the bitcointalk account is made only for posts in this thread, so there are options ...
There is one developer who has never written in this thread, but is known for other coins. This is osoese (bitcointalk, twitter). He is involved in the development of several coins (EGEM, SFRX, ELLA, LMO, XBI, maybe more ...), I think we should demand an answer from him and remind about responsibility to users.
And wasn’t the LMO originally conceived as a scam to finance other projects (perhaps even more scam)))
In any case, osoese said he would continue work on the LMO.

This is not a new dev, but an old one, from the LMO team ...

hashrate cn-lite-v7 to the moon ... came fpga? 

cryptocurrencies are spreading on social networks ... soon SMS ...
Well, it's not difficult for me:
https://medium.com/@cypruscoinclub/cypruscoin-network-upgrade-v0-1-5-af55233ada87

https - more credible ...

Please explain what this means:
Due to SCAM possibility, Cypruscoin will be removed from semiPOOL in 72 hours (March 22nd). Please stop mining Cypruscoin and pick another one!
(https://webxtri.semipool.com/#/dashboard)
 

Three days ago I sent 2 BCN to this exchange  
https://explorer.bytecoin.org/tx?hash=0bf160d1f02ad637325da1ae2ce9a1813635dd6a6a4e990b7fd76842d63c1fac
on account is empty  

everything is done just so that people buy TRD at a crazy price

"database write error. disk is full or database is corrupted"  

there is a lot of disk space.
what to do?

107.6.143.228:8081 - sorry, it works ... I think in a month the wallet is synchronized ...

does not work

Wallet syncs for a very long time. 
please give good nodes or write them on the first page ...

how are you?