VEYLOCKDOCS
Open app
Browse documentation Tokens & amounts
USE VEYLOCK / 05

Choose the right allocation.

Wallet token discovery, manual entry, balance shortcuts, and token compatibility.

Tokens in your wallet

The creation form asks the Robinhood Blockscout explorer for ERC-20 token addresses associated with the connected wallet. Select a token to read its current balance and decimal precision through your wallet’s provider.

This list is specific to Robinhood mainnet. Tokens held on another chain will not appear as mainnet holdings here. Explorer indexing can lag or be unavailable; a missing list entry does not prove the token balance is zero.

Enter a token manually

Choose Enter token address manually, paste the ERC-20 contract address, and select Check balance. The manual field stays available even when discovery succeeds.

Check the full address against the intended asset, not just its name or symbol. Different tokens can use the same label. Changing the token address clears the entered amount so you can choose the allocation again.

10%, 50%, or 100%

Each shortcut reads the selected token’s wallet balance again, then fills that percentage into Amount. Calculations use integer base units, preserving token precision and rounding down.

For a balance of 123.456789 tokens with six decimals, 10% fills 12.345678. A very small balance can round to zero; enter a larger amount if that happens.

100% means all of the selected ERC-20 balance at the time of the read. It does not include ETH. Keep ETH separately for transaction gas. The app checks the token balance again during review; later balance changes can still cause funding to fail.

Supported tokens

Use conventional ERC-20 tokens with predictable balances and exact transfers. Native ETH is used for gas and cannot be vested directly through this ERC-20 contract. The app does not wrap ETH for you.

Unusual token behavior is unsupported.

Fee-on-transfer, sender-tax, and rebasing tokens can fail funding or claims. Token issuer controls such as freezing or blacklisting can also prevent transfers. The workspace checks exact balance changes during funding and claims, but cannot remove an issuer’s powers.

If token decimals cannot be read, amount shortcuts cannot safely calculate a human-readable allocation. Existing schedule details fall back to explicitly labeled raw base units when metadata is unavailable.