officer
a4cf939be7
Tenth plugin out, and the one whose extraction turned on a permission decision rather than a mechanical move. The wallet permission was kind: 'admin' — owner only, not grantable, invisible to every other account. Plugin permissions are ALWAYS kind: 'app': mount.ts forces it and the manifest has no field for anything else, deliberately, so that "can a plugin escalate itself" is a question which cannot be asked. So extraction could not preserve admin, and that was raised as a blocker before any code moved. It was the right change anyway, and the objection inverts. Every wallet query is scoped by user_id, and that id comes from X-Officer-User which the platform injects from the authenticated session — a caller cannot name someone else's. So granting this gives an account ITS OWN wallet. Not through the API and not with root either does it hand over anyone else's, because their seed is sealed under a passphrase the server never stores. kind: 'admin' was single-user thinking; grantable is how a second person gets a wallet at all. Named bitcoin-wallet rather than wallet: it is a bitcoin wallet specifically, and the appName drives the route, the API prefix, the table prefix and the install key together. Tables renamed to bitcoin_wallet_* accordingly — the prefix guard normalises the hyphen. Free only because no wallet table existed on any server, which was checked before deciding: db:push treats a rename as a drop plus a create. The three custody test files moved with it and still run — 72 tests over scrypt sealing, envelope open and bolt11. bunfig.toml's test root was widened on 2026-08-15 after music took lyrics.test.ts and the suite silently shrank by nine, so that trap was already closed. 68 palette classes converted, five status vocabularies hoisted into shared.ts. Two deliberate flattenings recorded in PLUGIN.md: testnet/signet/regtest all read as warning, and the bitcoin and lightning rails no longer differ by hue. Deferred on purpose: watch-only data (xpubs, balances, history) stays unencrypted so a locked wallet still shows a balance. Anyone with the database can therefore SEE any user's balances; they can never move a coin.
37 lines
1.6 KiB
TypeScript
37 lines
1.6 KiB
TypeScript
import { Bitcoin, Loader2 } from 'lucide-react';
|
|
|
|
// The "no wallet selected" and "this backend cannot do that" placeholders.
|
|
//
|
|
// Deliberately not an error state: with no wallets registered there is nothing wrong, and a section a
|
|
// backend does not implement is a fact about the backend, not a failure. The nav hides those sections, so
|
|
// UnsupportedSection is only reached by a deep link — which should explain itself rather than 404.
|
|
|
|
export const EmptyWallet = ({ isLoading = false }: { isLoading?: boolean }) => (
|
|
<div className="flex h-full flex-col items-center justify-center gap-2 p-8 text-center">
|
|
{isLoading ? (
|
|
<>
|
|
<Loader2 className="h-5 w-5 animate-spin text-muted-foreground" />
|
|
<p className="text-sm text-muted-foreground">Loading wallets…</p>
|
|
</>
|
|
) : (
|
|
<>
|
|
<Bitcoin className="h-8 w-8 text-muted-foreground/50" />
|
|
<p className="text-sm font-medium">No wallet yet</p>
|
|
<p className="max-w-sm text-xs text-muted-foreground">
|
|
Add one from the panel on the left — a self-custodial seed sealed under a passphrase, or a connection to a
|
|
node you already run.
|
|
</p>
|
|
</>
|
|
)}
|
|
</div>
|
|
);
|
|
|
|
export const UnsupportedSection = ({ what }: { what: string }) => (
|
|
<div className="flex h-full flex-col items-center justify-center gap-2 p-8 text-center">
|
|
<p className="text-sm font-medium">Not available for this wallet</p>
|
|
<p className="max-w-sm text-xs text-muted-foreground">
|
|
This backend does not support {what}. Pick a different wallet from the panel on the left.
|
|
</p>
|
|
</div>
|
|
);
|