Safety
Security Architecture
Implemented and required controls for transaction and Vault safety.
Core controls
- PDA validation. Vault, authority, fee, custody, and user-position accounts use deterministic program-derived addresses where implemented.
- Supported mint validation. USDC flows must validate the configured mint; SOL flows must distinguish native SOL and WSOL implementation details.
- Strategy program validation. Configured strategy executable accounts and owned accounts are checked by program logic where implemented.
- Checked arithmetic. Share, asset, fee, and strategy calculations use checked arithmetic and integer units.
- Transaction simulation. Server-prepared Lucida transactions are simulated before wallet signature where the flow supports it, and local indexing is triggered from confirmed Solana transactions.
- Atomic execution. A Solana transaction either commits all program state changes or fails.
- Separate fee accounts. The program separates fee vault paths from user ownership and Vault accounting.
- Governance controls. Configured governance authority gates strategy setup and emergency receipt transfer paths.
- Monitoring. Production use requires monitoring and reconciliation across on-chain state, strategy state, and indexed data.
Operational controls
| Control | How to verify |
|---|---|
| Deposit caps | No launch deposit cap is configured unless later official Lucida disclosures state otherwise. |
| Deposit and withdrawal pause | No dedicated protocol-level pause action is available for deposits or withdrawals in the current Lucida Vault program. |
| Timelock | Mainnet launch governance uses a single configured authority with no timelock. |
| Monitoring | Use official Lucida status, on-chain state, and transaction confirmation rather than unverified third-party displays. |