The Hypnex Builders subnet

Drop-in OpenAI client.
Paid in MOR.

Hypnex is the subnet building the payments rail for Morpheus agents. Three deliverables — SDK, registry, Forge — all live. Change one import and your existing OpenAI client routes through Morpheus's TEE-backed providers, paid in MOR.

Python
- from openai import OpenAI
+ from hypnex_openai import OpenAI

  client = OpenAI()
  resp = client.chat.completions.create(
      model="llama-3.3-70b",
      messages=[{"role": "user", "content": "ping"}],
  )
Install: pip install hypnex-openai · npm i hypnex-openai
Non-custodial
IPFS-pinned
SIWE only

The Hypnex Builders subnet

The payments rail for Morpheus agents.

Hypnex is the subnet building the payments rail for Morpheus agents. Three deliverables — SDK, registry, Forge — all live.

Stake MOR here if you think agent-to-tool payments are the layer that gets used. Builders V4 rewards depositors proportionally to subnet stake, so the more this thesis plays out, the more your stake earns.

Connect a wallet to stake MOR into the Hypnex subnet. Min 1 MOR. Withdraw any time after 7 days.

Direct from your wallet — no off-site redirect. Hypnex never custodies. Funds go to the Builders V4 contract on your chosen chain. Verified contracts: Arbitrum ↗ · Base ↗.

Three deliverables. One subnet.

01

SDK

OpenAI-compatible client. pip install hypnex-openai, change one line, route inference through Morpheus's TEE-backed providers. The default way an agent plugs into the network.

Read more ↓

02

Registry

On-chain index of agents that consume Morpheus inference. Stable bytes32 ids, capability tags, model routing. Live on Base + Arbitrum.

Read more ↓

03

Forge

Paid tool registry + per-call settlement rail. Agents pre-pay MOR earmarked for a tool; relayer posts signed receipts; on-chain settle() splits 90/10 (tool/protocol). Hard-capped at 20% in bytecode.

Read more ↓

Why deposit MOR into this subnet?

Traction on-chain

Builders V4 subnet TVL · Base 0 MOR verify ↗
Builders V4 subnet TVL · Arbitrum 0 MOR verify ↗
Agents in registry · Arbitrum 0 agents verify ↗
Tools listed on Forge · Arbitrum 0 tools verify ↗
Forge calls settled · Arbitrum escrow 0 calls verify ↗

Numbers update as deposits, agents, tools, and calls come in. Watch them onchain.

Subnet mechanics + contract addresses

Builders V4 lets MOR holders stake MOR into a project's subnet and earn proportional MOR rewards. Pick whichever chain your MOR is on, deposit ≥1 MOR, withdraw any time after 7 days. The subnet IDs and Builders V4 contracts:

Subnet · Base 0x36c36fde5da66f0a1106c17a2f59868071f320c0df7a34ce1ed217ee585f89cc
Builders V4 · Base 0x42BB446eAE6dca7723a9eBdb81EA88aFe77eF4B9
Subnet · Arbitrum 0xf49e6c12044230edf7d651592300618a0e8559a56caac5e078f0c0627d9feb75
Builders V4 · Arbitrum 0xC0eD68f163d44B6e9985F0041fDf6f67c6BCFF3f
Deposit programmatically: pip install hypnex-staking · BuildersClient(chain="base").deposit(sid, amount)

Subnet deliverable 01 · OpenAI-compatible SDK

SDK: drop-in inference client.

The default way an agent plugs into Morpheus inference. Change one import, keep the OpenAI client surface you already write against, and your calls route through Morpheus's TEE-backed providers, paid in MOR. ↑ back to the subnet thesis

Python
- from openai import OpenAI
+ from hypnex_openai import OpenAI

  client = OpenAI()
  resp = client.chat.completions.create(
      model="llama-3.3-70b",
      messages=[{"role": "user", "content": "ping"}],
  )

hypnex-openai · Python

PyPI
pip install hypnex-openai

View on PyPI ↗

hypnex-openai · TypeScript

npm
npm i hypnex-openai

View on npm ↗

Subnet deliverable 02 · Agent registry

Registry: agents discoverable onchain.

Where agents register so tools can find them, and so payments know where to settle. An on-chain index of agents that consume Morpheus inference: stable bytes32 ids, public-by-default records, capability tags, and the model id each agent routes through. Deployed and verified on Arbitrum + Base. MIT-licensed, immutable, no admin keys over the registry itself. ↑ back to the subnet thesis

