Deployment and operator setup.

Services and responsibilities

The web service serves the site and account API, stores authenticated settings, runs the scheduled Favorites scanner and processes the testnet trading queue. The private engine service produces agent research. Supabase stores accounts, analyses, Favorites, settings and strategy state. The on-chain vault holds deposit balances and bounded agent permissions.

Run the web service continuously while scheduled scans or automatic exits are expected. A page visit is not the trigger for either worker.

1. Apply the database changes

1. Use the intended FETCHN Supabase project and confirm its identity before changing schema.
2. Apply the existing account, trading, Favorites and multi-position migrations in repository order. Do not rerun a migration that is already applied.
3. Before this release’s web deployment, apply 20261020150000_testnet_portfolio_risk.sql and 20261020160000_testnet_paper_strategies.sql in that order. The first is required for new agent entries; the second stores simulated decisions.
4. Keep service-role access on the server only. The client uses authenticated API routes.

2. Configure web and engine

The web service needs its existing Supabase public and server credentials, AGENTS_API_URL for the private engine, the matching AGENTS_API_KEY if configured, and the existing testnet agent settings. Set RH_TESTNET_AGENT_ENABLED=true and a dedicated RH_TESTNET_AGENT_PRIVATE_KEY on web only. The optional RH_TESTNET_RPC_URL must resolve to chain 46630.

Do not place the operator key in a NEXT_PUBLIC_ variable or expose it to the browser. The engine requires its own configured research providers. An absent engine URL or disabled operator leaves scheduled Favorites research inactive.

3. Fund the operator and check the venue

Send test ETH to the public address derived from the operator key so agent transactions can pay gas. User wallets need their own test ETH for contract deployment, approvals, deposits and withdrawals. Check that the Stock Token/USDG testnet pools have executable liquidity; a faucet claim alone does not create a trading route.

4. Release and observe

1. Deploy the engine and web services after the migration.
2. Confirm sign-in, wallet linking, balance reads and analysis availability.
3. In Terminal, star one Favorite Token, save an enabled schedule and authorize Automated Analysis & Trading.
4. Watch web logs for scheduled scanner and testnet agent messages; use the Terminal status and explorer links to inspect submitted transactions.
5. Keep mainnet order execution disabled until its own review and deployment path is ready.

For contract generation and the deeper operational flow, see the repository’s docs/TESTNET_TRADING_SETUP.md. Never paste private keys or account service credentials into support screenshots.