deutrino's picture

Hi there,

Just wanted to start a thread to gauge interest in a Monero appliance.

Would be monerod + p2pool + tor, most likely. Capable of being deployed as a public remote node, private remote node, for use with p2pool mining, etc.

If you don't know what any of this means:

tl;dr it's a cryptocurrency with strong privacy baked in to the protocol, "what bitcoin was supposed to be," and this appliance would allow users to easily self-host a node on the p2p network, which they could use for mining, or for them + their friends to connect wallets to, which is way better than selecting a random node off a list somewhere.

I'm currently on round 2 of building this atop Debian 11, when I do it all over again for round 3 I'm going to start documenting with an eye toward reproducing it in TKLdev eventually.


deutrino's picture

If I manage to get an XMR appliance built I'd love to repeat the process for Litecoin (LTC) as well.

badco's picture

That would be neat, I have been toying with the idea of running a node myself. Monero definitely is the future of cryptocurrency.

deutrino's picture

Last time I dabbled in cryptocurrency was about a decade ago (wow!) and while ease of setup is worlds better now than it was then, it's still very difficult.

I finally have a node working reasonably well and it took multiple efforts over multiple weeks looking at all manner of "documentation" in order to synthesize an understanding of what all the options mean, etc.

Having a Monero appliance that's essentially plug and play would be [b]amazing.[/b]

The one thing that scares me about this, confconsole bits will definitely have to be written, because it's going to need to ask the user what they want to deploy (e.g. public node, private node, Tor yes or no, etc) and act accordingly. I've never touched any of that, I post in here a lot but I've really only experimented with TKLdev to the point of pumping out a bunch of 16.x ISOs with a few customizations added.

So, we'll see. But I'd love to accomplish this.

Jeremy Davis's picture

Sounds cool.

Regarding inithooks/confconsole, it's all written in Python, so if you know python, you'll be fine. Otherwise, there will be a bit of a learning curve.

Considering that you'll want to ask initial config questions, Initihooks are what you'll need.

I'll try not to get ahead of myself, but firstboot scripts are (generally) triggered by a bash script (or if non-interactive, can just be done in bash). The interactive bit is done in python, with the actual commands required either being called directly by python, or in some cases via a glue script (often in an alternate language).

As for Confconsole, unfortunately, the code base between the 2 pieces of software aren't similar enough that a Inithook can simply be reused as a Confconsole plugin. I do hope to make that easier, but for starters, the inithooks are the most important (i.e. getting started).

deutrino's picture

Thanks for the info. I haven't written Python in a number of years but always enjoyed it when I did, so hopefully I can pick some back up here.

deutrino's picture

Just pinging the thread to report that while I am not ready to start on a Turnkey build for this yet, I have been continuing my research and am still intending to do it.

Bradly's picture

Please keep the hard work up I can't wait to hear more this will be amazing 
badco's picture

I ended up following this guide and running it in a dedicated VM. There is also another version of this guide that uses docker.

I also recommend reading Seth's other blog posts and even listening to his podcast.

Add new comment