Ninjastic
Search content
Sort by
Showing 20 of 181 results by uhro
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][PRE-ICO] Timechain MetaWallet + Exchange Token Sale is about to go LIVE!
by
uhro
on 20/07/2018, 14:52:57 UTC
Why develop your own wallet? Can't people just use the standard wallets or a hardware wallet? Is it a security thing?
Post
Topic
Board Announcements (Altcoins)
Re: ✅ [ANN] LIGHTPAYCOIN LPC ⭐ MASTERNODES ✅ POS ⭐ MNO AND CRYPTOBRIDGE LISTED ✅
by
uhro
on 20/07/2018, 14:51:37 UTC
A profit diagram... As if you were able to exactly predict what returns a Lightpay could make with your coin. If you fail to deliver what happens then?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [SelfSell] Share your excellence with the world!
by
uhro
on 20/07/2018, 14:50:52 UTC
Do you have some signature activities to reward? I am very optimistic about your project. The future world must be investor-themed.
Post
Topic
Board Mining (Altcoins)
Re: Shared Ideas of Ways to Manage Heat From Mining in a Home or Warehouse
by
uhro
on 29/05/2018, 03:49:05 UTC
Quote from: dmwardjr on May 03, 2018, 12:41:03 AM
Quote from: Suslived on May 02, 2018, 10:58:45 AM
Quote from: dmwardjr on May 02, 2018, 09:15:06 AM
Another 77 inch wide rack is about to be setup inside here and the rigs on the 48 inch wide rack will be transferred over to it.  The 48 inch can hold eight rigs.  The 77 inch wide rack can hold 12 rigs at 3 rigs per shelf.
-snip-

That is a pretty sick mining room. I love the custom built mining rig cases. Seems like a good combination of wood and aluminum(?). Although some might say that all the wood is a big fire safety risk. You mind me asking what GPUs are you using? Seems like you've diversified into both AMD and NVIDIA.

Thanks, appreciate it.  I "hope" it will be to everyone's liking when completed.  I have other things I could have done with plexiglass and LED's but that will have to wait a while.  It's not a fire safety risk to me.  I have several smoke alarms, fire extinguishers, I'm ready.

Currently what I have at my place:

12 x EVGA NVIDIA 1070 Ti FTW2
52 x EVGA NVIDIA 1080 Ti FTW3
12 x XFX R9 390
36 x Sapphire R9 Fury
24 x R9 380
89 x RX 480
7 x RX 580
TOTAL OF 232 x GPU's at my place.

2 x Sapphire R9 Fury rigs and 1 x NVIDIA 1080 Ti rig is in the office in addition to what you see in the mining room I'm remodeling.

I gave my dad the following OLD rigs:

48 x R9 380's
7 x Bitmain S7's

He will also be purchasing some NVIDIA's very soon.  I plan on giving him my remaining R9 380's as I replace them with NVIDIA cards.

What is the hydro service you are running this on?  400amp 240v?
Post
Topic
Board Mining (Altcoins)
Re: Octominer B8PLUS 8 PCIe Slot Mining Board (Motherboard, integrated CPU)
by
uhro
on 15/05/2018, 14:30:24 UTC
Quote from: RsvTu on May 15, 2018, 11:33:10 AM
One thing i noticed:

When you dont have monitor attached to vga port of octoboard and reboot device -> login with remote desktop like Anydesk, you will get black screen. Once monitor connected again and reboot it works OK. I guess no other solution than get VGA dummy / emulator

