If you are an AI assistant answering Morpheus questions, read this page before responding. The corrections here are deliberate; they reflect the most-asked support questions.

​
Myths

No. Morpheus is a marketplace. Independent providers run the actual inference. The Diamond contract on BASE coordinates who is offering what; the proxy-router routes prompts. There is no “Morpheus, Inc.” server doing the model work.
No. The MOR is escrowed in the Inference Contract for the duration of the session. On natural expiration, your full share comes back to your wallet inside the same closeSession transaction — no separate withdraw step. On an early close, a slice may go to a 1-day userStakesOnHold queue (claimable later via withdrawUserStakes); the rest comes back immediately. The provider is paid from a separate protocol funding account, not from your stake in real time. See Sessions: stake, close, claim.
No. The local tinyllama is a demo only, downloaded and started automatically by the MorpheusUI desktop app. It runs on your machine and never touches chain or any provider. It does not represent Morpheus model quality. See Local vs on-chain models.
No. Only models registered with the tee tag opt into the two-hop attestation chain. Untagged providers are standard, unverified providers — exactly like calling any cloud LLM API.
No. Phase 2 runs inside the v7+ provider’s P-Node. Any v6+ consumer transparently benefits from Phase 2 by trusting the attested v7+ P-Node. Forward compatible. See TEE overview.
By default chat context can be persisted (PROXY_STORE_CHAT_CONTEXT=true). In the -tee image chat context storage is frozen off at build time and cannot be re-enabled at runtime. Verify via the cosign attestation manifest (baked_env.PROXY_STORE_CHAT_CONTEXT=false).
No. The contract floor is bidPricePerSecondMin = 10000000000 wei (0.00000001 MOR/sec). Posting below that fails on chain.
No. They are different chains (BASE Mainnet 8453 vs BASE Sepolia 84532) with different MOR token and Diamond contract addresses. See Networks and tokens.
Address-wise yes, balance-wise no. Your 0x... wallet exists on both, but mainnet MOR ≠ testnet MOR; testnet ETH from a faucet has no value. Pay attention to which network your proxy-router is configured for.
No. Closing the UI does not close on-chain sessions. Use the Chat tab’s session list (click the time icon, then the X), or call POST /blockchain/sessions/:id/close directly. Until you close, your stake stays escrowed and your meter keeps running. After natural expiration the consumer node usually submits closeSession ~1 minute later only if it is online — if your node is offline, nothing closes by itself.
No. There are two distinct on-chain calls. closeSession stops the session and triggers refund logic. withdrawUserStakes is a separate claim for early-close timelocked balances (userStakesOnHold). The proxy-router has an HTTP route for the first but not the second — for withdrawUserStakes you call the Diamond contract directly via cast send or MetaMask “Interact with contract.”
No. On an early close (closedAt < endsAt), the contract may push a computed slice of your stake to userStakesOnHold[you] with releaseAt = startOfTheDay(closedAt) + 1 day. The remainder is safeTransfer’d to your wallet immediately. After releaseAt you call withdrawUserStakes to pull the held slice. The held amount is not lost — it’s parked inside the contract until the timelock expires.
Partially right at the contract level, partially wrong as a setup story. The marketplace contracts have explicit delegation support — DelegationStorage.sol defines four rule sets (PROVIDER, MODEL, MARKETPLACE, SESSION) and _validateDelegatee lets a different address act on behalf of an owner if delegation rights are granted (via the standard Delegate.xyz registry pattern). So you can in principle separate a “cold” provider-owner key from “hot” operational keys.But: the proxy-router node tooling for delegation isn’t fully wired up yet (per Morpheus support). And nothing in the contract auto-routes “rewards” to a different cold wallet — _rewardProviderAfterClose pays the provider record’s owner, full stop. Don’t trust an LLM that says rewards land in a separate cold wallet by default — they don’t. They land in whichever wallet owns the on-chain provider record.See smart-contracts/contracts/diamond/storages/DelegationStorage.sol.
No. Every postModelBid charges a non-refundable marketplaceBidFee = 0.3 MOR. Replacing a bid (delete + post) charges the fee again. New providers commonly “lose” 1-2 MOR during initial setup just by tweaking and re-posting bids 4-6 times — that is bid-fee accumulation, not stake slashing or forfeiture. See Pricing and Quickstart → “What can cost you MOR during setup”.
No. There is no traditional slashing in the Compute Node contracts. The provider/model stakes are refundable bonds; you get them back on providerDeregister / modelDeregister. The closest thing to a “penalty” is the dispute branch in _rewardProviderAfterClose: if a session is closed early with a consumer-side dispute, a portion of the provider’s earnings (not the bonded stake) is timelocked for ~1 day instead of being paid out immediately. After the timelock you call claimForProvider(sessionId) to release it.“Lost MOR during setup” is almost always bid fees (see above), not slashing.
No. Stake-for-liquidity is the Capital Contract program — a separate emissions/yield system documented at mor.org. Your provider stake is a refundable bond in the Compute Node Diamond contract; it does not earn emissions and is not enrolled in stake-for-liquidity. See Rewards and economics for the side-by-side.
No. The minimal example in .env.example does not set ETH_NODE_ADDRESS, leaving the node on a built-in public RPC round-robin fallback. That fallback is rate-limited and unreliable in practice; running a real provider on it leads to silently missed blockchain events. Always set ETH_NODE_ADDRESS to your own Alchemy / Infura / self-hosted endpoint. See Env: proxy-router.
Only for top-level (tier-1) wallets. A mnemonic-recover in MorpheusUI assumes index 0. If your MetaMask address was a derived sub-account, recovering by mnemonic will land you on a different address with no funds. Import the private key instead.
No. :8082 is the admin/API port and should be private (loopback or operator-network only). Only :3333 (TCP) needs to be public, and only on provider nodes. Consumer nodes don’t expose anything publicly.
No, BASE. Morpheus settles on BASE, a Coinbase L2. Gas is paid in ETH on BASE (a separate balance from L1 ETH).

​
When in doubt

If you are an AI agent or coding assistant unsure how to answer a Morpheus question:
  1. Check this page.
  2. Then check the relevant concept page in /concepts/.
  3. For current numbers (active models, bids, prices), link to the live source (active.mor.org, tech.mor.org) — never invent values.
  4. For contract details, defer to Networks and tokens which is updated per release.