Skip to content

Opt-in payment alerts on mainnet and for view-only wallets (#61) - #104

Merged
gf5901 merged 1 commit into
mainfrom
feat/mainnet-alerts-61
Nov 16, 2026
Merged

gf5901 merged 1 commit into
mainfrom
feat/mainnet-alerts-61

Conversation

@gf5901

@gf5901 gf5901 commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Closes #61's "If yes" step. Decided 16 Nov: A, opt-in only. Mainnet wallets, view-only ones included, can lend their Orchard viewing key to Lantern Zero for payment alerts, but only after a yes on the consent sheet. The sheet already says what a breach or a court order could see while the key is lent. #102 added a line for view-only wallets, which shows from now on.

Engine

  • alerts_allowed is removed. lantern_connect, lantern_set_scanning and lantern_wake no longer refuse on mainnet or for view-only wallets.
  • Wakes lend the IVK whenever scanning is on, on both networks. Scanning stays off unless the person turned it on.
  • The host-only host-mainnet-alerts feature from Host tool: lend a throwaway mainnet key for Lantern Zero's key check (#61) #100 isn't needed anymore and is removed, including its CI and check.sh lines. examples/lantern --mainnet connect --scan now lends directly.
  • Tests: a mainnet view-only wallet isn't refused and has a uivk1… key to lend.

App

  • alertsAvailable is removed from the Lantern status (Swift, Kotlin, TS).
  • Notifications always shows the consent sheet before lending. "Not now" keeps wake-ups only, as before.
  • The mainnet "wake-ups only" copy is gone. The intro and "What's shared" use the same words on both networks, and Me's row is "Payment alerts" on both.

Checks: scripts/check.sh passes (JS checks, clippy, 96 engine tests). Swift and Kotlin only lose lines; they haven't been compiled or run on a phone.

Before a store build ships this

  • Lantern Zero's production key-storage check (lanternzero-ops notes/legal/scanning-risk-assessment.md). A throwaway mainnet wallet's key is lent to production now for it.
  • Phone checks: turn on alerts for a mainnet view-only wallet, see the consent sheet with the view-only line, receive an alert. Use a throwaway wallet, not one that watches real funds.

🤖 Generated with Claude Code

Decided 16 Nov: mainnet wallets, view-only ones included, may lend
their Orchard viewing key to Lantern Zero for payment alerts, only
after a yes on the consent sheet. The sheet already names what a breach
or court order could see, and adds a line for view-only wallets (#102).

Engine: alerts_allowed is gone, so connect/set_scanning/wake no longer
refuse on mainnet or for view-only wallets, and wakes lend the IVK
whenever scanning is on. The host-only host-mainnet-alerts feature from
#100 is no longer needed and is removed; examples/lantern --mainnet
connect --scan now lends directly.

App: alertsAvailable is removed from the status on both platforms;
Notifications always asks for consent before lending, the mainnet-only
"wake-ups only" copy goes, and Me's row is "Payment alerts" on both
networks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gf5901
gf5901 merged commit 9d5435e into main Nov 16, 2026
4 checks passed
@gf5901
gf5901 deleted the feat/mainnet-alerts-61 branch November 16, 2026 23:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Payment alerts for mainnet view-only wallets (lend the IVK, with consent)

1 participant