MorScan: one page per model, every listing
On Morpheus, one model can be registered on chain many times: different spellings, vendor prefixes, web-search and TEE variants, each with its own listing id. MorScan reads through that. The model page aggregates every listing it assesses as the same model: providers offering it, sessions and consumers, MOR staked, live asks, and the 30-day session chart all span the full set, with each on-chain listing itemized below. And the model gets a URL worth sharing: morscan.io/compute/models/kimi-k3 is Kimi K3, whatever the listings are called.
Variants fold in instead of fragmenting: a web-search or TEE listing shows as a capability badge on the model, its bids, and its family row. The family view now lists canonical models rather than raw registrations, so a family reads as a handful of models with listing counts, not a wall of near-duplicate names. Every number still carries the same signed receipts as the rest of MorScan.
Published by
Robert Christian
Founder and CEO, DRM3 Labs Corp.
More from DRM3 Labs
How to trust the data your AI agent uses
Robert Christian · 4 min read
Data with receipts: what a provenance receipt proves, and what it cannot
Robert Christian · 4 min read
A pre-flight checklist for feeding data to a model
Robert Christian · 3 min read
2026 DRM3 Labs Corp. All rights reserved. DRM3 Labs builds infrastructure for open protocols.
This article is for informational purposes only. Nothing here is financial, investment, or legal advice. Tokens, staking, NFTs, and blockchain protocols are described as technical mechanisms, not investment recommendations. Digital assets carry risk. References to the Morpheus network describe the public protocol as documented at mor.org.
