Major SDK Components
Overview
The Dexible SDK repository is broken into several packages or modules. But when you create an SDK instance, it has several sub-layers that are useful for constructing orders, getting quotes, or querying the API.
Dexible SDK makes heavy use of ethers.js. Many of the arguments or Typescript interfaces expect ethers object types as input. We recommend you familiarize yourself with the ethers docs if you are not sure what the code in this documentation refers to. https://docs.ethers.io/v5/
Installation
Currently, the SDK is implemented in Typescript, so installation is simple for JavaScript projects. Future support for python is under development.
SDK
The top-most component is the SDK object. The SDK can be constructed with or without a ethers Signer instance. Omitting a signer will limit certain functionality within the SDK related to order submission.
Here is an example of creating an SDK instance:
In this code snippet, we first create an ethers InfuraProvider
instance. We use a wallet key found in the environment to create a new ethers Walle
t instance. Then we create the SDK instance using the wallet (signer). The SDK will detect the current network from the supplied provider.
Dexible currently supports the following networks:
Avalanche Mainnet
Binance Mainnet
Ethereum Mainnet
Ethereum Ropsten
Fantom Mainnet (Opera)
Polygon Mainnet
SDK in a Browser
The SDK can be used in a browser but requires a web3 provider, such as MetaMask or WalletConnect, and login support using JavaScript Web Tokens (JWT).
Using Web3 Provider
In a browser environment, you will likely have access to MetaMask or some other browser-based wallet. Here is an example to setup the signer you need for the SDK instead of a local wallet key:
JWT Handler
To create an SDK instance in the browser, you supply a handler that can store and retrieve a previously-created JWT. The interface looks like this:
The handler is given a token to store and is asked to retrieve a previously-stored token when needed. In most cases, you can store the token in localStorage in the browser or keep in memory if you don't want to store the token anywhere permanent.
Once you have a handler implementation, you can create an SDK instance with:
Here the JWTHolder just holds the token in memory. It's implementation might look like this:
Last updated