PackageFlashyFinancial

@flashyfinancial/signer

The FlashyFinancial-scoped home of the isolated signer: verifies an Ed25519-signed SpendAuthorization, re-derives the operation from the real call, refuses on any mismatch, executes through Tether WDK, and reports settlement — extracted verbatim from flashyos/packages/signer into wallet-core.

version 0.1.0 · measured 2026-10-30 from a checkout · source: github.com/FlashyFinancial/wallet-core/packages/signer

npm i @flashyfinancial/signer — prepared, not yet published; @flashyos/signer is the copy the registry serves today

The same five steps in the same fixed order as @flashyos/signer, documented on that page, with the cross-package dependency on wallet-wdk pointed at the @flashyfinancial scope. It still holds the seed and still never holds the plane’s private key.

Edge cases — each one paid for once

TESTNETS travels with the extraction, and widening it is still a pull request

The signer’s whole chain list is a source constant — Base, Ethereum, Arbitrum and OP Sepolia, Nile and Shasta — and every other chain throws MainnetNotEnabled at construction. Extracting the package into its own repository changed none of that: there is still no environment variable or option that enables a mainnet, so a team adopting the FlashyFinancial copy inherits the pilot gate rather than a switch.

← Full catalog · The doctrine behind the tools · Adopt one