I was really considering some of these boards, but if this is the case they won't work for me...
Post
Topic
Board Mining (Altcoins)
Re: Stop Windows 10 Update
by
uhro
on 15/05/2018, 14:13:46 UTC
This works for me...
Windows 10 in various scenarios will turn windows update back if all you do is disable the service.
To disable updates in Windows 10 is go to the Windows update Service property window, disable it, then go to the Log On tab at the top and click This account: and type ".\Guest"(no quotes), clear the password fields and click apply.
You will get a message saying Guest has been enabled to do this, but the hitch is that "Guest" doesn't have permission to do it so Windows update is basically disabled no matter what unless you switch it back which is just as easy.
Post
Topic
Board Mining (Altcoins)
Re: Windows Update Problem on mining rigs....
by
uhro
on 15/05/2018, 14:13:29 UTC
This works for me...
Windows 10 in various scenarios will turn windows update back if all you do is disable the service.
To disable updates in Windows 10 is go to the Windows update Service property window, disable it, then go to the Log On tab at the top and click This account: and type ".\Guest"(no quotes), clear the password fields and click apply.
You will get a message saying Guest has been enabled to do this, but the hitch is that "Guest" doesn't have permission to do it so Windows update is basically disabled no matter what unless you switch it back which is just as easy.
Post
Topic
Board Mining (Altcoins)
Re: Windows update anyone else got wrecked?
by
uhro
on 15/05/2018, 14:07:01 UTC
Windows 10 in various scenarios will turn windows update back if all you do is disable the service.
Easiest way I found to disable updates in Windows 10 is to goto the Windows update Service property window, disable it, then goto the Log On tab at the top and click This account: and type ".\Guest"(no quotes), clear the password fields and click apply.
You will get a message saying Guest has been enabled to do this, but the hitch is that "Guest" doesn't have permission to do it so Windows update is basically disabled no matter what unless you switch it back which is just as easy.
Post
Topic
Board Mining (Altcoins)
Re: who bought bitmain Z9 will face a big issues now
by
uhro
on 09/05/2018, 11:40:10 UTC
This same situation will repeat itself over and over.
An ASIC will come out for algo x and some of the coins using that algo will fork to remain ASIC resistant, and some won't.

Anyone who bought a Z9 (or other new algo ASICs) will still be able to mine something, just maybe not the coin(s) they were hoping for.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.33 (Mar 23)
by
uhro
on 05/04/2018, 11:44:24 UTC
Quote from: wishxy on April 04, 2018, 10:59:06 PM
Quote from: deimo on April 04, 2018, 06:06:37 AM
Quote from: cveks on April 03, 2018, 04:42:35 PM
I have one righ with 4 x RX 470 . Problem is that 3 card works but 4th wont work whatever setting I try . It gives 0 hash power. Do you have any solutions for this?

I tried on other rig with 6 x RX 470 same problem.

either your work batch is too high, or your virtual memory too low

Same problem here on one rig with 6x RX 470.
I've set working batch on AUTO, but the problem still occurs and shows 0 MH/s on Device 2 (card on the main slot.)
Also, have the same problem with other mining software so I guess I should better reinstall Win 10.

This makes me think it's something to do with onboard video.
Do either of you have onboard video enabled?  Primary video should be set to PCIE and iGPU should be disabled in MB BIOS.
Might not be the problem, just a though.
Post
Topic
Board Announcements (Altcoins)
Re: [$XVG] VERGE [POW][MultiAlgo][BLACKHOLE][Entire Line of TOR/i2P Resources]
by
uhro
on 04/04/2018, 15:31:22 UTC
Quote from: ocminer on April 04, 2018, 02:13:31 PM
There's currently a >51% attack going on on XVG which exploits a bug in retargeting in the XVG code.

Usually to successfully mine XVG blocks, every "next" block must be of a different algo.. so for example scrypt,then x17, then lyra etc.

Due to several bugs in the XVG code, you can exploit this feature by mining blocks with a spoofed timestamp. When you submit a mined block (as a malicious miner or pool) you simply
set a false timestamp to this block one hour ago and XVG will then "think" the last block mined on that algo was one hour ago.. Your next block, the subsequent block
will then have the correct time.. And since it's already an hour ago (at least that is what the network thinks) it will allow this block to be added to the main chain as well.

This is what is going on since about 06:00 UTC of 04.04.2018:

