Explanations > Operations
Operations
Explain operational responsibilities for Quovra.
Operations
Quovra operations focus on app availability, proof submission, and safe secret handling.
Responsibilities
| Area | Responsibility |
|---|---|
| Frontend | Serve markets, receipts, docs, and wallet actions |
| RPC | Read market state and send transactions |
| Keeper | Submit valid TxLINE proofs after fixtures finish |
| Faucet | Mint devnet-only test USDC |
| Secrets | Protect faucet authority and TxLINE credentials |
Health checks
https://quovra.xyzhttps://quovra.xyz/marketshttps://quovra.xyz/activityhttps://quovra.xyz/docs- Solana devnet RPC
- Keeper dry-run output
Incident response
- Identify the failing surface.
- Stop live keeper execution if settlement submissions are failing unexpectedly.
- Preserve logs and transaction signatures.
- Reproduce with dry-run commands.
- Patch configuration or code.
- Re-run tests and build.
- Resume keeper execution.
Backups
On-chain state lives on Solana devnet. Repository state and deployment config should be backed up through GitHub and host environment exports.
Do not back up secrets into the repository.
Related pages
Search keywords
operations, monitoring, incidents, backups, keeper
Last updated: [YYYY-MM-DD]