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

I've had a working Crocodile Cash node for the past few days.
Not much CROC to stake with but it's a start.
Where are the CROC social groups?
Telegram
Discord
The twitter is inactive; last tweet was in October last year

What's going on?

This coin is fine!

Thank you Heratys.
For about a week now i have been syncing because for over 20 times, i have had to stop and restart my wallet because syncing had simply ceased.
The wallet takes a lot of memory and CPU too

Hmm... I private-messaged the config file that I'm using a couple days ago (you have the right rpcport?? mine is using the rpcallowip=127.0.0.1 also).

Here's some more active nodes from the getpeerinfo command (none of which seemed to be in the config file info I sent earlier however):

5.13.143.100:39437
70.71.243.13:39437
104.254.110.125:39437
144.76.174.21:39437
162.211.173.18:39437
176.212.246.96:39437
190.198.8.5:39437
195.252.66.150:39437
198.89.30.53:39437
212.24.96.87:39437


Those have all been online in the last few mins and should get you synced.

Regards

My wallet is not syncing. I have tried addnodes.

Any other solution?

project is too good. the it will be development in the future.mọi người if you want to see it see this information

Re-posting in this thread too...

Hey folks,

I'm posting this in both Gizzard's original thread and the community-run one.

I'm still looking to (help) refine and improve this chain (or a future one for CROC).  I've been caught up lately in getting my crap together for a late-filing to pay tribute to the Empire and to one of its client-states.

