Glossary

WalletOrbits terms

Resolution

How confidently WalletOrbits matched the input to a real Ethereum wallet or ENS name.

Wallets or entities with enough repeated overlap to justify appearing in the relationship field.

Addresses or entities that repeatedly interact with the scanned wallet and help explain its flow patterns.

Prediction-market context derived from Polymarket-adjacent contracts, venues, and market behavior.

A short summary of how the wallet sits within its surrounding wallet, protocol, and market signals.

The main analysis panels on the site, such as identity, labels, orbit mapping, counterparties, and market context.

A compact signal for how reliable the current identity match and surrounding attribution look from the available evidence.

A proposed interaction path with explicit caps, approval limits, and postconditions; it is evidence for review, not permission to execute.

A read-only RailZero object that records target contract, selector, policy, warnings, and postconditions for a possible bounded route.

A WalletOrbits product mode for suspicious-token and approval triage using public-data-based, simulation-first risk inboxes.

A token permission that may let another contract move assets from a wallet until the user revokes or limits that approval.

A route that may justify only a negligible test-sized simulation or review step, never a full-value live action by default.

The maximum value or permission scope that a bounded route is allowed to risk under its stated policy.