blockyard 0.0.1 → 0.0.9

package/server/util/fmt.js

@@ -0,0 +1,29 @@
+// Server-side formatting. Deliberately small: the browser has its own copy of
+// the display rules (public/js/fmt.js) and the two must not drift in the
+// one place that matters -- the ETA shape, which this project already prints as
+// DD:HH:MM:SS in its own status line.
+
+// DD:HH:MM:SS, as used by the node's downloader ETA and its heartbeat `uptime`.
+export function formatEta(totalSeconds) {
+  if (totalSeconds == null || !Number.isFinite(totalSeconds) || totalSeconds < 0) return null;
+  const s = Math.floor(totalSeconds);
+  const d = Math.floor(s / 86400);
+  const h = Math.floor((s % 86400) / 3600);
+  const m = Math.floor((s % 3600) / 60);
+  const sec = s % 60;
+  return `${pad(d, 2)}:${pad(h, 2)}:${pad(m, 2)}:${pad(sec, 2)}`;
+}
+
+function pad(n, w) { return String(n).padStart(w, '0'); }
+
+// Decimal units, matching how the node prints sizes ("4.0KB" for 4096 bytes).
+const UNITS = ['B', 'KB', 'MB', 'GB', 'TB', 'PB'];
+export function formatBytes(n, dp = 1) {
+  if (n == null || !Number.isFinite(n)) return 'n/a';
+  let v = Math.abs(n);
+  let i = 0;
+  while (v >= 1000 && i < UNITS.length - 1) { v /= 1000; i += 1; }
+  return `${(n < 0 ? '-' : '')}${v.toFixed(i === 0 ? 0 : dp)} ${UNITS[i]}`;
+}
+
+

package/systemd/blockyard.service

@@ -0,0 +1,100 @@
+# BlockYard -- multi-user web monitor for a Bitcoin Core node.
+#
+# Install:
+#   sudo cp systemd/blockyard.service /etc/systemd/system/
+#   sudo systemctl daemon-reload && sudo systemctl enable --now blockyard
+#
+# Read-only by design: this unit needs no access to the node's datadir beyond the
+# log file and the RPC cookie, and the app performs no node writes unless
+# BLOCKYARD_ENABLE_ACTIONS=1 plus an explicit BLOCKYARD_ACTIONS list are set.
+#
+# Nothing in this file is machine- or person-specific on purpose: it is committed,
+# so real usernames and host addresses belong in config/local.json, which is
+# gitignored. Two lines below are therefore placeholders you must edit.
+[Unit]
+Description=BlockYard - Bitcoin node monitor
+Documentation=file:///storage/blockyard/AGENTS.md
+After=network-online.target
+Wants=network-online.target
+StartLimitIntervalSec=600
+StartLimitBurst=5
+
+[Service]
+Type=simple
+# EDIT ME: the account that may read <datadir>/<chain>/.cookie and the node log.
+# Cookie authentication is unusable without that read access, so a wrong user here
+# shows up as a permanently-offline node rather than a clear error.
+User=blockyard
+Group=blockyard
+WorkingDirectory=/storage/blockyard
+# Name the interpreter, do not go looking for it. Measured on this box 2026-09-09:
+#   /usr/bin/node        is v18.19.1 -- below package.json engines ">=22", and it starts
+#                        far enough to fail on syntax, which reads like a code bug.
+#   /usr/local/bin/node  is a symlink into a root-owned private runtime; that home is
+#                        mode 0700, so for any User= but root it does not exist -- and
+#                        /usr/local/bin is FIRST on systemd's default PATH.
+# `/usr/bin/env node` therefore resolves either to a runtime that is too old or to
+# nothing. Pin PATH for child processes and give ExecStart an absolute path; generate
+# the path once with `node -v` on the target and paste it in, since this file is
+# committed and a per-machine interpreter belongs in a drop-in, not here.
+#Environment=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/bin
+#ExecStart=/absolute/path/to/node server/main.js
+ExecStart=/usr/bin/env node server/main.js
+# always, not on-failure. The outage this box actually had -- service gone, nothing on
+# the port, no error line anywhere in the log, no journal entry because nothing was
+# supervising it -- is exactly the case on-failure cannot see: an exit 0, or a stop that
+# leaves no trace. With Restart=always the exit status and signal at least reach the
+# journal, which is the difference between "it died" and "it died of 9/KILL at 08:35".
+Restart=always
+RestartSec=10
+KillSignal=SIGTERM
+# SIGTERM triggers the durable-shutdown path (history + sessions are saved with
+# tmp+fsync+rename), so give it room to finish rather than SIGKILL mid-flush.
+TimeoutStopSec=45
+
+# BINDING. Which address to serve is a per-machine decision, so it lives in
+# config/local.json (`server.hosts`), not here -- that file is gitignored and the
+# app refuses to start if a configured address is absent at boot, rather than
+# silently falling back to a wildcard. A previous revision of this file embedded a
+# real LAN address here AND had two Environment= assignments concatenated onto one
+# line, which silently discarded BLOCKYARD_PORT; both are fixed by not putting
+# machine facts in a committed file in the first place.
+#
+# Consequences worth remembering: binding a single non-loopback address means
+# 127.0.0.1 on the host itself stops working (curl checks must use that address),
+# and clients that reach the box over a tunnel need that tunnel's address listed.
+Environment=BLOCKYARD_PORT=21000
+Environment=BLOCKYARD_NODE_URL=http://127.0.0.1:8331
+Environment=BLOCKYARD_DATADIR=/home/bitcoin/.bitcoin
+Environment=BLOCKYARD_LOGFILE=/home/bitcoin/.bitcoin/debug.log
+Environment=BLOCKYARD_LOG_LEVEL=info
+# ACCESS: accounts are OFF by default, so anyone who can reach the bound addresses
+# reads this monitor (role "viewer": charts, feeds, read-only RPC console). User
+# administration, the audit trail and node writes stay closed to them. Uncomment to
+# require sign-in (accounts, roles, sessions, CSRF, per-user audit):
+#Environment=BLOCKYARD_AUTH=1
+#
+# Node writes stay off, and while accounts are off they stay off even if actions are
+# enabled -- a write with no identity behind it is not attributable. Enabling needs
+# ALL of: the two lines below, accounts on (above), or the explicit
+# BLOCKYARD_ALLOW_WRITES_WITHOUT_AUTH=1. The second line names the specific actions, so
+# "we turned on writes" is never an unspecific statement.
+#Environment=BLOCKYARD_ENABLE_ACTIONS=1
+#Environment=BLOCKYARD_ACTIONS=testmempoolaccept,savemempool
+
+# Modest hardening. NoNewPrivileges plus a read-only /home is enough here: the
+# service must read the node's RPC cookie and log, so a full PrivateTmp/
+# ProtectSystem=strict would fight the thing it is monitoring.
+NoNewPrivileges=true
+ProtectKernelTunables=true
+ProtectKernelModules=true
+ProtectControlGroups=true
+RestrictSUIDSGID=true
+LockPersonality=true
+
+StandardOutput=journal
+StandardError=journal
+SyslogIdentifier=blockyard
+
+[Install]
+WantedBy=multi-user.target