Find your next step.
Common wallet, workspace, token, and transaction questions.
Wallet not detected
Open the live app in a browser where your EVM wallet extension is enabled, such as your configured Brave browser. Unlock the wallet and check its site permissions. Some embedded browsers do not expose wallet extensions.
The current app uses the wallet provider exposed by the browser. It does not include WalletConnect QR pairing or a dedicated multi-wallet chooser. If extensions conflict, select the intended default wallet in your browser/extension settings, then reload.
Wrong network or changed account
Switch to Robinhood mainnet, chain ID 4663, and reconnect. Testnet uses a different chain and its balances/contracts are separate. Changing the account or network clears the app’s connected context until you reconnect.
Workspace not found or code does not match
Check that you pasted the workspace contract address rather than your wallet or token address. Confirm the deployment succeeded on Robinhood mainnet and inspect its receipt.
A pending deployment, the wrong network, an unrelated contract, or a workspace from an incompatible build can fail verification. Do not redeploy just because you changed devices; first recover the original address from the receipt.
My token list is empty
Select Refresh list. If the explorer is delayed or unavailable, enter the ERC-20 address manually and select Check balance. Confirm that the wallet holds the token on Robinhood mainnet. Native ETH is not listed as a vestable ERC-20.
Approval succeeded, but creation failed
Check the transaction receipt, token balance, ETH for gas, and whether the start time is still in the future. Reopen the form and review current values before retrying. Unsupported token transfers can also revert.
An approval does not create a schedule. A failed creation does not leave a partially recorded schedule, but a previously successful approval can remain. Inspect it through your wallet if you decide not to continue.
Nothing to claim
Refresh the workspace and inspect its cliff and released amount. Before the cliff, nothing is claimable. Immediately after a claim, only newly vested tokens can be claimed; small increments may round to zero base units.
If the allocation is fully released, no further claims are available. If tokens vested but a transfer fails, inspect the token’s transfer restrictions and transaction receipt.
Names or schedules are missing on another device
Connect the same account and open the same workspace. The dashboard filters to schedules where that account is creator or beneficiary. Names saved in another browser are not synchronized; the public record still identifies the schedule by ID.
See Devices & saved data for the complete storage explanation.
A public link will not load
Use a link starting with https://veylock.app, not localhost. Check both the workspace address and schedule ID. The viewer requires no wallet, but its public RPC can time out or be rate-limited. Retry later and use the explorer to inspect available transaction records.