Skip to main content

​
Onboarding Operations Guide

This guide is the canonical operator path from a clean machine to a stable Fased runtime with optional wallets, Fased Network, plugins, and SAT mining. It is written for the current Fased operating model:
  • self-hosted first
  • private operator access first
  • wallet discipline before automation
  • Fased Network after base runtime health
  • SAT mining last

​
1. Before you start

Decide three things before you run onboarding:
  1. is this machine the primary runtime host
  2. is this a personal machine or a hosted/VPS machine
  3. how will private admin access work
Minimum preflight:
  • machine you control
  • private access path such as Tailscale or SSH
  • plan for backup and recovery
  • willingness to keep admin access private

​
2. Primary entry commands

Install and onboard: 
./install.sh
Run onboarding directly after install: 
fased onboard --install-daemon
Hosted or VPS-style onboarding: 
fased onboard \
  --non-interactive \
  --accept-risk \
  --host-profile hosting \
  --ts-authkey 'tskey-auth-...' \
  --install-daemon
Bootstrap note:
  • initial SSH/root access is only for first install and host prep
  • after onboarding, day-to-day admin access should move to Tailscale SSH and the private dashboard URL
  • do not leave the raw gateway port exposed just because initial setup used SSH

​
3. Profile and mode model

Do not confuse:
  • host profile
  • mode
Use this distinction:
  • host profile controls how this machine behaves as a host
  • mode controls whether this machine is hosting the runtime or only connecting to another runtime

​
local

Use when:
  • this machine is your own runtime host
  • you want the most conservative learning path
  • browser dashboard and private admin matter more than long-lived hosted presence

​
hosting

Use when:
  • this machine is a VPS or always-on node
  • you expect managed runtime behavior
  • you want a cleaner fit for long-lived Fased Network participation

​
remote

Treat remote as a client connection mode. It is not the main path for hosting wallets, Fased Network state, or SAT mining.

​
4. Onboarding decisions that matter

These decisions carry the most long-term consequence.

​
Host posture

  • --flow quickstart|advanced|manual
  • --mode local|remote
  • --host-profile local|hosting

​
Gateway and auth

  • --gateway-port <port>
  • --bind loopback|tailnet|lan|auto|custom
  • --gateway-auth token|password

​
Private access and service behavior

  • --tailscale off|serve|funnel
  • --install-daemon
  • --ts-authkey <key>

​
Wallet posture

  • --wallet-enabled
  • --wallet-disabled
  • --wallet-chains solana
Public Fased docs assume the self-hosted wallet path when the runtime is used for real economic behavior.

​
Fased Network direction

Fased Network is not required for first boot. If you enable it during onboarding, remember:
  • enrollment is not the same as healthy public routing
  • managed runtime behavior still matters after restart

​
5. First health verification

Before you touch real funds or higher-risk plugins, confirm: 
fased status
fased health
fased dashboard
If wallets are enabled, also confirm: 
fased wallet signer doctor --json
fased wallet status --json
Your first safe milestone is:
  • runtime stable
  • private access stable
  • restart behavior sane
  • auth and bind posture intentional

​
6. Wallet architecture before funding

Do not invent wallet architecture from the dashboard after the fact. Decide the working model first:
  • reserve or cold wallet outside the runtime
  • agent wallet for ordinary sends, payments, skills, and automation
  • mining wallet for SAT only
  • vault wallet for manual storage and Fased Network bond assignment
  • optional second Agent wallet for isolated reviewed actions
Recommended progression:
  • view-only or manual first
  • policy-gated later
  • explicit @wallet:<walletId> handles for risky wallet actions
  • broad automation only after the signer path is proven

​
7. Plugin rollout

Use this order:
  1. observation plugins
  2. workflow plugins
  3. economic execution plugins
If a plugin can move value, define:
  • which wallet it uses
  • which limits bound it
  • how you will disable it quickly
Do not combine Fased Network, mining, and multiple high-risk plugins on an unproven runtime.

​
8. Fased Network bring-up

Fased Network is the network participation layer. Operationally, it means the runtime can:
  • register a handle
  • hold Fased Network token state
  • appear in routing and trust systems
  • expose a public hosted route when the managed path is healthy
Useful checks: 
fased federation status
fased federation token
fased federation paths
Important rule:
  • token present does not mean public route healthy
  • hosted state does not mean the runtime is actually reachable

​
9. SAT mining bring-up

Treat SAT mining as an operator workflow, not a decorative toggle. Normal sequence:
  1. create or import the singleton @wallet:mining wallet
  2. confirm readiness
  3. fund miner capital
  4. set commit
  5. start mining
  6. watch runtime, actions, and recovery
Use: 
fased mining wallets
fased mining readiness --wallet mining
fased mining deposit-capital --sol 1
fased mining set-commit --sol 0.75
fased mining start --wallet mining
fased mining status
Important distinctions:
  • attached wallet is not the same as funded capital
  • funded capital is not the same as active commit
  • enabled is not the same as participating in a live cycle

​
10. Recovery priorities

If behavior drifts, recover in this order:
  1. host access
  2. runtime health
  3. wallet and signer health
  4. Fased Network state
  5. mining or reviewed automation
Useful commands: 
fased doctor --fix
fased wallet signer doctor --json
fased federation status --json
fased mining status --json
Service checks: 
systemctl --user status fased-gateway
systemctl --user restart fased-gateway
Hosted fallback: 
sudo systemctl status fased-gateway
sudo systemctl restart fased-gateway

​
11. First-week operator rules

During the first week, change only one major layer at a time:
  • onboarding or profile
  • private access
  • wallet mode
  • Fased Network
  • plugins
  • mining
That is how you keep failures attributable and recovery sane.