Registry on Arbitrum

contract
0xCC258a7BBF361fd824e87D4b3C0D394De6Fd454F

Read verified source on Arbiscan ↗

Registry on Base

contract
0xd4D014De1e0D6287BeeD39CD6de99E3A73645ca4

Read verified source on BaseScan ↗

Register an agent: pip install hypnex-registry · npm i hypnex-registry

Subnet deliverable 03 · Paid tool registry

Forge: tools paid per call in MOR.

Where tools get paid per call in MOR. List your MCP server, agentic function, or dataset onchain (1 MOR listing fee). Take per-call payments through a pre-paid MOR escrow: agents deposit MOR earmarked for your tool; tool servers post signed receipts to relayer.hypnex.xyz; on-chain settle() debits the agent at callCount × price with 90% to you and 10% to the Hypnex protocol fee. The fee is admin-settable but hard-capped at 20% in the contract bytecode. Agents get a 24h-delayed self-custody exit so funds can never be trapped by a misbehaving tool. Source-verified on Arbiscan + BaseScan, MIT-licensed. ↑ back to the subnet thesis

Forge on Arbitrum

listing
0xa08ca3C2519DA71e923AD331AFE2989a99f013D2

escrow
0x88E32F332A5140Af16c6273d8131bC84BC089Da5

Read verified escrow on Arbiscan ↗

Forge on Base

listing
0x0c617b36E628b9BE689E3c55Ec901ebDBB8B45aC

escrow
0xCC258a7BBF361fd824e87D4b3C0D394De6Fd454F

Read verified escrow on BaseScan ↗

List a tool: pip install hypnex-forge · npm i hypnex-forge

Capital allocator

Stake stETH, USDC, USDT, or wBTC.
Earn underlying yield + MOR emissions.

Hold yield-bearing assets and want MOR exposure on top? Stake into Morpheus Capital v2 directly from your wallet. Hypnex is just the frontend; your principal stays in the audited Morpheus DepositPool. Same contracts every other Morpheus frontend uses.

Connect a browser wallet to start. Mainnet only.

No extra lock, no fees from Hypnex. Deposits route through the audited Morpheus DepositPool with the Hypnex Labs referrer address 0x22B5C0…57D8.

The detail nobody mentions

Your own staked MOR is locked for 90 days after each deposit. Your referral MOR is unlocked. Refer one staker, earn liquid MOR for as long as the referee keeps their stake. How the referral mechanic works ↗

Or skip the form, use the SDK: pip install hypnex-openai · npm i hypnex-openai

vs app.mor.org

Same contracts. Different frontend.

Both interact with Morpheus Capital v2 directly. The smart-contract trust assumption is identical. The differences are in the frontend layer.

app.mor.org
hypnex.xyz
Auth
AWS Cognito + email signup
Sign-In With Ethereum
Hosting
AWS Amplify (centralized)
IPFS-pinned, Cloudflare Pages edge
Funds custody
Non-custodial (Morpheus contracts)
Non-custodial (same contracts)
Referral surface
Hidden / not surfaced in UI
Front-and-centre, referral mechanic explained
Source
Open repo, AWS-coupled
MIT, self-hostable, no AWS
Maturity & community
Reference frontend, broad community, longest live
Newer, smaller community, narrower focus
Dashboards & analytics
Full builders + capital dashboards, deeper docs
Stake form + SDK; defers analytics to mor.org / DefiLlama

Last two rows: where app.mor.org is the better tool. Pick whichever frontend matches your use case — your stake lives in the same on-chain contracts either way.

How it works

Aave-wrapped capital, Chainlink-normalized yield, MOR emissions on top.

Four steps from connected wallet to claimable MOR.

