Pitch deck · zkasuran · October 2026
Bond
Humans and AI agents, paid peers.
A Seeker group chat where every member, human or agent, holds a key that is also a Solana wallet. Talk, delegate and pay in USDC, right in the thread.
369 + 95 tests · ALL GREEN
ROOM · SEEKER BUILDERS
3 humans · 1 agent
5.00 USDC @Bond tool_call +1.60 to creator agent pays 1.00
Solana devnet BO AGENT YO You MA Maya PF Pixel Forge · creator
Bond is a group chat for Seeker where people and AI agents are the same kind of member. Every member holds a key that is also a Solana wallet, so anyone in a thread can pay anyone else. The drawing is one room: payments in mint, agent work in violet.
01 · The gap
Seeker put a wallet in every pocket.
A wallet with no room
Seeker ships a self-custody wallet in the phone. There is nowhere to use it with other people, inside a conversation.
Agents are single-player
Phone AI agents are bots for one person. They cannot hold value, pay anyone or work inside a group as a peer.
$0.00
0
Builders are paid nothing
Agent skill catalogs are free, so the builders behind the skills earn nothing when their work gets used.
Bond puts people, agents and the wallet in one thread , where anyone can pay anyone.
Seeker put a self-custody wallet in the phone and the Solana Mobile Stack exposes it to apps. What is missing is a place where that wallet is the identity you chat and transact under, with agents beside you as peers, not bots bolted onto a chat app.
02 · The insight
The key that signs your messages is already a Solana wallet.
Ed25519 public key
93 37 e1 3a c8 c9 1b c8
81 ae c0 ee 4c 4d 2d 2e
ca 7d fc 25 fc bc 0f ee
04 45 44 09 83 3b 99 3b
As a did:key
did:key:z6MkpMwQ…PavARoQ
multibase(base58btc, 0xed01 || key) Signs every message you send: Ed25519 over RFC 8785 canonical JSON, re-verified on every read.
As a Solana address
AugMQy69…cuFD22
base58(key) Anyone in the room, human or agent, can pay it in USDC.
This is the whole trick. Solana keys are Ed25519, and so is the did:key every Bond member signs messages with. So the chat identity is already a wallet: the same 32 bytes, encoded two ways. Agents hold a keypair of their own too, so an agent pays from its own wallet, under a hard cap.
03 · Solana Mobile Stack
Connect a Seeker wallet. One signature binds it.
1 A key made on the phone Your Ed25519 did:key is generated on the device and kept in its secure store. It is never uploaded.
2 Mobile Wallet Adapter The wallet checks Bond's Digital Asset Links against the release signing key and shows Bond as verified.
3 One signed challenge Wallet and did:key both sign the binding. It is re-verified on every load and version-checked.
4 Seed Vault signs value The device key signs chat, the wallet signs payments. Bond never sees the wallet's key.
Real device: signed APK on Android 15, Solana Mobile's reference test wallet, devnet.
On a real Seeker this is Mobile Wallet Adapter end to end. The wallet verifies Bond through Digital Asset Links on the identity domain, matched to the release signing key. One challenge, signed by both keys, binds the wallet to the did:key. The wallet's key never leaves Seed Vault; Bond only receives what the wallet signs.
04 · The product
One thread is and the economy.
Same kind of member People and agents share one room. Each carries a signed identity, and each can be paid.
Agents work in the open A mention starts a real tool-calling turn. Every tool call and result lands as its own node.
Pay without leaving USDC over Mobile Wallet Adapter, landing as a receipt that is re-checked on chain.
9:41
‹
Seeker builders 2 humans · 1 agent
MA YO BO
MA Maya 23:18
RPC bill came in. 5 USDC each?
YO You 23:19
@Bond how much USDC do I have on devnet?
BO Bond AGENT 23:19
called solana_get_balance
owner: AugM…FD22 · mint: USDC
BO returned
uiAmount: 12.4 · cluster: devnet
BO You hold 12.40 USDC on devnet. Enough to cover Maya.
YO You 23:20
Confirmed Settling
5.00 USDC devnet
To Maya · 7xKX…9fQ2
$ Send USDC Settles on Solana devnet
TO Maya · 7xKX…9fQ2
5.00 USDC
Over your limit: PIN first
Signed node Ed25519 · jcs-v1
tool_call → Solana devnet
transferChecked re-checked on chain
Scripted replay of the real flow, built in HTML.
This is the loop in ten seconds. Maya asks to split a bill. I ask the agent for my balance; it calls a real Solana tool and the call and the result land as nodes in the thread. Then I pay Maya in place, my PIN first, and a receipt lands that Bond re-checks against the chain.
05 · Agents
Mention @Bond. It runs real tools,
Streamed into the thread as server-sent events
turn_start text tool_call tool_result text turn_end done
100 USDC per transfer
500 USDC per process
8 tool steps per turn
The caps live in server code and are reserved atomically, never in a prompt. The system prompt is fixed on the server.
Model-agnostic: MiniMax today, any OpenAI-compatible API. Adapters for Hermes and OpenClaw.
A mention routes to a server loop that runs a tool-calling agent with Solana tools. It quotes a swap but never signs one. It can pay from its own keypair, under caps written in code: 100 USDC a transfer, 500 a process, 8 steps a turn.
06 · Many agents
Type @scout. Only Scout answers.
An @username and a persona Every agent you make gets a unique handle and a persona it keeps in every reply.
Talk to one, or to several Type its @username, with suggestions as you type. Only the agents you name reply, and each knows which replies were its own.
Bring it into any room Add the same agent to another room by @username. Same identity and persona, a job of its own for that room.
Real device: three agents in one room, addressed by @username.
Agents are people in the chat. Each one has an @username and a persona it keeps everywhere. In a room with several agents you type the one you want and only it answers. The same agent can join any other room by its @username, with its own job there.
07 · The core idea
The payment is the license.
No accounts, no license server, no NFT mint. The chain is the database.
01 · Buy
Unlock, then the wallet
Bond asks for your biometric or PIN before the wallet sees anything. The wallet signs over Mobile Wallet Adapter.
02 · One transaction
An atomic 80/20 split
1.60 creator 80%0.40 20%
2.00 USDC in one transaction. Both legs settle, or neither does.
03 · Agent turn
The server re-reads it
04 · Unlocked
The skill joins the turn
Its tools join the agent's turn, for this skill and this buyer only.
Nothing unlocks. That transaction never paid this skill's creator.
Nothing unlocks. A claim needs a fresh did:key signature and the wallet binding.
Buying a skill is one atomic USDC transaction: 80 percent to the creator, 20 to the platform, both or neither. When you ask the agent to use it, the server re-reads that purchase on chain and checks the buyer proved their wallet. Only then do the skill's tools join the turn. A reused or replayed signature unlocks nothing.
08 · Live on devnet
The agent uses the skill on the transaction
Devnet transaction 3DqUdGZt…JAksTzdK
slot 507,807,070 · 2026-10-05 17:29:04 UTC
Buyer paid 2.00 USDC4L91…MFK4
Creator, Pixel Forge · 80% 1.60 USDC6jRF…9fQS
Platform fee · 20% 0.40 USDCE523…uwL
Network fee 0.000005 SOL
Result succeeded, one atomic transaction
The purchase signature is the proof of purchase.
Real device and live server. Tx Explainer is a seeded sample listing; the payment is real.
Here is the interesting part. I ask the agent to use the skill I just bought on the very transaction that bought it. The runtime reads that purchase on chain, sees I paid the creator, and only then gives the agent the skill, which decodes its own sale.
09 · SKR
SKR, built into every listing.
Priced in SKR, live Every listing shows its SKR equivalent from a live Jupiter quote on Solana mainnet.
Holders pay less Hold SKR and get the creator's discount: 10% by default, hard-capped at 25%, read from your real mainnet balance.
Read-only, on purpose Nothing is signed and no SKR moves in this build. The sale itself settles in USDC on devnet.
Next, with mainnet Pay in SKR · SKR-staked creator listings
Tx Explainer price card, signed 1.2.x APK. The SKR equivalent is a live mainnet quote; the listing is a seeded sample.
SKR holder discount
0% 10% default 25% hard cap
SKR mint SKRbvo6G…NPGZhW3 · mainnet, read only
Every listing carries a live SKR price from Jupiter on mainnet. SKR holders get a creator-set discount, ten percent by default and never more than twenty-five, read from their real mainnet balance. Nothing is signed and no SKR moves in this build. Paying in SKR comes with the mainnet launch.
10 · Protection
Protection you choose. It fails closed.
When Default factor
Spend 1 USDC or more Use the signing key Run a skill Off, raise it any time Open the app Off, raise it any time
A wrong PIN never reaches the wallet. No factor available means no spend. Five wrong PINs lock for 30 s, doubling to 15 min, on a monotonic clock a date change cannot rewind. Weakening a guard needs a factor that existed before the request. Choose the app lock on first open. The PIN pad shuffles every time .
Real device: the PIN pad shuffles every time, then a confirmed receipt.
Protection is per action: open the app, run a skill, spend, use the signing key. Spending and the key default to a factor. When there is no factor, nothing moves. Brute force meets a lockout on a clock the user cannot rewind.
11 · Design
Designed as one material.
One system runs through the app, the website and this deck.
Colour with meaning
Mint action and trust Violet agents Cyan humans Ink the ground
Type
Aa Geist and Geist Mono SIL OFL 1.1, one family per weight
One physics: Reanimated springs
1.0 0
snappy 18/320 gentle 20/180 bouncy 11/260 Damping and stiffness per token. Reduce-motion is honoured everywhere, and ambient loops settle after three cycles.
The web build: same React Native code as the APK.
The mark is a human circle bonded to an agent square, the same two avatar shapes the app uses. Mint means action and trust, violet means agents, cyan means humans. Everything moves on three shared springs and stands still for reduce-motion.
12 · Proof
It is live, and it is real.
Real Solana devnet transactions
What Signature Slot
Skill purchase · Tx Explainer2.00 USDC: 1.60 to the creator, 0.40 platform 4Zb9eFr6…wHdkqZuP 507,897,796 Human payment · PIN-gated1.50 USDC, signed over Mobile Wallet Adapter yWEKn9us…EoAp4CGH 507,898,608 Agent-initiated refund 1.00 USDC from the agent's own keypair 62UKC2ZM…RA9u7EDA 507,898,816
zkasuran/bond · HEAD · summarised
$ ./verify.sh
app tsc --noEmit, strict
app jest: 369 tests, 32 suites
app lint
app expo export -p web: 16 routes
server typecheck
server tests: 95 pass, 0 fail
supply audit: high and critical fail the gate
ALL GREEN
Bond 1.3.6 · versionCode 12 · signed v2 · SHA-256 130bd954…cb2b8397
Everything on this slide can be checked. The transactions are on devnet. The release gate is one command anyone can run, a judge included, and it prints ALL GREEN only when the type-checks, both test suites, the lint, the web export and the supply-chain audit pass.
13 · Security
Built to be attacked.
A full audit before 1.3.1. Every row of SECURITY.md names the attacker, the defence, the file that holds it and the test that proves it.
Attack A relay forges or relabels a node
Defence Name, kind and every structural edge are signed. Verified on ingest and on read; a tampered node never renders.
app/src/identity/sign.ts
Attack A peer fakes a payment receipt
Defence It renders as an unverified claim until re-checked on chain: amount, mint, sender and recipient must match.
app/src/solana/confirm.ts
Attack Someone talks the agent into draining funds
Defence Per-transfer and per-process caps, checked and reserved in one synchronous step. Fixed system prompt.
server/src/limits.ts
Attack A public purchase is replayed by someone else
Defence The entitlement is bound to the buyer by a wallet-ownership proof over a fresh, expiring challenge.
server/src/agent/skills.ts
Attack A stolen phone grinds the PIN or weakens the policy
Defence Monotonic lockout, an HMAC-tagged policy, and a downgrade needs a factor that existed before the request.
app/src/protection/gate.ts
Attack A hostile client floods the sync server
Defence 64 KB frames, token buckets, socket and store ceilings with backpressure, origin checks that fail closed.
server/src/sync.ts
Bond moves value, so it was built to be attacked. Every message is signed and re-verified on read. Receipts are claims until the chain agrees. The agent's spend caps are code, not prompt. Purchases are bound to their buyer. The sync server has a ceiling for everything.
14 · Why it sticks
Every action makes the room worth coming back to.
Who it is for Seeker owners who hold USDC and want to split a cost, pay a collaborator or hand a bounded task to an agent, without leaving the chat.
Why they come back The thread is the loop. Payments, agent actions and skill purchases all land in the room they already use, not in another app.
Why builders come 80% of every skill sale, paid on chain the moment it settles. No invoices, no license server.
How Bond earns A 20% platform fee, inside the same atomic transaction.
one thread
More rooms More agent turns More skill sales Builders paid 80% More skills
The repeat-use loop is the thread itself. Every payment, agent action and skill purchase lands in the room you already use, and every sale pays a builder on chain, which brings more skills and better agents. Bond has no users yet, so there are no adoption numbers here.
15 · Status
What is real today. What ships next.
did:key identity, signing, verify on readHuman USDC payment over Mobile Wallet Adapter
Agent USDC payment from its own keypair, hard-capped
Atomic 80/20 skill purchase, the signature kept as proof
Three bought skills running in the agent, each unlocked by an on-chain license check
Tool-calling agent runtime on MiniMax, streamed into the thread
Live Jupiter swap quote. The agent returns an unsigned swap and never signs it
SKR price and holder balance, read from mainnet
Seeded for the demo The four marketplace listings and their creators are samples. Everything that moves money settles on devnet.
Listed on the Solana dApp Store within 30 days of the results. The APK is already release-signed
Mainnet USDC behind the same spend gate
Jupiter swap execution, signed in your own wallet
Pay in SKR, and SKR-staked creator listings
Self-serve skill publishing with signed manifests
The full roadmap is on the next slide
Here is exactly what is real. Payments, purchases and agent transfers are real on devnet. Mainnet is touched only to read a Jupiter quote and SKR. The roadmap starts with the dApp Store, then mainnet behind the same gates.
16 · Roadmap
Talk. Hire. Pay. Own. Everywhere.
Now Live on devnet
Humans and agents, as paid peers Wallet identity, signed messages USDC in the thread, checked on chain Agents with @username, persona, a job per room Skills where the payment is the licence 01 Talk
A full messenger On the Solana dApp Store within 30 days of resultsInvite links, DMs, groups of thousands Channels people and agents follow Public profiles, media, push, multi-device 02 Hire
The agent marketplace Hire an agent per task or rent it by the day, week or monthEscrow on Solana, released on delivery Ratings and a verified run history 03 Pay
Solana is the money layer Mainnet USDC, SOL, SKR and any SPL token Swaps in the chat, with your approval Agent wallets with limits you can revoke 04 Own
The SKR economy Stake SKR to publish and rank agents SKR rewards, discounts and holder-only rooms Holders vote on marketplace rules 05 Everywhere
An open platform SDK and agent API to build and earn Mini-apps inside a chat Desktop, web and an open protocol
Where Bond goes: a full messenger first, then a marketplace where anyone can hire or rent a public agent with escrow on Solana, then mainnet payments in any token, then an economy run on SKR, and finally an open platform anyone can build on.
Watch the demo2:42