I've also been procrastinating partly because I discovered Jeff Duntemann's _Assembly Language Step By Step: Programming with Linux_ (https://www.amazon.com/Assembly-Language-Step-Step-Programming/dp/0470497025/ref=sr_1_1?ie=UTF8&qid=1529467126&sr=8-1&keywords=jeff+duntemann ).  Ultimately C++/C/C# and all other programming languages (Python, Java, TLA+, Ruby, Pascal, etc) beside machine-code are translated at a low-level into object-code and I've been delving into this [compilers/development-environments usually have an option to output the related object-code].   One of the main themes of that book is figuring out HOW things work.

There are a few features from some wallets that I want to figure out and potentially incorporate into CROC (to add useful features, and make the wallet less generic/old-school or better aesthetically) but the main overall desideratum remains to slim the block-size and memory (RAM) usage  (one thing I encountered, for example, is coins such as XMR use a more dynamic block-size based on a weighted-average of recent blocks).

There are a few things I want to experiment with (and methodically improve relevant skill-sets) including the following: I encountered where in the codebase (for some coins) nodes can be hard-wired into the code (e.g. src/chainparamsseeds.h) and I sort of want to get more hardcore into Cmakefiles and Makefiles generally.  I also want to experiment with some networking material I've encountered (a lot of which is very relevant or useful). I'd like to be able to compile Linux and the useful Windows variants (7 through 10) and eventually Mac, Android, Iphone (Swift) and RaspberryPi (and similar [Arduino]).  The QT API (the GUI interface for most coins) and some of the database APIs/interfaces with C-code are areas I want to figure out and test/experiment with; also gaining some facility with running the test-suites and some other features that most coins have latently but are probably seldom used -- except by the more highly-skilled/experienced teams.

I also picked up a few more exhaustive classics on C++/C (Bjarne Stroustrup, Kernighan and Richie, Stephen Prata) -- the latter two books have a LOT of practice material, whereas the creator of C++'s book (Stroustrup) is more interpretive and encourages creative work through a sort of guideline approach.

Anyway, for now CROC is de facto like a staking DOGE with an arguably "goldilocks" rate of inflation.  On the inflation point, I've reconsidered the last post I made about possibly revisiting a DPOS-phase again; instead, I think it would be smarter to insure the inflation keeps its steady pace (sort of like how BTC, for instance, never had any big insta-mine and those coins are largely obtained through open, unhampered markets).

I do work long hours and am pretty bookish (have wide interests... [economics, philosophy, various languages, history are all on the back-burner at the moment] ... I was watching some PBS show on the First World War in the background while composing the bulk of this post, for instance) so please don't expect this to all unfold tomorrow -- but I did want to drop a note and poke people to indicate that this stocky critter [CROC] is still alive and will see later versions.

Well, I'm in for quite a while, and I think this small unrespected project may have some future ahead. So I'm accumulating.

As long as the coin is being used for something it will always have a value

Someone pushed CROC to 822 sat on Yobit last week (where the CROC are thinning out even more than at "the Hub").

I'm still working on increasing my skill-sets in things that are arguably related (Linux in depth, C++, then blockchain [in that order]). As I've mentioned a few times in various places I'm actually going to be declaring my crypto-income to the supposed "powers that be" -- in my case this includes filing tax returns in both Canada and the US and the FBAR/ Fincen Form 114 (so this upcoming month is going to suck -- and in a big way -- for me).  Nevertheless, in its due and proper course we'll have this chain kicking ass and keep on improving things from there.  While I don't expect this to be an instant "*Lambo*" situation, there will be improvement in a sustained and long-term manner and we'll be looking to extend the domain of things CROC-related (as Gizzard promised and we will help bring about) -- and these aren't empty words.

There is at least one geek/friend that I've known for several years who I'm hoping to bring into the picture to help with testing some of the Windows and server functionality... anyhow there's plans afoot.  

I think in the medium-term the crypto-space still has to calm from the mania-phase from December and January, but CROC is off-the-radar (in trading terminology it has "low beta" or "high alpha"; that is: it's relatively divorced -- in price-terms -- from the wider crypto-world as it's a micro-cap within the space).

For something a bit off-topic (but a worthwhile distraction in my opinion): perhaps no one else here is into this stuff but here's some off-the-well-trodden-track tunes for your entertainment/edification in the meanwhile: https://www.youtube.com/watch?v=vh2j33wD8pA (the british band Napalm Death's '94 album).  Maybe there's a CROC-related-theme here(?) -- ultimately, it's subject to your own interpretation.

CryptoHub now has widgets for all coins:

CROC price reached 400 sat

Pretty cool stuff, good to know this is still actively in research, maybe a bit slow, but hey, it's not even listed on CMC yet .

I'm in for a while, staking on an OrangePi. Would be happy to help testing on that platform (which is basically the same as Raspberry and all those small micro-PCs running some form of Linux).

Hey, I'm checking in here with updates...

I've momentarily parked getting re-acquainted with C++ -- the text mentioned earlier includes material up to the most recent C++14 standard -- in order to focus on getting more in-depth practical knowledge with the Linux distro I'm using (which is necessary and co-requisite).  One of the ROI-coin devs (Gary Hobson) was suggesting the most useful task at-the-moment is to learn to compile Windows wallets from source (this seems to be addressed in this link [ https://bitcointalksearch.org/topic/howto-compile-altcoin-for-windows-on-linux-using-mxe-and-mingw-1080289 ] that Gyman posted in Cryptohub's chat.  This'll probably require the use of some virtual machine to test the code on systems I have available now or near-term using different Windows versions... perhaps some people actually running Windows as their usual OS will be roped into testing when the appropriate stage is reached (Hyperjacked??).  I'm planning to get conversant with VMware, VirtualBox and Vagrant.  Essentially, I'm working on needed homework.

In the long-run, I think we want to make CROC more streamlined than simply changing MAX_BLOCK_SIZE's value from 20000000 to 750000 (line 34 in main.h https://github.com/RangaBoom/CrocodileCash/blob/master/src/main.h ), having people update their wallet, and hoping that solves the heavy-CPU usage.

A couple weeks back I was going through Peercoin's threads (the pre-announce and their current thread) and encountered this message [ https://bitcointalksearch.org/topic/m.1122256 ] where, early-on, they goofed and didn't change the pchmessage parameter so that transactions weren't properly being distinguished between BTC and PPC.  I bounced this off the ROI-coin devs and one of them referenced the same situation having happened to Feathercoin (here): https://github.com/FeatherCoin/Feathercoin/issues/7 .  This will be among the details to look at when we get closer to making this thing happen and effective/not-sloppily done.

To quote a message that Gary wrote: "pchMessageStart is not the only thing you need to modify , have a look at barterdex , where people have to add their coin , the info they need to supply for it, i ll get you an example
Checkpoints are not that important anymore despite popular believe… many think its a thing of the past.
Examples of what coins supply to get listed on a centralized exchange ( this one is BarterDex )
{“coin”:“LTC”, “name”:“litecoin”, “rpcport”:9332, “pubtype”:48, “p2shtype”:5, “wiftype”:176, “txfee”:100000 }
{“coin”:“DGB”,“name”:“digibyte”,“rpcport”:14022,“pubtype”:30,“p2shtype”:5,“wiftype”:128,“txfee”:100000}
{“coin”:“ROI”,“name”:“roicoin”,“confpath”:“USERHOME/.ROIcoin/ROIcoin.conf”,“rpcport”:3376,“pubtype”:60,“p2shtype”:122,“wiftype”:168,“txfee”:10000} " (end quote)

Admittedly the "wiftype" and "pubtype" are nebulous constructs to me at the moment (and only the other day did I see a reference elsewhere to "p2shtype" in something crypto-derived ).  My understanding is that the rpcport and txfee are chosen by the dev/dev-team (but obviously we want to establish a new port # that doesn't conflict with the old CROC or other chains that people are likely to be hosting/supporting).

I'm also putting a feeler out about possibly reinstating a DPOS-period for the forked coin  ... the idea being to encourage present holders to move to the new chain with a coin-swap (so that they'll end up with a greater percentage of the new chain instead of having a "CROC-classic" contingent stringing along the old one -- numbering among the living-dead Yobit chains).  The tentative values I'm kicking around are to make a premine not much more than 300,000 excess of the existing CROC at the moment of the fork.

These quantities aren't set in stone but the PoW and PoS blocks currently being kicked around are something along the lines of this:


int64 GetProofOfWorkReward(unsigned int nBits)
{
    int64_t nSubsidy = 0 * COIN;
 
    if(pindexBest->nHeight+1 <= 1)
    {  // Premine to permit coin-swap of Mk I CROC (excess to be used for airdrop or bounties)
        nSubsidy = 3,200,000 * COIN;
    }
        else if(pindexBest->nHeight+1 >= 2  && pindexBest->nHeight+1 <= 4000)
    {  // A shorter period of higher mining reward (to not inflate the coin supply too much)
        nSubsidy = 15 * COIN;
    }
        else if(pindexBest->nHeight+1 >= 4001)
    {
        nSubsidy = 1 * COIN;
    }
    
    if (fDebug && GetBoolArg("-printcreation"))
        printf("GetProofOfWorkReward() : create=%s nSubsidy=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nSubsidy);
    return nSubsidy;
}

// ppcoin: miner's coin stake is rewarded based on coin age spent (coin-days)
int64 GetProofOfStakeReward(int64 nCoinAge)
{
    int64_t nSubsidy = nCoinAge * COIN_YEAR_REWARD * 33 / (365 * 33 + 8 );  //default 12% yr

    // Proof-of-Stake begins at block 1440 (again)
    if(pindexBest->nHeight+1 >= 1440 && pindexBest->nHeight+1 <= 20160)
    {
        nSubsidy = 60 * COIN;
    }
        else if(pindexBest->nHeight+1 >= 20161 && pindexBest->nHeight+1 <= 40320)
    {
        nSubsidy = 45 * COIN;
    }
        else if(pindexBest->nHeight+1 >= 40321 && pindexBest->nHeight+1 <= 60480)
    {
        nSubsidy = 30 * COIN;
    }
       else if(pindexBest->nHeight+1 >= 60481 && pindexBest->nHeight+1 <= 80640)
    {
        nSubsidy = 15 * COIN;
    }
        else if(pindexBest->nHeight+1 >= 80641)
    {
        nSubsidy = nCoinAge * COIN_YEAR_REWARD * 33 / (365 * 33 + 8 );  //default 12% yr
    }
    
    if (fDebug && GetBoolArg("-printcreation"))
        printf("GetProofOfStakeReward(): create=%s nCoinAge=%" PRI64d"\n", FormatMoney(nSubsidy).c_str(), nCoinAge);
    return nSubsidy;
}

Finally, @ both Currypto and Hyperjacked I would like to ensure that you guys have _at least the stake or percentage of the net-chain that you had formerly_ (we will try to make you whole again if your wallets are defunct and not stake-able at the moment).

I did a google image search on "crocodile cartoon character" and found the earlier mascot:  https://www.bigstockphoto.com/image-51178135/stock-vector-strong-angry-alligator-mascot-vector-clip-art-illustration-all-in-a-single-layer

The copyright is listed as under the contributor name of Memo Angeles (other work here): https://www.bigstockphoto.com/search/?contributor=Memo+Angeles .
The CROC is about halfway down the third page (https://www.bigstockphoto.com/search/?start=300&contributor=memo+angeles).

The site says: "Bigstock is your fast, easy-to-use marketplace for quality stock images. We offer over 61 million royalty-free photographs and illustrations from talented photographers and artists around the globe, available for almost any purpose."  (https://www.bigstockphoto.com/aboutus.html)   So I think we're probably not going to be sued by this individual looking for redress its use (but perhaps he should be sought out).

@hyperjacked I like your son's work (and we can probably incorporate it into things) but the cold eye of a croc does have a slightly different impact and is perhaps not quite as approachable as the current one (which is both menacing and amusing at the same time).

lets get some feedback and see what ppl think...  
its the first draft so maybe we can have my son Luc improve on it depending up what the group thinks

I believe the other logo was a copy n paste off the internet that we don't have permission to use

this is new logo?   seems interesting

Just tweeted @croca$h possible new logo... 

https://twitter.com/CrocCash/status/962402013765099520

let me know what you think... 

cheers
jack

@ Currypto

This is the collection of links that I think we should add to the current OP (please feel free to edit any of my notes and put it in your own words):

Domain name registered for eventual website: www.croccash.com
Website (adminstered by Gizzard, so no access avail): www.crocodilecash.ga

Twitter: https://mobile.twitter.com/CrocCash

Active pools:
https://cryptohub.online/pools/
https://lpool.name/pool/CROC
the indelicately named http://coinraper.ddnss.de/

Makeshift blockexplorer:  https://lpool.name/explorer

Coinwiki info-page: https://altcoinwiki.org/en/CrocodileCash (I made updates on this today, including incorporating these links)

Paperwallet generator: https://github.com/RangaBoom/WalletGenerator.net (from the site this seems to also be 169 commits behind what it was forked from ... heh )
Gizzard's message on that: https://bitcointalksearch.org/topic/m.21156021

Android wallet: https://play.google.com/store/apps/details?id=org.mystphysx.wallet.CrocodileCash_Qt

~~~~~~~~~~~~~~~~~~~~~~~~~

Again, it would be pretty cool if we can unearth whatever font Gizzard used in his announcement (there's probably some way to search for this ... I poked around a little at What-font-type sites but didn't go too in-depth on this) so that we can incorporate it too.  It's an established part of the "brand" of CROC (hopefully it's open source or the rights to its use won't be an issue even if some sort of premium for its use might be required).