Offchain Systems
Lucent's offchain systems make the Soroban protocol usable, observable, and maintainable.
Frontend
The frontend should support Freighter Connect and Stellar Wallets Kit.
The transaction lifecycle should expose simulation before signing:
- Build the transaction.
- Simulate and inspect footprint/result.
- Assemble.
- Ask the wallet to sign.
- Submit.
- Poll confirmation.
User flows should include trustline onboarding, XLM reserve checks, and position simulation for resulting collateral ratio, redemption queue rank, distance to MCR, debt changes, price changes, and rate changes.
Public API and SDK
The TypeScript SDK should wrap contract calls, simulation, errors, and indexed reads. APIs are versioned so integrators can safely depend on them.
Indexer
The indexer builds durable views of:
- Troves and owner portfolios.
- Stability Pool positions.
- Liquidations and redemptions.
- Parameter changes.
- Revenue and interest routing.
- Oracle state.
- Contract versions.
Contract events are treated as a versioned public API. Event replay tests must prove the indexer can reconstruct user and protocol state.
Bots
Lucent uses several offchain agents:
| Bot | Responsibility |
|---|---|
| Redemption bot | Monitors starUSD peg, redemption fee, sorted Troves, expected XLM output, and slippage. |
| Liquidation bot | Monitors oracle price, ICR/TCR, Stability Pool depth, liquidation profitability, and reserves. |
| Interest-rate delegate bot | Manages approved individual or batch rate strategies. |
| TTL keeper | Extends or restores contract code, contract instances, and important persistent storage. |
| JIT liquidation bot | Sources missing starUSD at liquidation time and executes profitable liquidation routes. |
Monitoring
Internal monitoring tracks RPC health, indexer lag, bot liveness, oracle freshness, TTL health, failed transactions, admin activity, redemptions, liquidations, risk thresholds, and upgrade proposals.
External monitoring should track exploit patterns, multisig activity, oracle anomalies, treasury risk, and incident response triggers.
Release Process
Frontend, indexer, SDKs, and bots ship through GitHub CI. CI should run tests and staged releases before production deployment.