cBridge Transfer Web Widget
To make widget integration simple, we provide complete source files which support cBridge transfer.
- Download source files from cBridgeTransferWidgetRepo
- Compare package.json with your own package.json and inject all needed dependencies
- Put files from public, scripts and src folder inside your project where is easy to manage.
- Inside the src folder, there is a cBridgeTransferWidget.tsx file. You may import it wherever you want to put and use CBridgeTransferWidget as an element inside your web project.
- Copy .env.test to .env. cBridge transfer widget uses values inside .env. If .env is missing or mis-configured, interface error alert will appear.
Run Sample
To give a quick experience about cBridge transfer widget, we create a sample index.js and App.js inside the src file folder.
- run
npm installoryarn installinside cBridget transfer widget root folder on console - run
cp .env.test .envon console (Don’t skip, otherwise you will see interface error) - run
npm startoryarn start
Import cBridgeTransferWidget
/// Adjust import path according to your project
import { Provider } from "react-redux";
import store from "./redux/store";
import CBridgeTransferWidget from './cBridgeTransferWidget';
/// Put following code where you need
<div>
<Provider store={store}>
<CBridgeTransferWidget />
</Provider>
</div>
Launch Production Environment
Once your project with transfer widget is ready for production launch, you need to contact us for production chain and token white list which is pre-defined here. According to your project requirement, you will have a specific white list. Once you replace existing chains_mainnet.ts with this special white list and copy .env.mainnet to .env, you can do some test on production environment and prepare for production launch.