Show Posts
|
Pages: [1]
|
HI guys,
1)I have 7 vega 56 rig GPU running the new cast XMR for v8. With the 18.51 driver the miner on miningpoolhub.com statistics stayed at 9150 H/S for two weeks. We have not done the HBCC off optimization yet so I was not worried about the drop in hashrate--we used to do 11-12 KH/S on v7. Just this week the hashrate even went up to 10.5 KH/S. But started this Thursday the hashrate on the pool went down. Now it is at 7.64 KH/S. I am a newbie but is it possible that something to do with miningpoolhub.com would have caused this? The hashrate on miningpoolhub.com is the hashrate that the pool thinks we are mining at. Could it be possible that something on their end is causing this? When I look at the graphs it does not seem we are getting many blocks. Is it that the pool has not been optimized for V8 yet?
2) Can someone post their config for CAST-XMR please for vega 56 (I flashed mine to 64)? Want to see if I did everything ok.
3) What other hash rate optimizations can you recommend for my miner config? I looked through this read. I see some people talk about a PPT optimization. Thanks!
Thanks!
You should get at least 12.5kH/s at least with 7 modded vega 56 with a consumption of 1300-1400W. cast_xmr-vega -S xmr-eu1.nanopool.org:14444 -u monero_address %* --maxmem --fastjobswitch --algo=-1 --intensity=7 -G 0,1,2,3,4,5 Hi, Dear @ingyenfrag , after release version Cast XMR Version 1.1.0 (2018/6/1) option [--maxmem] are disabled Cast XMR Version 1.1.0 (2018/6/1) - All new --intensity option to specify the memory allocation in the range of 0 to 10, upto 12 for Vega Frontier Edition. The default setting will correspond with the settings of version 1.0 and are displayed at startup. - Vega Frontier 'Large Pages' support added, up to 30% higher hash rates for CryptoNight-Heavy, 5% increase for CryptoNight - Includes the switch-radeon-gpu command line tool to restart GPUs, switch on/off HBCC, Compute Mode and Large Pages - Nicehash supports now up to 24 GPUs - --maxmem option is deprecated, will now be mapped to an corresponding intensity setting - --forcecompute is deprecated, 'Compute Mode' of Polaris GPUs will be automatically detected. To overwrite use the --intensity option - Default mining algo changed to CryptoNightV7, to still mine CryptoNight Classic add --algo=0 - Tested with Radeon Adrenalin Driver 18.4.1
|
|
|
try this: switch-radeon-gpu --compute=on autorestart
|
|
|
@ut3wt: make sure crossfire and ULPS are disabled.
Maybe DDU and install 18.7.1 drivers? I see you have 000 and 001 there but no GPU are installed on these reg values. You can try to delete them before doing DDU and see if it's working. I had 20x Vega64 on Blockchain drivers, for Monero V8 I did DDU Blockchan drivers, installed 18.7.1 drivers, applied Soft Power tables, Disabled Crossfire and ULPS and all 20 of them are hashing at ~1900 h/s now on MoneroV8.
@ut3wt I got the solution. I went through the exact same suckage yesterday till I found the trick. The driver does not give a single f*ck what's in the registry! I reinstalled the 18.6.1 driver multiple times and manually set those values in the registry and after reboot I checked in AMD Settings and CF was still ON! I had to manually turn CF off in AMD Setting and the 2 out of 6 cards that were previously hashing at only ~100h/s got back to normal with ~1850h/s. Now all 6 cards are hashing fine with 18.6.1. I had to remove prev driver with amdcleanutility and install 18.6.1 from scratch. I also switched to Compute mode, but that my not matter for Vegas. FYI: BC drivers are shit at V8 indeed. Only ~700h/s Hi, many thanks for your help resolve this bug, after solution from @Zorg33. I observate this bug in AMD setting, after switch on\off HBCC memory and CF in AMD setings All GPUs hashing very good) everything began to work well, I use 18.7.1 driver. Conclusion: Utility Switch Radeon GPU 0.9.5 not correct switch trigger... log: [01:22:43] GPU0 | 47°C | Fan 3529 RPM | 1555.9 H/s [01:22:43] GPU5 | 43°C | Fan 3665 RPM | 1676.6 H/s [01:22:45] GPU1 | 52°C | Fan 3486 RPM | 1908.1 H/s [01:22:45] GPU4 | 43°C | Fan 3402 RPM | 1901.9 H/s [01:22:45] GPU3 | 44°C | Fan 3489 RPM | 1894.0 H/s [01:22:45] GPU2 | 45°C | Fan 3608 RPM | 1891.2 H/s
[Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-27 19:36:37] 5:46:09 (100%) Online 0:00:00 ( 0%) Offline
[Job: #422 | Difficulty: 321407 | Running: 7.0 sec | Avg Job Time: 49.3 sec]
[Hash Rate Avg: 11315.7 H/s] 1890.5 H/s GPU0 1909.4 H/s GPU1 1885.2 H/s GPU2 1886.6 H/s GPU3 1885.9 H/s GPU4 1858.2 H/s GPU5
[Shares Found: 713 | Avg Search Time: 29.1 sec] 713 (100%) Accepted 0 ( 0%) Rejected by pool 0 ( 0%) Invalid result computation failed 0 ( 0%) Could not be submitted because of network error 0 ( 0%) Outdated because of job change
[01:22:47] GPU5 | 43°C | Fan 3654 RPM | 1836.4 H/s
|
|
|
Maybe DDU and install 18.7.1 drivers? I see you have 000 and 001 there but no GPU are installed on these reg values. You can try to delete them before doing DDU and see if it's working. I had 20x Vega64 on Blockchain drivers, for Monero V8 I did DDU Blockchan drivers, installed 18.7.1 drivers, applied Soft Power tables, Disabled Crossfire and ULPS and all 20 of them are hashing at ~1900 h/s now on MoneroV8.
Thanks for the answer, after install 18.7.1 driver hashrate better but two gpu not hashing(( P.S. 001 it is Intel integrate GPU 000 I d'no, I delete it from registry, but not result... I think problem maybe in driver AMD two GPUs not switch memory HBCC after command on\off...? how to solve it? [Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-26 00:27:31] 0:01:37 (100%) Online 0:00:00 ( 0%) Offline
[Job: #4 | Difficulty: 266107 | Running: 35.0 sec | Avg Job Time: 20.7 sec]
[Hash Rate Avg: 8437.8 H/s] 1906.9 H/s GPU0 1903.9 H/s GPU1 1904.4 H/s GPU2 1905.9 H/s GPU3 454.3 H/s GPU4 362.4 H/s GPU5
[Shares Found: 12 | Avg Search Time: 6.8 sec] 12 (100%) Accepted 0 ( 0%) Rejected by pool 0 ( 0%) Invalid result computation failed 0 ( 0%) Could not be submitted because of network error 0 ( 0%) Outdated because of job change c:\xxx\cast_xmr150v8>switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=on autorestart ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Switch Radeon GPU 0.9.5
Restart GPUs and switch 'Compute Mode', 'Large Pages' and 'HBCC memory' on or off for example: 'switch-radeon-gpu -G 0 --compute=on restart'
Run with --help to list available optionss
Coded by [glph3k] for more info visit http://www.gandalph3000.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2639.5)
GPU0: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU GPU1: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU GPU2: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU GPU3: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU GPU4: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU GPU5: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU
Device Change privileges are required to apply the settings! The Windows User Account Control dialog will appear. When clicking 'YES' in the upcoming dialog the app will be granted the Windows privileges to execute the above listed actions.
Proceed? (Y/N)
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2639.5)
GPU0: Radeon RX Vega (gfx901) ... no changes. GPU1: Radeon RX Vega (gfx901) ... no changes. GPU2: Radeon RX Vega (gfx901) ... no changes. GPU3: Radeon RX Vega (gfx901) ... no changes. GPU4: Radeon RX Vega (gfx900) ... no changes. GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF GPU1: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF GPU2: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF GPU3: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF GPU4: Radeon RX Vega (gfx900) | HBCC: ON | Large Pages: OFF GPU5: Radeon RX Vega (gfx900) | HBCC: ON | Large Pages: OFF switch off c:\xxx\cast_xmr150v8>switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=off autorestart ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Switch Radeon GPU 0.9.5
Restart GPUs and switch 'Compute Mode', 'Large Pages' and 'HBCC memory' on or off for example: 'switch-radeon-gpu -G 0 --compute=on restart'
Run with --help to list available optionss
Coded by [glph3k] for more info visit http://www.gandalph3000.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2639.5)
GPU0: Radeon RX Vega (gfx901) ... switch HBCC Memory OFF ... restart GPU GPU1: Radeon RX Vega (gfx901) ... switch HBCC Memory OFF ... restart GPU GPU2: Radeon RX Vega (gfx901) ... switch HBCC Memory OFF ... restart GPU GPU3: Radeon RX Vega (gfx901) ... switch HBCC Memory OFF ... restart GPU GPU4: Radeon RX Vega (gfx900) ... switch HBCC Memory OFF ... restart GPU GPU5: Radeon RX Vega (gfx900) ... switch HBCC Memory OFF ... restart GPU
Device Change privileges are required to apply the settings! The Windows User Account Control dialog will appear. When clicking 'YES' in the upcoming dialog the app will be granted the Windows privileges to execute the above listed actions.
Proceed? (Y/N)
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2639.5)
GPU0: Radeon RX Vega (gfx900) ... no changes. GPU1: Radeon RX Vega (gfx900) ... no changes. GPU2: Radeon RX Vega (gfx900) ... no changes. GPU3: Radeon RX Vega (gfx900) ... no changes. GPU4: Radeon RX Vega (gfx900) ... no changes. GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU1: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU2: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU3: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU4: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU5: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
|
|
|
@ut3wt: make sure crossfire and ULPS are disabled.
yes all GPUs are disabled ULPS and crossfire 
|
|
|
Well my Vegas are running @ ~900Khs lool
And when I run cast xmr (last version) it says Gfx900(?) , can anyone confirm this ? it was supposed to say Gfx901(?)
A Vega lists as gfx901 when HBCC is on gfx900 when HBCC is off Hi dear glph3k! I find part answer in your previous post, but i have problem 6-gpu Vega64 in OLD mode (CN V7) work very good 12kHs stability, after update to cast xmr 1.5.0 and driver (this moment i use 18.5.2) two GPUs in my log example №4,5 not hashing... and i observe after command switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=on autorestart i have it: GPU0-3 it is ok gfx901 but GPU4,5 gfx900 --??? i confused [09:54:39] Initializing GPU, loading kernel ... Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6) Fast job switching mode enabled. Driver Version OK. GPU0: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 HBCC Memory Segment is enabled. It is recommended to turn HBCC off to run with higher stable intensity settings. GPU1: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 HBCC Memory Segment is enabled. It is recommended to turn HBCC off to run with higher stable intensity settings. GPU2: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 HBCC Memory Segment is enabled. It is recommended to turn HBCC off to run with higher stable intensity settings. GPU3: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 HBCC Memory Segment is enabled. It is recommended to turn HBCC off to run with higher stable intensity settings. GPU4: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 GPU5: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 i think that GPU 4,5 HBCC Memory Segment not switch, it is bug (soft, driver..e.t.c) or my two GPU (HBCC Memory) defective? half all hashrate [Hash Rate Avg: 4766.1 H/s] 922.9 H/s GPU0 913.3 H/s GPU1 893.3 H/s GPU2 879.3 H/s GPU3 730.9 H/s GPU4 426.4 H/s GPU5
[Shares Found: 233 | Avg Search Time: 14.2 sec] 68 ( 29%) Accepted 19 ( 8%) Rejected by pool 0 ( 0%) Invalid result computation failed 0 ( 0%) Could not be submitted because of network error 146 ( 63%) Outdated because of job change after command switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=off autorestart i have all gfx900, but GPU4,5 not hashing((( [10:15:10] Initializing GPU, loading kernel ... Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6) Fast job switching mode enabled. Driver Version OK. GPU0: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 GPU1: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 GPU2: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 GPU3: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 GPU4: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 GPU5: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 [10:15:14] Connecting to pool.supportxmr.com:7777 ... [Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-25 10:15:14] 0:02:38 (100%) Online 0:00:00 ( 0%) Offline
[Job: #3 | Difficulty: 185704 | Running: 87.0 sec | Avg Job Time: 35.0 sec]
[Hash Rate Avg: 7912.9 H/s] 1853.2 H/s GPU0 1871.1 H/s GPU1 1868.7 H/s GPU2 1873.9 H/s GPU3 227.9 H/s GPU4 218.2 H/s GPU5
[Shares Found: 16 | Avg Search Time: 11.3 sec] 8 ( 50%) Accepted 0 ( 0%) Rejected by pool 0 ( 0%) Invalid result computation failed 0 ( 0%) Could not be submitted because of network error 8 ( 50%) Outdated because of job change GPU0: Radeon RX Vega (gfx900) ... no changes. GPU1: Radeon RX Vega (gfx900) ... no changes. GPU2: Radeon RX Vega (gfx900) ... no changes. GPU3: Radeon RX Vega (gfx900) ... no changes. GPU4: Radeon RX Vega (gfx900) ... no changes. GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU1: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU2: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU3: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU4: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU5: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF... Plz help me to solve this issue, thank very much!
|
|
|
Hi, after update driver on my RIG i have problems! i dont no how to solve it... i try install different driver (latest include) but 4 GPU work ok, 2-GPU not hashing??? this moment 18.5.2  Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
GPU0: Radeon RX Vega (gfx900) ... no changes. GPU1: Radeon RX Vega (gfx900) ... no changes. GPU2: Radeon RX Vega (gfx900) ... no changes. GPU3: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU1: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU2: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF GPU3: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
[Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-24 21:43:39] 0:17:24 (100%) Online 0:00:00 ( 0%) Offline
[Job: #21 | Difficulty: 276363 | Running: 3.0 sec | Avg Job Time: 52.0 sec]
[Hash Rate Avg: 7426.2 H/s] 1825.7 H/s GPU0 1726.0 H/s GPU1 1729.8 H/s GPU2 1740.7 H/s GPU3 210.3 H/s GPU4 193.7 H/s GPU5
[Shares Found: 48 | Avg Search Time: 20.5 sec] 48 (100%) Accepted 0 ( 0%) Rejected by pool 0 ( 0%) Invalid result computation failed 0 ( 0%) Could not be submitted because of network error 0 ( 0%) Outdated because of job change
after switch-radeon-gpu --hbcc=on autorestart GPU0-GPU3= it is gfx901 and two gfx900  (fantastic) but also two GPU not hashing((( Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
GPU0: Radeon RX Vega (gfx901) ... no changes. GPU1: Radeon RX Vega (gfx901) ... no changes. GPU2: Radeon RX Vega (gfx901) ... no changes. GPU3: Radeon RX Vega (gfx901) ... no changes. GPU4: Radeon RX Vega (gfx900) ... no changes. GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF GPU1: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF GPU2: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF GPU3: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF GPU4: Radeon RX Vega (gfx900) | HBCC: ON | Large Pages: ON GPU5: Radeon RX Vega (gfx900) | HBCC: ON | Large Pages: ON
[Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-24 22:09:44] 0:06:53 (100%) Online 0:00:00 ( 0%) Offline
[Job: #10 | Difficulty: 74880 | Running: 34.0 sec | Avg Job Time: 42.0 sec]
[Hash Rate Avg: 3590.7 H/s] 785.5 H/s GPU0 767.1 H/s GPU1 780.2 H/s GPU2 786.5 H/s GPU3 197.2 H/s GPU4 274.2 H/s GPU5
[Shares Found: 24 | Avg Search Time: 17.2 sec] 22 ( 92%) Accepted 0 ( 0%) Rejected by pool 0 ( 0%) Invalid result computation failed 0 ( 0%) Could not be submitted because of network error 2 ( 8%) Outdated because of job change
|
|
|
Hi! I want to mining VIVO, and search good pool, I see NET hash speed VIVO this moment 4.5Gh/s, I monitoring and test all pool present in this topic and NO see any power pool... 0-3 or 0-5 or totally 0 miners VIVO... with hash speed 0-2 or 0-10 Mh/s... Where a power pool 100Mh/s-1Gh/s=? Tnx.
|
|
|
Hi! I use 6xVega64, after enable --maxmem option, on my RIG, cast_xmr work better, but I see message: HBCC Memory Segment is enabled. Up to 3% higher hash rate can be achieved for this card by disabling it in the Radeon Settings. GPU5: gfx901 | 64 Compute Units | Memory (MB): 8176 Radeon Settings not installed on my RIG, I use OverdriveNTool and registry table edited parameters.if possible or maybe you know, how to disabling HBCC Memory Segment in *regedit registry table? Win10x64 driver 22.19.659.0 Thanks! not possible without wattman what driver do u use ? old blockchain or adrenaline ? Hi! Wattman - not use it, from this program there is no use. I use old blockchain driver because new 18.3.4 not good work on my RIG, from 6xVega64 4GPUs-work fine 2025Hs and two GPUs 200Hs - no wont’s good work. A new driver fine work if you use no more 4GPUs...
|
|
|
Hi! I use 6xVega64, after enable --maxmem option, on my RIG, cast_xmr work better, but I see message: HBCC Memory Segment is enabled. Up to 3% higher hash rate can be achieved for this card by disabling it in the Radeon Settings. GPU5: gfx901 | 64 Compute Units | Memory (MB): 8176 Radeon Settings not installed on my RIG, I use OverdriveNTool and registry table edited parameters.if possible or maybe you know, how to disabling HBCC Memory Segment in *regedit registry table? Win10x64 driver 22.19.659.0 Thanks!
|
|
|
Если воспринимать Hash Rate как часть энергии которая выделяет тепло и прочее
будет логично:
1. Криптобатарея - выделяет тепло за счет добычи (майнинга) 2. Криптолампочки - на оплату потребленной энергии 3. и много др. устройств
т.е. цикл должен быть автономный, неотъемлемой частью возобновляемой энергии.
Спасибо.
|
|
|
Здравствуйте, анализируя принципы взаимодействия я пришёл к выводу (идеи) что процесс который называется майнинг это платформа к созданию вечного HDD с скоростью записи и считывания которая будет равняться максимальной пропускной способности сети, иными словами, условный спектр который понимают как Hash Rate. изучая графики сложности и стоимости пришел к выводу что они самые и являются чувствительными элементами в спектре, т.е. как взаимодействие поля магнитного или электромагнитного на что то...
итак: мысль: криптомодулятор-детектор, криптотранслятор, криптодискриминатор.
Если частота которая называется Гц это колебание , то 1H/sec -это также колебание
На этом основана идея.
Т.е. если я возьму и буду воздействовать на параметр Difficulty ( возможно и другие варианты - market price...) получится модуляция)
т.е. точка входа в сеть или воздействие на неё)
далее берем уже готовые принципы и механизмы для создания транслятора, далее файловая система и разметка и т.д.
Т.е. суть такая что процесс майнинга крутится* - некая несущая частота (условно) , Hash-это молекулы атомы)
Спасибо.
|
|
|
|