⚡Blockchains
We support all major public blockchains
expand.network provides connectivity to various EVM and Non-EVM based chains for both, query(Read) and transaction(Write). So now, the developer does not need to worry about how different blockchains work. The developer will be required to know only the chainID to perform multiple operations on different chains.
For example, if a developer wants to send two transactions, one on the Ethereum mainnet and another on Solana, then they just need to call the sendtransaction API with different chain IDs in the request body.
Following are the common APIs implemented for all the various chains:-
Every chain requires a different set of parameters to perform the common operations. Please refer to the sub-sections for details.
To perform sendtransaction() successfully, the user needs to sign the transaction first.
For more details, click here.
If the user wants to pass the RPC manually, the user can either use their own RPC or use our provided RPC, by using /getpublicrpc endpoint.
/getpublicrpc
Get the RPC of required chain.
GET
https://api.expand.network/chain/getpublicrpc
Query Parameters
/getapprovaldata
Retrieves approval-related information for a specified address, including token details, amount approved, spender, risk factor, value at risk, and timestamp. This is currently available for EVM chains
GET
https://api.expand.network/chain/getapprovaldata
Query Parameter
/estimategas
Generates and returns an estimate of how much gas would be necessary to complete a transaction. This is currently available for EVM chains
POST
https://api.expand.network/chain/estimategas
Request Body
/createfeetransaction
This endpoint lets users collect fees on transactions via the Expand API or plug-in. By default, it deducts 5 basis points from the transaction value, but the fee can be customized.
POST
https://api.expand.network/chain/createfeetransaction
Request Body
Following is a sequence diagram for sendTransaction() process in chains:-
Last updated