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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,7 +165,7 @@ If you want Connext to be able to bridge your token ([here's our pitch in the ne
165
165
```
166
166
* The `canonical` object should always have `11111` as the `domain`. Change the `address` and `decimals` to match your home chain xERC20. For example, `RADAR`'s home chain is Ethereum.
167
167
* For each chain where your xERC20 is deployed (including the home chain), add an entry into the `representations` field keyed on the chain's `domainId`. 
168
-
* [You can look up each chain's domainId here](../../resources/supported-chains.md). We encourage commenting the chain name above each entry.
168
+
* [You can look up each chain's domainId here](broken-reference). We encourage commenting the chain name above each entry.
169
169
* `local` and `adopted` should both be set to the xERC20 address. These exist as separate fields for non-xERC20 assets.
170
170
* _Note: `domainId` is a Connext-specific identifier per chain that exists for forward compatibility with non-evm chains._
0 commit comments