pastilhasandClaude Opus 5
bc06fbb2a5
freezing a coin promised it would not be spent, and the promise only held when the caller named outpoints explicitly. an ordinary send picked its own inputs from a snapshot in which every utxo said frozen: false — the chain has no idea what officer froze — so selectCoins, which has always filtered on that flag, never saw one set. sendAll was the worst case: "send everything" swept the frozen coin too. the frozen list now travels with the request, set by the route and overwritten if a caller supplies one. it can only ever restrict what is spendable, so smuggling a value in gains nothing. the backend still reads no officer table. three tests pin it, including a control that sends successfully once the coin is unfrozen — without it the other two would pass on a wallet that could not spend at all. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>