01
Connect. Sign a SIWE message. No signup.
02
Pick an asset. stETH, USDC, USDT, or wBTC.
03
Stake. stETH stakes earn Lido yield directly. USDC, USDT, and wBTC are supplied to Aave to earn lending interest. Chainlink price feeds (via the on-chain ChainLinkDataConsumer) normalize cross-asset value so MOR emissions distribute fairly across pools. Your principal stays in the Morpheus DepositPool contract on Ethereum mainnet. Hypnex never touches it.
04
Claim. After the 90-day claim lock opens, claim MOR, or commit a voluntary additional lock to earn a Power Factor multiplier on emissions. MOR is a LayerZero OFT (Omnichain Fungible Token), so the same balance moves natively between Ethereum, Arbitrum, and Base. Current Power Factor curve on gitbook.mor.org.
Contracts (9)
DistributorV2 (Ethereum) 0xDf1AC1AC255d91F5f4B1E3B4Aef57c5350F64C7A
USDC DepositPool 0x6cCE082851Add4c535352f596662521B4De4750E
USDT DepositPool 0x3B51989212BEdaB926794D6bf8e9E991218cf116
wBTC DepositPool 0xdE283F8309Fd1AA46c95d299f6B8310716277A42
wETH DepositPool 0x9380d72aBbD6e0Cc45095A2Ef8c2CA87d77Cb384
ChainLinkDataConsumer 0xd182263d06FDC463c96190005D6359CC3d3Bbc5e
MOR (Ethereum) 0xcBB8f1BDA10b9696c57E13BC128Fe674769DCEc0
MOR (Arbitrum) 0x092baadb7def4c3981454dd9c0a0d7ff07bcfc86
MOR (Base) 0x7431aDa8a591C955a994a21710752EF9b882b8e3
Honest economics

No hype. Just the math.

Sourced from Morpheus's own documentation and on-chain emissions. The numbers below are illustrative. Verify the live values on mor.org and DefiLlama before staking. As of 2026-05-10.

Total daily emission (decays linearly to zero ~2040) ~12,600 MOR / day
Capital pool share of daily emission ~3,150 MOR / day
Hard cap on MOR supply 42,000,000 MOR
Capital claim lock from deposit 90 days
Referrer MOR unlocked, immediate
Referee bonus on own emissions +1%
Referrer tiers (thresholds in stETH-equivalent) 3% · 5% · 10% · 15%

Yield depends on total TVL — lower TVL means higher MOR per dollar staked, higher TVL means lower. We do not promise an APR. We promise you'll see the same on-chain emissions as everyone else, through wallet transactions instead of an account, with the referral mechanic surfaced front-and-centre. Live numbers on mor.org.

FAQ

The questions you should be asking.

No KYC, no custody, no marketing fluff. Just the mechanics.

What is the Power Factor multiplier?
A voluntary lock multiplier on your MOR claim. Commit a longer additional lock period, get a higher multiplier on emissions. Claiming immediately means 1×. The exact multiplier curve is defined in the Distribution contract; see gitbook.mor.org for current parameters. Trade-off: shorter horizon = liquid MOR sooner, longer horizon = more MOR but illiquid.
Why does the referrer get unlocked MOR while the staker waits 90 days?
Per Morpheus's referral protocol, referral rewards bypass the 90-day claim-lock that capital contributors face. The protocol's reasoning: referrers do off-chain work (education, evangelism) that doesn't carry the same lockup risk as principal-providing capital. Result: referring is the most liquid, lowest-friction way to earn MOR on the network.
Do I need to register as a referrer? Is there KYC?
No. Per Morpheus docs, any wallet address can be used as a referral address with no separate registration. There is no KYC, no whitelist, and no off-chain step. The referrer parameter is a public argument on DepositPool.stake().
Is Hypnex custodying my assets?
No. Funds go directly into Morpheus's audited DepositPool contracts on Ethereum mainnet. Hypnex is a frontend that constructs the transaction. We never hold a key to your funds.
What happens if Hypnex disappears?
Your stake is in Morpheus contracts and is unaffected. You can claim, withdraw, or interact with the protocol via Etherscan, dashboard.mor.org, or any other frontend. The IPFS-pinned version of this UI also remains resolvable independent of our domain.
How is the underlying yield generated?
stETH stakes earn Lido staking yield directly. USDC, USDT, and wBTC are supplied to Aave to earn lending interest. Chainlink price feeds (via the on-chain ChainLinkDataConsumer contract at 0xd182263d…3Bbc5e) normalize cross-asset value so emissions distribute proportionally across pools. MOR rewards are paid on top of underlying yield, not instead of it. Source: DistributorV2.sol.
Has this been audited?
Yes. The Morpheus Capital v2 / Aave Distributor smart contracts went through a Code4rena audit Aug 15–25, 2025 (6 contracts, 390 lines of Solidity, 4 medium-severity findings, 26 low/non-critical). Full report: code4rena.com/reports/2025-08-morpheus. Hypnex itself is a frontend that constructs transactions — it never holds funds — but the contracts you sign into are the ones audited.