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.
Re-posting in this thread too...
PLEASE no forks needed here..
I am happy with what we currently have with CROC & it works for me and alot of other peeps.
Sorry folks don't expect to run this peer/nova coin clone on an ARM processor with no resources, or on a free tiny AWS node.
These clones are resources hungry, especially with the aggressive block gen time CROC has.
BTW, when is the last time you where able to have Yobit apply any update to a coin listed on the exchange?
Hello.
I support this plan and hope it ought be smash! Seamless activity, thoughtful vision!
Interesting, that would
seem to be a 50-50 split on a voice-vote. I suppose it's best to figure out how Bitcoin-Cash forked from BTC, Monero-classic from Monero, Wisp plans to from Spectrecoin, Linda-derivatives every-other-week from Linda. etc
(so that coins in a separate chain can be awarded one-for-one to CROC holders). Despite being a CROC-whale and determined holder, I have to point out that the chain is heavy (arguably, more memory-intensive than necessary) and the wallet is generic and minimal. I still want to work on and help improve things; so think this might be a better course: leaving CROC alone and working on a side-chain (a "baby-CROC" that is intended to see future development) that will be awarded one-for-one.
@MilkandPie4U Yeah... never tried to have Yobit update a chain and keep trading available (they don't exactly have the best reputation).
https://www.youtube.com/watch?v=EcerzD2XqWM Would we be speaking about a miracle, if CROC (CrocodileCash) reappears again in less than one year, with a new homepage and some new skills, other than a hardfork, where
all the older coins are swaped using some mad SWAP rate (50,000:1
), like some other devs have done, leaving the older investors at the rain?
We'll see... start the counter.
For my part, I'm getting heavily into assembly programming because I find it interesting (and it has points of overlap/interplay with Linux/Unix and C/C++). I had a few courses in college and university using C++ (and it was the first programming language I learned ... but only moderately in-depth at that point -- also learned/used some Java, VHDL, assembly for Motorola processors, and SQL and related stuff on data structures, databases, graphics, search algorithms, number theory, etc ). I recognize that higher-level languages like Python, Ruby, and TCL are useful because they make building stuff less of a chore (e.g., websites using frameworks or Ruby on Rails) but I kind of dig the first-principles and rigorous kind of stuff.
Just to indicate context, most bitcoin-derived cryptos are written in C++.
So guys, I hope the DEVs are prepairing something solid for the future of this old new coin.
The only one who ever called his-or-herself a developer for CROC was Gizzard and he's MIA. Others are interested parties only. I am very interested in CROC but maybe you should consider it to be hibernating. Croc's have a fossil-record of being around for last 55 million years; hopefully, you won't need to be so patient.
Hmmm... maybe we can come together as a bask (Group of Crocodiles) and get something going, I know Altcoins all too well
Hard Fork Reward Change or Hard Fork Codebase + Algorithm change + Swap:Ratio ? e.g PoW + PoS + Masternodes with one of the popular Exotic Algorithms that ASIC's are designed for ? Maybe Scrypt or X11 as a diversion away from SHA-256 ?
The swap ratio would be decided by polling from the community with the amount of CROC need to be traded in for said new coin, e.g CCASH ? 10:1 ? 5:1 ?
This will keep the Initial starting coins in existence to a minimum and we can add a lower reward schedule per Mechanism, e.g PoW Reward + PoS/Masternodes Reward + Ratio of Reward
Sound like an idea ?
We probably would also have to inform YoBit of the Coin Swap Hard-Fork to the new codebase if we wan't to keep a spot there as that is the only current Exchange to Trade CROC
I would be more than happy to help out this long living community coin as long as we all put our realistic ideas together and turn it into something compelling
MikeP243 are your perhaps a baller ? General research shows you could have been in crypto for years, looks like you are rolling in Lambos and playing DOGE games
