Locus

Product documentation · v1

What works,
and how.

Locus connects directly to a compatible browser wallet and reads live account state from its active EVM network.

Wallet connection operational

Current capabilities

A working wallet foundation.

Wallet discovery

Operational

Detects an injected EIP-1193 provider in the browser.

Account connection

Operational

Requests explicit permission through eth_requestAccounts.

Network detection

Operational

Reads the active chain and updates when the network changes.

Balance reading

Operational

Reads the connected account’s native balance from the active network.

Account updates

Operational

Responds when the user changes or removes the active account.

Connection flow

Permission stays with the wallet.

  1. 01

    Locus detects an EIP-1193 provider supplied by the browser wallet.

  2. 02

    The user approves account access inside the wallet interface.

  3. 03

    Locus reads the selected address, network identifier and native balance.

  4. 04

    Account and network changes update the interface automatically.

Security boundary

Connection is read-only.

Connecting does not move assets, approve tokens or sign a transaction. Locus never receives a private key. “Disconnect locally” clears the interface state; wallet permissions remain controlled by the wallet itself.

Requirements

Use a compatible EVM wallet.

Open the application in a browser that exposes an EIP-1193 provider. Unlock the wallet, select an account and approve the connection request.

Open Locus