How we classify builder subnets
Every Morpheus builder subnet is judged against what builder subnets are for: subsidising a builder, curated by stakers who lock MOR, with MOR as the base asset. We do not judge a subnet by "what is a staker owed", because builder rewards are a subsidy to the builder, not staker yield.
Classification is human-confirmed from automated signals. An engine proposes a bucket from on-chain and off-chain evidence; a person confirms it before it appears here. Only confirmed buckets are shown, so a subnet reads "Unclassified" until it has been reviewed.
The evidence we read
- On-chain claims and flows. When an operator claims MOR and where that MOR goes afterwards, indexed from the BuildersV4 contract and MOR token on Base. Destinations are labelled stakers, liquidity, exchanges/unrelated, or related wallets.
- Source status. Whether a linked public repository exists and is active, from the GitHub API.
- Service evidence. Whether the subnet runs a live product site, or settles inference on-chain. On-chain flows cannot see an off-chain service, so this is how a service-providing subnet is recognised rather than mistaken for extraction.
- Operator self-description. We read the website and socials the operator declares in the mor.org registry, plus their stated description and reward types. These are claims, not facts: a live marketing site is not proof of a shipping product, and we say so on the page.
Each figure carries its provenance. On-chain data is the strongest. Off-chain signals (a website, a repository) are weaker and are labelled as such. Confirming that a subnet returns fair value for a service is evidence plus judgement, not something on-chain data alone can prove.
Behaviour buckets
Provides a product or service (active linked repo, live website, or on-chain inference), whether or not it claims builder rewards on-chain.
Pairs claimed MOR into protocol-owned liquidity (MRC-22 style). A legitimate design pattern.
Redistributes claimed MOR to its own stakers. A neutral pattern, not a gold standard; retaining rewards is the by-design norm.
No admin claims in 60+ days and no product evidence. Abandoned or stockpiling.
Claims MOR and routes it to exchanges or unrelated wallets, with a confirmed absence of product and nothing to stakers or liquidity. The only adverse bucket; human-confirmed with dated evidence.
Not enough signal to classify yet: too new, or product and behaviour not yet verified.
Source status
A risk flag carried alongside the behaviour bucket. It reads how open the code behind a subnet is.
Public repo, linked to the subnet, active in the last 90 days, with a licence file.
Public linked repo, but archived, stale, or without a licence file. Peripheral or incomplete openness.
No public repo, or the linked repo is private, empty or removed.
No repository declared yet. Website-based discovery has not run, so this is "not checked", not "closed".
Custody model
The second risk flag. It reads where a staker's MOR sits when they stake.
On-chain stakes sit in the audited BuildersV4 contract. An operator-run parallel staking route, if any, has not been detected or audited.
The project’s own site stakes to a non-BuildersV4 operator-controlled contract, so principal sits in code outside the Morpheus audited template.
Both routes detected: some stakes in the audited BuildersV4 contract, some via an operator-controlled contract off the protocol template.
No stake interface detected and no on-chain stake to confirm protocol custody.
What this method cannot do
- It cannot confirm a service from on-chain data. A subnet that returns value as inference or an off-chain product shows MOR leaving to the operator's wallet, which looks the same as extraction. Service-providing subnets are recognised through product evidence and human review, never from flows alone.
- An adverse call (Extractive) is never made on missing data. It requires a confirmed absence of product, evidence on-chain, and a human signing off.
- It does not repeat a subnet's partnership or affiliation claims as fact. A subnet naming a backer or partner only counts once that partner's own sources confirm it (reciprocal verification). Registering a permissionless builder subnet is not an endorsement by Morpheus.
- Exchange deposit addresses are not separately labelled; they fold into "unrelated/unknown" and are checked by hand at review time.
- Figures are point-in-time and refresh on a schedule. This is a researched assessment, not a live metrics dashboard.