Architecture · Technical reference

Architecture, contracts, and economics.
Designed for users who want to evaluate the system at a deeper level.

A technical overview of the systems powering MoveQuest. Real contract addresses, real tokenomics, real tradeoffs. This page is meant to be scanned, cross-referenced, and verified — not read once and forgotten.

VERSION 1.0 · May 2026
CHAIN Avalanche C-Chain
L1 SHIPS Mid-summer 2026
STATUS Testnet live · mainnet in deployment
01System design philosophy

How to interpret what follows.

MoveQuest's architecture wasn't optimized in isolation — each decision reflects a position on what crypto should be. These six principles frame the rest of this document.

Activity-based participation instead of passive extraction.
Dynamic mining instead of fixed emissions.
Utility-driven ecosystem mechanics, not yield-as-feature.
Long-term liquidity support, structurally rather than promotionally.
Self-custody and direct smart contract interaction throughout.
Expansion through participation, not centralized allocation.
02Network & chain stack

Avalanche today. MQT L1 mid-summer 2026.

MoveQuest runs on Avalanche C-Chain through testnet and the early protocol launch. The dedicated MQT chain ships mid-summer 2026 as a sovereign L1 designed around activity-driven block production. The protocol contracts remain queryable across both phases.

Current chain
Avalanche C-Chain (EVM compatible).chainId 43114
Testnet
Avalanche Fuji.chainId 43113
Future L1
MQT mainnet. Sovereign chain. Mid-summer 2026.
Block explorer
snowscan.xyz· all current contracts indexed
Public RPC
L1 endpoint forthcoming
Bridge architecture
Cross-chain message passing planned for MQT mainnet · user-side migration not required
03Contract addresses

All on-chain. All verifiable.

Each contract below can be inspected directly on the block explorer. Source verification is in progress for the contracts that aren't already verified.

VAD - Miner NFT Contract0x7Caf521AF2969d8CAb7B399b68dD7e7C037Fc3ffView ↗
MQT - ERC20 Contract0xef0cdae2FfEEeFA539a244a16b3f46ba75b8c810View ↗
Mining Dock0x836344e444d999FDdecb6E9CC2Feb08E16D38789View ↗
Incubator0xa75d3edbC3AC10EbC6Ad965E6e8a42a118f100d7View ↗
Nest0x6e07eB8066D59440D9dc36A5d33ab8A70a9F969DView ↗
Golden Hatchery0x38BC395FB2f2688f11a5D28068F5a00a686591D7View ↗
Evolution Contract0x6ae434C092D6C6B3DC83793677508657F99b82bCView ↗
04Tokenomics

How MQT enters circulation.

MQT distribution is dynamic, scaled to verified activity, and structurally non-inflationary at the protocol layer. The numbers below describe the design; live state can be queried directly from the VAD contract.

Distribution model
Dynamic mining, scaled to verified PoPA submissions across the active network
Emission
Curve documentation forthcoming
Sinks
Hatchery commitments, evolution merges, ecosystem fees
Pre-launch
No VC allocation · No private round · No team unlock cliff · No insider distribution
Treasury
Treasury policy forthcoming
On "no insider allocation": the practical test is the contract state, not the marketing claim. The VAD contract holds distribution logic; minted-but-unallocated supply, team-held wallets, and any allocation outside of activity-driven mining can be enumerated directly on-chain. We encourage that verification.
05PoPA architecture

Proof of Physical Activity.

PoPA is the activity engine. Verified physical activity gets signed by the user's device, submitted to the protocol, and accepted (or rejected) by the contract. This section describes the verification path without revealing the surface that anti-cheat operates against.

Activity sources
Apple HealthKit · Google Health Connect · device-signed step and workout data
Verification
Device-side cryptographic signing · server-side aggregation and validation · contract-level acceptance
Submission cadence
Per-user, daily. Activity that occurs but isn't submitted is not retroactively counted.
Cost
Submission fee, paid in the chain's native gas token. Typical cost: cents per submission.
Anti-cheat
Multi-layer integrity checks at device, aggregation, and chain layers. Specific detection logic intentionally not published.
Privacy
Raw health data does not leave the device. Only verified activity summaries are submitted on-chain.
06Mining math

How daily MQT is computed.

Per-day mining for a single wallet is a function of three inputs: total active mining power (volts across docked miners), verified PoPA for the day, and the active network's distribution coefficient. The protocol's coefficient floats; the wallet's contribution is deterministic given its state.

daily_MQT=wallet_active_volts×popa_factor×network_coefficient
wallet_active_volts
Sum of volts across miners docked and active for the day. Phantom 100 · Trailblazer 100 · Explorer 150 · Vanguard 200 · Titan 400.
popa_factor
Binary or graded based on verified submission for the day. No submission, no mining.
network_coefficient
Distribution coefficient set per-period by protocol logic, scaled inversely to network-wide active mining power.
Calculator
Interactive estimator forthcoming
07Hatchery mechanics

Activity-gated farming cycles.

Hatcheries are not staking. A miner committed to a hatchery cycle farms rewards on a given day only if PoPA was submitted that day. The cycle runs on a structured timer, but the farming is gated by continued activity throughout that timer.

Cycle structure
Fixed-duration commitment windows during which a miner is allocated to the hatchery
Activity gating
Daily PoPA submission required for farming credit that day · missed days do not retroactively reward
Multiplier accrual
Cycle-level multipliers, capped per tier, with continuity bonuses for streak-active wallets
Commitment break
Early exit permitted with a defined cost · structural disincentive, not a slash
Capacity
Per-tier limits on simultaneous hatchery participation
08Evolution mechanics

Tier progression through merge.

Evolution lets two same-tier miners merge into a single higher-tier miner. The mechanic is one-way, capped at Tier 05 (Titan), and consumes both inputs. QCHIPs participate in the assembly path for mid-tier outcomes.

Merge requirements
Two same-tier miners · matching wallet · evolution path available for that tier
QCHIPs
Required for Trailblazer and Explorer assembly · not required for Vanguard or Titan merges
Capacity multiplier
Output tier produces the volt total of its position in the tier table — not a multiple of the inputs
Irreversibility
Merged miners cannot be un-merged. Both inputs are consumed.
Tier ceiling
Titan (Tier 05) is the apex. No further evolution path exists at this time.
09Engineering roadmap

What's next. In order.

Engineering milestones, not aspirational ones. Items below are the actual delivery roadmap — what's in development, what follows, what's further out. No "global wellness revolution" entries.

Now · 2026 Q2
Mainnet protocol expansion Full miner tier deployment across all five tiers. Hatchery system enabled. Evolution paths activated.
Mid-summer 2026
MQT L1 mainnet Sovereign chain launch. Validator rollout begins. Activity-driven block production. User-side migration not required.
2026 H2
Bridge architecture Cross-chain message passing between MQT L1 and Avalanche. Initial multi-chain support for ecosystem tokens.
2026 H2 · 2027
Validator decentralization Open validator participation. Progressive removal of bootstrap signers. Governance disclosure expansion.
2027
Node infrastructure tooling Public node operator tooling, RPC infrastructure, indexer support. Third-party integration surfaces.
Ongoing
Anti-cheat iteration Activity verification continuously refined. Detection surfaces expanded as adversarial patterns evolve.