Understand an operation and any continuing authority
AI output and DeFi operations can be wrong, incomplete or unsafe. You can lose some or all of the assets involved. A readable proposal, simulation, successful signature, passing rule check or displayed balance does not guarantee a safe outcome or a profit.
Manual approval and Auto authorization have different effects. In Manual, you review the operation before signing. With Auto, you grant authority for permitted operations to be signed and submitted without a new owner approval each time. Read the Wallet Notice and Auto Notice before approving an operation or enabling continuing authority.
This disclosure explains material risks. It does not remove ODEI's obligations, excuse a failure for which ODEI is legally responsible or waive your mandatory consumer, data-protection or other rights.
AI and information risks
Models can misunderstand instructions, invent facts, select an unsuitable asset or network, and rely on stale prices or incomplete protocol information. External content can contain deceptive instructions. An assistant’s confidence is not evidence of accuracy.
Check the recipient, contract, asset, network, amount, permissions and fees when reviewing a Manual operation. Before enabling Auto, understand which requests may be executed and the conditions that apply. An authorized connection can generate an incorrect or unwanted proposal that still satisfies the configured rules. Permission to act is not proof that an action is economically sensible.
The Auto execution feature applies authorization rules; it does not itself choose an investment strategy or provide a personalised investment recommendation. Information from other agents, providers or product features must be assessed according to what it actually contains. No proposal, rule check or execution result is a promise of suitability, profitability or future performance.
Auto permissions and automated execution
Auto uses a server-managed signing key that is separate from your wallet's owner key. Within the granted permission, ODEI's automation can sign and submit transactions when an eligible proposal arrives, including a proposal from an authorized connection. A separate approval prompt may not appear before the assets are exchanged, fees are charged or another permitted effect occurs.
Smart-contract permissions restrict what the account accepts, while other checks and limits are enforced by ODEI's server software. Not every displayed limit is an independent on-chain restriction. A defect, incorrect configuration, compromised credential or failure in server-side enforcement may permit activity that an operational limit was intended to prevent. The actual smart-contract permission remains the separate boundary of what its key can authorize, subject to defects or changes in that contract and its dependencies.
Limits on an individual transaction are not necessarily limits on cumulative spending or loss. Several permitted operations, repeated fees, changing prices, allowance renewals or separate protocol actions can have a larger combined effect. A spending limit also does not cap market losses on assets already acquired or deposited. Automation can continue while you are not watching the account.
Protect access to your ODEI account, connected applications and owner key. Monitor active permissions and completed operations. If you suspect misuse, use the available stop controls, review and revoke the relevant authority through the wallet, and contact ai@odei.ai. Neither a support request nor disconnecting one application should be treated as confirmation that every signing permission has been revoked.
Owner keys, server keys and recovery
The wallet's non-custodial design preserves owner authority. Auto nevertheless introduces a server-managed key with limited transaction-signing authority. Retaining the owner key does not remove risks arising from that delegated authority, the signing infrastructure, contract permissions or server-side controls.
A compromised or incorrectly used session key or signing service could authorize harmful operations within its effective permissions. A compromise of the owner key can expose broader account powers. Recovery material, wallet passwords, devices, browser profiles, hosted software and software updates all affect security.
In the normal Manual wallet flow, owner signing occurs on your device and the hosted service stores a password-encrypted backup. Losing required recovery material or the password can prevent recovery; encrypted backup availability is not a guarantee of successful access or recovery. Auto's separate signing key is not a replacement for the owner key or a general recovery mechanism.
Security controls reduce particular risks but do not make the service immune to compromise. This disclosure does not claim that the complete ODEI wallet or Auto implementation has passed an independent security audit, obtained a security certification or received regulatory approval.
Signatures and continuing permissions
A signature may authorize an immediate transaction, several calls, an order valid for a period, or a permission that continues after the review. Token approvals and smart-account permissions can allow a contract to act later. An Auto permission may allow multiple later signatures. Previously signed payloads and on-chain permissions can remain effective after you disconnect an application or switch settings.
Stopping ODEI's automation, revoking a signing permission, removing a token allowance and cancelling a transaction or protocol order are different actions. A required on-chain revocation can itself depend on network availability, fees and confirmation. It may race with an operation already signed or submitted. Revocation does not undo earlier execution or automatically withdraw assets already deposited into another protocol.
Signed data may be delivered or redelivered under its signed terms. A signed transaction cannot always be recalled, and cancellation can lose a race with settlement. Signing and signature release are handled within ODEI's wallet and execution services. The external Connector's proposal, action and status metadata can describe a workflow with financial effects even though the Connector does not receive the transaction signature.
Protocol, market and network risks
- Contracts and governance: bugs, compromised administrators, upgrades, oracle failures or governance changes can restrict access or cause loss.
- Prices and liquidity: volatility, slippage, transaction ordering, MEV and insufficient liquidity can change the outcome or prevent an exit.
- Lending and collateral: price movements, interest and protocol rules can cause liquidation, penalties or bad debt.
- Bridges and networks: bridge failures, network congestion, reorganizations, censorship or outages can delay or invalidate an operation.
- Stablecoins and tokens: a token may lose its peg, become illiquid, be frozen by its issuer or offer fewer redemption rights than expected.
- Staking and withdrawals: lockups, exit queues, slashing and changing protocol conditions can delay withdrawal or reduce assets.
- Costs: network fees can be charged for failed transactions. Estimates may change before execution or settlement.
Sending assets to a protocol or escrow subjects them to that system’s rules. Non-custodial signing does not mean those assets remain unconditionally withdrawable. An escrow dispute mechanism may give an arbiter powers over the deposited funds.
External systems and public records
RPC services, AI providers, relayers, signing infrastructure and protocol services may be unavailable or return inconsistent information. A transaction may be rejected, delayed, remain pending or be affected by a chain reorganization. ODEI status may lag behind the network. A successful submission acknowledgement is not final settlement, and a missing acknowledgement does not establish that nothing was submitted.
Public blockchain activity can be linked to your wallet or account and is generally irreversible and publicly observable. ODEI cannot erase public-chain records or guarantee deletion from independent services.
Legal, tax and availability risks
Rules vary by location, asset and activity and can change. DeFi is not a general exemption from financial-services, sanctions, consumer, privacy or tax law. Technical access does not establish that a service is lawfully available to you. See Service Availability & Restrictions.
No deposit insurance, investor compensation or similar protection should be assumed merely because you use ODEI or an underlying protocol. Any protection depends on the specific service and applicable law. Keep records needed to determine your reporting and tax obligations.
Reporting problems and preserving your rights
Report suspected unauthorized or incorrect activity to ai@odei.ai with the relevant account, action or transaction reference and the time you observed the problem. Do not send private keys, recovery phrases or wallet passwords. You can ask us to review an authorization or execution record; investigation or review does not guarantee reversal of a blockchain outcome.
Your responsibilities for choosing permissions and protecting your credentials do not remove duties that applicable law places on ODEI. A transaction's technical finality does not extinguish a valid contractual, consumer or compensation claim against a responsible party. See the Terms of Service, Billing and Refunds Notice and Privacy Notice.