Skip to content
Morphit
Start

Run a Morphit node

Operate your own instance. Earn 90% of the BLURT paid listing fees. Help make Morphit unstoppable.

Claim your operator tag

Operator registration is permissionless. Broadcast a one-time op to claim a tag on-chain — first-come-first-served. This tag appears in orders placed through your instance and in the /operators directory. Your posting key signs the op, so only you control your tag.

Sign in with your Morphit account to register as an operator.

Sign in

Why run a node?

  • Morphit where it matters

    Every additional node makes the network harder to censor. If your country blocks morphit.io, your instance stays reachable. You serve users who'd otherwise have no way to trade.

  • Serve your community

    Brand the interface for your region, your language, your local payment methods. Users trust frontends that speak their language and feel familiar — yours will.

  • Minimize metadata leakage

    Users trading through your instance share metadata with you and only you. No other operator, not even Agorise, sees their activity patterns.

    Encourage users to use a VPN and your (included) Tor and/or I2P addresses. Your alternate, hidden addresses let users reach your instance from jurisdictions where clearnet access is blocked. No SSL/https certificates are needed either and the impact is enormous for users in censored networks and countries.

  • Paid automatically by Smart Contract

    Every BLURT-paid listing fee your instance attracts pays you 90% — only 10% goes to the Morphit treasury to fund the furthering development and maintenance of the Morphit software itself. BTC- and XMR-paid fees flow 100% to the treasury for the same project obligations (the on-chain split mechanism only works for BLURT, but we made the BLURT split aggressively generous to compensate — 90/10 in your favor). A Smart Contract running on the blockchain enforces the split — not a person, not a company, not anyone who can change their mind. 100% automated. You provably assist, you provably get paid. Guaranteed in code. Payouts are denominated in BLURT, so if BLURT appreciates, so do your earnings — without any additional work on your part.

How to get started

  1. 1

    Get a machine and a web address

    A cheap VPS or an old PC/laptop running Ubuntu — aim for 4 GB of RAM or more (8 GB is comfy) and 80 GB of disk. A Raspberry Pi 4 works too. Add a domain name (about $10/year) from any registrar and point it at the machine. Hosting from home? No static IP needed — the setup wizard turns on dynamic-DNS for you. See the FAQ on minimum hardware for the full breakdown.

  2. 2

    Run one command

    Download the latest release, extract it into a /morphit/ folder, open a terminal there, and run sudo bash morphit-setup.sh — then choose "Full guided install." A short wizard asks a few plain-language questions (your domain, your Blurt account, an email for HTTPS) and sets up everything for you: Node.js, PostgreSQL, the app and its services, auto-renewing HTTPS, the firewall, and your Tor and I2P addresses. No files to edit.

  3. 3

    Register as an operator

    Run npx morphit-ops register to claim your tag on-chain, first-come first-served. Your instance appears in the /operators directory and starts earning your 90% share of Blurt-paid listing fees automatically, delivered on-chain. See the operator-earnings FAQ for the economics.

First time? If you've never set up a server before, start with the friendly walkthrough at RUN-A-MORPHIT-NODE.md.

Your instance, your asset policy

Morphit's federation lets each operator pick which tradable assets their instance accepts new orders for. New assets ship default-ON instance-wide — operators opt out per-asset via the `MORPHIT_INDEXER_DISABLED_ASSETS` environment variable. This is how a federation of instances can serve different user preferences without anyone needing to fork the code.

  • Default-on for new assets. When the project adds a new tradable asset (USDT shipped most recently), every instance accepts orders for it the moment they upgrade. No code change, no per-asset enablement step.
  • One env var to refuse. Operators who prefer their instance specializes in privacy-first or decentralization-first assets can disable any trade-only asset with `MORPHIT_INDEXER_DISABLED_ASSETS="USDT"` (or a comma-separated list for multiple). Users posting through this operator's frontend then can't pick a disabled asset.
  • Federation stays intact. Disabling an asset on your instance doesn't hide peer instances' orders from your users — chain history is shared, so the orderbook still surfaces them as read-only. The gate is only on NEW orders posted FROM your instance.

Resource requirements

Hardware
2+ CPUs, 4+ GB RAM, 80+ GB drive space (SSD is best)
Network
Home internet works fine — DDNS handles dynamic IPs, no static IP required
Your time
Under 15 minutes monthly for checking on your relay balance, claiming your income, etc

Ready to begin?

Clone the repo, set up your hardware (a Pi 4 or any old laptop will do), follow the runbook. Once you broadcast the operator-register op your instance is live and earning.

See the repo Browse operators