Rhys79

Ok, so I think I've added in all of the necessary bits and bobs to handle device self registration/provisioning into the library code, and I have it all deployed in...

Looks like it is this line causing the problem, not my modified library code. `Telemetry("deviceName", IMEI),` For some reason the Telemetry template is detecting the IMEI variable as an int...

Well then, helps if the Telemetry constructor includes a standard character array or String type. I duplicated the const char *val line removing the const modifier and my code at...

Still working out a few bugs, but I have most of the kinks worked out for using NodeJS-Pool for Fork-Note based coins such as KRB/XLC/DCY/etc. There are a number of...

The edits have been relatively minor so for, just difficult to track everything down that needs fixed.

Snipa has a krb.js (which is forknote) in the repo already, I just modified it to for XLC. @Bathmat yep, we came to the same solution for the orphan block...

All I did was change a couple lines in the packages file, delete the node_modules folder, npm install, and changed cryptonote-utils to forknote-utils in a couple of .js files

Don't know what you're talking about, we just got XLC working with only a few minor edits, and I have KRB spun up with almost no edits, one small problem...

Haven't tried xmr-node-proxy, as we are running xmrig-proxy and xmrigCC with some scripting. Add "forknote-util": "git://github.com/wallet42/node-forknote-util.git" in package.json, then change const cnUtil = require('forknote-util'); in api.js and the krb.js or...

I can say from experience, forknote based coins require multiple modifications to base nodejs-pool code to function. There is no one size fits all version of nodejs-pool to support shitcoins....