guy.davis

Good day. Machinaris v0.6.2 is now available with the following fixes and improvements: - Silicoin - cross-farming support for this blockchain fork. NOTE: Silicoin blockchain is currently paused by their developers. - fd-cli - Daily scheduled 7/8 coin win recovery for those farming NFT plots on other blockchains. - Madmax - support for plotting k33 and k34 plot sizes. - Machinaris - correctly show daily difference tooltips on Summary page statistics for all blockchains

Sorry, the icons shown on Unraid UI's Docker tab are only possible if you install each container individually from the Apps tab (aka Community Applications). docker-compose does not support Icon display in Unraid.

Hi Ystebad. Not all! Happy to help you out. Sorry to hear you've experienced trouble so far. As per the 0.6.0 upgrade guide, bridge network type is recommended. Since the error above looks like DNS, I recommend checking the DNS value in Network Settings on Unraid UI | Settings tab. For example, my DNS is my local router at 192.168.1.1 However, you could try a cloud DNS provided such as 1.1.1.1 or 8.8.8.8 instead to remove your LAN's router DNS from the equation. Hope this helps! Don't hesitate to ask further questions or join us in the Discord.

Hi everyone, let's talk about security in Machinaris and the wider Chia & forks ecosystem. Your private key, often represented as a 24-word mnemonic passphrase, is the most important Chia secret you have. This key controls your Chia wallet and your Chia plots. On setup of Machinaris your private key is stored in ~/.machinaris/mnemonic.txt. Then it is added to your Chia key ring with `chia keys add`, after which farming services of the fullnode are started. Your mnemonic is NOT used on on harvesters or plotters, only on fullnodes. In order for the blockchain forks such as Flax, Chives, HDDCoin, etc to farm the same plots as Chia, they also must be initialized with the same mnemonic. This increased exposure means it is even more important to set up a cold wallet to automatically receive won coins and pool payouts. Learn more on the wiki. Also, I am testing fullnodes being restarted/updated without the mnemonic.txt present, in hopes of removing it from disk after initial setup. So far, results have been mixed getting fullnodes to farm properly without mnemonic being imported on each restart. Your feedback on this is appreciated. Feel free to raise questions and make suggestions, either here, or in our new #security channel in the Discord. I am keen to improve Machinaris security in coming releases.

Yes, that's odd if you're using the Unraid Community Apps templates. If you're using straight docker-compose instead then I would expect that however. Since you're probably using the Unraid CA templates, try editing the Machinaris configs in Unraid UI | Docker tab. Look for Icon Url and use the paste the icon names like: https://raw.githubusercontent.com/guydavis/machinaris-unraid/master/logos/blockchain.png Just replace 'blockchain' with 'chives', 'hddcoin', 'nchain', 'flax', 'flora', etc. If they were already set like that and you still get a blank in Unraid UI, then I think you've discovered some strange Unraid UI bug. Hope this helps!

Good day. Machinaris v0.6.1 is now available with the following fixes and improvements: - Flora - cross-farming support for this blockchain fork. - ChiaDog - improved support for forks, fix coin symbol in certain alerts, Chives decimal placement, etc. - Machinaris - correctly report Chives plots from harvesters in the WebUI. Plots were farmed, but hidden from WebUI before. - Machinaris - fix error in Setup - Mnemonic Import wizard. - Machinaris - re-enable the Plotman Archving start/stop buttons. I really appreciate all those that made the big jump to v0.6.0 last week. For this v0.6.1 release, it's only a minor update.

Yes, lesson learned on my part. There is no 'alpha' tag allowed by Unraid CA to my knowledge, so I will simply not publish a template at all (beta or not) until the blockchain fork template works with the main Machinaris release at `:latest`. Early adopters who want to test new features will just have to run "docker-compose" for such new images. This will ensure the majority, running at machinaris:latest, don't encounter any breakage. Thanks for the feeback. Thanks. I code for fun though, not in it for the money. Appreciate the thought.

Yes, the Unraid Community App template for Machinaris provides a fullnode. It is possible to re-purpose the settings in that template to run as Harvester, however it can be a bit tricky. In particular you must enable "Advanced View" and 'Show more settings" in the Unraid UI | Docker tab | Machinaris "Edit" configuration. Then for a Chia harvester: Extra Parameters: -h $HOSTNAME Networking: Bridge Then, the easiest way to know exactly which Variables, Ports, and Volumes you need to configure in the Unraid UI on your Harvester is to visit the Machinaris WebUI on your controller and click New Worker. Fill in the form, for example: which gives as example this docker-compose.yml: Each volume line becomes an Unraid Path, each environment line becomes an Unraid Variable, and each port line becomes an Unraid Port in the Machinaris config, Unraid UI | Docker tab. Hope this helps. We've walked a handful of Unraid users through setup for a harvester in the Machinaris discord, so don't hesitate to drop in. EDIT: On re-read, it sounds like you might be running straight docker-compose on the harvester. That can work too. To trouble-shoot connectivity between harvester and fullnode, please paste a screenshot of your Workers page. Then let's see the "docker logs machinaris" output of your harvester. As well, please provide /mnt/user/appdata/machinaris/machinaris/logs/apisrv.log. Thanks!

