Convey

Gift real stocks in one link, from you or your AI agent. Convey gifts tokenized xStocks (NVDAx, AAPLx, TSLAx) on X Layer. People send from OKX Wallet. AI agents gift through Convey's MCP server, one-off or on a recurring schedule, after the user approves. Apps and services gift through the TypeScript Convey SDK. The recipient opens the link, confirms with a passkey, and owns the stock in their own OKX Smart Wallet. They don't need a wallet first, don't buy OKB, and don't pay gas.

Gifts can also be recurring, for example a stock every month. The sender approves a budget once, the Convey Agent delivers each gift on schedule, and the sender's own OKX Smart Wallet enforces the budget on-chain. This is proven on X Layer mainnet.

Live: conveyapp.site · App: conveyapp.site/app · Chain: X Layer mainnet (196)

▶ Demo video (3 min): watch on X. It covers the problem, the solution, and a real end-to-end gasless claim on X Layer mainnet.

Why it matters

Tokenized stocks are programmable, but receiving one still means installing a wallet, writing down a seed phrase, switching networks, and buying gas. That barrier is highest for exactly the people you'd most want to give a first share to.

Convey handles all of that at delivery time without taking custody. The asset settles to the recipient's own ERC-4337 account, not to a Convey balance.

Built for the OKX stack

Layer	What Convey uses	How
Chain	X Layer mainnet	All contracts, gifts and claims settle on chain 196
Assets	xStocks: NVDAx, AAPLx, TSLAx	Certified in Convey's on-chain `AssetRegistry`; live issuer prices
Sender wallet	OKX Wallet	EIP-6963 discovery (`com.okex.wallet`), with `window.okxwallet` as fallback; adds or switches to X Layer automatically; on phones, opens in the OKX Wallet app via deep link
Receiver account	OKX Smart Wallet (ERC-4337 v0.7)	Created from a device passkey; deployed on first claim
Recurring budget	OKX Smart Wallet owner hooks	The agent is a restricted owner; `ConveyRecurringGiftHook` enforces asset, caps, total budget and expiry inside the sender's wallet
Bundler	OKX OKBund (pinned)	Self-hosted, private; sponsored UserOperations only
AI agents	Convey MCP server	Agents list xStocks, check gifts, and send or reclaim gifts under a per-gift cap with user confirmation
Developers	Convey SDK (TypeScript)	Apps and services create, read and reclaim gifts and get claim links with their own wallet or key

How it works

 Sender (OKX Wallet)                                  Recipient (any phone)
        │ createGift(xStock, amount, claimKey)                 │ opens link, passkey
        ▼                                                      ▼
 ┌──────────────┐   reserve OKB   ┌──────────────────┐   ┌─────────────────────┐
 │  GiftEscrow  │ ──────────────▶ │ Claim paymaster  │◀──│ Convey gateway      │
 │  holds xStock│                 │ sponsors gas     │   │ policy + preflight  │
 └──────┬───────┘                 └──────────────────┘   └──────────┬──────────┘
        │ claim(giftId, signature)                                  │ private
        ▼                                                           ▼
 OKX Smart Wallet  ◀────────── EntryPoint v0.7 ◀─────────────── OKBund
 (recipient owns the xStock)

Send. The sender picks an xStock in the app and confirms one escrow transaction in OKX Wallet. It includes a 0.00002 OKB claim reserve.
Share. The link carries a one-time claim key. Only that key's address goes on chain.
Claim. The recipient's passkey creates their OKX Smart Wallet. The claim is a sponsored UserOperation, and the sender's reserve pays the gas.
Own. The recipient can hold the xStock, cash out to USDT0 with a live quote, or move it anywhere. The exits are gasless too.

Recurring gifts

 Sender's OKX Smart Wallet
   ├─ admin owner (the sender): full control, can revoke the Convey Agent at any time
   └─ Convey Agent owner (restricted) ──▶ ConveyRecurringGiftHook checks every call:
                                     • target is GiftEscrow.createGift only
                                     • one xStock, ≤ cap per gift, ≤ total budget
                                     • native reserve ≤ cap, before expiry

