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
ccip-sdk doesn't have static or cached `getWallet` anymore; instead, it
receives a `opts.wallet` directly in the `sendMessage` and
`executeReport` methods;
users are then expected to provide compatible wallets, like done by the
CLI without overriding any method in the SDK.
Optionally, `sendMessage` and `executeReport` also have companion `generateUnsignedSendMessage` and
71
+
`generateUnsignedExecuteReport` methods, returning chain-family-specific unsigned data, which one
72
+
can use to sign and send the transactions manually.
73
+
74
+
Notice that these are lower-level methods, and require the developer to handle the signing and
75
+
sending of the transactions themselves, skipping niceties from the higher-level methods, like
76
+
retries, gas estimation and transactions batching.
75
77
76
78
> [!TIP]
77
-
> For EVMChain on Browsers, there's no need to override like the above, since providing a `{ wallet: number | address }` option object will make it create a signer from `provider.getSigner(number)`, which should load the account from the browser's wallet extension.
79
+
> For EVMChain on Browsers, one can use `chain.provider.getSigner(numberOrAddress)` to fetch a
80
+
provider-backed signer from compatible wallets, like Metamask.
0 commit comments