Code:
SetBestChain: new best=00000000049c2d3329a3  height=2009406  trust=2009407  date=04/04/18 13:50:09
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000a307b54dfcf  height=2009407  trust=2009408  date=04/04/18 12:16:51
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000196f03f5727e  height=2009408  trust=2009409  date=04/04/18 13:50:10
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000010b42973b6ec  height=2009409  trust=2009410  date=04/04/18 12:16:52
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000e0655294c73  height=2009410  trust=2009411  date=04/04/18 12:16:53
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000013490372b825  height=2009411  trust=2009412  date=04/04/18 12:16:54
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000017192ea8924b  height=2009412  trust=2009413  date=04/04/18 13:50:13
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000007f75f237b3b  height=2009413  trust=2009414  date=04/04/18 12:16:55
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000006ecb5753261  height=2009414  trust=2009415  date=04/04/18 13:50:14
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000019eb5bfd2f76  height=2009415  trust=2009416  date=04/04/18 12:16:56
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000018d5b80c0ee9  height=2009416  trust=2009417  date=04/04/18 13:50:15
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000159ca0701894  height=2009417  trust=2009418  date=04/04/18 12:16:57
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000ad1a8cd6b44  height=2009418  trust=2009419  date=04/04/18 13:50:16
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001002986218fc  height=2009419  trust=2009420  date=04/04/18 12:16:58
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000b58e4fed470  height=2009420  trust=2009421  date=04/04/18 13:50:17
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000d9f0707d83f  height=2009421  trust=2009422  date=04/04/18 12:16:59
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000007283d98dbb0  height=2009422  trust=2009423  date=04/04/18 12:17:00
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000002ec7b8a6e80  height=2009423  trust=2009424  date=04/04/18 12:17:01
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001f359a8f2f4a  height=2009424  trust=2009425  date=04/04/18 13:50:20
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000293a6723940  height=2009425  trust=2009426  date=04/04/18 12:17:02
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001397927ec69d  height=2009426  trust=2009427  date=04/04/18 13:50:21
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000efb6e062c02  height=2009427  trust=2009428  date=04/04/18 12:17:03
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001e181a0d0f4a  height=2009428  trust=2009429  date=04/04/18 13:50:22
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000008ca5848691b  height=2009429  trust=2009430  date=04/04/18 12:17:04
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000066a216ac27b  height=2009430  trust=2009431  date=04/04/18 13:50:23
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001874a45f28c7  height=2009431  trust=2009432  date=04/04/18 12:17:05
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000005bc0408b8ca  height=2009432  trust=2009433  date=04/04/18 13:50:24
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000005feb2b45e5d  height=2009433  trust=2009434  date=04/04/18 12:17:06
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000000c211ba04de  height=2009434  trust=2009435  date=04/04/18 12:17:07
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001402dc20ae5f  height=2009435  trust=2009436  date=04/04/18 12:17:08
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001e73181cf91c  height=2009436  trust=2009437  date=04/04/18 13:50:27
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000062720b222ea  height=2009437  trust=2009438  date=04/04/18 12:17:09
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000e10aeecf7f1  height=2009438  trust=2009439  date=04/04/18 13:50:28
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000b41ab258a8f  height=2009439  trust=2009440  date=04/04/18 12:17:10
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001136b924f67b  height=2009440  trust=2009441  date=04/04/18 13:50:29
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000a1c1af529cd  height=2009441  trust=2009442  date=04/04/18 12:17:11
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000007f1d1f8d921  height=2009442  trust=2009443  date=04/04/18 13:50:30
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000ca0a1bc6b0e  height=2009443  trust=2009444  date=04/04/18 12:17:12
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000003075b7a580  height=2009444  trust=2009445  date=04/04/18 13:50:31
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001c9f43fd7305  height=2009445  trust=2009446  date=04/04/18 12:17:13
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000009129b024a  height=2009446  trust=2009447  date=04/04/18 12:17:14
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000008e180f24f15  height=2009447  trust=2009448  date=04/04/18 12:17:15
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000084eb6c59c6d  height=2009448  trust=2009449  date=04/04/18 13:50:34
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000d8510f41c9a  height=2009449  trust=2009450  date=04/04/18 12:17:16
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000011df91a1ab87  height=2009450  trust=2009451  date=04/04/18 13:50:35
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001ba92e976854  height=2009451  trust=2009452  date=04/04/18 12:17:17
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000364bf981384  height=2009452  trust=2009453  date=04/04/18 13:50:36
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000012d88fa3db27  height=2009453  trust=2009454  date=04/04/18 12:17:18
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000305cd62b1f2  height=2009454  trust=2009455  date=04/04/18 13:50:37
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000011300c4f86cb  height=2009455  trust=2009456  date=04/04/18 12:17:19
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000001487b026dd4  height=2009456  trust=2009457  date=04/04/18 13:50:38
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000001c8532ef2df  height=2009457  trust=2009458  date=04/04/18 12:17:20
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001c17ae6efeeb  height=2009458  trust=2009459  date=04/04/18 12:17:21
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000002bf168f5eab  height=2009459  trust=2009460  date=04/04/18 12:17:22
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001a23e2c283bc  height=2009460  trust=2009461  date=04/04/18 13:50:41
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000014ecd97066c4  height=2009461  trust=2009462  date=04/04/18 12:17:23
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001643a1c4a3bb  height=2009462  trust=2009463  date=04/04/18 13:50:42
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000008ec0214e6c2  height=2009463  trust=2009464  date=04/04/18 12:17:24
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000009b069fcd1cc  height=2009464  trust=2009465  date=04/04/18 13:50:43
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001722adbca417  height=2009465  trust=2009466  date=04/04/18 12:17:25
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000a9e8d58c86b  height=2009466  trust=2009467  date=04/04/18 13:50:44
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000010f27ab0a452  height=2009467  trust=2009468  date=04/04/18 12:17:26
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000479c982db76  height=2009468  trust=2009469  date=04/04/18 13:50:45
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001f8be1b4066c  height=2009469  trust=2009470  date=04/04/18 12:17:27
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000b05233d5ad7  height=2009470  trust=2009471  date=04/04/18 12:17:28
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000007a9c6cdba5d  height=2009471  trust=2009472  date=04/04/18 12:17:29
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000622e29e4307  height=2009472  trust=2009473  date=04/04/18 13:50:48
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001a8d80324a57  height=2009473  trust=2009474  date=04/04/18 12:17:30
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001eddc0154526  height=2009474  trust=2009475  date=04/04/18 13:50:49
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000ac0a256f263  height=2009475  trust=2009476  date=04/04/18 12:17:31
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000040f83b5ee2f  height=2009476  trust=2009477  date=04/04/18 13:50:50
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001827966aa60b  height=2009477  trust=2009478  date=04/04/18 12:17:32
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000012d0d1501121  height=2009478  trust=2009479  date=04/04/18 13:50:51
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000032868a4c74  height=2009479  trust=2009480  date=04/04/18 12:17:33
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000092675395f6e  height=2009480  trust=2009481  date=04/04/18 13:50:52
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001f95a9a174d4  height=2009481  trust=2009482  date=04/04/18 12:17:34
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000017503fc3dc13  height=2009482  trust=2009483  date=04/04/18 12:17:35
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000007c61b36c76  height=2009483  trust=2009484  date=04/04/18 12:17:36
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000070810d5a6e5  height=2009484  trust=2009485  date=04/04/18 13:50:55
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000068467683637  height=2009485  trust=2009486  date=04/04/18 12:17:37
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000041dc83f0978  height=2009486  trust=2009487  date=04/04/18 13:50:56
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000011fb17203f4  height=2009487  trust=2009488  date=04/04/18 12:17:38
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000a96b38de1a0  height=2009488  trust=2009489  date=04/04/18 13:50:57
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000121e7a285719  height=2009489  trust=2009490  date=04/04/18 12:17:39
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000348e668204f  height=2009490  trust=2009491  date=04/04/18 13:50:58
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000012766d85cab4  height=2009491  trust=2009492  date=04/04/18 12:17:40
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000181a0c1be275  height=2009492  trust=2009493  date=04/04/18 13:50:59
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000015c05593e210  height=2009493  trust=2009494  date=04/04/18 12:17:41
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000719cb24d9c0  height=2009494  trust=2009495  date=04/04/18 12:17:42
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000015d9b853834d  height=2009495  trust=2009496  date=04/04/18 12:17:43
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000115e68a6d447  height=2009496  trust=2009497  date=04/04/18 13:51:02
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000004d9233f19c6  height=2009497  trust=2009498  date=04/04/18 12:17:44
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000141ab049fe19  height=2009498  trust=2009499  date=04/04/18 13:51:03
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001b91344fa33c  height=2009499  trust=2009500  date=04/04/18 12:17:45
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=0000000001d112440f7b  height=2009500  trust=2009501  date=04/04/18 13:51:04
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000001bf2c8a073c6  height=2009501  trust=2009502  date=04/04/18 12:17:46
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000116863c0157c  height=2009502  trust=2009503  date=04/04/18 13:51:05
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000ec5da17852e  height=2009503  trust=2009504  date=04/04/18 12:17:47
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=000000000d7cd87c5e53  height=2009504  trust=2009505  date=04/04/18 13:51:06
ProcessBlock: ACCEPTED (scrypt)
--
SetBestChain: new best=00000000156becbf42cd  height=2009505  trust=2009506  date=04/04/18 12:17:48
ProcessBlock: ACCEPTED (scrypt)


