Control, choice and transparency.

Jethos does not automatically invest or move unrelated wallet assets. Movement requires a valid wallet signature or a token approval you have granted. You remain responsible for keys, signatures and reviewing/revoking approvals.

No system can make that absolute promise. It means Jethos cannot move assets you have not deposited or separately approved. Anyone who controls your keys, a contract with an existing allowance, token-issuer controls or a vulnerability may still affect assets. Self-custody replaces intermediary custody with explicit ownership and responsibility.

The selected base asset moves into the vault system and you receive shares representing the position. From that point, the capital follows deployed contract logic, configured integrations and documented administrative controls.

User ownership is represented through shares and withdrawal rights under the contract rules. Strategy execution and administrative functions use roles described in the technical documentation. The PoC is curated and not currently governed as a permissionless public system.

No. “Self-custodial financial home” describes the intended user experience. Jethos is currently DeFi software and a private proof of concept, not a regulated bank or insured deposit provider.

No. Smart contracts, protocols, assets, oracles, markets and operational systems can fail. Jethos aims to make constraints and evidence understandable, not to remove risk.

Not necessarily. The PoC currently uses a synchronous withdrawal path, but liquidity, reserve rules, pauses and protocol conditions can cause a transaction to fail or require unwinding. Future products may explicitly show immediate, unwinding or pending states.

The site does not claim a completed independent audit of the whole Jethos system. Underlying protocol audits cover their respective systems, not every Jethos integration and control.

USDC is an ERC-20 token. LiquidityManager needs an allowance before it can transfer the exact amount selected for deposit. The App requests an exact approval rather than an unlimited one.

Yes. The PoC console includes a revoke action that sets the LiquidityManager USDC allowance to zero. Revoking does not withdraw an existing vault position.

A private Arbitrum USDC proof-of-concept deployment and its recorded Aave, Euler and Morpho integrations. The broader wallet, multi-profile, multi-asset and financial-services experience remains progressive development or vision.

Jethos aims to combine a familiar financial interface with self-custodial ownership, understandable vault choices and verifiable capital routes. The current PoC validates only a narrow foundation of that direction.

The intended product is for people who want a simpler way to hold, invest and understand digital assets without hiding the technical and financial risks. The current deployment is for controlled technical validation, not general consumers.

A single native stablecoin and an established EVM network reduce the first validation scope. USDC still has issuer and depeg risk; Arbitrum still has smart-contract, sequencer and network dependencies.

The target methodology considers expected return together with liquidity, maturity, utilization, concentration and risk limits. Final numeric Conservative policy limits remain decisions to publish; registration alone does not imply allocation.

The PoC contracts expose configured deposit and withdrawal fee reads. The console shows the current result when available. Future management, performance or service fees require explicit product policy and disclosure.

For the current PoC it means a native-USDC, supply-only validation scope. Reserve, concentration, utilization, oracle and stress thresholds are not presented as final until policy decisions are approved.

On-chain contracts do not depend on this specific webpage to exist, but direct interaction requires correct addresses, ABI knowledge and careful transaction construction. The deployment record and developer documentation are intended to support verification; recovery procedures remain an assurance gate.

The code contains parameter, emergency and upgrade-related components, but the current public evidence pack does not yet publish a complete role map, owner addresses, multisig or timelock evidence. This remains explicitly open in the Trust Center.

No such capability is live. Any future payments, cards, credit or regulated asset service would require suitable technical and regulated partners, legal analysis and precise disclosures. The phrase financial home describes the intended experience, not a banking licence.