Public addresses
Save and find a public address, check its network and copy it in full.
Step by step
- Each page shows up to 12 addresses: network icon, name, shortened address with full copy, QR, native balance and refresh. Search and network filters cover the current page.
- Click an address row or activate its name with Enter/Space to open the shared side panel with native and token balances, tags, history and connection details. The separate chevron expands tokens below the row. Copy, QR and refresh keep their own actions. Check the exact network before using an address or QR.
- Tokens come only from the enabled catalog of that exact network. Amounts use the asset’s declared decimals; its symbol or logo is not a USD price. Open the token name to inspect its contract, amount in the asset’s smallest units and observation time.
- Balances are saved on this device for up to 5 minutes; address, wallet and token lists for up to 15 minutes. The displayed time is the actual observation time. Reloading reuses fresh saved data only after current access is checked. Use the balance refresh button for a new observation. Unsupported or failed balances never become zero. Browser settings keep language and appearance locally. Signing out removes the display cache; financial confirmation always uses current server checks.
- Choose Add wallet or address → Connect an external wallet. Select an enabled supported Ethereum network. Configured WalletConnect is the primary option; detected browser extensions appear in a compact grid with their available icons. MetaMask appears only when detected. The network never changes automatically.
- Choose the public account and a name. Review the full address, exact network and visibility, then Save address and continue. If it already exists or the response is unknown, use Check saved records instead of creating a replacement.
- Prepare the platform challenge, review its exact message and sign it once in your wallet. This proves address control, not login or spending authority. These controls are also available in the details of an existing Public address.
- After a lost completion response, read the original proof result. Retry original proof sends the same in-memory signature while the challenge is valid. Expired or rejected proofs can be explicitly replaced. Changing wallet account or network invalidates the connection.
- In Address history, choose Check history status to compare saved coverage with a bounded network observation. Read the check time, indexed block, observed head and coverage floors. Not observed stays unknown. Network disabled, review required, source unavailable, source behind and a differing checkpoint are distinct states. This button does not start, scan or repair history and never grants finality, credit or spending authority. It runs only when you select it; Refresh visible data does not repeat it.
- For a private address you own, open its started history and Background observation. With address sharing/management and API-client listing rights, choose a configured observation service and an explicit future expiry (UTC, at most 366 days). Review and confirm with your current key. The server verifies the service’s addresses.observe right; selecting it does not grant that right or start the separate worker. Permission recorded is not proof that indexing is running. An expired permission remains until you explicitly revoke it with DELETE and key confirmation. Revocation preserves history; a later grant resumes the same stream. Existing permissions can still be revoked after the address becomes organization-visible. Without API-client listing rights, you can read/revoke your existing permission but cannot create one here. After a lost response, Check original request; Finish checking only after the exact receipt is found. Continue original request retains the original ID, service, stream version and expiry. Missing or expired unresolved requests are never replaced automatically; ask the operator to reconcile an expired unresolved request. No credentials, signing authority or private financial access are delegated.
- The extension grid contains discovered providers only, without installation suggestions. In an embedded browser, copy the page link and open it in a browser with your extension, then check discovery again. WalletConnect’s temporary pairing QR is distinct from a public-address QR. Provider names and icons do not establish trust or authority.
- For an address already saved for observation, open its details → Connect an external wallet. Choose an extension or WalletConnect and select the exact saved account and network. Prepare the proof, then explicitly sign the address-control message in your wallet. The existing address, name, tags and history remain; no duplicate address or custodial source is created. A mismatched account or network must be corrected before preparing a proof.
Working details
Choose Add public address, select its exact network, paste the complete public address, add a name and choose who can see the record. Review address shows these terms before Save address. Saving or renaming this public record uses your current authenticated session without another key ceremony; proving control and changing access remain separate protected actions. A format error returns to the same fields. A duplicate or unknown outcome requires checking saved records; no automatic resubmission occurs.
Edit name changes only the label. The network and address are immutable. After saving, the selected details show the server result. If the response is lost, close the form and check the refreshed name before another change.
Check on-chain balance explicitly requests a native-asset observation on supported Ethereum/TRON mainnet addresses. It shows the provider observation time and block; it is not a custody balance or spending permission. No balance request runs just because you open the list.
Address history reads stored observations, with bounded pages and the stream’s native/token coverage floors. No configured history does not mean no transfers. A stream needing review is not fresh confirmation. Bitcoin spent-output value is not a net outgoing transfer; the history is not a complete statement or accounting balance. Advanced operations can limit saved address history by From (inclusive) and To (exclusive), using UTC RFC3339 block timestamps. The daily Address history panel still reads its existing bounded pages. The backend change-event replay API has no console control. Empty or incomplete coverage is not evidence that no transfers occurred.
Interface