Sorry for the trouble. Flora container, marked as Beta in Community Applications, requires v0.6.1 for the main Machinaris container which was published as `:test` images this morning. You can run it right now if you add `:test` to end of the Repository line in the Machinaris docker config in Unraid UI. I expect v0.6.1 will be promoted to `:latest` (aka fully released) in another day or two.

Hi, Chives is a neat blockchain fork, but is different from all the others. In particular, Chives requires its own plots of size k29, k30, or k31. Please see the wiki for details. Let me know if you have further questions.

Please accept my apologies on this error encountered with choosing Import Mnemonic from the initial Setup screen of v0.6.0. Very dumb oversight on my part. I have fixed in the next version. Easiest workaround is to manually create a file on the Unraid filesystem, just a single line with your 24-word mnemonic, at /mnt/user/appdata/machinaris/mnemonic.txt Then restart the Machinaris container and you should be taken right past the setup screen, to the main Summary page. Hope this helps!

Hi, please ensure that you have copied the mnemonic.txt over and restarted the Flax container: cp /mnt/user/appdata/machinaris/mnemonic.txt /mnt/user/appdata/machinaris-flax/mnemonic.txt Then take a look at /mnt/user/appdata/flax/mainnet/log files: debug.log and init.log. Hope this helps!

Hi, apologies for the shock. Known issue around default string values in the Chiadog version I enhanced to support the various forks. I'll get it fixed.

Sorry to hear that. try this: Stop all Machinaris containers. docker-compose stop or similar. Remove file /mnt/user/appdata/machinaris/machinaris/dbs/machinaris.db holding stale status records. Start up all Machinaris containers. docker-compose up -d or similar. Wait about 10-15 minute for all the containers to re-populate active status. Ideally, the stale records are gone and only active status remains. Please let me know how it goes.

Yes, Flora support is less than 1 day old and only supported on Machinaris v0.6.1+ (aka development branch). You'll need to upgrade all to ":develop" images. And expect breakages like this. I'll fix them though.

Sorry to hear you're having trouble. What did you find in the logs: /mnt/user/appdata/machinaris/machinaris/logs/webui.log? An error in the WebUI as you report does not mean that the underlying Chia farm is not functioning, just that there is a configuration issue preventing WebUI from displaying properly. Also, did you check out the upgrade guide? Hope this helps!

Good day. Machinaris v0.6.0 is now available with support for many more blockchain forks: - NChain- cross-farming support for this blockchain fork. - HDDCoin - cross-farming support for this blockchain fork. - Chives - support for this blockchain fork. - Flax - now farmed in a separate Docker container. Core enhancements to underlying components include: - Plotman - enhancement to support plotting for Chives via Madmax. - Chiadog - enhancement to support monitoring of other blockchain forks. Really big thanks to all those that helped review and provide feedback on this big step forward for Machinaris! Unraid users of Machinaris, please follow the upgrade guide: https://github.com/guydavis/machinaris/wiki/Unraid#how-do-i-update-from-v05x-to-v060-with-fork-support

Hi, sorry Machinaris makes use of calls against the Chia wallet. This doesn't preclude you from using a cold wallet though by changing the reward address and/or payout instructions under Settings | Farming I believe. Hope this helps!

Yes. Good question. Chives support is beta-only at this point as it requires different plots (k29/k30/k31) than Chia and other blockchains. I hope to improve Plotman soon to correctly interact with Madmax to perform that plotting. Until then, one must execute Madmax directly from inside the machinaris-chives container. Details at: https://github.com/guydavis/machinaris/wiki/Chives

Probably not critical as this is about to change in v0.6.0. By the way, which version of Machinaris are you running? See version at bottom of each page in Machinaris WebUI. Thanks.

Hi, there is likely a stale worker left on the Workers page. Please visit the page and Prune both. Don't worry if things vanish for 10 mins or so. The "real" one will begin to re-populate status shortly leaving only one Worker behind. Hope this helps!

Ok, yes the CA templates for your v0.5.7 Machinaris container are contaminated with settings from upcoming v0.6.0 Machinaris (currenly in development) with fork support. To fix, simply Remove the following from your config shown: * rpc_port * protocol_port * worker_api_port * worker_host * controller_host Then click Apply and the Machinaris container should restart. My apologies for the inconvenience. I am still learning the ins and outs of Unraid application templating.

Hmm, let's see if we can get this sorted out. Please ensure you are using a Repository setting of "ghcr.io/guydavis/machinaris" on the Docker settings for Machinaris: Then: 1) Stop Machinaris container 2) Delete /mnt/user/appdata/machinaris/machinaris/dbs/machinaris.db (on the Unraid host filesystem) 3) Start Machinaris container This should ensure you are using the latest release and create a fresh status database on launch. Please let me know how it goes.

Sorry to hear that. Please share: A screenshot of your Workers page to indicate status of install(s). The end of your log files (apisrv.log and webui.log) in /mnt/user/appdata/machinaris/machinaris/logs). Also available from right-hand side of your Workers page.

Sorry, to hear that. Please post a full-series of screenshots showing all settings for Machinaris under your Unraid Docker config, more than the snippets posted above. They seem to show one of the new beta templates for Machinaris forks. It seems like something is wrong with the Unraid Community Apps template for Machinaris which is unchanged for over 20 days now: https://github.com/guydavis/machinaris-unraid/blob/master/machinaris.xml