SudoStake playbook

TL;DR

SudoStake has two operators: vault owners who borrow against staked NEAR and lenders who supply USDC liquidity.
Both roles begin the same way—connect a wallet, choose a network, and register the tokens you intend to move.
Owners mint a vault, build collateral, publish a request, and repay on schedule; lenders review requests, fund them, and monitor repayments or liquidations.
The app mirrors this loop. Follow the checklists below to move through SudoStake without surprises.

Choose a network — Use the header toggle to pick testnet or mainnet. Every subsequent action, including minting a vault, targets that factory.
Connect your wallet — Follow the sign-in flow. Owners and lenders share the same flow, so switching roles is seamless.
Register tokens once — When you first interact with USDC (or another NEP‑141 token), register storage for both your wallet and, later, your vault. Refer to Token registration for the exact prompts.

Mint a vault — From the dashboard, open the create dialog and approve the mint_vault transaction. Follow Mint a vault for the exact prompts.
Build collateral — Deposit NEAR and delegate stake so the contract can prove your health buffer. Deposit and delegate dialogs live on the vault page.
Publish a liquidity request — Choose token, amount, target buffer, interest, and duration. The UI handles unit conversions. See Open a liquidity request.
Monitor lender commitments — Lenders fund directly; accepted offers appear in the dashboard and on the vault page.
Run daily operations — Watch available balance, undelegate if you need to free collateral, and trigger indexing when prompted so data stays fresh.
Repay before expiry — Use Repay a loan before the deadline. Once principal and interest clear, the vault returns to Idle and your lender is released.

Review active requests — The Discover page lists collateral ratios, annualised interest, and duration. Drill into the vault for history and health.
Fund from the vault view — Follow Fund a liquidity request. Behind the scenes we use ft_transfer_call with your chosen amount and attach the expected metadata.
Track funded positions — Use the dashboard’s Positions tab or Lender positions to monitor repayments and liquidation progress in real time.
Stay responsive after expiry — Repayments close positions automatically. If a term expires, watch liquidation updates and be ready to process claims.

Indexing — Fresh data keeps both sides aligned. After on-chain changes, the UI may ask you to re-run indexing. Follow Indexing and consistency for troubleshooting.
Viewer roles — Buttons shift based on whether you’re the owner, active lender, or observer. See Viewer roles if something looks unavailable.
Balances & tokens — Tokens and balances explains metadata, storage deposits, and helper utilities that keep wallet and vault balances in sync.

Wallet rejected or stalled: Retry from the UI. Nothing commits on-chain until the wallet signs, so you can safely try again.
Missing vault or position: Click Retry indexing or refresh—Firestore may be a few seconds behind the blockchain.
Unexpected permissions: Confirm you picked the right network and wallet. Roles are evaluated per vault.
Need a hand: Share the transaction hash from the toast, mention the doc you followed, and drop both in Telegram or GitHub.

With this playbook nearby, teams can switch between borrowing and lending confidently. Each linked guide dives deeper when you need more detail.