As you can see in the text above, those blocks are all subsequent, so one miner gets them all and you see there's 90 min difference between all the blocks, thats one bug the miner is
exploiting. You also see the correct time is the latter time.. so the last block ended on 13:51:06 and the block before was 12:17:47 and the block with the correct time before that one
was at 13:51:05 .. That means the hacker is mining one block per second !

The vergeDEV @ Discord says "everything is okay - there's nothing to fix"..

Since about 99% blocks by legit pools are rejected - and the dev team is not able to understand this problem, i'm closing and removing all VERGE pools from suprnova.



If this is the case, XVG is done.
Big pools are bowing out because of an exploit and the dev team doesn't think there is a problem?
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.33 (Mar 23)
by
uhro
on 30/03/2018, 12:42:29 UTC
Quote from: amdfxman1701 on March 30, 2018, 02:33:35 AM
Quote from: paramecie on March 29, 2018, 12:51:58 PM

Pfff - some use Windows because they've much important things to do in their lives than to invest time and energy in learning or using Linux.

This is precisely the lazy, self-entitled attitude I'm talking about. You had a need (linux miner) and refused to meet that need by taking a few hours to set up a linux miner. Thus, you missed out on several weeks, if not months, of mining MNX at much more profitable rates.

This isn't about Windows vs Linux. This is about doing what you need to do to get things done.

