PackageFlashyFinancial
@flashyfinancial/wdk
The FlashyFinancial-scoped home of the FlashyOS agent object: identity, authority, wallet, memory and partners behind one interface, on any chain Tether WDK reaches — extracted verbatim from flashyos/packages/wdk into wallet-core.
version 0.1.0 · measured 2026-10-30 from a checkout · source: github.com/FlashyFinancial/wallet-core/packages/wdk
npm i @flashyfinancial/wdk — prepared, not yet published; @flashyos/wdk is the copy the registry serves todayFlashyOrganization and FlashyAgent as @flashyos/wdk documents them, with refusals as values and only a transport failure thrown; it depends on @flashyfinancial/wallet-wdk rather than the @flashyos copy, which is the one place the two trees name different things.
Edge cases — each one paid for once
A dependency that names a scope the registry does not serve cannot install
wdk depends on wallet-wdk and signer depends on wallet-wdk, both under @flashyfinancial — so until @flashyfinancial/wallet-wdk is on the registry, neither dependant installs from npm even if it were published first. The publish order is a constraint the dependency graph imposes, not a preference, and it is why all three sit at “prepared, not yet published” together rather than one at a time.