World Agent
Manage World through an agent without signing every transaction
World Agent allows you to authorize an automated agent to manage your World account within rules you approve.
After setup, you can communicate with the agent through Telegram or another supported interface. The agent can approve tokens, deposit assets, trade, lend, borrow, repay obligations, and return assets to your wallet without asking you to sign every routine transaction.
You retain ultimate control through your owner wallet.
The agent cannot:
Increase its own authority
Change ownership
Change recovery settings
Add another signer
Add a new protocol
Add a withdrawal address
Send assets to an arbitrary wallet
Bypass the policy you approved
World Agent does not eliminate financial risk.
Trading, leverage, lending, borrowing, smart contracts, oracles, counterparties, liquidity, networks, wallet infrastructure, signer providers, and agent software can fail.
You may lose some or all of the assets used by the agent.
How World Agent works
World Agent separates asset ownership from day-to-day execution.
Owner wallet
Owns the assets and controls agent authorization
Agent signer
Signs permitted actions without exposing the owner key
Wallet policy
Restricts contracts, functions, assets, destinations, and spending
World policy
Restricts portfolio risk, leverage, borrowing, and execution
Agent runtime
Interprets instructions, monitors the account, and proposes actions
Telegram
Lets you communicate with the agent from your phone
World contracts
Execute and enforce onchain actions
The owner wallet remains the highest authority.
The agent signer is replaceable and may not:
Change the owner
Change recovery methods
Add another signer
Expand its policy
Withdraw to an unapproved address
Use an unapproved protocol
Bypass World’s onchain policy
What “no routine signatures” means
After activation, the agent may perform ordinary actions that are inside the policy without asking the owner to sign each transaction.
These actions may include:
Token approvals to approved World contracts
Deposits into World
Spot trading
Perpetual trading
Lending
Borrowing
Repayment
Refinancing
Order placement
Order cancellation
Portfolio rebalancing
Risk reduction
Withdrawal from World back to the predetermined owner wallet
Transaction-fee payment or sponsorship
A new owner authorization is still required when the agent’s authority is expanded.
Examples of policy expansions include:
Increasing the capital limit
Adding an asset
Adding a market
Adding a protocol
Enabling borrowing
Increasing the borrowing limit
Lowering the margin requirement
Adding a withdrawal destination
Adding another wallet
Replacing the agent signer
Extending an expired policy
Changing ownership
Changing recovery settings
Routine execution and expansion of authority are deliberately separate.
Quick start
1. Open World on desktop
Open the official World application and select:
Set up your World agent
Use the official World domain.
Do not follow an authorization link from an unknown bot, account, message, advertisement, or website.
2. Connect your wallet
Connect the wallet that should own the World account.
When the wallet supports portable delegation:
The wallet address remains the same
Assets remain in the wallet until the agent uses them
No special World-only wallet needs to be funded
No assets move during setup
The owner wallet remains in control
When the wallet is not compatible, World will explain the available alternatives before creating any wallet, account, or permission.
3. Set the capital limit
Choose the maximum value of wallet assets the agent may place under management.
This limit is separate from gross market exposure.
Borrowing and derivatives can create exposure greater than the amount transferred from the wallet.
The World policy therefore includes additional limits covering:
Leverage
Gross exposure
Net exposure
Borrowing
Margin
Execution cost
Daily loss
Turnover
4. Connect Telegram
Scan the displayed QR code and tap Start in Telegram.
The pairing request is temporary and can be used only once.
It does not contain a private key or signer credential.
5. Review the policy
World displays:
The owner wallet
The agent signer
The maximum assets the agent may use
The permitted contracts
The permitted assets
The permitted markets
The withdrawal destination
The most important portfolio limits
Whether borrowing is enabled
Whether the agent may open new positions
The policy duration
You may open the exact policy before signing.
6. Activate the agent
Approve the setup through your owner wallet.
This authorization creates the agent’s limited authority.
It does not deposit funds or open a position by itself.
7. Continue in Telegram
After activation is confirmed, World sends a message to the connected Telegram account.
You may then close the desktop page and manage the agent from your phone.
Wallet and account architecture
Owner wallet
The owner wallet is the ultimate authority.
It controls:
Agent creation
Policy expansion
Policy replacement
Agent revocation
Ownership
Recovery
Additional wallets
Additional protocols
Unrestricted withdrawals
The owner key is not provided to:
The agent
Telegram
The language model
The World front end
The agent runtime
The relayer
The signer provider’s application interface
The owner wallet is required only for actions that create, replace, expand, or revoke authority.
Agent signer
The agent signer is a separate cryptographic identity secured by:
[SIGNER PROVIDER]
The implementation may use:
A delegated user
An additional signer
An MPC signing share
A restricted authorization credential
Another provider-specific signing mechanism
The agent signer:
Does not replace the owner wallet
Does not receive the owner private key
Does not need to own the user’s assets
Cannot modify its own policy
Can be paused
Can be revoked
Can be rotated
Is bound to specific wallet permissions
Is bound to specific World permissions
The exact signer address appears in:
The setup review
Agent Settings
The exact policy
Onchain authorization records
Online agent credential
Autonomous operation requires an online credential capable of requesting signatures from the signer provider.
This credential is not the owner key.
It may not be the Ethereum private key.
It is still security-sensitive.
A compromised runtime credential may be able to request actions within the provider policy.
For this reason, World uses multiple policy layers.
The production implementation must document:
Which entity operates the agent runtime
Where the credential is stored
How the credential is encrypted
How the credential is rotated
How the credential is revoked
Which provider-side policies apply
Whether the provider can export the signer
Whether the provider can recover the signer
Which audit logs are available
Which personnel may access runtime systems
Which incident-response process applies
Telegram
Telegram is an instruction and notification interface.
Telegram does not:
Hold the owner key
Hold the agent’s Ethereum private key
Define the onchain policy
Expand the policy
Become the withdrawal destination
Control ownership
Control recovery
Someone who compromises the user’s Telegram account may issue instructions within the existing policy.
Users should enable Telegram’s own account-security protections and regularly review active Telegram sessions.
Existing-wallet compatibility
World Agent is designed to work through portable wallet-level delegation rather than a World-specific asset wallet.
EIP-7702-compatible EOAs
An EIP-7702-compatible EOA may gain smart-account capabilities while preserving its address.
This may allow the wallet to support:
Batched execution
Sponsored gas
Restricted subkeys
Token approval followed by deposit
Ongoing agent permissions
Policy-based execution
EIP-7702 alone does not provide a complete safe permission system.
The delegated account implementation must securely enforce:
Replay protection
Allowed contracts
Allowed functions
Allowed calldata
Native-token value
Gas limits
Nonces
Expiration
Signer authority
Withdrawal destinations
A poorly implemented delegation may expose the EOA to severe loss.
World supports only reviewed implementations listed under:
[SUPPORTED WALLETS]
Smart accounts
Supported smart accounts may authorize the agent through:
A wallet module
A wallet-native delegation system
A restricted signer
An account permission system
The existing wallet remains the owner.
The wallet’s normal ownership, recovery, and multisig rules continue to apply.
Multisigs
When a multisig owns the account, agent activation is a multisig transaction.
The organization’s existing threshold must approve the initial mandate.
After activation, routine agent actions may operate autonomously within the approved policy.
Unsupported EOAs
An unsupported EOA cannot safely provide ongoing autonomous access without:
An account upgrade
A wallet migration
A connected smart account
A separate portable wallet
Approval-per-action mode
World will not claim a no-signature experience for an unsupported wallet.
The user may:
Use another supported wallet
Create a portable smart account owned by the existing wallet
Wait until the wallet supports the required delegation
Use approval-per-action mode
World will never ask the user to paste a seed phrase or raw private key into the standard World interface.
How agent execution works
A normal agent action follows this sequence:
The user sends an instruction
The agent interprets the requested objective
The agent creates a typed World intent
Deterministic software constructs the exact transaction or transaction bundle
The action is simulated
The wallet-provider policy is evaluated
World’s policy is evaluated
The restricted signer authorizes the action
A relayer or transaction sender submits the action
World produces a structured receipt
The language model should not have unrestricted access to arbitrary transaction signing.
The model proposes structured intents.
Example:
The deterministic execution layer decides which exact orders and contract calls satisfy that intent.
Policy layers
World Agent uses two complementary policy layers.
Wallet-level policy
The wallet or signer-provider policy restricts what the agent signer may authorize.
It may restrict:
Chain ID
Target contracts
Function selectors
Decoded function arguments
Token addresses
Token amounts
Native-token value
Withdrawal destinations
Per-action limits
Time windows
Total capital
Expiration
Required co-approvals
Signer identity
Gas
Relayer
Allowed protocols
World-level policy
The World policy restricts the economic result of the action.
It may restrict:
Markets
Assets
Spot trading
Perpetual trading
Lending
Borrowing
Repayment
Refinancing
Gross exposure
Net exposure by asset
Available-margin ratio
Risk consumption
Leverage
Daily realized loss
Drawdown
Turnover
Order size
Bundle size
Slippage
Execution cost
Borrowing principal
Borrowing rate
Loan maturity
Counterparty concentration
Policy duration
Emergency behavior
Risk-increasing actions
Risk-reducing actions
When the wallet-level policy and World-level policy differ, the more restrictive result applies.
A transaction must pass every applicable policy check.
ATLAS-aware restrictions
World’s universal margin system evaluates:
Collateral
Lending
Borrowing
Spot exposure
Perpetual exposure
Hedging
Portfolio-level risk
World Agent policies use the projected portfolio state when evaluating an action.
The agent may be permitted to trade ETH but still be rejected when the proposed action would:
Reduce available margin below the policy floor
Increase gross exposure above the policy cap
Create excessive net ETH exposure
Borrow above the principal limit
Borrow above the interest-rate limit
Exceed an execution-cost limit
Exceed a daily turnover limit
Use an unapproved market
Use an unapproved asset
Violate a loan-maturity requirement
Increase portfolio risk beyond the approved level
A successful pre-execution check is not a guarantee that the account will remain above the threshold.
Markets, liquidity, collateral values, funding rates, borrowing conditions, and oracle prices may change after execution.
Default policy
The default policy is designed to let the agent manage World without receiving unrestricted wallet authority.
The exact live defaults are displayed before authorization.
Wallet restrictions
Chain: [SUPPORTED CHAIN IDS]
Approved contracts: [WORLD CONTRACT ALLOWLIST]
Maximum wallet assets under agent management: User-selected
Withdrawal destinations: Owner wallet only
Arbitrary transfers: Prohibited
Ownership changes: Prohibited
Recovery changes: Prohibited
New signer creation: Prohibited
Policy expansion: Prohibited
New protocol access: Prohibited
Unlimited token approvals: Prohibited by default
World restrictions
Markets: [DEFAULT MARKET ALLOWLIST]
Minimum available margin: [DEFAULT VALUE]
Maximum gross exposure: [DEFAULT VALUE]
Maximum net exposure per asset: [DEFAULT VALUES]
Maximum borrowed principal: [DEFAULT VALUE]
Maximum borrowing rate: [DEFAULT VALUE]
Maximum order size: [DEFAULT VALUE]
Maximum bundle size: [DEFAULT VALUE]
Maximum execution cost: [DEFAULT VALUE]
Maximum slippage: [DEFAULT VALUE]
Maximum daily turnover: [DEFAULT VALUE]
Maximum daily loss: [DEFAULT VALUE]
Policy duration: [DEFAULT DURATION]
Risk-reduction override
A strict daily-loss or turnover limit may prevent an agent from closing a dangerous position.
The recommended policy may therefore include a narrowly defined risk-reduction path.
A risk-reduction action may be permitted when it demonstrably improves a specified risk measure, even when it:
Realizes an existing loss
Exceeds ordinary turnover
Closes a position earlier than planned
Repays borrowing at an unfavorable moment
Cancels an otherwise valid strategy
The risk-reduction override must not permit:
A new withdrawal address
A new protocol
A new asset
Increased gross risk
Increased net directional risk
Ownership changes
Recovery changes
A capital-limit increase
Arbitrary external calls
Another signer
A policy expansion
The exact precedence rules must be published in the policy specification.
Understanding the capital limit
The capital limit controls the maximum value of owner-wallet assets the agent may place under management.
It is measured using:
[ORACLE OR VALUATION METHOD]
The capital limit is not the same as:
Maximum gross exposure
Maximum possible loss
Maximum borrowed principal
Maximum derivatives notional
Maximum liquidation loss
For example, an agent allowed to use $10,000 of wallet assets may create more than $10,000 of market exposure when borrowing or derivatives are allowed.
The setup screen therefore shows the simple capital limit.
The advanced policy contains separate limits for:
Gross exposure
Borrowing
Leverage
Margin
Daily loss
Net exposure
Execution cost
Price-feed failures or valuation delays may cause a policy limit to be evaluated incorrectly.
The policy cannot guarantee a maximum loss.
Deposits
The agent may deposit eligible assets from the connected wallet into World without a new owner signature when:
The asset is allowed
The World deposit contract is allowed
The deposit remains within the capital limit
The amount remains within the per-action limit
The wallet-level policy accepts the token approval
The World policy accepts the resulting portfolio
The signer authorization remains active
The policy has not expired
No deposit occurs merely because the agent was activated.
The user must instruct the agent or enable a specific automation before funds are deployed.
Token approvals
The agent may create token allowances only for approved contracts.
World should prefer:
Exact allowances
Time-limited allowances
Permit-based transfers
Batched approval-and-deposit transactions
Unlimited approvals should not be used by default.
When an underlying token or integration requires an unlimited approval, the interface must identify:
The token
The spender contract
Why the approval is required
How to revoke it
Whether the provider policy independently caps use
Whether the approval survives agent revocation
Revoking the agent does not necessarily revoke every previously created ERC-20 allowance.
Agent Settings must provide an allowance-review and revocation function.
Withdrawals and returning funds
The agent may withdraw from World only to:
The predetermined owner wallet
Another address explicitly approved by the owner
The agent may not add a new destination.
A Telegram instruction such as:
Return all my funds
may cause the agent to:
Cancel open orders
Close positions
Repay loans
Settle obligations
Withdraw available assets
Return assets to the owner wallet
Revoke unnecessary token allowances where supported
Returning all funds may not be immediate or fully possible when:
A loan has not matured
A loan cannot be refinanced
A market is paused
Liquidity is insufficient
An order cannot fill within the execution-cost limit
The account is being liquidated
A protocol is unavailable
The network is unavailable
An oracle has failed
An asset cannot be transferred
An asset has lost value
A smart contract has failed
A counterparty has failed
A position cannot be closed safely
The agent must report:
What was returned
What remains
Why it remains
Which obligations remain
Which risks remain
Gas and transaction submission
Routine agent actions should not require the user to maintain a separate gas wallet.
Depending on the supported implementation, gas may be:
Sponsored by a paymaster
Paid by a relayer
Reimbursed from the owner wallet
Paid in an approved ERC-20
Deducted from the action
Paid from a capped gas balance
The exact gas method and fees must be visible in Agent Settings.
Gas sponsorship is an availability feature, not a guarantee.
When gas sponsorship is unavailable, an action may be delayed or fail.
Using Telegram
Supported requests
The agent may support instructions such as:
Show me my portfolio
Put $5,000 to work conservatively
Keep my ETH exposure neutral
Stop borrowing
Cancel my open orders
Reduce my risk
Close the basis strategy
Return everything to my wallet
Pause
Explain my current risk
Show me recent actions
Show me what the agent is allowed to do
Agent responses
For every material action, the agent should report:
What it did
Why it did it
Which wallet it used
Which World account it used
Which policy authorized the action
Amounts
Assets
Markets
Estimated cost
Actual cost
Portfolio state before the action
Portfolio state after the action
Transaction hash
Whether any part failed
Whether another action remains pending
The agent may notify the user before an action without requiring approval when the action is already inside the policy.
Telegram cannot expand authority
A Telegram message cannot:
Increase the capital limit
Add a protocol
Add a market outside the policy
Add an asset outside the policy
Add a withdrawal address
Replace the owner
Add another signer
Disable owner recovery
Change the wallet implementation
Extend an expired mandate
Lower required safety limits
When a user requests one of these changes, the agent must provide a link to a World-controlled authorization page.
Pause
The user may pause the agent from Telegram.
Pausing:
Blocks ordinary new agent actions
Does not automatically close positions
Does not automatically repay loans
Does not automatically cancel every open order
Does not revoke the signer
Does not revoke token allowances
The user may separately request:
Pause
Pause and cancel orders
Risk reduction only
Return funds
Resume
For protection against a compromised Telegram account, resuming after a security pause should require owner authentication.
Telegram alone must not be able to reverse an owner-initiated emergency pause.
Telegram compromise
Anyone who controls the connected Telegram account may instruct the agent within its existing policy.
If Telegram may be compromised:
Pause the agent
Terminate unauthorized Telegram sessions
Open World Agent Settings from the official domain
Disconnect Telegram
Review recent agent actions
Rotate or revoke the agent signer if needed
Review token allowances
Review open orders and positions
The World bot will never request:
A seed phrase
A private key
A recovery phrase
A raw API credential
A wallet export
A password
A signer credential
Portability
World Agent is intended to be a wallet-level agent identity rather than a World-only asset account.
Other wallets
A user may connect additional wallets to the same agent.
Each wallet requires:
Its own owner authorization
Its own policy
Its own capital limit
Its own withdrawal destinations
Its own signer authorization
The agent must never assume that authority over one wallet applies to another wallet.
Users should assign clear names such as:
Main wallet
Trading wallet
Treasury
Safe
Personal ETH
Company wallet
When an instruction could apply to multiple wallets, the agent must state which wallet it will use.
Other protocols
The same agent identity may later receive permission to use another protocol.
Each protocol requires a separate policy.
World’s policy protects World actions only.
It does not automatically protect interactions with:
Aave
Uniswap
Morpho
Safe
Bridges
Other lending protocols
Other exchanges
Other smart contracts
Adding another protocol must not broaden the existing World policy.
Migration
The supported signer provider must provide a documented method to:
Export or migrate the owner-controlled wallet where applicable
Rotate the agent signer
Revoke the old signer
Preserve owner access during provider outages
Recover after a lost device
Verify that an old credential is no longer usable
Move to another provider when supported
The production implementation must describe its actual portability rather than relying only on labels such as non-custodial or user-controlled.
Customizing the policy
Open:
Agent Settings → Safety rules
The interface shows:
A human-readable policy
A machine-readable policy
The active policy hash
The active signer
The effective wallet
The effective withdrawal destinations
The user may customize:
Capital limit
Markets
Assets
Borrowing
Gross exposure
Net exposure
Margin floor
Daily loss
Drawdown
Turnover
Slippage
Execution cost
Loan rates
Loan maturities
Policy duration
Approval requirements
Counterparty rules
Telegram account
Return wallet
Allowed protocols
Allowed contracts
Allowed functions
Policy expansion
A change expands the policy when it gives the agent more authority.
Examples:
Increasing a limit
Adding an asset
Adding a market
Enabling borrowing
Increasing borrowed principal
Lowering the margin floor
Adding a protocol
Adding a withdrawal destination