Quite a bit must be done. See my source code report:
Code:
___ _ ___ _ _
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.4 October 2016 | http://www.fuzzbawls.pw
Checking Host OS... WIN
Creating temp folder to clone remote repository...
Cloning https://github.com/KingCrabDev/Crabcoin.git...
-= Repository Information =-
============================================================
Number of commits: 2
Last commit date: Sun, Oct 09, 2016 12:04:51 AM
Days since last commit: .06 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 1.0.0.0
Qt Bin: Crabcoin-qt
Daemon Bin: Crabcoind
-= Coin Specifications =-
============================================================
Coin Name: Crabcoin
Client Version: 1.0.0.0
Client Name: /Crabcoin:1.0.0.0/
Default P2P Port: 11339
Default PRC Port: 11338
Message Start String: 0x1c 0xfe 0x32 0x7e
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [!!]
Matching RPCPORT in init documentation: [!!]
Build & Client Version Match: [OK]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [!!]
OpenSSL v1.0.1k+ (Strict DER Signatures): [!!]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [OK]
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: [!!]
-= 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): [!!]
Windows Installer Script: [**]
Windows Installer Header Image: [!!]
Windows Installer Logo Image: [!!]
Windows Installer Icon: [!!]
============================================================
* This wallet has ZERO default connection methods!
* Use of addnodes and a conf file will be required!
* Windows deployment script is using an incorrect name!
* Deployment build won't have the correct metadata!
* 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.
============================================================
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.4 October 2016 | http://www.fuzzbawls.pw
Checking Host OS... WIN
Creating temp folder to clone remote repository...
Cloning https://github.com/KingCrabDev/Crabcoin.git...
-= Repository Information =-
============================================================
Number of commits: 2
Last commit date: Sun, Oct 09, 2016 12:04:51 AM
Days since last commit: .06 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 1.0.0.0
Qt Bin: Crabcoin-qt
Daemon Bin: Crabcoind
-= Coin Specifications =-
============================================================
Coin Name: Crabcoin
Client Version: 1.0.0.0
Client Name: /Crabcoin:1.0.0.0/
Default P2P Port: 11339
Default PRC Port: 11338
Message Start String: 0x1c 0xfe 0x32 0x7e
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [!!]
Matching RPCPORT in init documentation: [!!]
Build & Client Version Match: [OK]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [!!]
OpenSSL v1.0.1k+ (Strict DER Signatures): [!!]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [OK]
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: [!!]
-= 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): [!!]
Windows Installer Script: [**]
Windows Installer Header Image: [!!]
Windows Installer Logo Image: [!!]
Windows Installer Icon: [!!]
============================================================
* This wallet has ZERO default connection methods!
* Use of addnodes and a conf file will be required!
* Windows deployment script is using an incorrect name!
* Deployment build won't have the correct metadata!
* 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.
============================================================
ZERO default connection methods...really?
The OpenSSL issue is a potential detriment to the network's stability in and of itself! The signature malleability issue is yet another, and the miniupnpc check that failed is indeed another point of failed client stability.
The fact that this coin uses ZERO default connection methods is a MAJOR concern! addnodes should be considered as a last resort, and NEVER be mandatory for basic client opperation.
Coupled with the relatively low amount of hard coded checkpoints, the likelihood of a client forking to an invalid chain is extremely high with this source code.
You understand that the 90% of what you are saying is addressed at compile? Or do you enjoy fudding a trollcoin/funcoin?
That's probaby the best part. This is just a fun coin not even to be taken seriously yet you're so fired up! It's amazing. Really.
So this crappy work was done by you ? That is what happen when you learn coding from the google search engine 
Try to compile it in another server or anyother flavour of linux see what errors you ll get and give folks a solution
Try to compile it in another server or anyother flavour of linux see what errors you ll get and give folks a solution
You have amazing perception! That you might want to go have checked...
This wasn't designed as a serious "project" there very well are probably some MINOR SUPPORT ISSUES in the code that apparently you are getting so worked over.
Geez lol.
We don't code crap. It runs. Now if it doesn't run on your flavor of linux, don't come in here torching the place. Let us know, we'll have a look and work with the dev...