NO SEED PHRASES
MIROX never collects or transmits recovery phrases or private keys.
MIROX 1.0 / DOCUMENTATION
Read the field.
Technical and conceptual notes for the production interface: Arc Mainnet data, wallet discovery, EIP-712 signals and device-local archive truth.
INDEX / 01—06
01 / ARC FIELD
Public state becomes sensory input.
MIROX reads the latest Arc Mainnet block through a same-origin read-only RPC proxy, with direct RPC fallback. The interface displays the block number, hash, timestamp, transaction count and response latency.
The activity index is a clearly derived presentation value based on the current block response. It is not a price, prediction or trading signal.
02 / WALLET ENTRY
Discovery without fabricated detection.
MIROX uses EIP-6963 announcements and injected-provider flags to identify wallets actually present in the browser. The selector always lists supported interfaces in a stable order, but only discovered providers receive the DETECTED state.
Connection requests account access. If the wallet is on another chain, MIROX asks it to switch to Arc. If Arc is absent, the official Arc Mainnet parameters are offered through wallet_addEthereumChain.
Connect does not request a signature, token approval or transaction.
03 / SIGNAL
Typed intent, reviewed first.
A signal is an EIP-712 FieldEntry message. Its domain is MIROX version 1 on chain 5042. The message contains the observer address, Arc network name, current block number, timestamp and a cryptographically random nonce.
The complete payload is shown in a confirmation panel before the wallet prompt opens. Signing is optional and may be rejected without affecting read-only field observation.
04 / ECHO
The wallet returns evidence.
When the wallet returns a signature, MIROX creates an Echo ID and records the signature with its Arc block context. This proves that the connected wallet approved the structured message.
A signature is not a transaction. The product never labels it as submitted onchain, settled or contract-verified.
05 / ARCHIVE
Persistent on this device.
The 1.0 archive uses browser local storage. It retains up to 100 signed signal records and survives reloads on the same browser profile. Records can be cleared by the observer.
Arc block links point to the public explorer for independent verification of network context. The signature itself remains a device record unless a future contract registry is introduced.
06 / SECURITY
What MIROX never asks for.
NO SILENT SIGNATURES
Every signal begins with an explicit user action and payload review.
NO AUTOMATIC VALUE MOVEMENT
The current signal flow contains no transaction, token approval or USDC transfer.
NO FAKE NETWORK STATE
Unavailable RPC data is shown as unavailable rather than replaced by samples.