File tree Expand file tree Collapse file tree 1 file changed +4
-2
lines changed Expand file tree Collapse file tree 1 file changed +4
-2
lines changed Original file line number Diff line number Diff line change @@ -144,7 +144,7 @@ const usdcResult = await client.invoke({
144
144
uri: " ens/uniswap.wraps.eth:v3" ,
145
145
method: " fetchToken" ,
146
146
args: {
147
- address: " 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 " ,
147
+ address: " 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 " ,
148
148
chainId: " MAINNET" ,
149
149
},
150
150
});
@@ -208,7 +208,9 @@ if (!resolutionResult.ok) {
208
208
console .log (resolutionResult .value );
209
209
```
210
210
211
- Now, if we look at the ` uri ` property of ` resolutionResult.value ` , we will see a WRAP URI
211
+ Now, if we look at the ` uri ` property of ` resolutionResult.value ` , we will see a WRAP URI.
212
+ We can also see a ` manifest ` property which is set to ` null ` , which you can safely ignore for now.
213
+ This is because our ENS Text Record Resolver Wrap only resolves from an ENS Text Record to another URI.
212
214
213
215
Once we have the IPFS hash, we will use the IPFS Wrap to fetch the contents of the Wrap's manifest file (` wrap.info ` ), and print them out.
214
216
You can’t perform that action at this time.
0 commit comments