Releases: thirdweb-dev/dotnet
Releases · thirdweb-dev/dotnet
v2.9.0
What's Changed
- Fixed an issue with typed data signing using In-App/Ecosystem Wallets when one of the fields was larger than Uint32.
- Improved NFT Metadata Population & Added Filters
- The
ERC1155_GetOwnedNFTs
extension now returns theQuantityOwned
metadata field correctly for each NFT. - The
ERC721_GetNFT
andERC721_GetAllNFTs
extensions can now take in a newfillOwner
parameter that defaults to true and decides whether to make additional requests to populate theOwner
field of the metadata, otherwise defaulting toConstants.ADDRESS_ZERO
. - The
ERC1155_GetNFT
andERC1155_GetAllNFTs
extensions can now take in a newfillSupply
parameter that defaults to true and decides whether to make additional requests to populate theSupply
field of the metadata, otherwise defaulting toBigInteger.MinusOne
.
- The
v2.8.3
What's Changed
- Fixed edge case where migrating a sharded wallet to enclave would throw
Invalid enclave wallet details being migrated
.
v2.8.2
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.
v2.8.1
What's Changed
- The inability to fetch
NFTMetadata
when calling an NFT-related method no longer throws, and instead returnsNFTMetadata
with a description containing the error message.
v2.8.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 optionaltokenAddress
override to transfer ERC20 tokens using said function; this is an alternative toThirdwebContract.ERC20_Transfer
.- ERC1155 transfer-related functions'
data
bytes parameter has now been made optional.
v2.7.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
andGetPhoneNumber
have been deprecated in favor ofGetUserDetails
- 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.
v2.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).
v2.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 aSmartWallet
without passing optional parameters will now attempt to use defaults from your dashboard Account Abstraction settings if any.- Create a
SmartWallet
with anEcosystemWallet
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.
- Create a
v2.5.2
What's Changed
- Added
AuthProvider.Github
as a new auth provider option for logging in with In-App or Ecosystem Wallets.
v2.5.1
What's Changed
- Removes
latest
parameter frometh_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