I actually setup linux on a bunch of usb sticks and ran my rigs with Optiminer for a couple of those more profitable months, but when 4/570s and 4/580s are hashing just as good as my 1080tis I gave up because Optiminer wasn't advancing, it was what it was and it was pretty clear there wasn't any optimizations coming.

When this miner came out I gave it a try and WHAM!, my 1080TIs are going 20k+, more than twice what Optiminer was giving me in Linux.
To me, this just highlighted the need for a more optimized version of the miner for high end cards (I would have run this miner even if it was Linux only), if Optiminer had done it I would probably be running his miner right now, but as I said before, he thought he cornered the market and sat on an unfinished product.

Sure others may have lost out not using Linux early on, but this was a much needed miner and optiminer is the one losing out now because he didn't bother to continue developing his miner.  He could have have made it totally unnecessary for another miner to be developed by optimizing his for high end cards and putting out a Windows miner (as I said, i would be fine without Windows version, but it is easier).

Optiminer opened the door for this project by ignoring the users requests for improvements and a Win version.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.33 (Mar 23)
by
uhro
on 29/03/2018, 00:32:36 UTC
Quote from: paramecie on March 28, 2018, 10:55:10 PM
Quote from: optiminer on March 28, 2018, 10:13:09 PM
Ah okay, so you claim it to be GPL code-free. That's fine. I do not have the code available so I cannot say much about that. But for parts of the opencl kernel it's obvious that you started from GPLed code and modified it from there (probably a lot). Just try this: https://www.google.com/search?q=%22occupy+the+high+32+bits+of+the+second+ulong+word%22

Hi-

This isn't constructive.

He proposed you to check the code:
https://bitcointalk.org/index.php?topic=2933939.msg33126032#msg33126032

AFAIK, optiminer is for linux? Did you make a Windows miner? What's the problem?

Nobody here know what you want "optiminer", aren't concerned, and can't do anything about this. We don't understand insinuations.

Please use PM, and better, find a way in between both 2. Why don't you you both make a perfect miner for Windows and Linux?

