Somebody already checked wallet? It is safe?
safe or not, this standard of using mega.co.nz to host binary distributions for wallets is pathetic. Mega links are generally not permanent, and there has been a long history of malicious link manipulation. TBH, if these coin "devs" cannot spend the extra 2 minutes to host/distribute binaries in a sensible manner, what does that say about their ability to actually provide a solid/stable long-term cryptocurrency?
Here's the standard code/compliance review for this coin
___ _ ___ _ _
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.4 October 2016 | http://www.fuzzbawls.pw
Report Date: Wed Nov 2 17:36:37 PDT 2016
Checking Host OS... MAC
Creating temp folder to clone remote repository...
Cloning https://github.com/365coindev/365.git...
-= Repository Information =-
============================================================
Number of commits: 2
Last commit date: Wed Nov 2 03:24:04 PDT 2016
Days since last commit: .59 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 1.0.0.0
Qt Bin: The365Coin-qt
Daemon Bin: The365Coind
-= Coin Specifications =-
============================================================
Coin Name: The365Coin
Client Version: 1.0.0.1
Client Name: /The365Coin:1.0.0.1/
Default P2P Port: 15663
Default PRC Port: 15662
Message Start String: 0xb7 0xf5 0xe4 0xe5
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [OK]
Matching RPCPORT in init documentation: [OK]
Build & Client Version Match: [!!]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [!!]
OpenSSL v1.0.1k+ (Strict DER Signatures): [OK]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [!!]
IRC based peer fetching: [!!]
Contains signature malleability patch (PPCoin): [!!]
-= Connectivity Checks =-
============================================================
Contains unique ClientName: [OK]
Contains DNS seeder addresses: [**]
Contains Hex-Encoded seeder addresses: [!!]
Has at least ONE default connection method: [**]
Number of DNS Seeds: 1
Listing DNS Seed addresses...
* 198.199.90.93 [OK]
-= OS Specific Checks =-
============================================================
Mac OS X Native Notification Support: [OK]
Mac OS X Deployment Script: [OK]
Mac OS X Application Icon: [OK]
Mac OS X Dock Icon Menu (Qt5): [OK]
Windows Installer Script: [**]
Windows Installer Header Image: [!!]
Windows Installer Logo Image: [!!]
Windows Installer Icon: [!!]
============================================================
* At least one DNS seeder addresses is improperly formatted.
* DNS Seeders should be full hostnames and not IP addresses.
* IRC based peer fetching has long since been depreciated!
* Developer should remove it and use DNS Seeding instead.
* Windows deployment sript is using an incorrect version!
* Deployment build won't have the correct metadata!
Results should be manually verified and you should NOT rely
on any automated scripts (including this one) before running
or compiling any crypto wallet.
============================================================
ocminer has stated that the single IP address used as a seed node has been used in numerous other coins in the past (referenced from his google search link).
I'll add that IRC based peer discovery was disabled by default in the 0.6.x version of Bitcoin, and removed entirely as of Bitcoin version 0.8.2. The removal of IRC peer discovery is not a "recent" thing by any means (disabled mid 2012 and removed May 2013), and there really is NO excuse to have any new coin launch include such an antiquated and insecure peer discovery method here in 2016