Developers

Build on Emerging Protocol Infrastructure

A preview of how developers would work with the MoP research architecture. Tooling is planned and not yet available. Code samples show concepts only and are not functional APIs.

Protocol concepts

MoP is designed as one coordinated stack: consensus orders and finalizes blocks, MPVM executes them deterministically in parallel, XMSG carries verified messages between networks, and MAH/GAR settle multiple assets. See the Technology overview for the architecture.

MPVM execution model

Contracts would compile to a deterministic WebAssembly subset. Declared access sets let the scheduler run non-conflicting transactions in parallel.

access-set.ts · conceptual illustration
// Conceptual MPVM transaction access set (illustrative)
interface AccessSet {
  reads:  string[]; // state keys read
  writes: string[]; // state keys written
}
// Transactions with disjoint write sets may execute in parallel;
// conflicts are resolved in canonical block order.

XMSG messaging

Cross-chain messages carry ordered sequence numbers and payload commitments, and are verified on the destination by light clients. Explore the transaction journey.

xmsg-envelope.ts · conceptual illustration
// Conceptual XMSG envelope (illustrative — not a published API)
interface XmsgEnvelope {
  sourceChainId: string;
  destinationChainId: string;
  sequence: bigint;        // ordered, exactly-once delivery
  payloadHash: Uint8Array; // commitment to the message payload
  timeoutHeight: bigint;   // refund path if no acknowledgment
}

Asset settlement

MAH handles escrow, conversion, and atomic settlement. GAR maintains canonical asset definitions. Read more.

Developer interfaces

RPC, query, and event-subscription interfaces are being specified. Planned / Under Development

SDK roadmap

  • TypeScript client SDKPlanned
  • Rust contract toolkit for MPVMPlanned
  • XMSG integration helpersPlanned
  • Local devnet & CLIPlanned

No SDKs, repositories, or endpoints are published yet.

Research testbed

A research testbed with observability tooling and a reproducible benchmark method is planned. Results will be published once testing can be reproduced. Planned / Under Development

Security model

The planned security model covers BFT safety assumptions, deterministic sandboxed execution, resource metering against denial-of-service, light-client verification for interoperability, and responsible disclosure via ask@blockc.net.

Developer tooling for MoP is planned or under development. Interested in early research collaboration? Start a partnership discussion.