Topic: [ANN][CROC] Official CrocodileCash Update Board [Strength in Basking] - page 4. (Read 20101 times)

Where do you see that it is on maintenance? It says "delayed", that just means it takes a bit longer.

LOL CROC wallet is on maintenance at Yobit.   People want but can't but CROC for listing at CryptoHub 

I'm basing this on what I've found to work solomining other coins using ccminer (your mining software might have a slightly different "batch" input string)...

You'll need to spawn an address for your wallet where you'll want newly mined coins to be generated then put that in as your rpcpassword in your config file.  BTW, your rpcuser and rpcpassword should be private so I suggest you not use the rpcuser name that you just broadcasted.  

It's somewhat counterintuitive but I've found I can set gen to 0 (perhaps this was the problem?).  Maybe gen=1 is a legacy from coins that hash within the wallet, but your mining software is talking with your wallet as an external process.

I think you want to set mining to 1.

The rpcconnect doesn't seem to be necessary from what I've seen -- maybe try without it.

Also, it's probably obvious but you should be running a node at the same time (have CROC synced with the network to transmit your newly solved blocks).

Another security thing... after making changes it's best to have your config file read-only (and only accessible by your user account if you can set the permissions).

So your config should look essentially like this:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rpcuser=yourNewUserName
rpcpassword=OneOfYourCrocAddresses

rpcallowip=127.0.0.1 # this is your computer's "localhost" IP

rpcport=39438  # listen for RPC connections on this port
port=39437 # port on other nodes to connect to
server=1    # tells CrocodileCash.conf to accept JSON-RPC commands
gen=0   # the counter-intuitive part mentioned above
 
daemon=1 # allow command-line terminal calls
mining=1  # attempting to solo-mine
listen=1 # allow other nodes to transmit your IP to nodes they're connected to

addnode=101.165.225.41
addnode=174.92.179.126
addnode=139.59.228.94
addnode=75.130.162.248
addnode=177.33.1.40
addnode=192.169.6.218
addnode=68.105.33.92
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The batch file input to your miner would look something like this:

cgminer/bfgminer -a sha256 -o http://127.0.0.1:39438 -u yourNewUserName -p TheCrocAddressThatIsYourRPC_Password --any_other_settings_specific_to_your_hardware/software (power, intensity, temperature, difficulty etc)

I hope that helps you mine some CROC.

I'm still trying to get an old ant miner to mine on my networ to the wallet on a pc on same network. I have tried lots of config files. just cant seem to conect. It has been a year or more the last time i wrote a config for doing this and i know it something simple that im overlooking? This is my file
rpcuser=GoodGryphon
rpcport=39438
rpcpassword=x
rpcallowip=127.0.0.1
rpcallowip=192.168.1.99
rpcconnect=192.168.1.146
server=1
listen=1
daemon=1
port=39437
gen=1

CROC price reached 100 sat,   what will you say now?    

Is there any chance i can get a look at a solo mine config file so I can try and solo for fun experiment?

Hi,

I think at the moment you should sit tight.  I'm quite certain we will not be seeking to shake things up until we have tested things and have a robust alternative-chain to offer.  If you followed the previous thread, you probably recall that Gizzard said he read a few "how to build a coin"-type documents and experimented somewhat with some available codebases before he announced CROC.  At this moment, I haven't yet read a guide such as that.

I'm operating on the assumption that a coin-swap may occur (but it may instead be a simple "update" of the wallet to a Peercoin fork with the CROC parameters.)  I simply do not know at this time and am not going to claim to be an expert when I am honestly an interested amateur -- who has some past academic-but-not-industry coding experience.  I also work full-time (usually at least 50 hours a week), so time-management is a factor for me in this.

By far, the largest-part of my free-time is focused on the crypto-space and I am predisposed to be extremely thorough.  CROC is one of my favorite coins (and a dominant chunk of my crypto-portfolio) and I am interested in helping make it rewarding to the other holders.  CROC will not be a 1-cent-or-less coin over the course of 2018 -- this is a projection but I think it will prove to be an accurate one after enough work is applied to relevant and useful tasks.

