Skip to content
Launch ZeFi

How it works

What runs today,
and what does not

ZeFi is a product with a credible path, not a finished autonomous system. This page is the honest inventory: every capability, its real status, and what it depends on.

From intent to execution

Six stages sit between
a sentence and a signature

Natural language on its own is not enough to move money. ZeFi puts verification and simulation between the prompt and the transaction — and shows you every stage.

  1. 01 · Prompt

  2. 02 · Intent

  3. 03 · Plan

  4. 04 · Simulation

  5. 05 · Approval

  6. 06 · Onchain action

01Prompt

A sentence, not a form

The user writes what they want in their own words. No chain selector, no token dropdown, no hex.

Input sanitised · framed as untrusted data · 4,000 character ceiling

02Intent

Language becomes structure

ZeFi extracts a typed intent — action, networks, asset, amount, recipient, priority — and scores its own confidence.

Forced tool call · Zod-validated · one repair attempt, then an error

03Plan

Structure becomes a sequence

A deterministic planner resolves every reference against the chain registry and builds the ordered steps. The model never supplies an address, an amount or a fee.

Registry lookup · EIP-55 checksums · exact-amount approvals only

04Simulation

The plan is tested before it is offered

Chain, asset, decimals, balance, recipient and approval scope are checked deterministically. A check that could not run is reported as skipped, never as passed.

Local validation always · deep simulation when a provider is configured

05Approval

A human decides

ZeFi states in plain language what will happen, what it costs, and what could go wrong — then waits. The confirm control names the real action.

“Review 250 USDC transfer” · never “Execute instantly”

06Onchain action

The wallet signs, not ZeFi

The transaction is handed to the connected wallet. ZeFi holds no keys and takes no custody. It tracks the hash and explains what happened.

Idempotent recording · status tracking · explorer link

Capability matrix

Nothing here is aspirational

“Available now” means it works in a correctly configured deployment. “Provider required” means ZeFi builds and shows the plan but will not produce calldata. “Not built” means exactly that.

ZeFi capability status
CapabilityStatus
Explain crypto concepts and contract behaviourRequires OPENAI_API_KEY and OPENAI_MODEL (or the Anthropic pair).Available now
Read native and ERC-20 balancesFive EVM networks, via configured RPC endpoints.Available now
Parse natural language into a typed intentTen intent categories, Zod-validated.Available now
Build a transaction plan with risk and approvalsFully deterministic; no model input.Available now
Local deterministic validationEight checks. Runs with no provider configured.Available now
Native-currency transfersUser-signed. Gated by TRANSACTION_EXECUTION_ENABLED.Available now
ERC-20 transfersRegistry tokens only. User-signed.Available now
Persistent conversations and plansRequires DATABASE_URL; otherwise session-scoped and labelled.Available now
Deep simulation against live chain stateeth_call runs the contract before you sign. Needs SIMULATION_PROVIDER=rpc.Available now
Fork traces and full account diffsNeeds a vendor adapter. eth_call catches reverts, not every balance change.Provider required
Swap executionNeeds SWAP_PROVIDER. ZeFi plans the steps but builds no calldata.Provider required
Bridge executionNeeds BRIDGE_PROVIDER. ZeFi plans the steps but builds no calldata.Provider required
USD-denominated amounts on volatile assetsNeeds PORTFOLIO_PROVIDER for pricing. ZeFi will not estimate a price.Provider required
Scheduled or conditional executionNot built.Not built
Policy-bounded autonomous agentsNot built. Depends on smart accounts.Not built
Solana transactionsRecognised for planning; no Solana wallet connection.Not built

Two plans, side by side

One ZeFi can sign. One it cannot.

The difference is visible in the interface itself. A plan ZeFi cannot execute is still built, still validated, and still explained — it simply never reaches a signature request.

Executable todayERC-20 transfer on Base
Transaction planIllustrative
Ready for signature

You asked

“Send 250 USDC to 0x4E8F2A1b9C7D3e5f6A0B1C2d3E4f5a6B7c8D9E0F on Base”

ZeFi understood

Transfer 250 USDC on Base to a single external address.

SENDconfidence 0.97

Sequence of actions

1 step · 1 signable
  1. 1

    Transfer 250 USDC on Base

    An ERC-20 transfer call on the USDC contract. Your wallet signs it directly; ZeFi never holds the funds.

    Wallet signature

Estimates

Network cost

0.0000164 ETH

$0.06

Slippage

Not applicable

Execution time

~4s

Approvals

None

Simulation

