From d59cf6d299be47a4322d5da59d2d4b3fe6be2ad1 Mon Sep 17 00:00:00 2001 From: archipelago Date: Sat, 20 Jun 2026 12:28:24 -0400 Subject: [PATCH] =?UTF-8?q?docs:=20session=203=20=E2=80=94=20ecash=20confi?= =?UTF-8?q?rm+refund,=20#5=20confirmed,=20#7=20fmcd-on-.116=20EPERM?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/HANDOFF-2026-06-20-mesh-netbird.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/HANDOFF-2026-06-20-mesh-netbird.md b/docs/HANDOFF-2026-06-20-mesh-netbird.md index 26f071e9..ddf9ad12 100644 --- a/docs/HANDOFF-2026-06-20-mesh-netbird.md +++ b/docs/HANDOFF-2026-06-20-mesh-netbird.md @@ -39,6 +39,26 @@ claude-login.html, chown 1000:1000, restart, verify sha256+health). Recreate fro `2679725907` = federation_peer_contact_id(.120 pubkey 535fb91f…), name "Archy-X250-EXP". It's a **duplicate-contact SURFACING** problem (user confirmed doubles). +## SESSION 3 PROGRESS (2026-06-20 — deployed fleet-wide, binary `e1f2e88`) +- **#5 Arch Mobile messages CONFIRMED FIXED** by the #12 dedup — user verified MeshCore surfaces them. +- **#3 ecash pay-for-file — confirm UI + auto-refund** (`12f54e39`): PeerFiles shows a confirmation + step (amount + which wallet Cashu/Fedimint + balances + switch + styled Confirm); `content.download-peer-paid` + takes `method`, logs the backend+outcome, gives backend-specific rejection errors, and RECLAIMS the + spent token on any failure (fedimint reissue / cashu receive) so funds aren't lost. Root cause of the + user's failed pay: `.198` had no Cashu → spent Fedimint notes → seller `.89` not in the SAME federation + → rejected → notes stuck (now auto-refunded; old stuck notes auto-return in ~1h via the 3600s spend timeout). + To COMPLETE a fedimint pay, payer+seller must share a federation (or share a Cashu mint w/ balance). +- **#1 companion crash** — added an on-screen red error overlay (`242baf5d`) since chrome://inspect isn't + reachable on the WebView; user reproduces → screenshots the box → that's the real error to fix on. +- **#7 NEW: can't add Fedimint federations on `.116`** — fmcd sidecar crash-loops `Operation not permitted + (os error 1)` on every start (DHT can't bootstrap), so `:8178` answers HTTP 000 and `wallet.fedimint-join` + fails. fmcd data dir IS correctly owned (100999). NODE-SPECIFIC: fmcd WORKS on `.198` (spent notes there), + fails only on `.116` → likely a seccomp/rootless syscall restriction on `.116`'s kernel (6.12.74). + Survives container recreate (reconciler made a fresh fedimint-clientd, still EPERM). NOT the ecash code. + Likely fix: add `--security-opt seccomp=unconfined` (or the specific cap) to the fmcd container spec, or + disable the fmcd DHT. WORKAROUND: test fedimint on `.198`/`.89`, not `.116`. +- Deploy: all 6 nodes verified on `e1f2e88`; pushed gitea-vps2 (gitea-local token still 401s). + ## SESSION 2 PROGRESS (2026-06-20, code-complete — NOT yet deployed; user held deploy) All committed to local `main`; NOT pushed to gitea-vps2/origin yet, NOT sideloaded. - **#12 dup contacts DONE** (`f92e442b`, +3 unit tests pass). Backend `group_peer_twins()`