Developer Hub

Operate MetaQuantum services with live telemetry and automation.

Discover API keys, monitor Layer2 batches, and pull health metrics from the gateway. Everything mirrors the canonical REST surface that your automation uses in production.

Membership Guest
API keys 0
Layer2 batches —
Requests (24h) —

Account overview

A snapshot of your membership tier, developer usage, and Layer2 health. This data mirrors what the API returns to automation clients.

Membership

Loading…
Quantum ID
—
Level
—
Loyalty points
—
Cashback
—

User contract

Loading…
Contract ID
—
Template
—
Execution mode
—
Internal address
—
WASM hash
—
WASM stored
—
Updated
—

Pulls metadata from /contracts/metadata/{quantum_id}.

API usage

Waiting…
Total API keys
—
Total requests
—
Latest key created
—
Layer2 batches (pending)
—

Layer2 snapshot

Waiting…
Latest batch
—
State root
—
Finality
—
Forced inclusion queue
—
State sourced from /layer2/status and /layer2/metrics.
Signature counters surface through layer2_signature_valid_total and layer2_signature_rejected_total.

Platform metrics

Live gateway metrics pulled from /metrics/performance. Use them to monitor throughput and latency while iterating on services.

Performance

Loading…
Rolling TPS —
Average block time —
Storage write MB —
Last block height —

Network & tools

Bind the hub to your network settings, validate production readiness for wallet/bridge flows, and use the developer utilities for deployment and testing. Values are stored locally in your browser.

Network profile

Loading…

These values are pulled from the server and used to populate quick links below.

Quick actions

Launch tools

Deploy toolkit

Hardhat

Use the bundled Hardhat workspace to deploy MQPY and the Layer1 suite.

cd hardhat && npm run deploy:mqpy:sepolia
cd hardhat && npm run deploy:sepolia

Update .env with your RPC + deployer key before running.

Network health

Live checks
Layer2 health —
Bridge health —
Performance metrics —
Prometheus —

Logs & faucet

Dev actions
No log entries loaded.

Faucet actions depend on your treasury policy. Use the faucet URL above or mint via authorized operators.

Wallet & bridge readiness

Loading…
Bridge USD balance
—
Fiat available
—
Fiat verification
—
Bridge contract
—
Trusted gateways
—
Last refresh
—

Bridge summary reads /api/qmask/bridge_summary; gateway trust is sourced from /api/gateways/trusted.

Production readiness checklist

Awaiting checks
Network profile ready
/api/network/profile
—
Bridge watcher healthy
/health/bridge
—
Layer2 batches advancing
/health/layer2
—
Prometheus scraping
/metrics/prometheus
—
Bridge summary reachable
/api/qmask/bridge_summary
—
Trusted gateways loaded
/api/gateways/trusted
—
Secrets + vault configured
Manual check
Manual
Node mode = full
Manual check
Manual
Sessions & identity verified
Manual check
Manual

Automated checks refresh from live endpoints. Manual items follow the production checklist in docs/operations.md.

Layer2 operations

Inspect rollup batches, data availability hashes, and forced inclusion queue lengths directly from the gateway.

Committed batches

Loading…
Batch L2 block State root Finality L1 Tx Submitted Payload
Loading…

API keys

Manage scoped API credentials for automation and integrations. Keys live under /developer/api-keys.

Your keys

Loading…
Label Key ID Suffix Created Last used Requests Actions
Sign in to view keys.

Usage guardrails

Quotas
Max keys per user
10 (configurable via DEVELOPER_MAX_API_KEYS_PER_USER)
Rate limit window
60 requests every 60s (DEVELOPER_RATE_LIMIT_MAX_REQUESTS / DEVELOPER_RATE_LIMIT_WINDOW_SECS)
Telemetry
developer_rate_limit_hits_total, developer_api_keys_created_total

When a limit is reached the gateway returns HTTP 429 and increments the Prometheus counters above (see docs/ops/monitoring.md).

Treasury signers

Vault quorum

The multi-sig treasury vault requires approvals from three of the following trusted operator inboxes:

  • meta-qunatam@qmail
  • mq@qmail
  • omar@qmail
  • oms.nl@qmail

Exposed via /admin/vault/* endpoints once authenticated with signer credentials.

Service catalog

Quick references for common endpoints and integration runbooks. All routes are served from the configured gateway.

Identity & login

Accounts
  • POST /quantum_register – Create deterministic identities.
  • POST /quantum_login – Exchange credentials for session tokens.
  • GET /trusted_devices/{user} – Device posture.

MQPY operations

Liquidity
  • GET /api/mqpy/balance/{user}
  • POST /stake_mqpy / /unstake_mqpy
  • GET /get_fees_config

Layer2

Rollup
  • GET /layer2/status
  • GET /layer2/batches
  • POST /layer2/forced_inclusion

Notifications

Messaging
  • POST /send_qmail
  • POST /fetch_notifications
  • GET /notifications/stream

Support & runbooks

Build confidence in releases with repeatable runbooks and contact points for the MetaQuantum core team.

Operational checks

Before release
  • Run scripts/run_security_checks.sh.
  • Verify /metrics/performance and Layer2 queue.
  • Audit forced inclusion and API key rotation.

Contact

Core team

builders@mqpy.io

Reach out for validator onboarding, bespoke tooling, or SLA escalations.