Good day to you people and undercover crabpeople, we hit our first exchange today!
ANN updated!
ANN updated!
It seems you have hard work in recent days, Good Jobs !
Topic: CRABCOIN[CRAB] X15 POW/POS - page 5. (Read 9475 times)
It seems you have hard work in recent days, Good Jobs !
Good day to you people and undercover crabpeople, we hit our first exchange today!
ANN updated!
ANN updated!
can someone help with a conf file ? i cant get it working
still says no connections
this is what i have
listen=1
daemon=1
rpcuser=X
rpcpassword=X
addnode=173.24.153.52:11338
addnode=82.34.172.175:11338
addnode=107.170.212.222:11338
still says no connections
this is what i have
listen=1
daemon=1
rpcuser=X
rpcpassword=X
addnode=173.24.153.52:11338
addnode=82.34.172.175:11338
addnode=107.170.212.222:11338
If you're on Windows also open your firewall to port 11338 (will help you overall)
Linux: sudo ufw allow 11338
Mac: Google it lol
here's one of my configs:
server=1
listen=1
daemon=1
testnet=0
rpcuser=someuser
rpcpassword=somepassword
rpcport=11337
port=11338
addnode=173.24.153.52:11338
addnode=82.34.172.175:11338
addnode=107.170.212.222:11338
can someone help with a conf file ? i cant get it working
still says no connections
this is what i have
listen=1
daemon=1
rpcuser=X
rpcpassword=X
addnode=173.24.153.52:11338
addnode=82.34.172.175:11338
addnode=107.170.212.222:11338
still says no connections
this is what i have
listen=1
daemon=1
rpcuser=X
rpcpassword=X
addnode=173.24.153.52:11338
addnode=82.34.172.175:11338
addnode=107.170.212.222:11338
POS begins after block 100,000?
Nope PoS starts after block 10,000
PoW Stops at block 100,000
Blockexplorer: http://crab.acc-pool.pw/
That's awesome.
Creepy crab picture. No wonder they were forced underground.
Lol right? Who knows... I think Dev should release periodic updates on the crab people's plight in their modern day crab society.
Creepy crab picture. No wonder they were forced underground.
Blockexplorer: http://crab.acc-pool.pw/
POS begins after block 100,000?
Nope PoS starts after block 10,000
PoW Stops at block 100,000
POS begins after block 100,000?
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
The answer is the dev asked us to make this so he could launch a fun as in community coin. There are defines missing in makefiles yes, it's something we didn't have time for when we supplied the dev with the source.
Corrected the makefiles in Github, there are still other minor things that will need to be addressed but nothing crazy.
The wallet would not sync without adding your node from 1st post and the makefile is indeed broken
That's not the makefile, that's the really crappy Node 1 connections. That's why there is another more proper node launching. The other was only meant as a temp
Btw: thank you very much for supporting the Dev in his for-fun coin. It's definitely nice to see not everyone is baring teeth.
Just one last time: This is mess around with coin, you can mine it or not, it will probably make it's way to an exchange and as long as it has a node it will probably live for a while. That being said even the dev said this was made for fun and to if anything get others to play with it as well. This isn't a serious industry changing product. So please don't take it as such. Personally I'll probably mine a little here and there and watch what happens once no one wants to rip the Dev's or My throat out anymore.
The wallet would not sync without adding your node from 1st post and the makefile is indeed broken
No bounty for premine ?
Doesn't look like the dev posted anything yet on that.
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.
1. I'm not your "bud", dude.
Fuzzbawls Script is doing well as it's an easy checker for obvious things in code which should nowadays be fixed on launch.
I've had a quick look, it wouldn't compile because it's missing several objects in the Makefile and I've also noticed no dnsseeds in the code and the
provided addnode is/was hosted obviously on a home/residential connection.. So if someone cannot even afford a $3 VPS to host his node I didn't even
look further but maybe this is the next zcash 2.0
Good luck with your attitude and your "project(s)"
1. Didn't realize we struck a nerve, ease up.
It doesn't need the DNS Seeds, once the VPS launches its node connectivity will go to the way they should be.
Again like I told Fuzzbawls, if you ACTUALLY look in the code you'll see there are two nodes coded into it that the client connects to immediately.
It's also not about affordability, it's about time, we manage many projects and have one main one we focus on. This was a fun coin that the dev asked for.
We're not pouring money into it. So if the Dev has nodes, he has nodes. Once his VPS launches I'm sure things will be fine.
Good luck with your pools and overaggressive pessimism
EDIT: All the stuff you say is "missing" is done at compile by your system. Upgrade your deps then you won't have that script read that out. Not the coins fault.
Active pool?
Tekyboy and maxminers check pool links on previous page 
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.
1. I'm not your "bud", dude.
Fuzzbawls Script is doing well as it's an easy checker for obvious things in code which should nowadays be fixed on launch.
I've had a quick look, it wouldn't compile because it's missing several objects in the Makefile and I've also noticed no dnsseeds in the code and the
provided addnode is/was hosted obviously on a home/residential connection.. So if someone cannot even afford a $3 VPS to host his node I didn't even
look further but maybe this is the next zcash 2.0
Good luck with your attitude and your "project(s)"
Active pool?
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
No bounty for premine ?
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
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...
Jump to: