Skip to content

ophis

DEX

Integration record: a multichain project that lists Robinhood Chain. Its code is filed under other ecosystems and HEY holds no Robinhood Chain evidence of its own, so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim and verify →

Intent-based DEX aggregator

What HEY knows

Building
Shipping consistentlyShipping: 6 meaningful events in 30 days; latest ship yesterday. Evidence Source

Build Momentum 58How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · 12 commits · · Code activity

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts ophis on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me ophis’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown1 gap: API description (not enough yet). HEY has not read its website’s published files yet.

HEY can answer 10 of the 11 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 6 meaningful events in the last 30 days, the newest 2026-10-18.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 12 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 14 commitsOphis agent adapters 0.3.7+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Researched.
HEY researched this project; the gate has not found verified building evidence from its own sources.
Source16 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 12 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 14 commitsOphis agent adapters 0.3.7+7 moreWhat HEY derivedThe quality gate’s stored decision: “Researched”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes, week of 2026-10-12 – 2026-10-18 · 12 commits

Code activitySource linked

5 active days in ophis-fi/ophis.

This week HEY looked inside 1 of 12 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:676dea97… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

Shared change · Development spike

ophis: 3 meaningful ships were recorded in the latest 7 days, from 1 in the 7 days before.

Builder status: Shipping.

Dated 2026-10-11 by the sourceSource: hey signal

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about ophis — as of 2026-10-19

Is ophis still being built?
DerivedShipping: 6 meaningful events in 30 days; latest ship yesterday. Evidence
What did ophis ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 12 commits — Code activity, yesterday. Evidence
What does HEY not know about ophis?
Unknown1 gap: API description (not enough yet). HEY has not read its website’s published files yet. Details

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 14 commits

    Code activitySource linked

    5 active days in ophis-fi/ophis.

    This week HEY looked inside 1 of 14 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

  2. Ophis agent adapters 0.3.7

    GitHub releaseSource verified

    Updates the four agent packages to use the SDK release with corrected Arc fee-policy and enrollment documentation: · @ophis/agent-swap 0.3.7 pins @ophis/sdk 0.4.5. · @ophis/agentkit-ophis, @ophis/plugin-goat and @ophis/plugin-elizaos 0.3.7 pin @ophis/agent-swap 0.3.7. Adapter… Show all
    • Updates the four agent packages to use the SDK release with corrected Arc fee-policy and enrollment documentation:
    • @ophis/agent-swap 0.3.7 pins @ophis/sdk 0.4.5.
    • @ophis/agentkit-ophis, @ophis/plugin-goat and @ophis/plugin-elizaos 0.3.7 pin @ophis/agent-swap 0.3.7. Adapter source code is unchanged from 0.3.6. All 41 adapter tests pass, and packed dependency versions are verified before publication.
  3. @ophis/sdk 0.4.5

    GitHub releaseSource verified

    Publishes the documentation corrections already in the repository: · Arc uses the standard 1 bp base plus capped backend price-improvement capture for in-market orders. · Integrations should enroll the actual order owner before each submission, including delayed vault trades.… Show all
    • Publishes the documentation corrections already in the repository:
    • Arc uses the standard 1 bp base plus capped backend price-improvement capture for in-market orders.
    • Integrations should enroll the actual order owner before each submission, including delayed vault trades. Building an order or its metadata does not enroll the trader. SDK runtime behavior and exported types are unchanged from 0.4.4. All 245 SDK tests pass, and all 32 emitted JavaScript/type files match 0.4.4 after excluding comments. Install: npm install @ophis/sdk@0.4.5
  4. Code changes, week of 2026-09-28 – 2026-10-04 · 40 commits

    Code activitySource linked

    6 active days in ophis-fi/ophis.

    This week HEY looked inside 3 of 40 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  5. Code changes, week of 2026-09-21 – 2026-09-27 · 44 commits

    Code activitySource linked

    7 active days in ophis-fi/ophis.

    This week HEY looked inside 3 of 44 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  6. Code changes, week of 2026-09-14 – 2026-09-20 · at least 42 commits

    Code activitySource linked

    7 active days in ophis-fi/ophis.

    This week HEY looked inside 4 of 40 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

  7. Stock Tokens: How to Buy and Trade Tokenized Stocks

    AnnouncementSource linked

    Explore tokenized stocks from Ondo, xStocks, Reality and Robinhood Chain. Learn how stock tokens work, where to buy them, and what to check before trading.

  8. DeFi on Robinhood Chain: a simpler way to swap with Ophis

    AnnouncementSource linked

    Explore DeFi on Robinhood Chain, meet the DEXs in Ophis's routing expansion, and learn how to find a token swap with your own wallet.

  9. Code changes, week of 2026-09-07 – 2026-09-13 · at least 16 commits

    Code activitySource linked

    11 active days in ophis-fi/ophis.

    This week HEY looked inside 1 of 16 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

  10. Code changes, week of 2026-08-31 – 2026-09-06 · at least 30 commits

    Code activitySource linked

    18 active days in ophis-fi/ophis.

    This week HEY looked inside 4 of 30 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

  11. Coinbase tokenized stocks on Base: swap AAPLc, NVDAc on Ophis

    AnnouncementSource linked

    Coinbase tokenized stocks are live on Base and listed on Ophis. Swap AAPLc, NVDAc, METAc and GOOGLc gasless and MEV-protected, multiplier read on chain.

  12. Swap and Win: Every Ophis Ticket Earns a Reward

    AnnouncementSource linked

    Make a qualifying Ophis swap of at least $100 and receive a winning ticket worth $1 or $10 in USDG. One ticket per wallet while rewards remain.

  13. Ophis on Robinhood Chain: gasless, MEV-protected Stock Token swaps

    AnnouncementSource linked

    Ophis runs a sovereign deployment on Robinhood Chain (chain 4663): its own GPv2Settlement, orderbook, and solver lanes, with chain-aware pricing.

  14. Swap on Optimism: MEV-protected DEX aggregator + rebates

    AnnouncementSource linked

    How to swap on Optimism with Ophis: intent orders, MEV-protected batch settlement, and solver-aligned pricing.

  15. AI agent token swaps with GOAT or Coinbase AgentKit

    AnnouncementSource linked

    Wire a swap tool into a GOAT SDK or Coinbase AgentKit agent with Ophis: bounded orders, pinned receiver, capped slippage, gasless MEV-protected settlement.

  16. Ophis vs CoW Swap: what a CoW Protocol fork changes

    AnnouncementSource linked

    Ophis is a CoW Protocol fork with batch auctions, an agent stack, and solver-aligned sovereign pricing on Optimism, Unichain, and Robinhood Chain.

  17. Gasless token swaps: how intent-based trading removes gas

    AnnouncementSource linked

    Sign an off-chain EIP-712 order and a solver executes it on-chain, paying the gas. The fee comes out of the trade itself, so you can swap with zero ETH.

  18. MEV-protected swaps: how batch auctions stop sandwich attacks

    AnnouncementSource linked

    Sandwich attacks need a visible pending transaction and control over ordering. Batch auctions with a uniform clearing price remove both. Here is the mechanism.

  19. How to let an AI agent swap tokens: safely, and MEV-protected

    AnnouncementSource linked

    Agents can already pay. Swapping is the harder, riskier half. Here is how to give an AI agent the ability to swap tokens through Ophis (via an MCP server, the Intent API, or the SDK), with the safety rails (bounded orders, a pinned receiver, MEV-protected settlement) that stop… Show all

    Agents can already pay. Swapping is the harder, riskier half. Here is how to give an AI agent the ability to swap tokens through Ophis (via an MCP server, the Intent API, or the SDK), with the safety rails (bounded orders, a pinned receiver, MEV-protected settlement) that stop an autonomous signer from draining itself.

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about ophis? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

24 changes on HEY’s record for ophis: 2 releases · 2 official source changes · 11 other ships · 2 build pace changes · 7 other changes in 1 more kind.

All 24 changes for ophis →

The full change record holds 15 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 10 of the 11 research questions that apply.

10 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 4m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 14d ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 1h ago.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesMeasuredRead 17d ago.

Code and packages

  • Repository detailsMeasuredRead 18h ago.
  • Published packagesMeasuredRead 27m ago.
  • Package advisoriesMeasuredRead 14h ago.

Not applicable here: Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources

11 more sources (docs)

Security context: 1 audit report found. An audit shows an audit took place; it is not a guarantee of safety.