Search content
Sort by
Showing 20 of 45 results by maxime506
Re: [SCAM] Crex24 sudden KYC - while Crex24 wishes to stay anonymous
After I registered with crex24 they all of a sudden ask me to do KYC, and after that they told me that service was not available in the US and Canada. There's no warning when I first logged in and registered with them and that's how to scammed my personal information. Also they blocked me from trading so I will lost quite a bit of bitcoins in withdrawal fees
What a shady exchange. Don't trade on crex24
What a shady exchange. Don't trade on crex24
Why did you deposit in a new exchange ? When there are already many reputed and good exchanges available there is no point in depositing at a shady exchange. Such incidents happen every day but no one gets any lesson from them. I would only use a low volume exchange if i had to trade a coin which is only avaible on that exchange.
Normally I won't go there I was just trying to dump some shit coins and trade them to litecoins. Luckily I only lost like about 10 USD or something over there
Re: PhoenixMiner 5.0e: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
The new beta version is ready. You can download PhoenixMiner 5.1c from here:
https://mega.nz/folder/nQV0WYoR#RmjOXDuVLeyBfNgWx5X8KQ (MEGA)
If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):
The new features in this release are:
Here are the other features from 5.1b:
Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:
Please let us know if you have any problems or questions related to PhoenixMiner 5.1c.
https://mega.nz/folder/nQV0WYoR#RmjOXDuVLeyBfNgWx5X8KQ (MEGA)
If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):
Code:
File: PhoenixMiner_5.1c_Windows.zip
===================================
SHA-1: 3bb183cecbc723d687a322a5296d545006ceec3d
SHA-256: 851e35adfe256439d96c960f87ef844e8d38a58b96148a3bce6de157a2f82f43
SHA-512: a4add5d8e8029e28af007d95e44ebe2af743bd44d12d808fab4a32e132ad42ccbc09cc401cf379df432d7505709baec7a612eb669f4454612933a8eb0067fa20
File: PhoenixMiner_5.1c_Linux.tar.gz
====================================
SHA-1: 28e0f85f305e10bc16f3d35188e368bf23ae83bc
SHA-256: 3a7828a60e374b58608d7d2f6c9ac5f390a33cd275b993873b3cbea703bbab9f
SHA-512: 3ed20df13740aedd0992d9e50215c5c706dc9d2ff7aaa962d3a30c81c03e29236b134f6a46694100f9dee559b8c0afe68fc08b195f52cabab6e18d5cedd4cfef
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
===================================
SHA-1: 3bb183cecbc723d687a322a5296d545006ceec3d
SHA-256: 851e35adfe256439d96c960f87ef844e8d38a58b96148a3bce6de157a2f82f43
SHA-512: a4add5d8e8029e28af007d95e44ebe2af743bd44d12d808fab4a32e132ad42ccbc09cc401cf379df432d7505709baec7a612eb669f4454612933a8eb0067fa20
File: PhoenixMiner_5.1c_Linux.tar.gz
====================================
SHA-1: 28e0f85f305e10bc16f3d35188e368bf23ae83bc
SHA-256: 3a7828a60e374b58608d7d2f6c9ac5f390a33cd275b993873b3cbea703bbab9f
SHA-512: 3ed20df13740aedd0992d9e50215c5c706dc9d2ff7aaa962d3a30c81c03e29236b134f6a46694100f9dee559b8c0afe68fc08b195f52cabab6e18d5cedd4cfef
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are:
- Added more Pascal-based Nvidia cards to the list of supported Nvidia cards for memory timing (straps)
- Added new parameter -nvmem to force using straps even on unsupported Nvidia GPUs (use -nvmem 1 for GDDR5 cards, or -nvmem 2 for GDDR5X cards)
- Removed some dead ethash-based altcoins and updated the support for the rest of them
- Other small fixes
Here are the other features from 5.1b:
- Added support for VRAM timing adjustments for Nvidia cards of 10x0 series (see the new command-line parameters -straps, -vmt1, -vmt2, -vmt3, and -vmr for more information)
- Added -ttli option to automatically decrease the mining speed to avoid overheating the GPUs over the target temperature (useful when -tmax option is not supported by the drivers)
- Added support for latest AMD drivers 20.7.1 under Windows and 20.20-1089974 under Linux
- Fixed long-standing problems with -gpow option, which now works properly
- Many other small improvements and fixes
Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:
- Most recent Nvidia drivers require running as administrator (or as root under Linux) to allow hardware control, so you need to run PhoenixMiner as administrator for the VRAM timing options to work.
- The four independently adjustable VRAM timings are controlled by four different parameters: -vmt1, -vmt2, -vmt3, and -vmr. The last one controls the memory refresh rate, and the first three are other timings. The possible values for each of them are from 0 to 100, where 0 are the default timings, and 100 is the most aggressive timing (most GPUs probably wont work with 100).
- The -straps option gives an easy way to set one of the predefined levels of VRAM timing adjustment. The possible values are 0 to 6. 0 is the default value and uses the default timings from the VBIOS. Each strap level corresponds to a predefined set of memory timings ("-vmt1", "-vmt2", "-vmt3", "-vmr"). Strap level 3 is the fastest predefined level and may not work on most cards, 1 is the slowest (but still faster than the default timings). Strap levels 4 to 6 are the same as 1 to 3 but with less aggressive refresh rates (i.e. lower "-vmr" values).
- When using the VRAM timing options, start with lower values and make sure that the cards are stable before trying higher and more aggressive settings. You can use -straps along with the other options. For example -straps 1 -vmt1 60 will use the timings from 1st strap level but -vmt1 will be set to 60 instead of whatever value is specified by the 1st strap level. In such case the -straps option must be specified first.
- The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.
Please let us know if you have any problems or questions related to PhoenixMiner 5.1c.
Unfortunately it doesn't work on my P106-90 3GB and P106-100 6GB cards. The "unable to apply strap" error is gone after adding -nvmem 1 option but the miner still doesn't apply any memory timings
Re: [SCAM] Crex24 sudden KYC - while Crex24 wishes to stay anonymous
After I registered with crex24 they all of a sudden ask me to do KYC, and after that they told me that service was not available in the US and Canada. There's no warning when I first registered with them and that's how to scammed my personal information. Also they blocked me from trading so I will lost quite a bit of bitcoins in withdrawal fees
What a shady exchange. Don't trade on crex24
What a shady exchange. Don't trade on crex24
Re: PhoenixMiner 5.0e: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
please advice me. Now almost all vendor in my country cut off warranty if I flash bios so I have been use claymore with strap for a long time. after he look like stop update I start to try mining with pheonix miner but got a probelm.
I try -mt option. My asus 570 8gb (not flash bios) with mt 0 got 25MH, 4.0MH with -mt 1 and crash with -mt 2.
What am I done wrong? please advice me. I use latest amd driver.
This is strange, as the -mt option works fine with most cards. We are going to implement more flexible straps for AMD cards soon (ideally - in the 5.2 version of PhoenixMiner) but in the meantime, you can try different drivers because the -mt option actually uses the straps from the driver.I try -mt option. My asus 570 8gb (not flash bios) with mt 0 got 25MH, 4.0MH with -mt 1 and crash with -mt 2.
What am I done wrong? please advice me. I use latest amd driver.
Just reporting an issue I ran into on v5.1b with mixed-gen ETH mining on one XFX RX 5700 8GB + one XFX RX 480 8GB + one MSI RX 480 8GB on Ubuntu 20.04 (via both minerstatOS v1.5 and v1.6). When I upgraded from PhoenixMiner v5.0e to v5.1b, I saw my RX 5700 hashrate drop to about 58% of normal, and the two RX 480s dropped to about 67% of normal hashrate. Whether related to the miner or the OS, I cannot say, but I also saw the GPU memory clocks intermittently bouncing back to stock settings for 20 seconds at a time instead of locking in at my normal overclocks, and I would hear the fans adjust their throttles each time the clocks adjusted.
Rolling back to v5.0e followed by a reboot seems to have resolved these issues. I have happily used a few versions of the PhoenixMiner for about four months on this mixed-gen rig without issue, so this was a bit of a surprise. Unfortunately, my normal log file didn't have any suspicious messages or errors to report.
This could be related to the OS and driver versions. We haven't tested on Ubuntu 20.04 yet (our Linux test rigs use Ubuntu 16.x and Ubuntu 18.x) and it is possible that the new AMD pro drivers for 20.04 are different that these for 18.04 (this is certainly true for 20.20-1098277, which is released only for 20.04 and is not supported by PhoenixMiner yet). We are going to build some rigs with 20.04 soon but this will only be reflected in the next release of PhoenixMiner.Rolling back to v5.0e followed by a reboot seems to have resolved these issues. I have happily used a few versions of the PhoenixMiner for about four months on this mixed-gen rig without issue, so this was a bit of a surprise. Unfortunately, my normal log file didn't have any suspicious messages or errors to report.
Can you add memory strap support to the P106 series GPUs as well (P106-100, P106-90). They're basically just GTX 1060 but the mining version.
Here's the log output:
First, you must run the miner as administrator in order to use the straps. It this doesn't help, we are also adding straps support for more Pascal-based cards for the next release (5.1c), which should be ready in a few days. As the number of different Pascal-based GPUs is too big to be able to obtain and test on all of the, we also added a new parameter in 5.1c that will allow you to "trick" PhoenixMiner that the card is supported even when it isn't, which should be useful for the more "exotic" GPU variants like Quadro, mining cards, etc.Here's the log output:
Could someone explain what does this new strap command do? Does it worth to start experiment with it? Should we see better hashrate with it?
It tightens the memory timings of GDDR5 or GDDR5X chips of the Pascal-based Nvidia cards (GTX10x0), which may lead to better hashrate. If your card is supported it is definitely worth it to try this option. For some cards (these with GDDR5X memory) the results are quite good but even for GDDR5 cards there will be some improvement. Note that for some cards like 1070 (but not 1070Ti), which suffer from lower hashrate with each new epoch, you may need to allow more power by using higher power limit or higher core clock in order to see the improvement with the current high DAG epoch numbers on ETH and ETC.Hello,
I have two 5700xt mining together.
I would like to put differents fan settings like that, but it's not working, only one card is working the first one (-gpus 1) :
Is there a way to make different settings for each cards?
Thanks for any advice.
The way to specify different settings for each GPU is as follows:I have two 5700xt mining together.
I would like to put differents fan settings like that, but it's not working, only one card is working the first one (-gpus 1) :
Code:
PhoenixMiner.exe -pool pool -wal wallet -worker worker
-gpus 1 -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 75 -fanmax 100 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1
-gpus 2 -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 50 -fanmax 75 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1
-gpus 1 -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 75 -fanmax 100 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1
-gpus 2 -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 50 -fanmax 75 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1
Is there a way to make different settings for each cards?
Thanks for any advice.
Code:
PhoenixMiner.exe -pool pool -wal wallet -worker worker -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 50,75 -fanmax 75,100 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1
So, when the parameter is the same for all cards, just specify it once like thsi: -tt 67. When you want different values for each GPU, use it like this: -fanmin 50,75 - it this case the fanmin for the first card will be 50, for the second 75. Note that there must be no spaces between the comma and the numbers, and if you have more than two GPUs, you must specify a number for each of them.
do new features work under linux?
Yes, both -ttli and the Nvidia memory timing adjustments work under Linux too. You must run the program as root in order to use the straps.@Phoenixminer - if you can make a section of config file for delayed execution that would be good enough.
good job on timings integration!
adding kawpow could be even better, as this miner is mostly very stable:)
Not a bad idea but it may lead to instability. We will think about this for the next release. We are also exploring the possibility of adding KawPow support for the next release if time permits.good job on timings integration!
adding kawpow could be even better, as this miner is mostly very stable:)
Thank you Phoenix Miner! Unfortunately running it at admin level doesn't work either. I'll wait for next release
Re: PhoenixMiner 5.0e: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
The new beta version is ready. You can download PhoenixMiner 5.1b from here:
https://mega.nz/folder/XYkTQZiI#HT_dcKdLtsU26nwbE8pMBQ (MEGA)
If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):
The new features in this release are:
Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:
Please let us know if you have any problems or questions related to PhoenixMiner 5.1b.
https://mega.nz/folder/XYkTQZiI#HT_dcKdLtsU26nwbE8pMBQ (MEGA)
If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):
Code:
File: PhoenixMiner_5.1b_Windows.zip
===================================
SHA-1: b71a5b22bb9a6fbd26d4a85272f73defabad2b70
SHA-256: 1592d04efa4ef427b6e42388d012ac6a68154f09848aaaa4f0418e3425e07155
SHA-512: c543b8bc5d0c345e81fb2586b2807b842fc2b666bd033ceb78820d1732a61ef8529a228f9df8777029dfc9f7a8e90853fa65600c4d3b976787e1630f0ea03dfd
File: PhoenixMiner_5.1b_Linux.tar.gz
====================================
SHA-1: 9ba244a12698ca30015ef273c9f3cd9a9443c04f
SHA-256: ade4a07bd0c738fb875b2a42b5153271fedd23c60ba4527655360a8f718be4de
SHA-512: 860491408731c63bf42bb8288711de2f29534b4bac14313e376869d221a62a985ce4ea1a5a22cb39d875eb876016aa741275702665cc3ee1116c5cc3637ec21c
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
===================================
SHA-1: b71a5b22bb9a6fbd26d4a85272f73defabad2b70
SHA-256: 1592d04efa4ef427b6e42388d012ac6a68154f09848aaaa4f0418e3425e07155
SHA-512: c543b8bc5d0c345e81fb2586b2807b842fc2b666bd033ceb78820d1732a61ef8529a228f9df8777029dfc9f7a8e90853fa65600c4d3b976787e1630f0ea03dfd
File: PhoenixMiner_5.1b_Linux.tar.gz
====================================
SHA-1: 9ba244a12698ca30015ef273c9f3cd9a9443c04f
SHA-256: ade4a07bd0c738fb875b2a42b5153271fedd23c60ba4527655360a8f718be4de
SHA-512: 860491408731c63bf42bb8288711de2f29534b4bac14313e376869d221a62a985ce4ea1a5a22cb39d875eb876016aa741275702665cc3ee1116c5cc3637ec21c
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are:
- Added support for VRAM timing adjustments for Nvidia cards of 10x0 series (see the new command-line parameters -straps, -vmt1, -vmt2, -vmt3, and -vmr for more information)
- Added -ttli option to automatically decrease the mining speed to avoid overheating the GPUs over the target temperature (useful when -tmax option is not supported by the drivers)
- Added support for latest AMD drivers 20.7.1 under Windows and 20.20-1089974 under Linux
- Fixed long-standing problems with -gpow option, which now works properly
- Many other small improvements and fixes
Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:
- Most recent Nvidia drivers require running as administrator (or as root under Linux) to allow hardware control, so you need to run PhoenixMiner as administrator for the VRAM timing options to work.
- The four independently adjustable VRAM timings are controlled by four different parameters: -vmt1, -vmt2, -vmt3, and -vmr. The last one controls the memory refresh rate, and the first three are other timings. The possible values for each of them are from 0 to 100, where 0 are the default timings, and 100 is the most aggressive timing (most GPUs probably wont work with 100).
- The -straps option gives an easy way to set one of the predefined levels of VRAM timing adjustment. The possible values are 0 to 6. 0 is the default value and uses the default timings from the VBIOS. Each strap level corresponds to a predefined set of memory timings ("-vmt1", "-vmt2", "-vmt3", "-vmr"). Strap level 3 is the fastest predefined level and may not work on most cards, 1 is the slowest (but still faster than the default timings). Strap levels 4 to 6 are the same as 1 to 3 but with less aggressive refresh rates (i.e. lower "-vmr" values).
- When using the VRAM timing options, start with lower values and make sure that the cards are stable before trying higher and more aggressive settings. You can use -straps along with the other options. For example -straps 1 -vmt1 60 will use the timings from 1st strap level but -vmt1 will be set to 60 instead of whatever value is specified by the 1st strap level. In such case the -straps option must be specified first.
- The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.
Please let us know if you have any problems or questions related to PhoenixMiner 5.1b.
Can you add memory strap support to the P106 series GPUs as well (P106-100, P106-90). They're basically just GTX 1060 but the mining version.
Here's the log output:
2020.07.19:07:08:19.473: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001 -bench 0 -straps 5
2020.07.19:07:08:19.673: main CUDA version: 11.0, CUDA runtime: 8.0
2020.07.19:07:08:19.740: main No OpenCL platforms found
2020.07.19:07:08:19.740: main Available GPUs for mining:
2020.07.19:07:08:19.740: main GPU1: P106-100 (pcie 2), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2020.07.19:07:08:19.740: main GPU2: P106-100 (pcie 3), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2020.07.19:07:08:19.740: main GPU3: P106-090 (pcie 6), CUDA cap. 6.1, 2.9 GB VRAM, 5 CUs
2020.07.19:07:08:19.740: main GPU4: P106-090 (pcie 7), CUDA cap. 6.1, 2.9 GB VRAM, 5 CUs
2020.07.19:07:08:19.740: main GPU5: P106-090 (pcie
, CUDA cap. 6.1, 2.9 GB VRAM, 5 CUs2020.07.19:07:08:19.740: main GPU6: P106-090 (pcie 9), CUDA cap. 6.1, 2.9 GB VRAM, 5 CUs
2020.07.19:07:08:19.749: main NVML library initialized
2020.07.19:07:08:19.796: main Nvidia driver version: 445.87
2020.07.19:07:08:19.800: main NVAPI error in NvapiWrapper.c:301 : -6
2020.07.19:07:08:19.800: main Unable to load NvAPI: error 3
2020.07.19:07:08:20.841: main Benchmark mode. DAG epoch #0
2020.07.19:07:08:20.841: main GPU1: unable to init NvAPI with bus ID 131072
2020.07.19:07:08:20.841: main GPU2: unable to init NvAPI with bus ID 196608
2020.07.19:07:08:20.841: main GPU3: unable to init NvAPI with bus ID 393216
2020.07.19:07:08:20.841: main GPU4: unable to init NvAPI with bus ID 458752
2020.07.19:07:08:20.841: main GPU5: unable to init NvAPI with bus ID 524288
2020.07.19:07:08:20.842: main GPU6: unable to init NvAPI with bus ID 589824
2020.07.19:07:08:22.660: hwmc GPU5: unable to get fan speed - Unknown Error (999)
2020.07.19:07:08:23.847: GPU1 GPU1: Starting up... (0)
2020.07.19:07:08:23.847: GPU1 GPU1: Generating ethash light cache for epoch #0
2020.07.19:07:08:23.851: GPU2 GPU2: Starting up... (0)
2020.07.19:07:08:23.854: GPU3 GPU3: Starting up... (0)
2020.07.19:07:08:23.860: GPU4 GPU4: Starting up... (0)
2020.07.19:07:08:23.865: GPU5 GPU5: Starting up... (0)
2020.07.19:07:08:23.867: GPU6 GPU6: Starting up... (0)
2020.07.19:07:08:23.872: wdog Starting watchdog thread
2020.07.19:07:08:24.487: hwmc GPU1: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU2: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU3: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU4: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU5: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU6: unable to set straps - unsupported GPU
Re: [ANN] Zilliqa Auto Switcher. Auto Mine ZIL, 0% Fees, HIVE + SMOS + more
The newest version doesn't work for me:
[00:03:43 INF] ----------------------------------------------------------------------------------------------
[00:03:46 ERR] An exception occurred during a Ping request.
[00:03:43 INF] ----------------------------------------------------------------------------------------------
[00:03:46 ERR] An exception occurred during a Ping request.
Re: lolMiner 0.9.8: Improved C29M performance & Beam on Navi (Feb 24th)
0.9.7 works flawlessly though...
Setup Miner...
Device 0:
Name: Radeon (TM) RX 480 Graphics
Address: 28:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8142 MByte free)
Active: false (Unsupported device or driver version.)
Connecting to pool...
Connected to mine.thegrinpool.com:4747 (TLS disabled)
Authorized worker: maxime506.Rig2
New job received: 0 Height: 599489 Difficulty: 15
Start Mining...
All devices deselected or failed compatiblity check. Closing lolMiner
Setup Miner...
Device 0:
Name: Radeon (TM) RX 480 Graphics
Address: 28:0
Vendor: Advanced Micro Devices (AMD)
Memory: 8192 MByte (8142 MByte free)
Active: false (Unsupported device or driver version.)
Connecting to pool...
Connected to mine.thegrinpool.com:4747 (TLS disabled)
Authorized worker: maxime506.Rig2
New job received: 0 Height: 599489 Difficulty: 15
Start Mining...
All devices deselected or failed compatiblity check. Closing lolMiner
Well, I cannot change the wiring, that is out of my control. The electricity is free but it has to be 120 volts only, unfortunately.
Anyway, the S9 can work on 120 volts just fine it appears, from all the various threads I've read. (on 20 amp anyway; 15 amp is pushing it) Maybe not much room to overclock, but 1400-1500 watts is pretty much a bit less than a space heater or many hair dryers on high (hair dryer is short term load I know, but space heaters are not, and I have many running in winter 24/7 with no shut off time at all).
Z11 wattage seems to be right on the edge of doable on 120V/20 amp... (1580 watts?) I could do the minis to distribute the load better, but they are not cost-effective.
Glad you mentioned that Braiins OS - is that preferable now to that bulldozer one (don't remember the exact name) or ASICBoost (https://support.bitmain.com/hc/en-us/articles/360011930734-ASICBoost-firmware-for-Antminer-S9-series-and-T9-)? Also, I read somewhere that newer batches don't allow custom firmware? But also seemed that meant, they cannot be reflashed, but you can run custom firmware from SD card still, is that accurate?
I do tune my GPUs to fit better on the PSUs I have, so if I can count on being able to do that on S9, that would be sweet!
Final question - you say plan on a year to ROI? The SHA-256 difficulty is not rising as fast as it used to though... Right now whattomine estimates $4.30 a day for 13 TH/s... rounding down to $4, that's $120 a month - even if I pay $600 per machine, and difficulty rises 25% in six months, I think by month 7 they're covered? (don't forget, electricity cost is zero) Or you think difficulty will still somehow double if BTC rises? I was kind of thinking, maybe the SHA-256 hashrate is starting to get to a slower growth - newer machines aren't much faster on a per watt/joule basis... although if BTC goes to $50k, then I guess, sure, any old miner will find a place to get turned on again...
As a whole, I dunno. It's hard to predict if GPUs will slow again. Or if they'll magically rise. (hard to see how, alts are taking a beating every time BTC rises lately, and NOT recovering when it dips!) It would be a lot more exciting to get several Z11s, but riskier of course since they might double the capable hashrate in a few batches from now. Whereas S9s will probably retain some decent used value if BTC stays the same, and one S9 at current earn rates would pretty much equal one GPU machine, for 1/5th the cost.
Edit: was just looking at a hashrate chart again - tough to predict. It did go to all time highs recently. But hard to tell if it will now grow as fast as it did in 2017. I don't know if it's possible, if SHA-256 ASICs are slowing their efficiency increases?
https://www.blockchain.com/en/charts/hash-rate?timespan=2years
Anyway, the S9 can work on 120 volts just fine it appears, from all the various threads I've read. (on 20 amp anyway; 15 amp is pushing it) Maybe not much room to overclock, but 1400-1500 watts is pretty much a bit less than a space heater or many hair dryers on high (hair dryer is short term load I know, but space heaters are not, and I have many running in winter 24/7 with no shut off time at all).
Z11 wattage seems to be right on the edge of doable on 120V/20 amp... (1580 watts?) I could do the minis to distribute the load better, but they are not cost-effective.
Glad you mentioned that Braiins OS - is that preferable now to that bulldozer one (don't remember the exact name) or ASICBoost (https://support.bitmain.com/hc/en-us/articles/360011930734-ASICBoost-firmware-for-Antminer-S9-series-and-T9-)? Also, I read somewhere that newer batches don't allow custom firmware? But also seemed that meant, they cannot be reflashed, but you can run custom firmware from SD card still, is that accurate?
I do tune my GPUs to fit better on the PSUs I have, so if I can count on being able to do that on S9, that would be sweet!
Final question - you say plan on a year to ROI? The SHA-256 difficulty is not rising as fast as it used to though... Right now whattomine estimates $4.30 a day for 13 TH/s... rounding down to $4, that's $120 a month - even if I pay $600 per machine, and difficulty rises 25% in six months, I think by month 7 they're covered? (don't forget, electricity cost is zero) Or you think difficulty will still somehow double if BTC rises? I was kind of thinking, maybe the SHA-256 hashrate is starting to get to a slower growth - newer machines aren't much faster on a per watt/joule basis... although if BTC goes to $50k, then I guess, sure, any old miner will find a place to get turned on again...
As a whole, I dunno. It's hard to predict if GPUs will slow again. Or if they'll magically rise. (hard to see how, alts are taking a beating every time BTC rises lately, and NOT recovering when it dips!) It would be a lot more exciting to get several Z11s, but riskier of course since they might double the capable hashrate in a few batches from now. Whereas S9s will probably retain some decent used value if BTC stays the same, and one S9 at current earn rates would pretty much equal one GPU machine, for 1/5th the cost.
Edit: was just looking at a hashrate chart again - tough to predict. It did go to all time highs recently. But hard to tell if it will now grow as fast as it did in 2017. I don't know if it's possible, if SHA-256 ASICs are slowing their efficiency increases?
https://www.blockchain.com/en/charts/hash-rate?timespan=2years
Have you mined for Nicehash before with your GPU miners and how do you find it?
Re: [ANN] Zclassic, Zcash Fork No Premine, No 20% Founders Tax
LOL, delisted.
It literally remained a pump n' dump scheme till its last hours:
https://i.imgur.com/VsOV7bT.png
RIP!
They have done that so many times after Bittrex announced their removal.
Re: [ANN][$MUSIC] Musicoin Blockchain Upgrades to V3.0(“Quantitative Tightening 🎸
Looks like we are about to go to 5 sats or so with MUSIC.
Its pretty sad how badly this coin has performed since last January 2018. I never would of assumed it would hit 10 sats even, we are currently at 6 satoshis and looking at the order book there aren't that many bids in total. Basically less than 2 BTC worth of bids. The ask side on the other hand is pretty thick.
I don't know if we will be able to recover if we ever hit 1 satoshi, coins that go in that area usually end up being delisted and dead a few months later.
Hopefully MUSIC can survive that.
Its pretty sad how badly this coin has performed since last January 2018. I never would of assumed it would hit 10 sats even, we are currently at 6 satoshis and looking at the order book there aren't that many bids in total. Basically less than 2 BTC worth of bids. The ask side on the other hand is pretty thick.
I don't know if we will be able to recover if we ever hit 1 satoshi, coins that go in that area usually end up being delisted and dead a few months later.
Hopefully MUSIC can survive that.
i do not understand this is so great a project.
But why the coin price is so crap ?
How the team is working on this ?
Is it be gave up ?
Bittrex will remove Music from its market. That's why.
https://bittrex.zendesk.com/hc/en-us/articles/360029727892-Pending-Market-Removals-7-12-2019
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.6 (Windows/Linux)
I have 3gb and 6gb Nvidia cards (P106-90 and P106-100). Try to use the 3gb ones to mine UBQ and 6gb ones to mine ETC. Once I open a second session to mine the other coin, the program always shows "driver is in use" and won't apply the mining straps for the second session. How to fix this?
You cannot use -strap option in two sessions, you could try to add straps on first session to all cards and mine UBQ and then stop 6gb
cards and then start second session and start mining with 6gb cards only, not sure if this will work.
That works for me! Thanks for the suggestion
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.6 (Windows/Linux)
I have 3gb and 6gb Nvidia cards (P106-90 and P106-100). Try to use the 3gb ones to mine UBQ and 6gb ones to mine ETC. Once I open a second session to mine the other coin, the program always shows "driver is in use" and won't apply the mining straps for the second session. How to fix this?
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v14.5 (Windows/Linux)
What kind of bug was that? The Hashrate will drop to next to 0 after some time. Happens on some of my rigs already, no GPU crashed. Driver is 19.4.1, compute mode on. Use -rxboost 1 and -strap 1
21:01:39:019 6b4 ETH - Total Speed: 73.538 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:01:39:019 6b4 ETH: GPU0 14.945 Mh/s, GPU1 14.944 Mh/s, GPU2 14.953 Mh/s, GPU3 28.696 Mh/s
21:01:40:081 6b4 buf: {"id":0,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:01:40:081 6b4 ETH: 05/19/19-21:01:40 - New job from etp.2miners.com:9292
21:01:40:081 6b4 target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:01:40:081 6b4 ETH - Total Speed: 73.545 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:01:40:081 6b4 ETH: GPU0 14.945 Mh/s, GPU1 14.947 Mh/s, GPU2 14.957 Mh/s, GPU3 28.696 Mh/s
21:01:44:787 1e7c em hbt: 16, fm hbt: 16,
21:01:44:787 1e7c watchdog - thread 0 (gpu0), hb time 4703
21:01:44:787 1e7c watchdog - thread 1 (gpu0), hb time 4312
21:01:44:787 1e7c watchdog - thread 2 (gpu1), hb time 4359
21:01:44:787 1e7c watchdog - thread 3 (gpu1), hb time 4703
21:01:44:787 1e7c watchdog - thread 4 (gpu2), hb time 4703
21:01:44:787 1e7c watchdog - thread 5 (gpu2), hb time 4359
21:01:44:787 1e7c watchdog - thread 6 (gpu3), hb time 4312
21:01:44:787 1e7c watchdog - thread 7 (gpu3), hb time 4703
21:01:44:949 6b4 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3480bbe", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}
21:01:45:094 6b4 buf: {"id":6,"jsonrpc":"2.0","result":true}
21:01:45:204 6b4 ETH: checking pool connection...
21:01:45:204 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:01:45:333 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:01:49:491 1ea4 GPU0 t=47C fan=0%, GPU1 t=46C fan=0%, GPU2 t=46C fan=0%, GPU3 t=60C fan=42%
21:01:55:229 6b4 ETH: checking pool connection...
21:01:55:230 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:01:55:396 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:04:975 6b4 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3f0b6b", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}
21:02:05:120 6b4 buf: {"id":6,"jsonrpc":"2.0","result":true}
21:02:05:265 6b4 ETH: checking pool connection...
21:02:05:265 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:02:05:411 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:15:301 6b4 ETH: checking pool connection...
21:02:15:301 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:02:15:431 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:17:520 1e7c em hbt: 31, fm hbt: 0,
21:02:17:520 1e7c watchdog - thread 0 (gpu0), hb time 3328
21:02:17:520 1e7c watchdog - thread 1 (gpu0), hb time 8187
21:02:17:520 1e7c watchdog - thread 2 (gpu1), hb time 8187
21:02:17:520 1e7c watchdog - thread 3 (gpu1), hb time 3328
21:02:17:520 1e7c watchdog - thread 4 (gpu2), hb time 3328
21:02:17:520 1e7c watchdog - thread 5 (gpu2), hb time 8187
21:02:17:520 1e7c watchdog - thread 6 (gpu3), hb time 8187
21:02:17:520 1e7c watchdog - thread 7 (gpu3), hb time 3328
21:02:19:349 6b4 buf: {"id":0,"jsonrpc":"2.0","result":["0x3cd8fc592c3cb07cda97b393bb121129f6760ca49903959d2b87ecff4e47addc","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:19:444 6b4 ETH: 05/19/19-21:02:19 - New job from etp.2miners.com:9292
21:02:19:444 6b4 target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:02:19:567 6b4 ETH - Total Speed: 4.121 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:02:19:698 6b4 ETH: GPU0 0.780 Mh/s, GPU1 0.780 Mh/s, GPU2 0.780 Mh/s, GPU3 1.782 Mh/s
21:02:19:845 1ea4 GPU0 t=50C fan=0%, GPU1 t=49C fan=0%, GPU2 t=49C fan=0%, GPU3 t=54C fan=33%
21:02:25:002 6b4 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3ecca2", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}
21:02:25:163 6b4 buf: {"id":6,"jsonrpc":"2.0","result":true}
21:02:25:337 6b4 ETH: checking pool connection...
21:02:25:337 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:02:25:483 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x3cd8fc592c3cb07cda97b393bb121129f6760ca49903959d2b87ecff4e47addc","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:32:702 6b4 buf: {"id":0,"jsonrpc":"2.0","result":["0x7c83633d401594ae85b51f8fc309491da4e6cf24131570112436c278574cf72c","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:32:702 6b4 ETH: 05/19/19-21:02:32 - New job from etp.2miners.com:9292
21:02:32:702 6b4 target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:02:32:812 6b4 ETH - Total Speed: 4.142 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:06
21:02:32:957 6b4 ETH: GPU0 0.784 Mh/s, GPU1 0.784 Mh/s, GPU2 0.784 Mh/s, GPU3 1.791 Mh/s
21:01:39:019 6b4 ETH - Total Speed: 73.538 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:01:39:019 6b4 ETH: GPU0 14.945 Mh/s, GPU1 14.944 Mh/s, GPU2 14.953 Mh/s, GPU3 28.696 Mh/s
21:01:40:081 6b4 buf: {"id":0,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:01:40:081 6b4 ETH: 05/19/19-21:01:40 - New job from etp.2miners.com:9292
21:01:40:081 6b4 target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:01:40:081 6b4 ETH - Total Speed: 73.545 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:01:40:081 6b4 ETH: GPU0 14.945 Mh/s, GPU1 14.947 Mh/s, GPU2 14.957 Mh/s, GPU3 28.696 Mh/s
21:01:44:787 1e7c em hbt: 16, fm hbt: 16,
21:01:44:787 1e7c watchdog - thread 0 (gpu0), hb time 4703
21:01:44:787 1e7c watchdog - thread 1 (gpu0), hb time 4312
21:01:44:787 1e7c watchdog - thread 2 (gpu1), hb time 4359
21:01:44:787 1e7c watchdog - thread 3 (gpu1), hb time 4703
21:01:44:787 1e7c watchdog - thread 4 (gpu2), hb time 4703
21:01:44:787 1e7c watchdog - thread 5 (gpu2), hb time 4359
21:01:44:787 1e7c watchdog - thread 6 (gpu3), hb time 4312
21:01:44:787 1e7c watchdog - thread 7 (gpu3), hb time 4703
21:01:44:949 6b4 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3480bbe", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}
21:01:45:094 6b4 buf: {"id":6,"jsonrpc":"2.0","result":true}
21:01:45:204 6b4 ETH: checking pool connection...
21:01:45:204 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:01:45:333 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:01:49:491 1ea4 GPU0 t=47C fan=0%, GPU1 t=46C fan=0%, GPU2 t=46C fan=0%, GPU3 t=60C fan=42%
21:01:55:229 6b4 ETH: checking pool connection...
21:01:55:230 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:01:55:396 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:04:975 6b4 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3f0b6b", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}
21:02:05:120 6b4 buf: {"id":6,"jsonrpc":"2.0","result":true}
21:02:05:265 6b4 ETH: checking pool connection...
21:02:05:265 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:02:05:411 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:15:301 6b4 ETH: checking pool connection...
21:02:15:301 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:02:15:431 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5b93ccbeaf1615d5b55d7a2e1105331ea2e7cb8abc2780415398ceccf55f57c3","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:17:520 1e7c em hbt: 31, fm hbt: 0,
21:02:17:520 1e7c watchdog - thread 0 (gpu0), hb time 3328
21:02:17:520 1e7c watchdog - thread 1 (gpu0), hb time 8187
21:02:17:520 1e7c watchdog - thread 2 (gpu1), hb time 8187
21:02:17:520 1e7c watchdog - thread 3 (gpu1), hb time 3328
21:02:17:520 1e7c watchdog - thread 4 (gpu2), hb time 3328
21:02:17:520 1e7c watchdog - thread 5 (gpu2), hb time 8187
21:02:17:520 1e7c watchdog - thread 6 (gpu3), hb time 8187
21:02:17:520 1e7c watchdog - thread 7 (gpu3), hb time 3328
21:02:19:349 6b4 buf: {"id":0,"jsonrpc":"2.0","result":["0x3cd8fc592c3cb07cda97b393bb121129f6760ca49903959d2b87ecff4e47addc","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:19:444 6b4 ETH: 05/19/19-21:02:19 - New job from etp.2miners.com:9292
21:02:19:444 6b4 target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:02:19:567 6b4 ETH - Total Speed: 4.121 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:05
21:02:19:698 6b4 ETH: GPU0 0.780 Mh/s, GPU1 0.780 Mh/s, GPU2 0.780 Mh/s, GPU3 1.782 Mh/s
21:02:19:845 1ea4 GPU0 t=50C fan=0%, GPU1 t=49C fan=0%, GPU2 t=49C fan=0%, GPU3 t=54C fan=33%
21:02:25:002 6b4 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x3ecca2", "0x000000000000000000000000000000000000000000000000000000005121eb8e"]}
21:02:25:163 6b4 buf: {"id":6,"jsonrpc":"2.0","result":true}
21:02:25:337 6b4 ETH: checking pool connection...
21:02:25:337 6b4 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
21:02:25:483 6b4 buf: {"id":3,"jsonrpc":"2.0","result":["0x3cd8fc592c3cb07cda97b393bb121129f6760ca49903959d2b87ecff4e47addc","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:32:702 6b4 buf: {"id":0,"jsonrpc":"2.0","result":["0x7c83633d401594ae85b51f8fc309491da4e6cf24131570112436c278574cf72c","0x789121f005cf40651e361085512f0540e36453fb34ca66fbe38e2836348b9f73","0x7fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3"]}
21:02:32:702 6b4 ETH: 05/19/19-21:02:32 - New job from etp.2miners.com:9292
21:02:32:702 6b4 target: 0x000000007fd9a601 (diff: 8600MH), epoch 74(1.58GB)
21:02:32:812 6b4 ETH - Total Speed: 4.142 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:06
21:02:32:957 6b4 ETH: GPU0 0.784 Mh/s, GPU1 0.784 Mh/s, GPU2 0.784 Mh/s, GPU3 1.791 Mh/s
Re: SRBMiner Cryptonight AMD GPU Miner V1.6.8 - V8 & algo switching
@doktor83 The RX 550 cards are noticeably slower with NormalV8 when there are other cards in the rig. Wasn't like that with v7. I hope you can fix it if possible.
Mine are RX550 2GB cards with baffin core and elpida memory.
986mhz core and 1901mhz mem should give you around 14mh. I even downvolt them to 800mv in OverclocknTool. Running cool at 62-66 celcius
986mhz core and 1901mhz mem should give you around 14mh. I even downvolt them to 800mv in OverclocknTool. Running cool at 62-66 celcius
Re: [ANN] <808> BlockChain Hi Rate Proof of Stake, Earn 17%+ after every 8.08+ day
I forgot to come in here and report that my 50 million block staked the other day. It took 26 days to stake, at the time it was showing 82% chance of staking so I got lucky however most times I have seen my coins stake when its over 80% within 24 hours. This time instead of selling 30% of my stake I only sold 10% as now the diff is getting higher I thought now is the time to also build on my stack to try and stake quicker next time. That 10% went into buying more 421 coins.
It's day 12 now for my 119 million stash (altogether in one block), and 28% chance to mint in 24 hours. Difficulty has gone up from 26000 when my 91 million coins staked to around 30,000 today