Skip to content

Commit 4e57fc6

Browse files
authored
Update website/src/pages/en/token-api/faq.mdx
1 parent a3349cd commit 4e57fc6

File tree

1 file changed

+1
-1
lines changed
  • website/src/pages/en/token-api

1 file changed

+1
-1
lines changed

website/src/pages/en/token-api/faq.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ Large numeric values (like token amounts or supply) are returned as strings to a
130130

131131
### What format should addresses be in?
132132

133-
For EVM addresses, the API accepts hex addresses with either 42 or 40 characters, with or without the `0x` prefix. The endpoint is case-insensitive, so both lower and uppercase hex characters work. Ensure EVM addresses are exactly 42 hex digits, or 40 if you remove the prefix. For contract queries, use the token's contract address. For balance/transfer queries, use the wallet address.
133+
For EVM addresses, the API accepts hex addresses with either 42 or 40 characters, with or without the `0x` prefix. The endpoint is case-insensitive, so both lower and uppercase hex characters work. Ensure EVM addresses are exactly 42 characters, or 40 if you remove the prefix. For contract queries, use the token's contract address. For balance/transfer queries, use the wallet address.
134134

135135
SVM addresses are base58-encoded strings that are typically 32-44 characters long. They contain a mix of uppercase letters, lowercase letters, and numbers. Unlike Ethereum addresses which are hexadecimal and start with "0x", Solana addresses don't have a consistent prefix pattern.
136136

0 commit comments

Comments
 (0)