Local validation · local

Local validation passed. Deep simulation is not configured, so this transaction has not been executed against chain state.

  • pass

    Chain resolves to a supported network

    Base · chain id 8453.

  • pass

    Wallet is on the plan’s network

    Connected wallet matches the plan’s network.

  • pass

    Recipient address

    Checksum valid · 0x4E8f…9e0F

  • pass

    Asset resolves in the registry

    USDC · 6 decimals · 0x8335…2913

  • pass

    Amount is representable

    250 USDC encodes exactly at 6 decimals.

  • pass

    Balance covers the amount

    Balance 1,284.30 USDC.

  • pass

    No unlimited approvals

    This plan requests no token approvals.

  • pass

    Every step can be encoded

    All steps map to a known function on a registry contract.

Risk review

  • First transfer to this address

    Caution

    ZeFi has no record of you sending to this address before. Transfers are irreversible — check the full address, not just the first and last four characters.

  • Deep simulation is not configured

    Info

    Local deterministic checks passed. ZeFi has not executed this transaction against forked chain state.

Where these figures came from

  • ZeFi chain & asset registryregistry · Mar 18, 2026, 09:41 AM UTC
  • Illustrative fixture — Example figures for demonstration.illustrative · Mar 18, 2026, 09:41 AM UTC

Every plan requires explicit approval. Your wallet signs; ZeFi never holds funds.

Review 250 USDC transfer
Plan-onlyCross-VM bridge to Solana
Transaction planIllustrative
Missing information

You asked

“Move $2,000 of USDC from Base to Solana using the safest route.”

ZeFi understood

Bridge 2,000 USDC from Base to Solana, prioritising the lowest-trust route.

BRIDGEconfidence 0.94

Assumptions ZeFi made

  • USDC is treated as a 1:1 dollar equivalent, so $2,000 resolves to 2,000 USDC.
  • The destination is your own wallet unless a Solana address is supplied.

Sequence of actions

3 steps · 0 signable
  1. 1

    Approve 2,000 USDC for the bridge contract

    An exact-amount approve on the Base USDC contract. ZeFi does not plan unlimited approvals.

    No signature
  2. 2

    Bridge 2,000 USDC from Base to Solana

    A burn-and-mint route rather than a liquidity pool, so the USDC that arrives is canonical rather than a wrapped claim.

    Bridge routing provider (BRIDGE_PROVIDER)
  3. 3

    Receive 2,000 USDC on Solana

    Settlement on the destination chain. No signature is required from you.

    No signature

Estimates

Network cost

0.00021 ETH

$0.71

Slippage

0%

Execution time

~2 min

Approvals

1 exact-amount

Some figures could not be established. ZeFi shows them as unavailable rather than estimating a number it cannot source.

Simulation

Local validation · local

Local validation passed. Deep simulation is not configured, so this transaction has not been executed against chain state.

  • pass

    Chain resolves to a supported network

    Base · chain id 8453.

  • pass

    Asset resolves in the registry

    USDC · 6 decimals · 0x8335…2913

  • warn

    Amount is representable

    Amount is a US-dollar value; it resolves to an exact token amount at signing time.

  • skipped

    Recipient address

    No Solana destination address supplied yet.

  • pass

    No unlimited approvals

    1 exact-amount approval.

  • warn

    Every step can be encoded

    1 step needs a routing provider before calldata can be produced.

Risk review

  • Route crosses virtual machines

    Caution

    Base is an EVM chain and Solana is not. The destination address format differs, and an address valid on one side is invalid on the other. ZeFi requires the Solana address to be confirmed separately before signing.

  • Bridging adds a trust assumption

    Caution

    For the period funds are in transit you rely on the bridge’s attestation set rather than on Base or Solana alone.

  • 1 step needs a routing provider

    Info

    ZeFi has planned the bridge and can describe every step, but cannot build calldata without a bridge provider configured. Nothing will be submitted for signature.

Where these figures came from

  • ZeFi chain & asset registry — Contract addresses, decimals and chain ids.registry · Mar 18, 2026, 09:41 AM UTC
  • Illustrative fixture — Example figures for demonstration. Not a live reading.illustrative · Mar 18, 2026, 09:41 AM UTC

Before this can proceed

  • Missing: recipient

Every plan requires explicit approval. Your wallet signs; ZeFi never holds funds.

Add the missing details

ZeFi provides informational, technical, and transaction-planning tools. Outputs may contain incomplete assumptions and do not constitute financial, investment, legal, tax, compliance, or security-audit advice.