fased federation
Inspect Fased Network runtime state, token state, and hosted routing paths from the CLI.
In Fased, Fased Network is the network participation layer. The command name is
still fased federation because that is the current CLI/API surface. Use it to
verify whether the runtime is merely configured, actually enrolled, trusted, and
publicly reachable.
It is also the quickest terminal-side check when you need to know whether a runtime should be treated as:
- discovery-only
- trusted and reachable
- ready for public routing or marketplace-facing workflows
Common commands
Commands
fased federation status
Show the current Fased Network runtime picture:
- whether Fased Network is configured
- whether auto-connect is enabled
- base URL
- handle
- public origin
- token presence
- trust state
- hosted state
- public URL when present
- whether the hosted probe is healthy or broken
fased federation token
Show the persisted Fased Network token summary.
This is the quickest way to inspect:
- token id
- handle
- issue and expiry times
- trust state
- hosted state
- scopes
- public URL
fased federation paths
Show where Fased Network state is stored on disk.
fased federation bond-wallet status
Show the Vault wallet currently configured for Fased Network bond.
fased federation bond-wallet set <walletId>
Assign the Vault wallet that the runtime should use for Fased Network bond and bond proof.
fased federation bond-wallet clear
Clear the configured bond Vault without deleting the wallet itself.
What this command is for
Usefased federation when you need:
- a quick SSH-side health read
- token inspection without opening the UI
- confirmation that hosted routing and token persistence are wired correctly
- confirmation that the public route is healthy, not just enrolled
- a fast reality check before using the runtime in public-facing network workflows
joinedor token present means Fased Network state existshostedState: readymeans the network accepted the runtime- hosted probe health tells you whether the public route is actually serving correctly
- trust state tells you whether the network currently regards the runtime as verified, pending, revoked, or blocked
- Fased Network state is not the same thing as payment, SAT, or marketplace workflow readiness
- payment workflows remain separate from SAT participation logic
- hosted app browsing and self-hosted execution are different product roles
- this CLI group manages the configured bond Vault assignment
- the bond lifecycle itself is run through the Fased Network control surface and SAT tooling
- a separate Vault wallet is required by Fased for bond authority