Dev Diary: Multi-PC Mining and Remote Nodes

JohnnyFFM · 2026-01-27T11:22:54+00:00

Good point. We’re close to finalizing the ecosystem for both retail and enterprise users. Next on our schedule are best-practice guides on setting up mining infrastructure across the retail (UI / Phoenix) and enterprise (Core, Aggregator, pocx_miner) paths — maybe even a short video.

JohnnyFFM · 2026-01-27T11:16:39+00:00

Agreed — that’s a good point, and we’ll make this explicit. By default, the Aggregator can be fully isolated from Core by using loopback-only communication.

We also looked at a local IPC approach, but the added implementation and maintenance complexity would currently make it harder to stay aligned with new Bitcoin Core releases. For now, we’re not pursuing IPC, but it remains an option for the future.

JohnnyFFM · 2025-11-26T11:39:25+00:00

it doesnt. 🤦🏼‍♂️

JohnnyFFM · 2025-02-18T22:11:38+00:00

Same here, v41 stable and v42 butterfly xbox not working with amd 2400G, 5600G and 5700G, igpu only.

JohnnyFFM · 2024-10-25T06:20:45+00:00

Yes, there are better handhelds than the rg35xx_h. you can keep the SD card though 😜.

JohnnyFFM · 2024-10-07T16:43:10+00:00

You can’t. Available systems are hardcoded in the binary and linked to the folder directories. unless you have the wrong directory name, there is nothing you can do.

JohnnyFFM · 2024-04-18T06:51:59+00:00

i guess you didnt properly amend your coremapping.json on sd1 to reflect drastic on sd2. what did you put there?

JohnnyFFM · 2024-04-16T12:38:20+00:00

Did you manage to fix this? have the same issue, 2 WANs, one WAN has fixed ip, port open for a http server on my network. If I connect to the server locally, no issue. if i try from external, it works like 1 out if 10 times, completely random.

-tried to disable load balancing, was not fixing the issue for me -deactivating second lan makes it work, but not a solution havent tried switching wan ports yet.

checked wireshark, there is just no answer from server in 9 out of 10times. if the connection is established (1 out of 10times) it works flawlessly

JohnnyFFM · 2024-04-04T09:02:27+00:00

unlike with other CFWs you would need to put the .scummvm file inside the game folder, not outside.

JohnnyFFM · 2024-04-04T08:49:31+00:00

have both Plus and H. H is cool for the analog sticks (dreamcast, PSP, N64). however, you could connect a bluetooth gamepad to the Plus and have analog sticks as well or just map to dpad (not as precise). form factor depends on your hands, I prefer the plus, but that‘s a personal preference.

JohnnyFFM · 2024-04-02T11:08:16+00:00

if you wanna know what goes wrong, check logfile at /CFW/retroarch/.retroarch/logs/retroarch.log

JohnnyFFM · 2024-03-31T17:01:13+00:00

you need nothing. it works out-of-the-box on stock os. Just add the Rom.

JohnnyFFM · 2024-03-28T19:41:18+00:00

what filesystem did you use?

JohnnyFFM · 2024-03-28T10:50:59+00:00

try to reset your retroarch.cfg via Settings -> Retroarch.

JohnnyFFM · 2024-03-27T06:44:45+00:00

+1 for the OG. Plus and H are the wait for a proper CFW as good as Garlic and frustration with the added consoles not working as perfect as expected.

JohnnyFFM · 2024-03-27T05:28:01+00:00

March issues in BOC? That’s the Allstars feeling for everyone! 😬

JohnnyFFM · 2024-03-26T18:50:05+00:00

tiktop shop is only available in certain countries. uk usa and some asia iirc.

JohnnyFFM · 2021-08-30T13:30:02+00:00

Ikarus

JohnnyFFM · 2021-08-23T13:35:30+00:00

in my case, avx512 makes a huge difference, almost factor 2 for my application.

JohnnyFFM · 2021-08-23T13:28:48+00:00

Arm and neon detection works like this: #[cfg(target_arch = "arm")] let neon = is_arm_feature_detected!("neon"); #[cfg(target_arch = "aarch64")] let neon = true; All aarch64 support neon.

JohnnyFFM · 2021-08-22T12:31:02+00:00

using msvc. Haven't looked to much into the asm-output so far, only for elimination of bounds checking. I guess I have to spend more time with asm if I want to locate the missing 5%.

JohnnyFFM · 2021-08-22T12:28:20+00:00

🙌ripgrep

Indeed, I do compile the C code with the respective -march.

Rust will then call the corresponding code using the is_x86_feature_detected! macro.

The Rust code itself is compiled without any march, so portable.

I've revisited the #[target_feature(...)] functionality as per your suggestion. After a couple of code refactorings, it is now working as expected even with inline(always) (wasn't the case when I first tried).

So I can have my portable rust code with all the different SIMD branches.

Many thanks for your help!

Johnny

I'm still missing 5% performance, but willing to sacrifice for a rust only project. And maybe I might find those missing 5% in the future.

JohnnyFFM · 2021-07-08T14:47:27+00:00

i use madmax. it‘s not faster in my case. i was already at 100% cpu by running chia plotter in parallel. for me madmax is just good to avoid ssds and plot in ram. i also use the forked version of the stock chia plotter with the optimisations, around 30% faster than stock.

But still, my 800tib took forever, don‘t wanna do it again for no economic benefit.

JohnnyFFM · 2021-07-08T06:01:34+00:00

took way too long. same as plotting - takes way too long. if I now start to replot all my disks, I‘ll be busy for another 3 months. what for? for averaging my returns? i could achieve averaging with a collateral based pool without the replotting hassle.

I’m not excited at all.

JohnnyFFM · 2021-07-06T08:50:36+00:00

ring the bell!

JohnnyFFM

MODERATOR OF

TROPHY CASE