aboutsummaryrefslogtreecommitdiffstats
path: root/settings.js.sample
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-10-04 13:05:53 -0700
committerAdam Soltys <[email protected]>2026-10-04 13:05:53 -0700
commit1ff2623dbb43148267eac5cbe68c76d2c0639805 (patch)
tree469260cac95741bbd319ee1e699ed56834e1abcc /settings.js.sample
parent41a5819f5d7c662a5a2884952e49a14464e83c41 (diff)
downloadcoinos-server-1ff2623dbb43148267eac5cbe68c76d2c0639805.tar.gz
coinos-server-1ff2623dbb43148267eac5cbe68c76d2c0639805.zip
v3 bridge: a migrated name's legacy receives are paid on to its v3 wallet
A user who moved their name to coinos v3 keeps their legacy account, and old BOLT12 offers, bolt11 invoices and bitcoin/liquid deposit addresses keep paying into it. Each confirmed receive of those kinds is now forwarded as it lands to the name's v3 lightning address (registrar invoice on the ASP node; the v3 forwarder delivers to the Ark mailbox even with the wallet closed). Only new receives move; existing balances stay. Routing cost only: the platform fee is waived (debit exempt), and the direct channels to the ASP node quote 0. Proof required: the registrar holds the name for the legacy account's own key, or for the wallet its session named in a migration grant (/name granted flag). Autowithdraw stands down for forwarded receives; failures retry with backoff (v3fwd:retry, one process at a time) and otherwise stay put. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_011bvzKaZosXGHkigcGcSzAR
Diffstat (limited to 'settings.js.sample')
0 files changed, 0 insertions, 0 deletions