Approve once. The sender sets the xStock, amount, schedule, recipient and total budget. The wallet adds the agent as a restricted owner bound to the hook, with a matching token allowance.
Gifted on schedule. The Convey Agent (through Convey's MCP server) gifts each one when it's due. It never sends early, never twice, never over budget, and it recovers from crashes. Each gift arrives as a normal link.
Enforced on-chain. Even with a leaked agent key, the wallet refuses anything outside the policy. The sender can revoke the agent at any time.

On X Layer mainnet, the Convey Agent gave two gifts within budget. A third gift, an oversized gift and a token withdrawal were rejected. The agent was then revoked, and its next call failed. See Onchain proof.

For AI agents: Convey MCP server

Convey also runs as an MCP server, so any agent (Claude, Cursor, or an OKX AI agent) can gift xStocks to a person. For example, it can reward a contributor, pay a bounty, or send a birthday share on a user's behalf. The recipient still needs no wallet and pays no gas.

Tool
`list_xstocks`	Giftable xStocks with live issuer prices
`get_gift`	Live state and USD value of any gift
`agent_wallet`	Agent balances and per-gift cap
`send_gift`	Creates a gift and returns its claim link
`reclaim_gift`	Returns an unclaimed gift
`create_recurring_plan` · `run_due_gifts`	Recurring gifts, e.g. 0.01 AAPLx every month, under an approved total budget
`list_recurring_plans` · `cancel_recurring_plan`	Review or stop plans

claude mcp add convey -- node /path/to/convey/mcp/server.ts

The read tools need no key. The spending tools need an agent key, a per-gift cap, and confirm: true. For recurring gifts, one approval covers the whole plan, bounded by its total budget.

For a budget the agent cannot exceed even if its key leaks, Convey also has an on-chain recurring mode, proven on mainnet. The sender's OKX Smart Wallet adds the agent as a restricted owner, bound to ConveyRecurringGiftHook. The wallet then enforces the asset, the per-gift cap, the total budget and the expiry itself, and the admin can revoke the agent at any time. The full send, cap, confirm and reclaim flow and recurring plans (schedule, budget, and crash recovery) were exercised against the live v2 contracts on a mainnet fork. See mcp/README.md.

For developers: Convey SDK

The Convey SDK is what the web app and the MCP server use to send gifts. Apps, bots and backend services can use it directly with their own wallet: the SDK signs through any EIP-1193 provider, so keys stay in your process and Convey never holds them.

import { ConnectedWalletSender } from "convey/sender";

const sender = new ConnectedWalletSender({
  rpcUrl: "https://rpc.xlayer.tech",
  provider: window.okxwallet, // or any EIP-1193 provider, e.g. one backed by a server key
  deployment: {
    registry: "0x156d160e004B7fb2021CFCA8fC6cF069c3b8b029",
    escrow: "0xffd2DACE75dbC3bC3f2e10C6c7b011Aa4EC043cD",
    claimPaymaster: "0x655025c861C1848BA5324863D85BFA32cCF69e5B",
    claimBaseUrl: "https://conveyapp.site",
  },
});

await sender.connect();
const gift = await sender.createGift({ asset: "0xa8ddb5cd96b5222afe198316e9a57caa642850d5" /* wNVDAx */, amount: "0.01", note: "Happy birthday" });
console.log(gift.claimLink); // send this link to the recipient

Entry point	For
`convey/sender`	Create, read and reclaim gifts, build claim links (`ConnectedWalletSender`)
`convey/receiver`	Passkey vault, enrollment, recovery and the gasless claim flow
`convey/relayer`	Client for Convey's private claim gateway

The SDK isn't on npm yet; add it from this repository. For headless use with a server-held key, mcp/local-provider.ts shows a minimal EIP-1193 provider. See docs/relayer.md for the gateway and claim side.

Security design

Claims can't be front-run. The link secret never goes on chain. It signs (chainId, escrow, giftId, claimer) and GiftEscrow checks that signature against the stored claim-key address. A claim observed in a bundler, a mempool or a failed attempt can't be replayed to redirect the gift. It is covered by replay, wrong-key, malformed-signature, high-s and fuzz tests.
Non-custodial. The recipient's owner key is created and encrypted on their device. Convey never receives it.
Scoped sponsorship. The paymaster signs only single-call claims to GiftEscrow and draws on that gift's own reserve. The exit paymaster checks the route and a fresh on-chain quote before signing.
Fails closed.
- The gateway won't start without a bearer token.
- Each UserOperation must pass event-aware EntryPoint preflight before it is forwarded.
- Sponsor signing is limited per account and per IP, and exit sponsorship has a daily spend cap.
Recurring budgets are enforced by the wallet. A recurring agent is a non-admin owner of the sender's OKX Smart Wallet. Every call it makes passes ConveyRecurringGiftHook, and it can never change owners or move funds elsewhere.
No mock data. Prices, balances, quotes and claim state are read live. Anything that can't be read is shown as unavailable, never estimated.

The contracts have an in-house review and 51 Foundry tests. There has been no third-party audit.

Onchain proof

Component	Address
`GiftEscrow` (v2, signature-bound)	`0xffd2DACE75dbC3bC3f2e10C6c7b011Aa4EC043cD`
`ConveyClaimPaymasterV07` (v2)	`0x655025c861C1848BA5324863D85BFA32cCF69e5B`
`ConveyExitPaymasterV07`	`0xcfd241979d578e0b43f4c3f6b9b3fab83b41974c`
`AssetRegistry`	`0x156d160e004B7fb2021CFCA8fC6cF069c3b8b029`
EntryPoint v0.7	`0x0000000071727de22e5e9d8baf0edac6f37da032`
OKX Smart Wallet factory	`0xdd3fea01cd550c9effc893f346690b9a649f35ef`

Milestone	Evidence
Sponsored ERC-4337 v0.7 operation through private OKBund	`0xfdb3ef41…df09`
End-to-end browser claim through the v2 escrow: a new recipient, a passkey, zero gas, 23 s to confirmation	`0x47236b16…0283`
Gasless gift claim (Gift 2, 0.0309 NVDAx, v1 escrow)	`docs/verification.md`
Gasless NVDAx → USDT0 cash-out through the exit paymaster	`docs/verification.md`
v2 escrow deployment and migration	`0x24175d02…0e69`
On-chain recurring gifts: an agent key bound by `ConveyRecurringGiftHook` sends 2 gifts in budget, the 3rd is rejected, then it is revoked	gift 1 · gift 2 · revoke

Every hash, receipt and readback is recorded in docs/verification.md and docs/product-deployment.json.

The receiver flow (passkey enrollment, gasless claim, and recovery) has been run end to end on a physical device, in addition to the first recorded claim through Chromium's WebAuthn virtual authenticator. Removing an owner on-chain is proven: the recurring-gift proof's admin revoked the agent owner with removeOwner.

Drop (multi-claim gifts) is implemented and tested, but deliberately not deployed.

Repository

app/                 Next.js app
  page.tsx           landing page
  app/page.tsx       send studio (OKX Wallet)
  g/[secret]/        recipient claim screen
  lib/okx-wallet.ts  OKX Wallet discovery, X Layer switching, mobile deep link
  api/               same-origin relay proxy (rate-limited) and issuer price proxy
mcp/                 MCP server for AI agents (send, check, reclaim gifts)
contracts/
  core/              AssetRegistry, GiftEscrow, DropEscrow
  paymaster/         claim and exit paymasters (ERC-4337 v0.7)
  bootstrap/         one-operation account bootstrap paymaster
  recurring/         on-chain recurring-gift hook for agent owners
src/
  sender/            Convey SDK: sender (gift, read, reclaim)
  receiver/          passkey vault, claim and exit builders
  relayer/           gateway, OKX account builder, preflight, limits
test/, test-solidity/  Node and Foundry suites
infra/               OKBund, gateway and web service units
docs/                design notes, verification record, operations

Run it

pnpm install
cp .env.example .env && chmod 600 .env   # fill in the addresses above
pnpm dev                                  # http://localhost:3000
pnpm test && forge test                   # 52 Node + 51 Foundry tests
pnpm mcp                                  # MCP server on stdio

Operator commands for deployment, funding, the gateway and monitoring are in docs/operations.md. Live evidence is in docs/verification.md.

Further documentation

docs/architecture.md: contract and account model
docs/claim-paymaster-design.md: reserve, validation and postOp accounting
docs/relayer.md: gateway, SDK and preflight
docs/sender-flow.md: sender module and gift creation
docs/receiver-flow.md: passkey vault and claim flow
docs/recurring-authorization.md: on-chain recurring gifts (proven on mainnet)
docs/drop-design.md: multi-claim Drop (not deployed)
mcp/README.md: MCP server for agents

License

MIT

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
app		app
brand		brand
contracts		contracts
docs		docs
infra		infra
mcp		mcp
script		script
src		src
test-solidity		test-solidity
test		test
.env.example		.env.example
.gitignore		.gitignore
.test-predeploy.ts		.test-predeploy.ts
LICENSE		LICENSE
README.md		README.md
foundry.toml		foundry.toml
next-env.d.ts		next-env.d.ts
next.config.ts		next.config.ts
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
tsconfig.json		tsconfig.json

Navigation Menu

Repository navigation

About

Repository files navigation

Convey

Why it matters

Built for the OKX stack

How it works

Recurring gifts

For AI agents: Convey MCP server

For developers: Convey SDK

Security design

Onchain proof

Repository

Run it

Further documentation

License

About

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

Convey

Why it matters

Built for the OKX stack

How it works

Recurring gifts

For AI agents: Convey MCP server

For developers: Convey SDK

Security design

Onchain proof

Repository

Run it

Further documentation

License

About

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages