Orin Roadmap
Docs · v0.1 · October 2026

The personal agent you can check.

How Orin does everyday tasks for people, runs on stablecoin payments, and proves every action with on-chain receipts verified by the $ORIN network.

Summary

Orin is a personal AI agent that does everyday tasks and proves what it did.

It books, cancels, follows up and saves people money. It asks before anything important. Agentic payments come next: Orin will pay merchants for the user, within limits written into a smart contract.

Users pay for Orin in USDC on-chain. Every action produces a receipt anchored on-chain. $ORIN has one job: it secures an independent validation network that checks Orin's actions before their receipts are final.

The problem

Personal agents now act for people, but they ask for blind trust.

The new generation of personal agents can send email, book travel and make purchases. To do that they need access to inboxes, calendars and money. Today the user has to trust the company running the agent on three things it cannot check:

  • That the agent asked first. Some agents act before confirming and only ask at checkout.
  • That it stayed within budget. Limits usually live on the company's own servers.
  • That its records are accurate. Activity logs are written by the same system they describe.

When the company running the agent also earns from advertising or data, that trust is harder to give. Orin replaces each of these promises with something the user can verify.

What Orin does

You ask in your own words. Orin plans the task, does it in the background, and comes back when it needs you.

Everyday tasksBook a table, cancel a trial, check in for a flight, lower a bill, reschedule an appointment, fill in a form.
Proactive helpOrin notices what needs attention, such as a check-in window opening, and offers to handle it.
Where you areThe Orin app and web, voice with push-to-talk, and Telegram. WhatsApp for task updates and approvals, within its platform rules.
Live viewWatch Orin work in its own browser at any time, and pause or stop a task.

How it works

An agent loop does the work. A rules layer decides what it is allowed to do.

The agent loop

A language model turns a request into a plan of steps and calls tools to complete them: official integrations where they exist, a cloud browser where they don't, and phone calls for businesses that only take calls. Progress is saved after every step, so a task survives interruptions and retries safely.

Approvals

Every tool is labelled safe (search, read) or needs approval (pay, send, book, accept terms). The server will not run a needs approval step until the user approves that exact action. The rule is enforced in code, not left to the model.

Permissions

Users choose what Orin can do in each connected account. For example: read email, but send only with approval and never delete. Permissions can be changed or revoked at any time.

Stablecoin payments

Users pay for Orin in USDC on-chain from day one. Agentic payments, where Orin pays merchants for the user, follow in phase 2.

At launch: paying for Orin

WalletEvery user gets their own non-custodial wallet at sign-in.
Plans in USDCPlans are paid in USDC through a recurring on-chain permission the user grants once and can cancel at any time. Prepaying is also possible.
Pay only on successAn optional small fee on money Orin recovers for the user, such as refunds or lower bills, charged only when it succeeds.
Ready to payWhen a task needs a purchase, Orin prepares everything up to checkout and the user completes the payment themselves.
Verifiable billingEvery payment to Orin is on-chain, so users can check exactly what they paid.

Phase 2: agentic payments

Orin pays merchants on the user's behalf, from a wallet the user tops up, within limits enforced on-chain.

Top up your walletUsers hold USDC in their own smart wallet, created at sign-in, and top it up whenever they like. Other assets can be swapped in, and fiat can be converted through an on-ramp partner.
Asks before spendingBefore any payment, Orin shows the amount, the merchant and the limit it falls under, and waits for the user's OK.
Asks to top upIf the balance is too low for a task, Orin says how much is missing and asks the user to top up. It never adds funds on its own.
Spending limitsThe agent acts through a restricted session key: a maximum per task, a monthly budget, allowed categories and an expiry. Transactions outside these limits are rejected by the contract.
Paying merchantsCrypto-native merchants are paid in USDC directly. Others are paid with a one-time virtual card, funded from USDC for the exact approved amount.
No gas for usersNetwork fees are sponsored, so users never need to hold a gas token.
FreezeOne tap revokes the agent's session key and stops all spending.
Why a topped-up wallet is safer than a card
  • Orin can only spend what is in the wallet, never a full card limit or bank balance.
  • The user's own card number is never handed to the agent or to merchants.
  • Each merchant payment uses a one-time card for the exact approved amount, so it can't be charged again.
  • Limits are enforced on-chain, and one tap freezes everything.

On-chain receipts

Every action gets a fingerprint anyone can check. No personal details go on-chain.

After each action, Orin builds a record: what was done, when, which rule allowed it, and the user's approval signature. The full record is stored encrypted and belongs to the user. Only its fingerprint, a cryptographic hash, is published.

Fingerprints are grouped into batches and anchored on-chain as a single Merkle root. This keeps costs low while letting each user prove that their own receipt is included and has not been changed. Payments made in USDC also link to their on-chain transaction.

What a user can prove That an action happened, when it happened, that they approved it, and that the record has not been edited since.

$ORIN validation network

Independent validators stake $ORIN to check Orin's work. Correct checks earn fees. Wrong ones lose stake.

Before a receipt is final, a group of validators checks the action against three questions. When enough of them agree, they co-sign the receipt and it is anchored.

Orin acts with user approval Validators check 1. Approved? Signature matches the action 2. Within rules? Amount, merchant, limits 3. Happened? Evidence of outcome A quorum must agree before signing Co-signed receipt Anchored on-chain, in batches Validators stake $ORIN Earn fees for correct checks Lose stake for wrong ones
Every action is checked by staked validators before its receipt is anchored.

What validators check

  • Approval. The user's signature matches the exact action taken. Fully automatic.
  • Rules. Amount, merchant and category fall within the user's on-chain limits. Fully automatic.
  • Outcome. Evidence that the action happened, such as a confirmation, matches the request. Checked against fingerprints, never raw personal data.

Rewards and penalties

Validators are paid for each check from a share of Orin's stablecoin revenue. A validator that signs an incorrect receipt, or fails to do its work, loses part of its stake. Slashed stake flows to a protection pool used to refund users when Orin makes a mistake.

Disputes

A user can flag an action, for example "I didn't approve this" or "it booked the wrong date". A larger group of validators reviews the evidence. If Orin was at fault, the user is refunded from the protection pool.

Opening up in stages

The network starts permissioned, with Orin and selected partners running validators. It opens to independent operators once the checks and economics are proven in production.

Token design

$ORIN is a work token for validation. It is not required to use Orin and is not a payment method.

  • Staking to validate. Operating a validator requires staking $ORIN.
  • Accountability. Stake can be slashed for incorrect or missing work.
  • Demand from usage. More tasks need more validation capacity, and so more stake.
  • Separation from payments. Users and merchants transact in stablecoins only.

The parameters below will be set before launch and published with the audited contracts.

ParameterValue
Chain[TBD]
Total supply[TBD]
Allocation (community, validators, team, treasury)[TBD]
Minimum validator stake[TBD]
Share of revenue paid to validators[TBD]
Slashing rates by fault type[TBD]
Unstaking period[TBD]

Privacy and security

Orin earns no money from ads or data, and personal information never goes on-chain.

  • Non-custodial wallets. Users own their wallets. Orin only holds a limited session key that the user can revoke.
  • Encrypted records. Full action records are encrypted and belong to the user.
  • Private validation. Validators work from fingerprints and proofs, or inside secure hardware, so they never see the underlying data.
  • Least access. Each connected account has its own permissions, set by the user.
  • Audits. Smart contracts are audited before mainnet, and findings are published.

Roadmap

Four phases, each building trust before the next.

Phase 1Orin launchApp and web, sign-in with an automatic wallet, plans paid in USDC on-chain, core tasks (cancel, book, check in, follow up, prepare checkouts), approvals, on-chain receipts, voice mode, Telegram.
Phase 2Agentic paymentsOrin pays merchants within on-chain spending limits, with wallet top-ups, one-time cards, refunds, live view of the agent's browser and WhatsApp updates.
Phase 3$ORIN validation, permissionedToken launch after audits, validators run by Orin and partners, protection pool and disputes.
Phase 4Open validation networkIndependent validators, public network stats, a developer marketplace for new skills.

Risks and notices

  • Execution. Websites and services change, and tasks can fail. Orin starts with tasks that have reliable integrations.
  • Regulation. Payments, cards and tokens are regulated differently by country. Orin will seek appropriate licences and legal advice before each launch.
  • Smart contracts. Audited code can still contain bugs. Limits and protection pools reduce, but do not remove, this risk.
  • Network maturity. Validation starts permissioned and decentralizes over time.

This document describes a product and network in development. It is for information only and is not an offer to sell, or a solicitation to buy, any token or security. $ORIN is designed as a utility for operating validators. It carries no rights to profits, dividends or ownership. Nothing here is financial, legal or tax advice. Plans and parameters may change.