Stuck? We've got you.

Open the app, tap Create a wallet, and let it generate a private key for you. You'll then need a small amount of MOR (the Morpheus network token) and a tiny amount of ETH on the Base network to chat. Two paths:

• If you already have crypto: copy your new wallet address from the home screen and send some MOR + ETH to it.
• If you don't: read the New to crypto? walkthrough — it covers the calmest path from zero to your first chat in about 25 minutes.

Once your wallet has MOR and ETH, tap any model on the home screen to start chatting.

MOR is your perpetual access stake — you lock a small amount per chat session and it returns to your wallet when the session closes. ETH pays the network gas fees for opening and closing those sessions on the Base blockchain, typically a fraction of a cent per session.

Roughly: a few dollars of ETH lasts hundreds of sessions; the MOR stake size depends on which model you pick and how long you chat. The Why Node Neo? page explains the "library card" framing in detail.

No. Node Neo is a self-custodial client for a decentralized inference network. The wallet is what pays providers and proves you opened a session — it's not optional. The good news: the wallet is generated automatically on first launch, you don't have to set up anything externally.

Today: iOS (iPhone, iOS 16+) via the App Store and macOS (Apple Silicon and Intel) via DMG download from our GitHub Releases page. iPad, Android, and Linux are on the roadmap.

Open Settings → Backup & Reset → Export and save the encrypted .nnbak file somewhere safe (iCloud Drive, an external drive, a password manager attachment). The backup is encrypted with a passphrase you choose; without that passphrase the file cannot be restored.

You can also use Settings → Wallet → Export Private Key to copy the raw private key — useful for restoring into MetaMask, Rainbow, or any other self-custody wallet.

No. This is the trade-off you make for self-custody — we have no copy of your key, and there is no recovery mechanism on our side. If you lost the key and don't have a backup, the funds in that wallet are permanently inaccessible.

Your future option: create a new wallet inside Node Neo (Settings → Backup & Reset → Erase Wallet, then go through onboarding again), back it up immediately, and start fresh.

No. Blockchain transactions are irreversible by design. Once a transaction is confirmed on the Base network, only the recipient can return the funds — we cannot retrieve them and neither can the network operators.

If you sent to a wallet you control on a different chain (e.g., you accidentally sent to your Ethereum mainnet wallet instead of your Base wallet), tools like a bridge may let you move them back. If you sent to someone else's address, your only path is to reach out to that person directly.

Yes — but indirectly. Node Neo manages its own wallet, and you import a private key on first launch. To use a key from MetaMask: in MetaMask, Account → Account Details → Show Private Key, copy it, then in Node Neo onboarding tap I have a private key and paste it.

The same address can be used in multiple wallets at the same time — nothing conflicts. You'll see the same balance in MetaMask and Node Neo simultaneously.

The New to crypto? page covers this in detail. Short version: buy about $7–$10 of ETH on Base through Coinbase Wallet, MoonPay, or Coinbase, send it to your Node Neo wallet address, then swap most of it for MOR via Uniswap on Base. Total cost including fees: ~$10. Time: about 25 minutes the first time.

For your first chat, try a general-purpose model like GLM-4.6 or Qwen3 — they handle most everyday tasks well and have lower stake requirements. As you get comfortable, try the Max Privacy (TEE-attested) models for sensitive prompts, or coding-focused models like Qwen3-Coder for technical work.

You can switch models any time — each session is independent and there's no account to migrate.

Max Privacy models run inside a Trusted Execution Environment (TEE) on the provider's hardware, with their runtime cryptographically attested before the session opens. This gives a hardware-level guarantee that the provider cannot read or log your prompt — the model executes in a sealed enclave that even the provider's operators can't introspect.

For non-TEE models, your prompt is sent to the provider in cleartext over TLS. The provider could log it; whether they do is a function of their privacy policy. For anything sensitive, prefer Max Privacy.

A few possibilities, in order of likelihood:

• You hit the stop button (the amber square in the chat composer).
• Your network dropped briefly — the chat will show an offline banner if so. Reconnect and tap retry.
• The session timed out — sessions have a configured duration (default 1 hour). Open a fresh session and continue.
• The provider had a transient issue — try again. If a specific provider keeps failing, switch to a different model and the protocol will route you to a different provider.

The MOR you stake is locked, not spent — it returns to your wallet when the session closes. The actual cost per session is two things:

• ETH gas for opening and closing the session on Base: typically a fraction of a cent.
• Provider yield: a small portion of your staked MOR is paid to the provider over the session duration.

The pre-session confirmation modal shows you the exact stake size and duration before you commit, so there are no surprises. If you can't afford a model, it shows up greyed out on the home screen.

Yes — conversations are included in the encrypted .nnbak file produced by Settings → Backup & Reset → Export. Restore the same backup on another device to bring your chat history with you. Direct export of individual conversations as text or markdown is on the roadmap.

No. Zero analytics, zero telemetry, zero crash reporting. The app does not include any first-party or third-party SDK that sends data to us. The full breakdown is in the Privacy Policy.

On iOS and macOS, Apple's Keychain survives an app uninstall by default — that's fumble-finger protection for password managers, but for a crypto wallet it's the wrong default. Node Neo includes a FirstLaunchGuard that detects the first run after install and proactively wipes any wallet keys left in Keychain, so a reinstall always starts truly fresh.

If you're still seeing your old wallet on a fresh install, contact us — that's a bug we want to know about immediately.

Settings → Backup & Reset → Full Factory Reset, type DELETE ALL to confirm, then uninstall the app. The factory reset wipes your wallet key, all conversations, all settings, and all logs. Uninstalling removes the data directory itself.

Because we never had a copy on our side, that's all there is to delete — nothing remains anywhere we control.

The app is online but couldn't reach the Base blockchain RPC endpoint. Two common causes:

• Public RPC is rate-limited or down right now — rare but happens. Tap Try Again; the app rotates through several public endpoints.
• You set a custom RPC that's broken — check Settings → Network → Edit blockchain endpoint. If unsure, clear the custom value to fall back to defaults.

The app runs a quick DNS probe on launch (against cloudflare.com and friends). If the probe times out, this screen appears. Likely causes:

• You're on a restricted captive portal (hotel/airport WiFi) that hasn't been signed into yet — open Safari and load any page to trigger the captive portal sign-in, then return to Node Neo.
• Your VPN or DNS-over-HTTPS provider is blocking the lookup.
• You disabled cellular data for Node Neo specifically (iOS: Settings → Cellular → Node Neo).

If you're on an iPhone 13/14/15/16/17 Pro running iOS 26, you may be hitting a known Flutter framework issue (the implicit-engine VSyncClient crash). Make sure you're on the latest Node Neo release — we shipped a workaround in v3.3.0.

If you're already on the latest version: force-quit the app, reboot your device once, then reopen. If it still hangs, contact us with your iOS version and device model.

Settings → Version & Logs shows the recent log output, log file location, and a log-level switch (set to Debug for verbose tracing during a troubleshooting session). The logs are local-only — nothing is uploaded automatically. When you open a support email, attaching a copy of the log usually shortens the back-and-forth.