Documentation & Support

Get started
with Web3Luma.

Learn how to sign in, set up a WalletScope workspace, and use your tools. Find a guide below whenever you need a hand.

01 / Product Quickstarts

First steps in WalletScope.

Open the guide to see the workflow and its boundaries. Sign in with Web3Luma to open your WalletScope workspace.

WalletScopeMonitor addresses, reconcile receipts and follow up on alerts. Show steps Hide steps

Observing addresses and configuring detection rules

WalletScope observes Base Mainnet native USDC Transfer and Approval logs. Its daily destinations are Overview, Wallets, Alerts, Receipts, and Reports. Rules, incidents and raw events live under Alerts. Use the Workspace menu to choose or create a workspace and access account/sign-out controls directly. Enabled rules evaluate saved observations; incidents are separate records for team follow-up.

  • Step 1: Register an observation target — In Wallets, enter the EVM address and Workspace label, check I confirm this workspace is authorized to observe this address, then choose Register wallet. Registration queues initialization; it is an authorization declaration, not proof of ownership or complete scan coverage. Check Overview for saved scan progress.
  • Step 2: Create and enable a detection rule — In Alerts → Rules, choose Create a rule, select its type and wallet scope, then set any required threshold, priority, and cooldown. Save the rule and use Enable when it should apply to future observations.
  • Step 3: Preview saved history — Where available, choose a rule, wallet, and stored block range to preview history, then choose Preview without notifications. This evaluates up to 24 hours and 1,000 saved observations; it does not run the scanner or create detections, incidents, or emails.
  • Step 4: Read observations and detections separately — In Alerts, inspect saved Transfer or Approval evidence and rule detections. A detection is a rule result with its own state; an observed event does not automatically mean an incident was created.
  • Step 5: Follow up on incidents — In Alerts, review incident records and use their actions to acknowledge, assign, comment, resolve, or reopen an incident. “Resolved” records the team's disposition; it does not mean assets were recovered or an on-chain action was reversed.
  • Receipts and reports — Review incoming USDC alongside invoices in Receipts. Import invoice CSVs there and confirm every match yourself. Use Reports for monthly statements, with coverage and integrity information.

WalletScope details

02 / Identity & Sign-in

How Web3Luma authentication works.

We separate address discovery from session authentication to protect user security.

What is the difference between connecting a wallet and signing in?

Connecting a wallet makes an address available to the page; it does not sign you in. Signing in requires a wallet signature for an EIP-4361 (Sign-In with Ethereum) challenge, which proves control of the address and creates a platform session. It does not authorize token transfers or submit an on-chain transaction.

What should I do if I cancel or reject the signature request?

If you cancel the signature modal in your wallet, the sign-in flow resets safely. Simply click "Sign in with wallet" again when ready. No transaction is submitted and no gas is consumed.

What is the difference between signing out of one app vs everywhere?

WalletScope provides account and sign-out controls in its Workspace menu. Signing out of WalletScope clears its active session for that domain. To sign out everywhere, open the central Web3Luma SSO page and confirm; that revokes the shared session, requiring you to re-authenticate when accessing workspace tools.

Are TimeCapsule and Spendkit part of the SSO session?

TimeCapsule remains an independent application. Spendkit is being connected to Web3Luma sign-in; the public deployment has not switched yet. TimeCapsule's network selector lists Monad, Ethereum, BNB Chain, Arbitrum One, Base, OP Mainnet, and Polygon, plus configured testnets; a listed network does not guarantee a deployed Registry or completed wallet acceptance. Spendkit keeps Agent Payment Wallet and MCP identity separate from Dashboard sign-in.

03 / Common Situations

Troubleshooting & next steps.

If you encounter an unexpected state or restricted view, here is how to proceed.

"No wallets registered"

WalletScope needs at least one registered Base address before it can show activity. Open Wallets and add an address your workspace is authorized to observe.

"No scan history / Stale sync"

Check the latest sync status and sampled block time in Overview. A delayed or unknown state means coverage is not confirmed; ask your workspace administrator to review service availability.

"Access restricted (product_access_required)"

Your platform account does not currently have access to this product or workspace. Ask a workspace owner or administrator to review product access and your role, then re-check the signed-in account.

"Email notifications not arriving"

All automated email notifications, weekly digests, and reminder broadcasts are currently paused across the platform. All status items must be reviewed within workspace dashboards.

Still have questions?

We're here to help.

Contact support