v5.9.1

What's Changed

• Adds GenerateExternalLoginLink method to forward the logged-in session of In-App or Ecosystem Wallets from .NET to React apps built using thirdweb.
  • Configure your React website to use thirdweb Connect, open the link generated by this method and your users will be autoconnected.
  • If using Ecosystem Wallets, make sure to create the ecosystem wallet with the same ecosystem id and partner id (if any) and include it as one of your wallets in, for example, your ConnectButton's wallets prop.
  • Make sure you're using the same api key on both ends.

v5.9.0

What's Changed

• Having an incorrect or slightly off system time would produce errors when logging in with In-App Wallets in some cases, we have added a fallback in this scenario that will work around this issue.
• IThirdwebWallet.Transfer now has an optional tokenAddress override to transfer ERC20 tokens using said function; this is an alternative to ThirdwebContract.ERC20_Transfer.
• ERC1155 transfer-related functions' data bytes parameter has now been made optional.
• The inability to fetch NFTMetadata when calling an NFT-related method no longer throws, and instead returns NFTMetadata with a description containing the error message.

• Enables custom implementation for OTP Verification Modal by @Vingator in #218
  • Introduces abstract OTP verification modal so you can customize it more easily.
  • Shared by In-App and Ecosystem Wallets.

New Contributors

• @Vingator made their first contribution in #218

v5.8.0

What's Changed

• In-App Wallets now use the same infrastructure as Ecosystem Wallets.
  • Up to 90% performance increase, specially on lower end devices or web platforms.
  • Much less cryptography done client side, using secure enclaves over shamir's secret sharing.
  • If you were using In-App Wallets previously, they will be automatically migrated to the new infrastructure upon first login.
    • If you were using custom auth with In-App Wallets before this release, you may pass your legacy encryption key during the creation of your wallet - it will be used to migrate your wallets to the new infrastructure upon first login.
    • Encryption keys are no longer required for In-App Wallets when logging in with JWT (OIDC Compatible Custom Auth) or AuthEndpoint (Generic Custom Auth).
• Added GetUserDetails method to In-App/Ecosystem Wallets that returns more information about your logged in user.
  • GetEmail and GetPhoneNumber have been deprecated in favor of GetUserDetails
• Added GetEcosystemDetails method to return general information about your Ecosystem Wallet, can be used for dynamic branding, etc.
• Fixes TokenERC721_MintTo functions failing with invalid signature; the token id parameter has also been removed.

v5.7.0

What's Changed

• Upgraded base project/examples to Unity 6 and Playground from In-App to Ecosystem Wallet.
  • Much faster on platforms like WebGL and lower end devices.
  • Ecosystem Wallets are shareable with third parties.
• Added a link.xml to cover Thirdweb's .NET Core assemblies. Minimal stripping is no longer a hard requirement unless using WalletConnect as one of your wallet provider options.
• Updated base project Android settings to target Min API 34 to match latest store policies.
• Upgraded EDM4U (External Dependency Manager) - contains various improvements.

v5.6.1

What's Changed

• Added support for passing generic List or Array types to ThirdwebContract.Read and deserializing tuples into them.
  • Supports List of objects return type.
  • Supports object[] return type.
  • Supports Lists and Arrays of primitive types (if your function returns a tuple of multiple values of the same type such as uints).
  • Supports complex structs (indexed and non indexed MySolTuple is serialized then deserialized into your passed type).
  • Supports complex struct arrays (indexed and non indexed MySolTupleArray is serialized as a dictionary then deserialized into your type).

v5.6.0

What's Changed

• Added AuthProvider.Twitch as a new auth provider option for logging in with In-App or Ecosystem Wallets.
• Upgrading an EcosystemWallet to a SmartWallet without passing optional parameters will now attempt to use defaults from your dashboard Account Abstraction settings if any.
  • Create a SmartWallet with an EcosystemWallet as a signer and no additional conflicting overrides to make use of this feature.
  • Explicitly passed SDK overrides will always take priority over dashboard options.
  • If dashboard options are unavailable/unset, we revert to previous default values for gas sponsorship and account factories.

v5.5.5

What's Changed

• Added AuthProvider.Github as a new auth provider option for logging in with In-App or Ecosystem Wallets.

v5.5.4

What's Changed

• MetaMaskWallet: GetAddress now enforces returning correctly checksummed address.
• WalletConnectWallet: Closing the modal now throws and interrupts the connection process properly.

v5.5.3

What's Changed

• WalletConnect and MetaMask wallet providers now hexify messages passed to IThirdwebWallet.PersonalSign before signing.
  • If you were signing a hash or a string starting with 0x before, nothing changes.
  • If you were signing a raw message like "Hello World" UTF8 String, we'd hexify it before sending it over to the wallet.
  • This fixes display issues on the latest version of MetaMask (specially mobile) which no longer supports plain text parameters for personal_sign.

v5.5.2

What's Changed

• Removes latest parameter from eth_estimateGas being used in ThirdwebTransaction.EstimateGasLimit on non-zk chains and methods that use it by extension, fixing issues on chains that do not support that parameter such as Binance Testnet.