Wallet boundary
Assets outside a vault are not automatically managed by Jethos. Users remain responsible for keys, signatures and approvals.
Security
Controls reduce risk. They do not remove it.
Jethos combines explicit authorization, modular integrations, monitoring and pause mechanisms while documenting the trust and failure assumptions that remain.
Contract boundary
Deposited assets follow deployed code, authorized modules and administrative permissions.
Protocol boundary
Underlying integrations add smart-contract, market, oracle, governance and liquidity risk.
Security is shared across boundaries.
Boundary
User
Jethos
Underlying systems
Responsibility
Protect keys, inspect signatures, review/revoke approvals.
Constrain routes, monitor state, disclose powers and incidents.
Protocol code, governance, markets, assets and oracles must continue functioning.
Control layers
- Deposit and withdrawal toggles.
- Global and module pause capabilities.
- Protocol registration and activation.
- Registry-based market allowlists.
- Position observation through LensAdapters.
- Operational monitoring and transaction records.
Assurance status
Private PoC—not a completed audit claim.
Contracts have local tests and a recorded verified deployment. This site does not represent the complete Jethos system as independently audited or free of vulnerabilities.
Residual threats
Self-custody changes responsibility; it does not create immunity.
Keys and signatures
Compromised keys, deceptive signatures or malicious wallet software can authorize movements that Jethos cannot reverse.
Allowances and assets
Previous approvals and token-issuer controls can affect wallet assets independently of a new Jethos deposit.
Code and dependencies
Bugs, upgrades, admins, oracles, bridges and underlying protocols may affect deposited capital and exit conditions.
Underlying protocol resources
Audits of Aave, Euler or Morpho cover their respective systems, not Jethos integration logic as a whole.