feat(runtime): add MRC-91 (Token Native Docker Compute) and MRC-92 (S…#85
Open
robertjchristian wants to merge 1 commit intoMorpheusAIs:mainfrom
Open
feat(runtime): add MRC-91 (Token Native Docker Compute) and MRC-92 (S…#85robertjchristian wants to merge 1 commit intoMorpheusAIs:mainfrom
robertjchristian wants to merge 1 commit intoMorpheusAIs:mainfrom
Conversation
…ubnet Service Registry) MRC-91: Router-integrated runtime layer for Docker/OCI workloads - Converts MCU stake entitlement to MEU execution capacity - Epoch-scoped accounting with rollover policy - Capability profiles: deterministic (d.strict) and confidential (t1.confidential) - Provider adapter interface for decentralized compute backends - Governance parameters: EPOCH_LENGTH, ROLL_OVER_POLICY, MIN_PROVIDER_BOND MRC-92: Canonical on-chain registry for subnet-hosted services - Discovery schema aligned with Agent Registry (MRC-58) and Namespace (MRC-59) - Pricing models (fixed, subscription, metered) with revenue splits - Network Programs (RFPs/Bounties) with verifiable acceptance criteria - Router-verified reputation scoring and SLA tiers - Token-gated access support via ERC-20/721/1155 contracts Together these MRCs extend the MOR economy from inference to general-purpose compute and establish a verifiable service marketplace for subnet capabilities.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request: Add MRC-91 (Token Native Docker Compute) and MRC-92 (Subnet Service Registry)
Type: Feature / Protocol Specification
Author: Robert Christian (@robertjchristian)
Date: 2025-10-28
Summary
This PR introduces two complementary MRCs that complete the economic loop for autonomous agent infrastructure, extending Morpheus from inference marketplace to full-stack application cloud.
The Change
Before: Agents could reason, infer, and trade information within the MOR network, but developers couldn't host arbitrary APIs or services under unified MOR accounting. External infrastructure fragmented settlement and weakened token alignment.
After: Agents can host, subnets can operate entire application stacks, and MOR becomes a self-contained, on-chain application cloud with unified accounting across inference and execution.
MRC-91: Token Native Docker Compute
Extends the Router to support general-purpose Docker/OCI workloads using MOR-denominated resources. Subnets stake MOR to earn Morpheus Compute Units (MCUs), which convert 1:1 to Morpheus Execution Units (MEUs) at runtime. MEUs are epoch-scoped (default 24h), consumed by execution, and burned on completion.
Key capabilities:
d.strict) and confidential compute (t1.confidential)This closes the operational loop: stake → compute → burn.
MRC-92: Subnet Service Registry
Provides the canonical on-chain registry for subnet-hosted services, bridging community-built APIs to Morpheus Core (MCP, Router, Agents). Services are discoverable via standardized schema, priced transparently (fixed/subscription/metered), and ranked by Router-verified reputation (uptime, latency, success rate).
Key innovation: Network Programs (RFPs) enable Core and governance to procure capabilities from the community with verifiable SLAs. Providers submit services, Router canary tests validate, and escrow releases on acceptance. This creates a two-way marketplace between Core and community.
Economic Impact
Every workload (inference, execution, or service) now consumes the same accounting units (MCU/MEU), unifying the MOR economy. Staking generates capacity, usage burns supply, and reputation anchors to Router telemetry. MOR value becomes anchored to productive work across the full application stack.
Result: Permissionless participation, composable markets, and verifiable coordination that turn subnet autonomy into network-level extensibility. Stake becomes capacity. Capacity becomes work. Work burns supply.
Governance
Router: Epoch configuration, rollover policy, stake-weighted quotas, refund windows, slashing rules.
Registry: Listing stakes (100/50/10 MOR tiers), SLA-based reputation thresholds, schema versioning, moderation policy.
All parameters are tunable; all weight or tier changes emit events for reproducibility.
Files Changed
MRC91-PLACEHOLDER.md- Router runtime extension and MEU accountingMRC92-PLACEHOLDER.md- Service registry schema and discoverySee MRC files for full technical specification and open questions.
MRC-91 provides autonomy and uniformity of accounting and holistic streamlining of ops footprint for subnets. MRC-92 provides an API economy marketplace which can further power the velocity of MOR ecosystem growth. Together they define the first permissionless AGI-ready economic substrate.
Full specification, open questions, and reference implementation details are in the MRC files.
Discussion & Follow-ups