SudoStake playbook
TL;DR
- SudoStake has two roles: borrowers (vault owners) and lenders.
- Borrowers open collateralized requests; lenders fund requests from Discover.
- After funding, the owner repays, or claims are processed after expiry.
Product flow in one view
| Stage | Borrower action | Lender action | Where in app |
|---|---|---|---|
| 2. Prepare | Create vault, manage NEAR collateral | Review request terms | Dashboard, vault page, Discover |
| 3. Open/Fund | Open request | Accept request | Vault page |
| 4. Active loan | Monitor countdown and repay status | Track funded position | Vault page, dashboard positions |
| 5. Resolve | Repay loan or start liquidation/claims after expiry | Process claimable collateral after expiry | Vault page |
Borrower flow
- Connect wallet from the landing page or navigation.
- Open
/dashboardand create a vault. - Add NEAR and delegate if needed for collateral capacity.
- Open a request from the vault page.
- While pending, you can cancel the request.
- After funding, monitor the loan timer on the vault page.
- Repay while liquidation has not started.
- If expired, start claim processing from the vault page.
Guides:
Lender flow
- Open
/discoverand filter/search open requests. - Open a vault detail page to review terms.
- Register storage if prompted.
- Accept the request (wallet signs an
ft_transfer_call). - Track funded vaults in Dashboard -> Positions.
- After expiry, process claims from the vault page when claimable.
Guides:
Important behavior to know
- Request creation is currently USDC-only in the request dialog.
- UI actions are role-based (
owner,activeLender,potentialLender,guest). - State-changing actions always require wallet confirmation.
- If indexing fails after a transaction, the app shows a blocking retry modal.
If something looks wrong
- Confirm the connected account in the nav menu.
- Confirm the active network label in the header.
- Refresh or retry indexing after recent transactions.
- Use the transaction hash from wallet/toast when escalating.