MAZEX

Protocol

Protocol Cognitive advancement, Solve Blocks, state inheritance, and MAZEX unlocks.

OverviewHow the protocol advances state. WhitepaperFormal protocol definition. VocabularyCanonical protocol terminology.

Solve

Solve Observe behavior, build candidate models, submit signed explanations.

ConsoleCurrent challenge workspace. Solve BlocksAccepted Solve records. WalletSign candidate submissions.

Build

Build Run nodes, inspect APIs, package releases, and verify chain data.

Run a NodeLocal node and replay path. DownloadsWallet, node, chain data. CLI and APIOperator references.

Network

Network Inspect chain state, roots, Solver records, and public commitments.

ExplorerBrowse state records. Latest BlocksSolve Block previews. Node StatusNetwork and sync view.

Resources

Resources Documentation, packages, whitepaper, and implementation references.

DocsArchitecture and security. Release CenterPackages and checksums. English PaperPublication format.

Native Wallet

Keys stay local. Signatures enter the protocol.

The MazeXChain wallet manages accounts, encrypted vaults, site connections, signed candidate models, and MAZEX transfers. The website requests signatures; it does not receive private keys.

Download Extension

mazex1f8a2...92c1

Confirmed 0 MAZEX

Connect Sign Transfer

Signature Boundary

The site requests intent. The wallet signs authority.

Key material remains inside the local wallet vault. The console receives addresses and signatures, never private keys or recovery phrases.

Site Request Wallet Approval Signed Payload

Account Flow

Create or Import

Generate a recovery phrase, import an existing phrase, or import an advanced private key.

Encrypt Vault

Key material is stored inside the extension vault and unlocked by the local password.

Connect Site

The user approves a site connection before the web console can read the active address.

Confirm Signatures

Candidate submissions and transfers require explicit wallet signing before broadcast.