PackageFlashyOS
@flashyos/signer
The isolated signer for the FlashyOS wallet authorization plane: verifies an Ed25519-signed SpendAuthorization, re-derives the operation from the real call, refuses on any mismatch, executes through Tether WDK, and reports settlement. Holds the seed; never holds the plane’s private key.
version 0.1.0 · measured 2026-10-30 from a checkout · source: flashyos/packages/signer (private repository; the package is on npm as @flashyos/signer) · public face flashyos.com
npm i @flashyos/signerThe only process that holds a seed, and it never holds the authorization plane’s own private key. For every request it verifies the authorization’s signature and validity window, refuses a replayed nonce, re-derives the OperationRecord from the actual call, and refuses any mismatch between what was authorized and what is being asked — kind, chain, asset, destination, amount above the cap.
Three lines of defense: the plane grades an envelope and a human decides above autoApproveMax; the signer enforces that verdict against the real call; and an optional SafeAllowanceLimit reads the Safe Allowance Module on-chain before execution, so the signer refuses what the chain would refuse anyway.
Edge cases — each one paid for once
TESTNETS is the whole list of chains this signer will talk to
Base, Ethereum, Arbitrum and OP Sepolia for EVM, Nile and Shasta for TRON — every chain backend throws MainnetNotEnabled when constructed for anything else, and there is no environment variable, flag or option that widens it; enabling a mainnet is a source change made in a pull request, after the pilot gate in the runbook is met.
The re-derivation, not the authorization, decides what happens
The authorization says what may happen; the call says what is happening. If an agent was authorized to pay vendor A and the call pays vendor B, no valid signature makes that acceptable — UNRECOGNISED_CALL refuses any call shape no extractor vouches for rather than executing it blind, because a signer that executes what it cannot describe is a signer with no policy.
The deploy image needs the manifest, not just the import
npm links a workspace into an image only when its manifest was copied before npm ci. The api imported this package and the Dockerfile’s copy list stayed at four, so Deploy prod died on Module not found one step after an earlier fix got it that far. A test now reads imports with the TypeScript scanner and refuses the omission.