nodes can be found here https://cryptohub.online/glossary/coininfo/6/

I have just install the wallet and made the cinf file but it will not conect?  is there a new list of addnodes?
Thanks for any help!

hello guys,

im an strong hodler since the initial airdrop back in 2017 and would like to ask just one question

do i have to do something as an hodler for the upcoming fork?


thank you very much and keep up the good work!

@heratys111 thanks, some interesting observations. I'm not involved in CROC (other than I love the crazy staking), but looking into something completely different for other reasons. Gives some ideas.

And yes, happy new year guys!

Happy New Year.  I think 2018 will be a good (but interesting) year for crypto in general.  As long as we work to improve or refine things, CROC will share in the more long-term successful part of the space. 

HAPPY NEW YEAR

2018 will be the year of croc

I was poking around in main.h on CROC yesterday (and for comparison I had the old NIST5-version of Solaris open [nearly identical to CROC's main header file] and Bulwark [much different from CROC's main.h as that's a DASH/PIVX fork]).   Today I opened up this section in Peercoin's code and Heavycoin also.

One thing that I noticed was that CROC has a relatively huge MAX_BLOCK_SIZE constant declared (it seems to be directly from Anti-bitcoin--which also shares this number)... the value is 20,000,000.  The unit seems to be in bytes based on the more fully commented code of PPC and HVC. 

For comparison:

the MAX_BLOCK_SIZE for solariscoin (the old NIST5 version) was 1,000,000
the DEFAULT_BLOCK_MAX_SIZE for Bulwark is 750,000

for Heavycoin (which has several interesting features [but much too high a coin-count IMO, and no PoS], notably the algorithms which may make it more quantum-computer-resistant when that need eventually arises
... see https://bitcointalksearch.org/topic/ann-hvc-heavycoin-ultra-secure-decentralized-block-reward-voting-fast-506774 ) the MAX_BLOCK_SIZE is 1,000,000.

The section of code in BTC is obfuscated/hidden somewhere but BTC is 1 MB (so 1,000,000 again give-or-take [unless it's a base-16 value such as 1,000,256 or something]).

and finally Peercoin also has MAX_BLOCK_SIZE of 1,000,000.

So, I think the current version of CROC is too big for its britches on that particular parameter (as that seems to be where the block size is set).  That is probably a good part of where the memory-usage that CROC gobbles up might stem from too.

I am going to do some more work on that test coin fork this weekend (just the examples of the coins mentioned above show some inputs that can be experimented with at the front end without descending too much into the underlying class declarations elsewhere in the code [which can be treated like a "black box" to be pragmatic right now]).

Hi, what's the price to list a coin

I'm happy to say that CryptoHub grows and some people already paid for coin listing and some additional services using CROC coin.   So CROC coin have some real use now.
After moving wallet to another server with SSD I don't have performance problem anymore, so there is no problem to maintain CROC pool, market and online staking at CryptoHub.

It's an open question at this point.  I think that would potentially be a mechanism to update to a new wallet (if the wallet has been overhauled significantly).  I am new at this though (see below however), and could be complicating this more than necessary.

Just as a backgrounder, I studied computer and electronics engineering (and had some academic -- not professional -- experience coding in C++, Java, assembly, and VHDL) for several years but how I earn cash to live is not geek-related stuff at all.  I am a perfectionist and along with that I tend to bite off more than I can chew ... the other day I picked up _Professional C++ (third edition)_ by Marc Gregoire which is a technical 800-page survey of C++ and have designs on working through this as a refresher.  I am also using a Linux-based system and am not so well-versed with that too (but, again, have a bit of a program/comprehensive-text to get significantly more engaged with this -- but this is not as useful as the C++ would be).

I'm also interested in looking at early iterations of BTC, LTC to see how much I can grok the intricacies of the shared codebase underlying most alts as well as Peercoin, ANTI, (possibly MOZZI) that are more immediately-direct forerunners to CROC.

So time-management and focus are stumbling blocks for me to do something substantive.  As can be seen, you are probably not going to be encouraged to swap your CROC's in say a month's time.    Particularly as this is December as well.

I also had the thought today that perhaps we might want to recruit or induce a dev such as Kingcoin's dev to handle some aspects (coding, code-review and/or testing).  (We've also kicked Bumbacoin's dev around as a name too.)   I reflected a bit on helping KING get up off the mat by making a deal out of my own stash to trade them some of their coin for a stake in one that offers cash-flow (below the 1000%-type PoS coins which I think are flash-in-the-pan parameters*).  I've got an idea of the coin supply of that and was going to take that into account to try to make a win-win offer in an exchange (trading coins potentially for services, nothing to do with incorporating the two into either blockchain).  I downloaded KING's wallet but got fascinated by the TOR information I found in the "/doc" directory (remembering a post in BWK's thread about setting up TOR nodes) and haven't done much with that wallet at this point ^_^

Anyhow, I think there is an avenue of approach to the communities of left-for-dead pure-PoW coins where CROC simply gobbles them up into the ecosystem which would help foment something approximating a more useful/utilitarian model (one which helps make more opportunities for models such as the following: http://abolishwork.com/2014/01/21/the-rich-economy-by-robert-anton-wilson/ -- although my approach is also along the lines of Bastiat, Mises, and Murray Rothbard).


* footnote: I suspect coins with an excessive amount of staking percentage (much beyond CROC) will not hold long-term value as there are simply too many issued to find buyers of the newly generated coin -- contrast that with CROC [with only about 7.5% of the total CROC-universe/supply sitting in sell orders -- and (at the moment) 96% of those (7.3% of the CROCs) aren't staking unless Yobit is doing it surreptitiously].
  

In theory your private keys and the rest of the network remain the same.

The PPC fork should not change the currently mined blocks or anything, besides using updated client and server code for everything. I am sure these chains are 100% compatible, but we will have to wait and see. Currently I have no time for this.

In any case, holding onto your CROC doesnt cost anything

So what will happen to the croc am holding presently. Are you planning coin swap

So... underway on that at https://github.com/Sviluppo718/Cow-chip_Thrower_Coin.   I did get a little side-tracked earlier with a task in Bulwark's thread (but got paid 10 of that coin for the trouble).

As the README.md file states, only really superficial changes have been made (titling, the readme file itself).  At this point this is not changed in any significant way from PPC.

Also, when I started to look at the header files main.h (C++ usually [always??] has main.cpp and main.h -- it's the skeleton around which the program runs off of) from PPC simultaneously with CROC's, I noticed in Gizzard's source that there seems to be the incorporation of a zerocoin library whereas Peercoin's source doesn't seem to have this.  It's kind of an interesting detail that could bear keeping around or tinkering with.

I think if any others are looking to help manipulate this into something awesome that could then be forked and incorporated as a more robust CROC we will want to follow the guidelines for pulls/development as indicated in the bottom of the readme.

Things that will need doing include figuring out where the port/rpc is in the code base (to reduce the likelihood of conflicts with other coins that people might be running nodes of).  [Or noob as I am at this... is this not in the codebase at all and simply a matter of handshaking by setting these to agreed-upon numbers in the config files at the user's end??]

Also, there are no addnodes provided here but if people want to mess around cpumining the initial block or two just for kicks (did Peercoin have a genesis block with a big fat premine?) feel free but I think any of these coins will be superseded in later versions.  There effectively is no network unless people want to pm to individuals or publicly announce nodes (perhaps they have a remote host setup?).  [Been watching _Mr. Robot_ lately so pretty security-conscious.]

The version.h has been left alone for now as I didn't want to potentially cause any conflicts with the PPC codebase -- it's probably best to make small changes, test, and repeat.