v4.7.10

What's Changed

• [General] Updated chains package.
• [Native] Providing a chain id that is not officially supported through the chains package should no longer be a blocking action i.e. you should still be able to connect so long as an rpc is available as well as interact with other thirdweb libraries without null references.
• [Native] Avoid posting wallet analytics when no client id provided

v4.7.9

What's Changed

• [General] Added Utils.ResolveAddressFromENS and Utils.ResolveENSFromAddress cross-platform utilities.
• [General] Added alternative Initialize function in ThirdwebManager.cs for more granular control.
• [Native] Fixed issue where bundle id would be appended to default rpc urls when no client id was provided, this should fix potential 401s.

v4.7.8

What's Changed

• [General] Added simpler Wallet.IsDeployed API for cross-platform Smart Wallet deployment checks.
• [Native] Improved error messaging when a Smart Wallet is not connected.

v4.7.7

What's Changed

• [WebGL] Improved Smart Wallet receipt polling mechanism. Added optimized support for newer factories.

v4.7.6

What's Changed

• [WebGL] Removed unnecessary WebGL-specific logs, improved stability and speed in some cases.

v4.7.5

What's Changed

• [WebGL] ERC20 Paymasters are now supported cross-platform.

v4.7.4

What's Changed

• [General] Better support for Unity 2021.x - removed duplicate dlls - the importing process should now be smoother.
• [Native] Removed Contract.Read raw result logging that might otherwise get spammy.
• [Native] Fixed issue where Wallet.SendRawTransaction value override would only be applied with hex values.

v4.7.3

What's Changed

• [Native] Hotfix receipt polling failing in Wallet.SendTransaction occasionally when using external wallets.

v4.7.2

What's Changed

• [General] Offline transaction - or more importantly UserOp (Smart Wallet Transaction) - signing is now supported by using the Transaction.Sign API. This will return a signed transaction or signed UserOperation respectively. These results can be forwarded to thirdweb Engine for later broadcasting. This is specially useful for cases where you may want to create a session key for new users, while not necessarily broadcasting it (and potentially paying for it) instantly; you might want to wait a few minutes to make sure they want to actually interact with your app before committing to the sponsorship, at which point you can broadcast the op first before handling further transactions. In this case, deployment of the smart wallet would also be bundled with the session key creation. Niche use case, but extremely powerful.
• [General] Added an example of the above use case in Prefab_SmartWallet.cs in the ridiculously-named method PreSignSessionKeyTxAsUserOpForLaterBroadcastingThroughThirdwebEngine
• [General] Wallet.SignTypedData no longer forcefully deploys your smart wallet, saving your users an unwanted extra signature.
• [WebGL] Wallet.SignTypedData is now supported in WebGL.
• [WebGL] Array arguments passed to custom contract calls are now treated as IEnumerable and any byte[] types are automatically hexified. This was the case for non array arguments only previously.

v4.7.1

What's Changed

• [Native] Upgrade MetaMask SDK to 1.3.1 by @ecp4224 in #153