Quote from: heratys111 on June 20, 2018, 06:20:24 AM

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

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?