Avast? Seriously? The last few versions are becoming increasingly annoying.
Just have your mass wallets on linux cold storage. Connect every once in a while to recharge your live wallets and be done with it.
|
|
|
Pffft! You lost me with the ending!
|
|
|
THANKS AGAIN! You're welcome. I hope neuro and the other folks at myr can get the old system at least marked as non-updated anymore! I know they're all fairly busy with their real world life right now.
|
|
|
Not to worry. The original source is always cited (in this case if you scroll down to the bottom of the post, you'll see it).
The idea is not to re-invent, but to consolidate and make pertinent digital currency information as less "techie" and the most accessible to the general public as possible.
I'm pretty sure I'm being misunderstood. The document you have produced reads: "Taken from the most updated source available compiled from actual miner inputs: http://myriad.theblockexplorer.com/help.php". Which is the same as Taken from the old myriad configuration settings. It's not a problem of attribution. Feel free to use the data as you see fit. Albeit it has never been stated, I'd assume it's public domain. The problem is that your source is obsolete and has been obsolete for months. The source you pointed to is not the official MYR configuration anymore and it is not being maintained AFAIK. All the data was ported in gdocs so they effectively replace the old tables.
|
|
|
Taken from the old myriad configuration settings. Myriad transitioned to gdocs months ago. GPU benchmarksCPU benchmarksASIC benchmarksGdocs gives a few advancements, it's easier to manage and fully collaborative-oriented, implying your additions can be seen in real time as opposed to require a review.
|
|
|
It was my understanding this coin was a community experiment.
|
|
|
I’ve started to populate the mining section of the new forum: http://asistec-ti.com "FORUM" > "Mining - how you can mine 'em" > "Hardware" > "What Do I Need to Mine with a GPU?" I would just make the forum open exactly like any other web page. I find the current opening (in its own window) very invasive compared to normal workflow with modern browsers. Tabs shall be allowed.
|
|
|
DGB beating DOGE? I'd love to see that happen. It certainly has potential. Sadly, the old DOGE I admired is no more there.
|
|
|
Oddly enough, I have tested both pools and I can tell those are supposed to work. Do the shares get confirmed or rejected? While blocksfactory reports my hashrate in less than a minute, it can take up to 10 minutes before I get listed on P2P. I am now working on the nonce-checking system which would allow to detect kernel wrong results. Nonetheless: - I know by direct experience old drivers don't compile the kernels correctly.
- I have received comments in the past about compatibility with hi-end cards. With no hardware and no extensive testing this cannot be fixed any time soon; hopefully next release will alleviate the problem.
- I have received comments about compatibility with multi-gpu systems. Oddly, some users also reported the thing works exactly as expected. Again, with no hardware and very sporadic feedback the chance this gets fixed any time soon is extremely slim.
|
|
|
A new version of M8M is out.The algorithms (qubit, grs-myr) are unchanged but hopefully fixed the long-standing bug of high rejects on some pools. There's some slight chance this fixed bug might have impacted high-performance configurations as well but this can only be confirmed by testing. Required: Windows x64, AMD GCN card (tested to work on 7750), drivers 14.12 Ω. Please report all issues with pools and configurations. I have got some complaints by high-hashrate users who cannot get their boxes to hash correctly. Hopefully the new drivers and the new difficulty calculation will fix that issue as well. Note there's no thread for this miner as it's still little more than an experiment at this point. I'm considering a subreddit however. In the meanwhile, I attach it to the minable coins.
|
|
|
That looks a bit too good to be true, let's hope it holds.
|
|
|
A new version of M8M is out.Hopefully fixed the long-standing bug of high rejects on some pools. It turns out the difficulty calculation was wrong. I have trouble understanding how this could go unnoticed so far but since I have been mining only on a couple of pools I guess I have been lucky. There's some slight chance this fixed bug might have impacted high-performance configurations as well but this can only be confirmed by testing. Required: Windows x64, AMD GCN card (tested to work on 7750), drivers 14.12 Ω. Wait! Last drivers? Yep. This is for occasional users and I want them to keep their systems up to date. I am proud to say it keeps my system so smooth I can play simple video games while mining and still being at least as efficient as established miners. Please report all issues with pools and configurations. Hopefully the reject rate is now on a reasonable level.
|
|
|
Update on the above issue: DBG-qubit pool uses --difficulty-multiplier 1 instead of the standard qubit 256 multiplier. Albeit this is apparent once one checks worker status, it should be noted in setup instruction.
Of course, I would much rather see the pool move to the appropriate difficulty multiplier but that's it.
|
|
|
I'm playing Qbeh-1. It's a simple game. The mechanics are solid but there are a few glitches here and there. I was expecting more from something UDK based. Interestingly enough, I cannot run this simple game while using a legacy miner. By contrast, I lose only 10fps if I mine using my own, even if it's doing NeoScrypt!
|
|
|
I see nothing wrong with the farmers going for dual-production. Their work habits don't shift in a day. Perhaps they will go completely hi-quality in the future but as long as the race-to-bottom continues I guess that's not foreseeable future. Vote with your wallets.
In the meanwhile, if they feel their family requires hi-quality food, I really won't blame them.
|
|
|
Lyra2RE, which is use in Vertcoin after switching from Scrypt-N (in my opinion, switching the hashing algorithm is a bad idea unless there is some serious flaw). From the zero, Lyrabar. We also have NeoScrypt. "We" ... who?
|
|
|
Duuuuudes! VTC is 15th coin on Coingecko right now. That's exciting that market cap must go up up up!
|
|
|
Please add this to your command line if you are having issues. --difficulty-multiplier 1 I am very well aware of that switch (sgminer issue #312, #317). The real question "between the lines" is... why is this still needed in 2015? This is unnecessarily fragmenting a standard as far as I am concerned and that switch makes the problem worse. The bottom line is that the end user should not be concerned about this. Why is this happening?
|
|
|
Trying to improve compatibility of my miner, I ended up stumbling on a rather odd situation. I cannot figure out if this is something I should figure out or signal to pool operator. Using sgminer as pulled out from sgminer-5.1-2014-12-20-win32.zip, just downloaded from nicehash. My hardware gives 1141 khs with the following settings: sgminer --no-extranonce -o uk.p2pool.geek.nz:5567 -k qubitcoin -u WALLET -p bleh -I 16 (P2P qubit uk node) Resulting in: sgminer 4.2.2-310-g8985f-dirty - Started: [2015-02-02 18:05:40] - [0 days 00:05: -------------------------------------------------------------------------------- (5s):1.137M (avg):1.142Mh/s | A:19 R:0 HW:0 WU:4.000/m ST: 1 SS: 0 NB: 8 LW: 474 GF: 0 RF: 0 Connected to uk.p2pool.geek.nz (stratum) diff 18 as user MCmR2QAnPeHbJWgRT23Rh45 Block: 412ac196... Diff:19.2K Started: [18:10:08] Best share: 39 -------------------------------------------------------------------------------- [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 0: 48.0C 39% | 1.139M/1.142Mh/s | R: 0.0% HW:0 WU:4.000/m I:16 -------------------------------------------------------------------------------- [18:05:38] Startup GPU initialization... Using settings from pool uk.p2pool.geek .nz. [18:05:38] Startup Pool No = 0 [18:05:39] Initialising kernel qubitcoin.cl with bitalign, unpatched BFI, nfacto r 10, n 1024 [18:05:40] uk.p2pool.geek.nz difficulty changed to 2.375 [18:05:40] Accepted 4b37fc99 Diff 3.403/2.343 GPU 0 [18:05:41] uk.p2pool.geek.nz difficulty changed to 2.382 [18:05:41] Accepted 0b74b9f3 Diff 22/2.375 GPU 0 [18:05:42] uk.p2pool.geek.nz difficulty changed to 4.709 [18:07:07] Accepted 314b179b Diff 5.193/4.709 GPU 0 [18:07:17] uk.p2pool.geek.nz difficulty changed to 9.408 [18:08:13] Accepted 06739e9b Diff 39/9.408 GPU 0 [18:08:30] uk.p2pool.geek.nz difficulty changed to 18.798
Diff 18 is already extreme for a 1MHs miner, staying at 4.5 would be more appropriate in my opinion but at least I got some initial accepts which confirm me this thing is working and after all, the pool is trying to guess against my luck. Now, let's try again with noncepool: sgminer --no-extranonce -o mine1.myr.nonce-pool.com:3360 -k qubitcoin -u login.worker -p bleh -I 16 sgminer 4.2.2-310-g8985f-dirty - Started: [2015-02-02 18:19:40] - [0 days 00:03: -------------------------------------------------------------------------------- (5s):1.141M (avg):1.145Mh/s | A:0 R:0 HW:0 WU:4.190/m ST: 2 SS: 0 NB: 6 LW: 215 GF: 0 RF: 0 Connected to mine1.myr.nonce-pool.com (stratum) diff 512 as user MaxDZ8.wtf Block: 29351c6b... Diff:18.4K Started: [18:21:58] Best share: 30 -------------------------------------------------------------------------------- [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit GPU 0: 47.0C 39% | 1.142M/1.145Mh/s | R: 0.0% HW:0 WU:4.190/m I:16 -------------------------------------------------------------------------------- [18:19:33] Started sgminer 4.2.2-310-g8985f-dirty [18:19:33] * using Jansson 2.6 [18:19:33] Probing for an alive pool [18:19:38] mine1.myr.nonce-pool.com difficulty changed to 512 [18:19:38] Startup GPU initialization... Using settings from pool mine1.myr.nonc e-pool.com. [18:19:38] Startup Pool No = 0 [18:19:38] Initialising kernel qubitcoin.cl with bitalign, unpatched BFI, nfacto r 10, n 1024
Diff 512, WTF. This apparently relates to the "difficulty multiplier". Please give this a go and provide results, I need to test a few pools to figure out what's going on.
|
|
|
|