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.
48 lines
2.0 KiB
TypeScript
48 lines
2.0 KiB
TypeScript
import { useEffect, useState } from 'react';
|
|
import { useLockState } from './useWalletData';
|
|
|
|
// The unlock window, as a second-by-second countdown.
|
|
//
|
|
// The sidecar's `secondsRemaining` is a snapshot taken when the request was served, and re-polling once a
|
|
// second to animate a clock would be absurd. So the poll re-syncs the truth every ten seconds and this
|
|
// hook interpolates between syncs from React Query's `dataUpdatedAt`, which is the wall time the snapshot
|
|
// arrived. Drift is bounded by the poll interval and always errs towards showing LESS time than remains —
|
|
// a countdown that overstates the window is the one that surprises you mid-signature.
|
|
//
|
|
// When it reaches zero the UI flips to locked immediately rather than waiting for the next poll to agree.
|
|
// Nothing else is invalidated when that happens: every read in this app works fine against a locked
|
|
// wallet, and blowing the caches away would make an expiring timer look like a connection failure.
|
|
|
|
export type LockCountdown = {
|
|
/** Null while the first lock-state request is in flight, or when no wallet is selected. */
|
|
hasSeed: boolean | null;
|
|
unlocked: boolean;
|
|
secondsRemaining: number;
|
|
isLoading: boolean;
|
|
};
|
|
|
|
export function useLockCountdown(walletId: number | null): LockCountdown {
|
|
const { lock, dataUpdatedAt, isLoading } = useLockState(walletId);
|
|
const [now, setNow] = useState(() => Date.now());
|
|
|
|
const ticking = lock?.unlocked === true;
|
|
|
|
useEffect(() => {
|
|
if (!ticking) return;
|
|
const timer = setInterval(() => setNow(Date.now()), 1_000);
|
|
return () => clearInterval(timer);
|
|
}, [ticking]);
|
|
|
|
if (!lock) return { hasSeed: null, unlocked: false, secondsRemaining: 0, isLoading };
|
|
|
|
const elapsed = dataUpdatedAt ? Math.floor((now - dataUpdatedAt) / 1000) : 0;
|
|
const secondsRemaining = Math.max(0, lock.secondsRemaining - Math.max(0, elapsed));
|
|
|
|
return {
|
|
hasSeed: lock.hasSeed,
|
|
unlocked: lock.unlocked && secondsRemaining > 0,
|
|
secondsRemaining,
|
|
isLoading,
|
|
};
|
|
}
|