CRABCOIN[CRAB] X15 POW/POS

[Fuzzbawls]

any Exchange ?  *cough*

no, the "project" is less than 2 hours old...

Mining in solo why I do not find blocks?

What should I put in the conf file?

unless you manage to get a solid connection to a reliable node, then solo-mining this is rather pointless

this node is not reliable? addnode=173.24.153.52:11338

considering that the IP address (node) is not included in the wallet's source code....no, it is not a reliable connection medium.

The last hard-coded checkpoint was at block #11, and without default connection options, this coin is taking on a very serious security risk.

[zerocom]

any Exchange ?  *cough*

no, the "project" is less than 2 hours old...

Mining in solo why I do not find blocks?

What should I put in the conf file?

unless you manage to get a solid connection to a reliable node, then solo-mining this is rather pointless

this node is not reliable? addnode=173.24.153.52:11338

considering that the IP address (node) is not included in the wallet's source code....no, it is not a reliable connection medium.

The last hard-coded checkpoint was at block #11, and without default connection options, this coin is taking on a very serious security risk.

and what must be done?

[Fuzzbawls]

any Exchange ?  *cough*

no, the "project" is less than 2 hours old...

Mining in solo why I do not find blocks?

What should I put in the conf file?

unless you manage to get a solid connection to a reliable node, then solo-mining this is rather pointless

this node is not reliable? addnode=173.24.153.52:11338

considering that the IP address (node) is not included in the wallet's source code....no, it is not a reliable connection medium.

The last hard-coded checkpoint was at block #11, and without default connection options, this coin is taking on a very serious security risk.

and what must be done?

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.
============================================================

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.

[qwep1]

pool ?

[fitraok09]

thread is looks simple and there is no bounty

[btcdevil]

Even after so many queries about the coin, the Developer is not responding to any queries, so i think this coin is a scam coin or the developer dont know what to do next after facing so many problems, better be safe if you are downloading the wallet as it may contain some virus or hacking exe file.

[c1791]

Why have choosen X15??simply using an advanced algo does bring investors attention and moreover you will stuck in such errors which cannot be fixed easily

[MaxMinersNet]

The source on github is not compiling

[crunck]

The source on github is not compiling

Its fucked, there are so many errors its not worth fixing

[kevin1234a]

OP needs to change this coin name from CRABcoin to CRAPcoin

[MaxMinersNet]

We somehow got it running:

https://crab.maxminers.net

[tekyboy]

http://tekyboy.tech

CrabCoin

stratum+tcp://stratum.tekyboy.tech:17036
wallet address as username
password of your choice (it does not matter what you choose)

port 7036 is lowdiff
port 17036 is vardiff
port 27036 is highdiff

Payouts every 15 mins; minimum 10 XCRAB

[szachta]

Who is mining crabcoin.

[qwep1]

wtf Net Hashrate

1,050.92 MH/s 

[CryptoCoderz]

Ugh.. so many error in the code... unbelievable

Ugh so many damns not given omg... wow bud is this all you do? Run around threads and complain?
This was something we made for the Dev quickly as a fun token. Nothing more nothing less. If there's issues we'll fix it for the dev.

Ugh.. so many error in the code... unbelievable

yep!

There really isn't any excuse to NOT get a 100% passing score from my lil script these days. pretty much ALL of the tests are against known and verified updates and can be considered "basic maintenance" of coin source code

Well we're not script kiddies... so... ?

Ugh.. so many error in the code... unbelievable

maybe crapcoin?instead of crabcoin

Grow up.

if you fix the wallet i add it to Tradesatoshi

Compiled fine for Ubuntu Server 14.04...

Ugh.. so many error in the code... unbelievable

yep!

There really isn't any excuse to NOT get a 100% passing score from my lil script these days. pretty much ALL of the tests are against known and verified updates and can be considered "basic maintenance" of coin source code

Doesn't seem like the Dev had any idea what he's actually doing

The dev asked us to make a fun little coin for him. If there's issues we'll fix them when he asks.

any Exchange ?  *cough*

no, the "project" is less than 2 hours old...

Mining in solo why I do not find blocks?

What should I put in the conf file?

unless you manage to get a solid connection to a reliable node, then solo-mining this is rather pointless

this node is not reliable? addnode=173.24.153.52:11338

considering that the IP address (node) is not included in the wallet's source code....no, it is not a reliable connection medium.

The last hard-coded checkpoint was at block #11, and without default connection options, this coin is taking on a very serious security risk.

Actually that node is added. Do you only use source checkers or do you look into anything?

Why have choosen X15??simply using an advanced algo does bring investors attention and moreover you will stuck in such errors which cannot be fixed easily

What errors?

OP needs to change this coin name from CRABcoin to CRAPcoin

Grow up.

The source on github is not compiling

Its fucked, there are so many errors its not worth fixing

You sir, are hilarious



@Everyone here

The source compiles on Ubuntu 14.04 Server, Windows clients work, the node is hardcoded in but NOT a DNS seed node, the windows client works fine as well.

So if someone would liek to report how this is NOT working We're all ears. Minor source items picked up by generic source scanners... well if that's what you want to look at go for it.
If you actually care to look and understand what the source is then you'll quickly realize there are fewer problems than there are made out to be.

The biggest issue right now is that there is only ONE node and it's on a limited connection as is was setup for temp use for the dev's more permanent nodes...

But apparently everyone just wants to rant and rave and whine. Wow.

[DigitalCurrencyConsultant]

tell them how it is You also should probably mention for those who don't get it you don't use scripts.. you code and make your own stuff.

[kevin1234a]

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

[CryptoCoderz]

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.
============================================================

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

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...

[oser41eric]

No bounty for premine ?
 

[kevin1234a]

I have done my work already just for your info define missing algos in your makefile which you reffered in other parts of your code but heh one thing on which i StumbleUpon is you mentioning couple of times that it is not serious project and made it for fun so what you are trying to achieve fun about your skills or fun about this community here