zks_getConfirmedTokens
curl --request POST \
--url https://api.mainnet.abs.xyz/zks_getConfirmedTokens \
--header 'Content-Type: application/json' \
--data '
{
"jsonrpc": "2.0",
"id": 1,
"method": "zks_getConfirmedTokens",
"params": [
0,
10
]
}
'{
"jsonrpc": "2.0",
"result": [
{
"decimals": 18,
"l1Address": "0x0000000000000000000000000000000000000000",
"l2Address": "0x000000000000000000000000000000000000800A",
"name": "Ether",
"symbol": "ETH"
}
],
"id": 1
}ZKSync API
zks_getConfirmedTokens
Lists confirmed tokens. Confirmed in the method name means any token bridged to Abstract via the official bridge. The tokens are returned in alphabetical order by their symbol. This means the token id is its position in an alphabetically sorted array of tokens.
POST
/
zks_getConfirmedTokens
zks_getConfirmedTokens
curl --request POST \
--url https://api.mainnet.abs.xyz/zks_getConfirmedTokens \
--header 'Content-Type: application/json' \
--data '
{
"jsonrpc": "2.0",
"id": 1,
"method": "zks_getConfirmedTokens",
"params": [
0,
10
]
}
'{
"jsonrpc": "2.0",
"result": [
{
"decimals": 18,
"l1Address": "0x0000000000000000000000000000000000000000",
"l2Address": "0x000000000000000000000000000000000000800A",
"name": "Ether",
"symbol": "ETH"
}
],
"id": 1
}Body
application/json
Was this page helpful?
⌘I