You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: usecases/xerc20/setup-guide.md
+20-3Lines changed: 20 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,11 +99,28 @@ function burn(address _user, uint256 _amount) external;
99
99
100
100
#### LockboxAdapter
101
101
102
-
You might have noticed there's a `LockBoxAdapter` contract in the diagram above when you have a Lockbox setup. This contract facilitates the unwrapping of `xERC20 -> ERC20` on the destination chain. 
102
+
You might have noticed there's a `LockBoxAdapter` contract in the diagram above when you have a Lockbox setup. This contract facilitates the unwrapping of `xERC20 -> ERC20` on the destination chain and is needed for UIs to do this step for users.
103
103
104
-
We recommend deploying an adapter on each Lockbox chain so that bridge UIs can deliver the asset that the user expects to receive.
104
+
The Connext team has a `LockboxAdapter` deployed to all our supported chains (the implementation is available [here](https://github.com/connext/chain-abstraction-integration/blob/c35fbe757946cc76a826d93595cd99fd0db39c27/contracts/integration/LockboxAdapter.sol)). Use these if you plan to enable Connext as a bridge and want your token listed in our UI. 
105
105
106
-
You can deploy a simple Lockbox adapter like [this one](https://github.com/connext/chain-abstraction-integration/blob/next-lockbox-adapter/contracts/integration/Connext/NextLockboxAdapter.sol).
0 commit comments