No turns hidden.
No reward attached.

A clear choice.
One step at a time.

A basic chain action should be understandable before a wallet is asked to sign. Mazevra makes that action a single legal move on a visible fixed map. The website explains the project; the separate maze page owns every read, review and action.

Each account has an independent run. There is no leaderboard, matchmaking, social backend, real-world route planning, geolocation, wager or reward. A wallet is not proof of one person.

The map is public.
The rules are fixed.

The contract contains a fixed 5×5 set of open cells. The top-left cell is the entry and the bottom-right is the goal. Directions are north, east, south and west. A step cannot cross the outer boundary, wrap from a row end into the next row or enter a wall.

The map is deterministic, not generated from chance or a private seed. Branches and backtracking are allowed when their cells are open. Reaching the goal marks the run inactive; no further step is accepted until a reset.

Your caller.
Your current run.

The transaction sender owns its own round, move count, current cell and active flag. There is no substitute player input, administrator override, proxy or upgrade key. Starting/resetting advances that wallet's round and returns it to the entry with zero moves.

A step includes the expected round and move count. The contract rejects stale values, so an old reviewed step cannot silently continue after a move or reset has changed the run. The interface also checks the current cell and active flag before asking the wallet.

A new round.
Not an erased past.

Reset may start an unwritten, active or completed run. It replaces the current position and moves with a new round at the entry. It does not delete previous public Reset or Stepped events.

Unlike step, reset has no expected-round parameter. The interface rereads its reviewed state, but another transaction can still mine first. An unexpected receipt round must lead to a fresh read of the real run, not a claim that nothing changed.

Network Gas only.
No application payment.

Every prepared business write is nonpayable. There is no deposit, token allowance, custody, application fee, prize, reward or withdrawal. A future deployed reset and every step consume native network Gas, including gas consumed by a reverted transaction.

The review displays owner, exact action/direction, before/after position, round/moves, target network/contract, estimated Gas, buffered Gas limit, fee cap and maximum estimated fee. Runtime identity, account/network, current state, simulation, fee and native balance are checked, including a final 60-second expiry after asynchronous checks.

Success requires a matching successful receipt and exact Reset or Stepped event with the reviewed account, resulting round/cell/moves/finished state. An uncertain outcome must not be presented as unchanged. Read actual state again before the next action.

A local Demo.
Not a public deployment.

The same retained project contains the contract, actual in-process chain tests, unsigned backend deployment preview and an independent maze interface. No public chain, address or verified runtime is configured. Chain reads, estimates and writes remain disabled.

Memory-only practice uses labelled example wallets and the same map/move rules. It has no wallet, backend, network, storage, persistence, transaction or Gas. Clear memory or reload removes every practice run. It is not a chain event or receipt.

A public deployment requires separately reviewed network/RPC, controlled signer public address, balances, fees, Gas, nonce, bytecode and explicit authorization. The unsigned preview cannot sign or broadcast; no private key belongs in the website. Rule changes use a new reviewed version/address, not a silent migration.

A read-only path history could be added later, but no indexer or leaderboard is running now. X is pending. Local tests are not an independent security audit.