One explicit configuration
arbitrum-usdc-poc-1
The browser console, public record and diagnostics must agree before the release gate passes.
Trust Center · evidence before assurance
Trust should be decomposed into sources, powers and failure assumptions. This page gathers the current PoC evidence without turning it into an audit claim.
arbitrum-usdc-poc-1
The browser console, public record and diagnostics must agree before the release gate passes.
Recorded base asset; issuer controls and asset risk still apply.
Consumer deposits and withdrawals pass through the configured core.
4 recorded integrations; registration does not imply allocation.
Control boundaries
Jethos cannot move assets you have not deposited or separately approved. Key compromise and existing allowances remain outside that promise.
Deposited capital follows code, configured modules and administrative powers. Visibility reduces hidden assumptions; it does not remove them.
Lens and registry reads expose integrations and positions. Underlying code, governance, markets, assets and oracles remain dependencies.
Status language
Live means timestamped onchain data—not safe. Implemented means present in code—not audited. PoC means controlled validation—not public readiness.
Read from chain with a timestamp.
Present in the repository.
Private validation deployment.
Direction, not current functionality.
Long-term possibility.
Explanation, not account data.
Open assurance gates
No completed whole-system audit is claimed.
Repeat funded end-to-end flows against a controlled fork.
Finalize monitoring, incident response and public release controls.
Validate jurisdictional, product, disclosure and tax requirements.
Reproduce the evidence
npm run ready validates the site, editorial contract, deployment and protocol registry. It does not sign or broadcast transactions.