[11:10:11] https://cdn.discordapp.com/attachments/416000318149754881/610399623458193417/nav00.JPG [11:10:13] https://cdn.discordapp.com/attachments/416000318149754881/610399630936506399/nav0.JPG [11:10:14] https://cdn.discordapp.com/attachments/416000318149754881/610399638570270731/nav1.JPG [11:10:16] https://cdn.discordapp.com/attachments/416000318149754881/610399645805445123/nav2.JPG [11:10:18] https://cdn.discordapp.com/attachments/416000318149754881/610399652935893033/nav3.JPG [11:10:19] https://cdn.discordapp.com/attachments/416000318149754881/610399658379968523/nav4.JPG [11:10:20] https://cdn.discordapp.com/attachments/416000318149754881/610399663543025675/nav5.JPG [11:10:21] https://cdn.discordapp.com/attachments/416000318149754881/610399668735574016/nav6.JPG [11:10:23] https://cdn.discordapp.com/attachments/416000318149754881/610399674486226944/nav7.JPG [11:11:12] @mxaddict Here you go pal from windows version, firstly I can see formatting error with the text on the radio buttons for the DAO screen [11:12:56] @Verrideo thanks! [11:20:50] @mxaddict No problem, happy to help. Also on first installation effort it crashed the system I installing it on causing a full OS bomb out and reboot. After reboot it froze up again just after the install when it pops to ask if you want to create a new wallet or restore previous one but recovered this time. The system I ran it on is a windows 10 64bit system that is part of my sandbox environment, I suspect AV scanning it during [11:20:50] runtime caused the crash but would need to try and recreate to prove it [11:28:24] Unfortunately the dump log failed to write to the disk 😦 [11:28:25] https://cdn.discordapp.com/attachments/416000318149754881/610404210810290176/unknown.png [11:49:13] I see [11:49:23] What AV are you using? [11:50:12] @prole @aguycalled I think we still have miner code in the wallet right? Could that be the reason for the false positives that we get in some AV software? [12:23:24] In this case it was Avast. I think it was their cyber capture feature trying to sandbox part if the process that crashed it. [12:24:28] Obviously being security minded I analysed the EXE before running and yes it is being detected by some AV due to a mining element being found in the file. [12:27:34] However that came from deep analysis, avast itself scanned the file and was happy with it but I think managed to break it by it's own efforts to sandbox parts of the code. You will still get false positives from AV for sure until the miner code is removed. [12:27:46] Obviously the lack of code signing in this case doesn't help either [12:36:26] Eset AV is currently detecting the coinminer and blocking as a virus [12:38:46] Eset is a core trusted AV scanning engine so many other vendors take signals from it [12:40:31] There are other malicious indicators in the code that AV scan engines take into consideration: It makes suspicious amount of network connections to internet hosts. [12:40:54] particularly it's direct calls to various time servers [12:41:47] it uses uncommon ports [12:44:24] The installer EXE writes data into the navcoin-qt.exe remote process [12:45:53] Mostly it is being blocked by AV becasue of it containing coin mining software and being detected by ESET but the other malicious indicators add wight to this diagnosis and make it suspicious even without the detection [13:35:00] Yeah [13:35:13] Unfortunately some of these can't be changed as of now [13:35:52] But I think removing the miner code, which if I remember correctly is deprecated anyway, we should be able to atleast reduce the weight of the detection [13:36:19] The installer is also using code from btc-core wallet, so I guess they have similar issues [13:36:26] Unless they have updated it [13:36:55] If they have updated it we can port the changes back into navcoin in a future update [13:43:45] @Verrideo is it possible for you to check the dark theme of the wallet if it works ok on windows? 😃 [13:43:55] There is a new setting in options dialog [13:44:08] Should be able to switch to "dark" theme [13:48:17] the miner code was adapted for the staking thread [13:48:30] im not sure if theres much we can remove but prob worth to have a look [13:49:52] Ohh, I see [13:50:01] If that's the case, then we really can't remove it [13:50:07] As it's used for staking. [13:50:24] 😢 [13:51:14] I think code signing might help us with false positives [13:51:30] It is static analysis that is detecting it which to be fair is usually pretty simple to beat. You just need to adapt the code enough through renaming things here and there and maybe a bit of obfuscation and the AV engine won't pick it up [13:51:38] Or atleast "show" that the exe is from a verified source [13:51:46] Right now it's unsigned and very sketch [13:52:12] You need to be code signed these days. Without it AV will constantly go off and even basic features of windows like smartscreen will try their best to bock it [13:52:27] Code signing is pretty much a must for any kind of serious software now [13:54:19] Especially when people are putting their money into your software. The last thing they want to do is have to go past virus alert screens. To be honest I would train anyone to run away at that point [13:57:20] Right now as it stands I can backdoor the Navcoin installer with a RAT. If we are telling users to click past AV then they would do so on a backdoored version of the software also and let me right in. This is quite bad really and only doesn't stop people installing it because really they don't know any better but people are becoming more cautious and security conscious these days. Doesn't cost that much for a code signings cert [13:57:21] from a public authority. [14:35:05] @mxaddict [14:35:15] https://cdn.discordapp.com/attachments/416000318149754881/610451230719868929/nav1.JPG [14:35:16] https://cdn.discordapp.com/attachments/416000318149754881/610451234771435520/nav2.JPG [14:35:17] https://cdn.discordapp.com/attachments/416000318149754881/610451237896192002/nav3.JPG [14:35:17] https://cdn.discordapp.com/attachments/416000318149754881/610451240857370654/nav4.JPG [14:35:18] https://cdn.discordapp.com/attachments/416000318149754881/610451242615046155/nav5.JPG [14:35:18] https://cdn.discordapp.com/attachments/416000318149754881/610451244603015172/nav6.JPG [14:35:19] https://cdn.discordapp.com/attachments/416000318149754881/610451247174123521/nav7.JPG [14:35:20] https://cdn.discordapp.com/attachments/416000318149754881/610451250021924864/nav8.JPG [14:35:36] Think I prefer that to be honest [14:37:01] Can't work out if the purple on the menu bar looks OK or not. I like the purple on black but don't know if my brain is telling me something looks odd with it exactly like that because I'm used to the other look or because it looks odd 😃 [14:37:55] Either way personally prefer the purple on black theme to the purple on white. I think it has a more modern look [15:06:39] I don’t think the current purple works very well with the dark either. Perhaps a lighter or darker shade. Or even just a light border between the purple and grey [15:11:31] I'm open to suggestions [15:11:44] I can make some variations [15:19:47] we can make a contest [15:20:16] and give a bounty to the winner [15:20:23] its just a css file iirc [15:27:16] That's a good idea, something for people to get involved with and maybe draw in some more interest [15:34:16] is it technically possible? @mxaddict [15:48:17] @mxms Try picking from the 4 colours @Beekart came up with in #dev-websites. That way it will conform with the website. [15:49:04] @mxaddict Try picking from the 4 colours @Beekart came up with in #dev-websites. That way it will conform with the website. [15:49:34] 7bd0f5 6091de 6252e2 7841b1 [15:55:34] https://cdn.discordapp.com/attachments/416000318149754881/610471443888603146/NAV.png [15:57:15] Just a suggestion 😃 [16:02:59] https://deploy-preview-234--navcoin.netlify.com/en/bounties/ [16:20:17] @aguycalled yes [16:20:45] It's on my branch most of the view styles are in a CSS file [16:46:02] https://github.com/mxaddict/navcoin-core/tree/updated-main-menu/src/qt/res/themes