Trust & Safety

Carpe Diem is deployed and live on Base mainnet, and is currently in an experimental beta ahead of its public launch. Treat it as such: use small limits, and do not connect critical keys. What is testnet, mainnet, and beta is stated explicitly rather than blurred.

Carpe Diem is a project of Lumen Labs, a Swiss non-profit association (art. 60 ff. of the Swiss Civil Code) based in Geneva. The association is the legal entity responsible for the protocol — not an anonymous team. Detailed team and governance communication will follow.

We identify the responsible legal entity and jurisdiction. Internal documents (e.g. the association's statutes) are not published, which is standard practice.

Carpe Diem does not hold your funds. You keep your own wallet. When you buy credits, you purchase a service (AI inference): the escrow records non-refundable credits, it is not a deposit account managed on your behalf. There is no custody of user money — which keeps the protocol outside heavier financial-intermediary regimes.

• You control your wallet and your spending.
• The escrow contract holds purchased credits on-chain.
• Providers earn DIEM, withdrawable to their own wallet.
• Venice serves the inference; Phala secures the keys.

All official addresses in one place — beware of look-alikes. The escrow source is verified and reproducible from the repository: Sourcify reports a full bytecode match against the deployed contract.

The escrow is upgradeable (UUPS) so security fixes can ship without migrating user balances. Upgrade and admin rights are being migrated from the deploying account to a Gnosis Safe multisig governed by a Timelock with a public delay. Once in place, no single party can change the contracts instantly — every change passes through a multi-signature approval and an announced, on-chain waiting period.

On-chain roles (admin, operator, guardian) are readable directly from the contract on BaseScan.

Provider keys are sealed inside a hardware Trusted Execution Environment (Intel TDX on Phala Cloud). They are never written to disk, never logged, and cannot be extracted from the enclave — not by the host, not by the Carpe Diem team. The running enclave is cryptographically attested against a published image digest, so anyone can verify what code is actually running.

To date, the protocol has undergone an internal security review (AudiBot, Lumen Labs — May 2026). An independent external audit is planned, funded by accumulated protocol revenue. There is no external audit report yet — so we do not present the protocol as “externally audited.” The public report (scope, commit, findings, remediations) will be published when that audit is complete.

• Use an inference-only Venice key — never an admin key.
• Scope it with a consumption limit and an expiry; this stays entirely under your control.
• Choose RAM-only (re-provision after reboot) or encrypted-at-rest persistence.
• Revoke anytime — from the provider page (removed from the TEE immediately) or from Venice.

Found a security issue? We welcome responsible disclosure. Please report privately first and give us reasonable time to remediate. A public bug-bounty program is planned.