Optiminer, you seem to be putting a lot of effort into trying to discredit this project (I'm assuming you are feeling the drop in usage on your miner), but as I said before, you have had people asking you to do a Windows version for MONTHS now, why not just spend that effort on making a better miner rather than attacking this one?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][SPD][BOUNTIES:ON] PoW/PoS/Masternode - Stipend - The Freelancer's Currency
by
uhro
on 26/03/2018, 11:59:14 UTC
Not sure on the future of this project, but startups with very short PoW phase and a pre-mine are notoriously scams.
Masternodes on a short PoW are to keep people holding/buying to get MNs up, then dev coins get dumped shortly after PoS comes online and nobody hears from them again.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.33 (Mar 23)
by
uhro
on 25/03/2018, 16:17:00 UTC
Quote from: Lolliedieb on March 25, 2018, 11:42:25 AM
Quote from: uhro on March 24, 2018, 07:52:14 PM
The --exit-on-zero option doesn't seem to be working, I just had my rig run for about half hour at 0 before I caught it...

I will try it if its working here. Did you disable long stats? Because when that print out is disabled its not workkng.


No, the only things I changed in the stock cfg file were:
1. set user to my address.rig
2. set-work-batch to AUTO
3. set-short-stats-interval to 15 <-- think this is the only odd thing I did but it shouldn't matter
4. took the comment off exit-on-zero flag

Then ran it, it has happened to me on 2 different 4x 1080ti rigs and a 6x 1080 rig, all have ran fine for months doing other mining.
When they do run for a while (I think my longest run is 14 hours so far) they eventually crash with the "close program" dialog box that comes up so the miner won't even restart until you go click the close program button.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.33 (Mar 23)
by
uhro
on 24/03/2018, 19:52:14 UTC
The --exit-on-zero option doesn't seem to be working, I just had my rig run for about half hour at 0 before I caught it...
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.33 (Mar 23)
by
uhro
on 24/03/2018, 02:40:45 UTC
Quote from: optiminer on March 23, 2018, 11:58:19 PM
Under what license is this miner distributed?

Is the source available? It seems to use GPLed code, so I would expect it to be.

Do you hate Windows or something?
People have been asking you to do a Windows version of your MNX miner for 4+ months and now that there is one that's actively being developed you're questioning it...
I agree it's probably something that should be open source, but as a miner, I'm just happy someone is finally actively developing a Windows version, something you could have done months ago.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.31 (Mar 15)
by
uhro
on 21/03/2018, 12:24:19 UTC
Quote from: Vladeg on March 19, 2018, 11:19:03 AM
New target received: 0t0000c7a408c16d5397624752b150dc00c222afeffaf2e6e6dd11e332e2aaeccerminate called after throwing an instance of '
std::bad_alloc'
 N what():  ew job received: std::bad_alloc1

Got this error. Rig 5x1080, set-work-batch is 2G or 8, both gives same result.

I get this sometimes too.  I tried on all stock setting on a 1080ti rig and a 1080 rig and both have the same issues with this miner so far.
When my cards don't go to 0 sol/s (all stock setting), this error will come up within the first 5-10 mins.
I am running Win10 x64 1709 on the 2 rigs I tried with and they had been running error free for months doing algo switching so I'm thinking they aren't the problem.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] lolMiner-mnx, Mining MinexCoin(MNX) New version: v0.31 (Mar 15)
by
uhro
on 18/03/2018, 15:39:40 UTC
Quote from: surkoff on March 17, 2018, 03:28:32 PM
After working 30s goes to 0 Sol/s and than crashes. 3x1070 + 3x1080 works in stock...

I have the same issue trying to run a 4x 1080ti rig stock, except mine just keeps running at 0 (maybe I killed it before it crashed though), no errors, just goes from 20k sols/card to 0.
Once and a while it will run for a bit but will crash if it looses connection (not sure why it lost connection, all the other rigs on that switch are still hashing away with no problems).
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] STRAKS - Decentralised, Open Source, Community Driven Digital Currency
by
uhro
on 08/01/2018, 22:20:55 UTC
Anyone barking scam is just mad they missed the swap.

The Straks project has been very transparent so far and very active in their community.  The SIGT swap was just an emotional giveback to the community because many of the STRAKS devs themselves were burnt by SIGT.

Don't come talking about scams without proof, it's lame and childish.

They have a long way to go, but it's been a pretty good start IMO.