It's not wired to do that, but absolutely could be. I basically just followed the OpenAPI specs as there are right now.

Between your comments and codex, I think I have adjusted the math correctly, here I pulled up: @fnzcmd in the pool and hovered over his ATX:SWAP.HIVE, and I think the math looks right now.

Link is fixed, and I don't know why it timed out, but i restarted it and it seems, ok, at least at the momen. Maybe I spoke too soon on, "how well it went" 😅

i still need to enable ipv6 on my router You would think if they wanted universal adoption they would have made it more "user friendly."

You are not wrong. But, I only have this one computer, so it's also my daily driver, dev machine, home server, etc.

gemma4:12b runs pretty good locally. I have a discord bot my wife talks to that is video game focused.

When this happens again, can you try to find if the node is divergent? Will do Let's see... funny that contributions for these projects depend on what people have problems with :D Necessity is the mother

I did get Sandrone. I'm hoping since superconduct is a physical based mechanic that they bring physical damage back sometime this year too.

Yeah, no worries, I'm not in any kind of hurry. I will say it seems stable with this patch, but also could be a fluke, I'll know more if/when the power goes out. (not willing to willfully test hard power

$ mongod --version took 1h38m34s [09:55:43] db version v8.2.11 Build Info: { "version": "8.2.11", "gitVersion": "ee01d36638a00a07a6aa42ee80a125890f11aeed",

here is a different one: 1_689_118 Jun 25 07:50:03 mina node[3626163]: 2026-06-25 07:50:03 info: [JsonRPCServer] successfully initialized 1_689_119 Jun 25 07:50:03 mina node[3626163]: RPC Node now listening

Light node. Lot of logs, but here is one example: 586_687 Jun 15 14:34:11 mina systemd[1870]: Started engine.service - Hive Engine Service. 586_688 Jun 15 14:34:30 mina node[2200]: (node:2200) [MONGODB

Yeah, no problem, let me see if can find a journalctl of the exact issues, there should be plenty of them 😅

It's been an ongoing issue for as long as I've tried to run a node, earliest kernel i can remember off the top of my head was before debian 13 was released, so 6.12.xx(ish), I just got tired of restoring

Could be similar to the issues I had with io on the ssd, still don't have an nvme. But still the replica set transaction wasn't implemented right. Right now it: writes block starts processing transactions

I lose power frequently, more than I like, but also when I do kernel updates and reboot, almost any time I restart the service I have issues.

Should be up within the hour after some final tests.

There is no hard Anther-level limit on the number of concurrent block or operation streams, but developers should treat streams as RPC-backed polling loops, not as an unlimited firehose. StreamBlocks starts