Just kidding they're still down. I had all four go into Enabled for about 15 minutes, then back to watchdog expired.

Masternodes back online for me. Did all the troubleshooting others have listed, but I'm guessing the IPs were being ddos'd as they were previously unreachable.

Error in the Windows wallet as well.

Event Logs:
Faulting application name: BLOC.exe, version: 0.0.0.0, time stamp: 0x5b03c678
Faulting module name: BLOC.exe, version: 0.0.0.0, time stamp: 0x5b03c678
Exception code: 0xc000001d
Fault offset: 0x00000000003767f0
Faulting process id: 0x3b98
Faulting application start time: 0x01d3f210182d21e9
Faulting application path: C:\bloc\BLOC.exe
Faulting module path: C:\bloc\BLOC.exe
Report Id: ace72401-a2b0-4c7a-ab13-18fec7e31318
Faulting package full name:
Faulting package-relative application ID:


Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program BLOC.exe because of this error.

Program: BLOC.exe
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
   - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
   - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

4.5 WAVI every 18 hours is normal. If you set your MN up correctly, you should see a payment in of 4.5 every 18ish hours. There are fluctuations, but that does seem correct.

Thanks for the update, it's good to know you're still dedicated to the project.

What's a 'reup'? Just a re-upload? What's the purpose in re-uploading the binary?

The GUI is coming. Take advantage of the network pre-GUI and use the guidelines posted in the original post. Every instruction can be found there. Following the instructions = profit

Your numbers are correct. Yenten uses yescryptr16 while WAVI uses the yescryptr32 algorithm. Yescryptr32 by design will mine at half the hashrate as yescryptr16. It's part of what makes yescryptr32 more GPU and asic resistant compared to yescryptr16.

Because everyone's client application is programmed to talk to the MN on port 1393. You can't change what port the wallet communicates with. The best you could do is set up a second static IP on your VM, assuming you could launch multiple wavi-daemons.

So i guess we actually have entered the GPU/ASIC era with a GPU miner now available for Yescryptr32. 450H/s on a 980ti and 1,200H/s on an overclocked 1080ti FTW3.

What does this mean for a coin who's primary advantage over similar alts was CPU-only? Mining WAVI on a 1080ti could almost even be considered power efficient compared to the many older CPUs that are chipping away at this project.

Agreed on it being a Dash fork, I noticed that a couple weeks ago when I was researching WAVI deeply.

Has anybody heard from the dev? I searched his profile on btctalk and github and there isn't much for contributions lately. Since April 10th, and that was for a yescrypt16 thread. WAVI has so much potential, I just hope the dev is dedicated to the project.

I'm guessing he may be talking about the Yescrypt16 algo that excavator got support for in 2015. I don't believe there is any support for GPU yescrypt32 mining at all. It could be done, but mining yescrypt32 on a GPU would be extremely inefficient. Not that I wouldn't do it anyways

In the command line syntax c=WAVI, what does c=WAVI do? I notice on hashfaster.com, the Extra column indicates c=WAVI. Could I use this for my miner hostnames? What does this argument do?