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.
32 lines
1.4 KiB
TypeScript
32 lines
1.4 KiB
TypeScript
import { Bitcoin } from 'lucide-react';
|
|
import { WALLET_SECTIONS } from './shared';
|
|
import { Amount, UnitToggle } from './Amount';
|
|
import { LockBadge } from './LockBadge';
|
|
import { useWalletSection } from './useWalletSection';
|
|
import { useSelectedWallet } from './useSelectedWallet';
|
|
import { useBalances } from './useWalletData';
|
|
|
|
// Panel header for the right (wallet-view) panel: which section, which wallet, the spendable balance and
|
|
// the lock state. The lock indicator is compact here — it reports, it does not act, because the actions
|
|
// live in the nav and on the signing surfaces themselves.
|
|
|
|
export const WalletViewHeader = () => {
|
|
const section = useWalletSection();
|
|
const { wallet, walletId } = useSelectedWallet();
|
|
const { balances } = useBalances(walletId);
|
|
const label = WALLET_SECTIONS.find((s) => s.id === section)?.label ?? 'Wallet';
|
|
|
|
return (
|
|
<>
|
|
<Bitcoin className="h-3.5 w-3.5 shrink-0" />
|
|
<span className="flex-1 truncate text-xs font-medium">
|
|
{label}
|
|
{wallet && <span className="ml-1.5 font-normal text-muted-foreground">· {wallet.name}</span>}
|
|
</span>
|
|
{balances && <Amount sats={balances.onchainConfirmed} className="shrink-0 text-[10px] text-muted-foreground" />}
|
|
<UnitToggle className="shrink-0" />
|
|
<LockBadge walletId={walletId} walletName={wallet?.name ?? 'this wallet'} compact />
|
|
</>
|
|
);
|
|
};
|