|
| 1 | +--- |
| 2 | +date: "2025-11-24T09:22:50+08:00" |
| 3 | +external_site: circle |
| 4 | +external_url: https://www.circle.com/blog/integrating-rainbowkit-with-bridge-kit-for-crosschain-usdc-transfers |
| 5 | +noindex: true |
| 6 | +tags: |
| 7 | + - circle |
| 8 | + - javascript |
| 9 | +title: "Integrating RainbowKit with Bridge Kit for crosschain USDC transfers" |
| 10 | +--- |
| 11 | + |
| 12 | +Given that browser-based wallets are among the most common types of crypto wallet, having a “Connect Wallet” button on an application is becoming an expectation among users. As the ecosystem expands, there are more competing wallets on the market, and it is not uncommon for someone to have multiple wallets installed and active at the same time. |
| 13 | + |
| 14 | +Even though we have the [EIP-1193: Ethereum Provider JavaScript API](https://eips.ethereum.org/EIPS/eip-1193) that standardizes a Provider object and specifies its expected behaviors, the fragmented wallet ecosystem has made it quite challenging for application developers to connect to their users’ wallets. Thankfully, we have libraries like [wagmi](https://wagmi.sh/core/why) that help to abstract the wallet, provider and network logic into a more convenient developer experience. |
| 15 | + |
| 16 | +In this tutorial, we will be integrating [RainbowKit](https://rainbowkit.com/), which is a React library built on top of wagmi and viem that allows us to add a wallet connection component to our bridging application, powered by [Bridge Kit](https://developers.circle.com/bridge-kit). |
| 17 | + |
| 18 | +## Crosschain transfers with Bridge Kit |
| 19 | + |
| 20 | +Bridge Kit is powered by [CCTP](https://www.circle.com/cross-chain-transfer-protocol) under the hood, and abstracts away a lot of the complexity of implementing CCTP, especially with the large number of bridge routes across numerous chains. An example of the key method call is as follows: |
| 21 | + |
| 22 | +```ts |
| 23 | +// Transfer 10.00 USDC from Arc Testnet to Solana Devnet |
| 24 | +const result = await kit.bridge({ |
| 25 | + from: { adapter: viemAdapter, chain: "Arc_Testnet" }, |
| 26 | + to: { adapter: solanaAdapter, chain: "Solana_Devnet" }, |
| 27 | + amount: "10.00", |
| 28 | +}); |
| 29 | +``` |
| 30 | + |
| 31 | +Bridge Kit makes use of adapters to manage the blockchain-specific bridging operations for a particular network and is fully compatible with viem or ethers for EVM-compatible blockchains and Solana. |
| 32 | + |
| 33 | +To retrieve a full list of supported chains, we can use the `getSupportedChains()` method, which returns an array of blockchain objects, each containing key information about the chain that can be used in our application’s UI. |
| 34 | + |
| 35 | +```json |
| 36 | +{ |
| 37 | + "type": "evm", |
| 38 | + "chain": "Arc_Testnet", |
| 39 | + "name": "Arc Testnet", |
| 40 | + "title": "ArcTestnet", |
| 41 | + "nativeCurrency": { |
| 42 | + "name": "Arc", |
| 43 | + "symbol": "Arc", |
| 44 | + "decimals": 18 |
| 45 | + }, |
| 46 | + "chainId": 5042002, |
| 47 | + "isTestnet": true, |
| 48 | + "explorerUrl": "https://testnet.arcscan.app/tx/{hash}", |
| 49 | + "rpcEndpoints": ["https://rpc.testnet.arc.network/"], |
| 50 | + "eurcAddress": "0x89B50855Aa3bE2F677cD6303Cec089B5F319D72a", |
| 51 | + "usdcAddress": "0x3600000000000000000000000000000000000000", |
| 52 | + "cctp": { |
| 53 | + "domain": 26, |
| 54 | + "contracts": { |
| 55 | + "v2": { |
| 56 | + "type": "split", |
| 57 | + "tokenMessenger": "0x8FE6B999Dc680CcFDD5Bf7EB0974218be2542DAA", |
| 58 | + "messageTransmitter": "0xE737e5cEBEEBa77EFE34D4aa090756590b1CE275", |
| 59 | + "confirmations": 1, |
| 60 | + "fastConfirmations": 1 |
| 61 | + } |
| 62 | + } |
| 63 | + }, |
| 64 | + "kitContracts": { |
| 65 | + "bridge": "0xC5567a5E3370d4DBfB0540025078e283e36A363d" |
| 66 | + } |
| 67 | +} |
| 68 | +``` |
| 69 | + |
| 70 | +In our React application, we make use of a custom hook just for the bridging functionality by initializing the SDK, then calling the bridge method on it, passing in the necessary parameters supplied from the user interface. |
| 71 | + |
| 72 | +```ts |
| 73 | +import { BridgeKit } from "@circle-fin/bridge-kit"; |
| 74 | + |
| 75 | +const kit = new BridgeKit(); |
| 76 | +const result = await kit.bridge({ |
| 77 | + from: { adapter: params.fromAdapter, chain: params.fromChain as any }, |
| 78 | + to: { adapter: params.toAdapter, chain: params.toChain as any }, |
| 79 | + amount: params.amount, |
| 80 | +}); |
| 81 | +``` |
| 82 | + |
| 83 | +## Adding the Connect Wallet button |
| 84 | + |
| 85 | +Make sure to follow the instructions from [RainbowKit’s documentation](https://rainbowkit.com/docs/installation) to install and set up RainbowKit into the project. It has dependencies on wagmi, [viem](https://viem.sh/) and [TanStack Query](https://tanstack.com/query/latest). The application has to be wrapped in the necessary providers for the ConnectButton component to work. |
| 86 | + |
| 87 | +```ts |
| 88 | +import { ConnectButton } from "@rainbow-me/rainbowkit"; |
| 89 | + |
| 90 | +export const App = () => { |
| 91 | + return <ConnectButton />; |
| 92 | +}; |
| 93 | +``` |
| 94 | + |
| 95 | +The component comes with a button that triggers a modal which detects available wallets to connect to and connects the application to the wallet chosen by the user. |
| 96 | + |
| 97 | +**Building the adapter object with wagmi** |
| 98 | + |
| 99 | +Once the user’s wallet is connected to our application, wagmi allows us to pull the wallet connection information and extract the EIP-1193 provider so we can build an adapter object that Bridge Kit recognizes and will use for the transfer. |
| 100 | + |
| 101 | +```ts |
| 102 | +import { useConnectorClient } from "wagmi"; |
| 103 | +import { createAdapterFromProvider } from "@circle-fin/adapter-viem-v2"; |
| 104 | + |
| 105 | +// Get the connected wallet's provider from wagmi |
| 106 | +const { data: client } = useConnectorClient(); |
| 107 | +const provider = client?.transport?.value?.provider; |
| 108 | + |
| 109 | +// Use that provider to create a Circle adapter |
| 110 | +const adapter = await createAdapterFromProvider({ provider }); |
| 111 | +return adapter; |
| 112 | +``` |
| 113 | + |
| 114 | +Depending on how the application is structured, this logic can be put in a separate custom hook or implemented as part of a component. If this adapter logic is implemented as a custom hook, we can use it in the relevant component when the bridge hook is called. |
| 115 | + |
| 116 | +## Putting it all together |
| 117 | + |
| 118 | +We would use state to capture the user’s inputs for their chosen source chain, destination chain and amount to transfer, and call the bridge hook with the adapter and user inputs. |
| 119 | + |
| 120 | +```ts |
| 121 | +const { evmAdapter } = useEvmAdapter(); |
| 122 | +const [sourceChain, setSourceChain] = useState<SupportedChain>("Arc_Testnet"); |
| 123 | +const [destinationChain, setDestinationChain] = useState<SupportedChain>(""); |
| 124 | +const [amount, setAmount] = useState<string>("0"); |
| 125 | + |
| 126 | +const { bridge, isLoading, error, clear } = useBridge(); |
| 127 | + |
| 128 | +const response = await bridge({ |
| 129 | + fromChain: sourceChain, |
| 130 | + toChain: destinationChain, |
| 131 | + amount, |
| 132 | + fromAdapter: evmAdapter, |
| 133 | + toAdapter: evmAdapter, |
| 134 | +}); |
| 135 | +``` |
| 136 | + |
| 137 | +The response object contains a lot of information about the entire CCTP transaction, including chain details, contract addresses and details of each step, which can be used to build out informative UIs for the end-user. The following is an abridged version of the response: |
| 138 | + |
| 139 | +```json |
| 140 | +{ |
| 141 | + "state": "success", |
| 142 | + "amount": "4000000", |
| 143 | + "token": "USDC", |
| 144 | + "source": { |
| 145 | + "address": "0xf6aa88ee4b7b10abbffbfa7d85bcffef7eab6fe4", |
| 146 | + "chain": {...} |
| 147 | + }, |
| 148 | + "destination": { |
| 149 | + "address": "0xf6aa88ee4b7b10abbffbfa7d85bcffef7eab6fe4", |
| 150 | + "chain": {...} |
| 151 | + }, |
| 152 | + "steps": [ |
| 153 | + { |
| 154 | + "name": "approve", |
| 155 | + "state": "success", |
| 156 | + "txHash": "0x0efe59bf6b418484963d54a46d7cf7314cae906c3ced6d1ed4ab74aacddb062b", |
| 157 | + "data": { |
| 158 | + "txHash": "0x0efe59bf6b418484963d54a46d7cf7314cae906c3ced6d1ed4ab74aacddb062b", |
| 159 | + "status": "success", |
| 160 | + "cumulativeGasUsed": "222484", |
| 161 | + "gasUsed": "55684", |
| 162 | + "blockNumber": "8359932", |
| 163 | + "blockHash": "0xfb96409a5cf4f370196911c5b79daaf304b4744b7ab44362b0e92f75ad456727", |
| 164 | + "transactionIndex": 6, |
| 165 | + "effectiveGasPrice": "660000000000" |
| 166 | + }, |
| 167 | + "explorerUrl": "https://testnet.arcscan.app/tx/0x0efe59bf6b418484963d54a46d7cf7314cae906c3ced6d1ed4ab74aacddb062b" |
| 168 | + }, |
| 169 | + { |
| 170 | + "name": "burn", |
| 171 | + ... |
| 172 | + }, |
| 173 | + { |
| 174 | + "name": "fetchAttestation", |
| 175 | + ... |
| 176 | + }, |
| 177 | + { |
| 178 | + "name": "mint", |
| 179 | + ... |
| 180 | + } |
| 181 | + ], |
| 182 | + "config": { |
| 183 | + "transferSpeed": "FAST" |
| 184 | + }, |
| 185 | + "provider": "CCTPV2BridgingProvider" |
| 186 | +} |
| 187 | +``` |
| 188 | + |
| 189 | +## Wrapping up |
| 190 | + |
| 191 | +We have built a sample application that incorporates the key points covered in this tutorial to bridge USDC across all the [chains that support CCTP](https://developers.circle.com/cctp/cctp-supported-blockchains). Feel free to clone the [GitHub repo](https://github.com/circlefin/circle-bridge-kit-transfer) and play around with the application to see how it works. |
| 192 | + |
| 193 | + |
| 194 | + |
| 195 | +Combining RainbowKit for wallet connection and Bridge Kit for crosschain USDC transfers allows us to build a smoother user experience with fewer lines of code. Check out [Bridge Kit](https://developers.circle.com/bridge-kit) to start integrating crosschain transfers into your own application. |
0 commit comments