EVM Only APIs
Last updated
Last updated
EVM chains include Avalanche, Binance Smart Chain, Base, Ethereum, and Polygon. Some capabilities are chain specific and some are specific to asset standards. If you need more info about asset standards or would like to request we support a specific asset standard's capability, please reach out to us.
When giving wallet holders the ability to add an asset, you may choose to fetch information about the asset directly offchain. This EVM only API is capable of pulling the name, symbol, and decimal of an asset given the contract address.
Since multiple on-chain assets may share names/symbols, you must first add the asset to your business directly and then a wallet holder will be able to add the correct one. More detail about this in Assets, Addresses, & Balance Fetching APIs.
ERC-1404s and the equivalent on other EVMs function as a security token standard that enables the creator to define restrictions. For example, you can restrict transfers to certain addresses or only allow them after certain holding periods. These APIs enable you to check if and why a transfer is restricted BEFORE sending the transaction saving the wallet holder fees and/or time on reverted/failed transactions. See more in Transfer API
ERC-20s and token standards that build on ERC-20s such as the 1404 enable you to allow a designated address to spend a specified amount of funds on your behalf. This is similar to a spending authorization. This also works on most other EVM blockchains. See Spending Authorization for more detail.
EVM token contract address on chain
0x28aef3b18daec312860dd030102a427ed43dac71
EVM token asset info returned successfully
Origin address
0x9bf4001d307dfd62b26a2f1307ee0c0307632d59
Recipient address
0xb44e88ff3c67de6e6548a6caf006bf6e1cb84111
value being sent
109203.1281
Asset ID inside wallaby system
ed378076-80c0-43ed-9914-5988e1abd748
Optional ERC1404 token contract address on chain, when this is supplied, the assetId field will be ignored
0x28aef3b18daec312860dd030102a427ed43dac71
Restriction info returned successfully
Restriction code to be interpreted by the API, by reading data from the contract
0
Asset ID inside wallaby system
ed378076-80c0-43ed-9914-5988e1abd748
Optional ERC1404 token contract address on chain, when this is supplied, the assetId field will be ignored
0x28aef3b18daec312860dd030102a427ed43dac71
Restriction message info returned successfully
Message retrieved from the backend
717ea458b62a430cb37ced7c22ebec97
e3421d7f9d6888ea83bef6b28ce0a2ab6eb6fe8a8fbfa3743240992590816b08f9a62edcc63296d056c552054d583fec36d23ef11dffb24c95aaf4a47d50dccc
Signature generated after signing the provided data field
0xb44e88ff3c67de6e6548a6caf006bf6e1cb841119d0b9ea1b7e9b2d36a5e0ed42fd9f5e543243d1d73dc4b7800cc2026f74961f4edc769699678a316abb34e661c
The owner's address
0x44Fa139F39D97b000cfAB1266ce8154782Bcef9D
The spender's address
0x44Fa139F39D97b000cfAB1266ce8154782Bcef9D
The amount the owner wishes to allow the spender to spend
10
The asset ID for which you wish to specify an alloance
ed378076-80c0-43ed-9914-5988e1abd748
The asset contract address
0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48
Transaction reference
a4dedb83-4d59-41ca-84b5-4b24a98878d8
Transaction memo or note
Allowance for buying NOTE
Seed encrypted asymmetrically by current user corresponding wallaby auth public key, to be decrypted inside the secure code execution environment
{"iv":"b7b643ebccf35c262aa2d5c2729c5f3d","ephemPublicKey":"040cff71ed16f1105c45c2214c9e72d3eabde48efe3759c6f150352b19aa8054c302dc1fd8b4f3927bd7d74ae0186854b3a13de7673be4f8424a6ba3702c239729","ciphertext":"736bc1881a02fa08df4a3f1e35d426660e3c35471facba2866e960f8a19b783bac30d037b07dc9e6406e258d09a4a7e4a7cf58d20cf7b8b7201db0f80849a48d20389039e3fc196f42796fe6d501f47afb030f9946ecbc148d8da1e46c3793a4","mac":"b6cbbdbbc3a311d919340fc3ec9ee1911d9ead6d989efa73e0ac3303c51a353e"}
Allowance has been created successfully