Buy MOR
OverviewModelsDocs
mor.orgapp.mor.org

From Promises to Proofs

How MorpheusAIs moves AI inference from operator integrity to hardware-enforced guarantees — verifiable by anyone, trusted by no one.

Step 1 — Choose your access path

Max Privacy

MorpheusAIs

The decentralized protocol

Run your own local C-Node (consumer node)

Identity is wallet address only — no email, no signup

Stake MOR to earn inference credits on-chain

Sessions routed via smart contracts — P2P

Your C-Node verifies TEE attestation directly

No centralized intermediary touches your prompts

Pipeline: Consumer -> Local C-Node -> Blockchain -> P-Node -> LLM

Convenience

API Gateway

A separate product — centralized access layer

Sign up with email (AWS Cognito)

Create an API key — gateway knows your identity

Centralized C-Node managed by the gateway operator

Cannot currently attest that the gateway does not log prompts

Pay with Stripe / crypto — no MOR staking required

Easy onramp — standard REST API, familiar DX

Pipeline: Consumer -> API Gateway (email/key) -> Centralized C-Node -> P-Node -> LLM

Step 2 — Choose the TEE maturity phase

Privacy Properties (MorpheusAIs path — local C-Node -> TEE provider)

Permissionless

100%

Native web3 — anyone can provide or consume

Anonymous

100%

Wallet-only — no KYC, no email, no signup

Decentralized

100%

P2P smart-contract routing, no central authority

Open Source

100%

Cosign + SBOM + RTMR3 — fully verifiable

Private

82%

Hardware-enforced CPU; external LLM gap

v6.0 — Shipped

TEE Phase 1 — Pipeline + CPU Attestation

Hardware-enforced isolation. The P-Node operator cannot access memory, attach debuggers, or modify the running image. Cryptographic attestation proves what's running — to anyone who asks.

Maximum privacy with TEE Phase 1

Run your own local C-Node (v6.0.0 or higher) and stake your own MOR for inference. Your C-Node verifies the TEE attestation quote directly against the CI/CD-published golden values — no centralized intermediary ever sees your prompts. Download C-Node.

Inference Pipeline — MorpheusAIs (hardware-attested)

Your Control

Consumer

wallet only

->

Local C-Node

v6.0+ TEE-aware

- encrypted session ->

C-Node checks before session

Blockchain

MOR

GHCR

golden

TDX Quote

TLS bind

Hardware-enforced boundary

TEE P-Node

SecretVM

->

LLM

outside TEE

CI/CD Supply Chain (signed + attested)

Open-source build

Source

GitHub

->

Build

Actions

->

Cryptographically signed

Cosign

Sigstore

->

RTMR3

computed

->

GHCR

manifest

What changed

P-Node runs inside Intel TDX / AMD SEV. Memory is hardware-encrypted. No SSH. Image is cosign-signed, digest-pinned, measured into RTMR3. Your local C-Node verifies the hardware attestation quote against the CI/CD-published manifest before opening a session. TLS cert fingerprint bound to quote (anti-spoofing). No centralized party is involved.

Per-prompt re-verification (v6.2+): After the initial full attestation, every subsequent prompt re-fetches the quote and TLS fingerprint from the provider. If the quote hash or TLS cert changes mid-session (image swap, VM restart, DNS hijack), the prompt is blocked. ~50–150ms overhead, no external API call on the fast path.

Remaining gap: If the P-Node calls an external LLM API, that hop leaves the TEE boundary. Phase 2 closes this.

Inference Pipeline — API Gateway (TEE providers)

Identity known

Consumer

email + API key

->

API Gateway

Cognito

->

Central C-Node

managed

- TLS ->

TEE provider

GHCR

golden

TDX Quote

TLS bind

TEE P-Node

SecretVM

LLM

outside TEE

API Gateway with TEE providers

The P-Node side gains the same TEE protections — hardware attestation, no operator access. But the gateway layer is not attested. You sign up with email, authenticate with an API key, and your prompts pass through a centralized C-Node managed by the gateway operator. We do not log prompts, but we cannot cryptographically prove that today. Bottom line: TEE protects you from the provider. It does not protect you from the gateway. For maximum privacy, use your own local C-Node.

Progression Summary (MorpheusAIs — local C-Node -> TEE provider)

Any provider

Pre-TEE MorpheusAIs

88%

Privacy Score

  • Permissionless (native web3)
  • Anonymous (wallet only)
  • Fully decentralized routing
  • Open-source code
  • Encrypted transport (MOR-RPC)
  • Operator could log — no proof
  • CI/CD not yet hardened
TEE provider

TEE Phase 1 (CPU)

96%

Privacy Score

  • Permissionless (native web3)
  • Anonymous (wallet only)
  • Fully decentralized routing
  • Verifiable build (cosign + SBOM)
  • Operator CANNOT log
  • Hardware attestation (CPU)
  • External LLM gap
TEE + GPU provider

TEE Phase 2 (GPU)

~100%*

Privacy Score

  • Pseudonymous (wallet only)
  • RA-TLS end-to-end
  • Open-source + verifiable build
  • Decentralized routing
  • Operator CANNOT log
  • CPU + GPU attestation
  • Per-message signing

Privacy scores assume the MorpheusAIs path (local C-Node, wallet-only identity) connecting to a TEE-tagged provider. Non-TEE providers remain available on the marketplace — their trust model stays at Pre-TEE levels regardless of phase. Using the API Gateway reduces anonymity and decentralization scores — the gateway knows your email and API key, and prompts transit a centralized C-Node.

The first decentralized AI where privacy isn't a policy — it's physics.

Run your own C-Node. Stake your own MOR. Verify the TEE yourself. No trust required.

Run Your Own C-NodeTEE Provider Setup (P-Node)API Gateway (app.mor.org)
mor.org

·

app.mor.org

·

GitHub

·

Discord

MorpheusAIs Compute Marketplace · Confidential AI inference with cryptographic attestation.