.NET/Unity - RPC Overrides, AutoConnect & Extensions

.NET 2.13.0 and Unity 5.14.0/5.14.1 ship some popular requests - enjoy!

.NET/Unity - RPC Overrides, AutoConnect & Extensions

.NET Updates

  • Added DropER721_Burn, DropERC1155_BurnBatch, TokenERC721_Burn, TokenERC1155_Burn, TokenERC1155_BurnBatch contract extensions.
  • Overriding default RPCs is now allowed through a new ThirdwebClient creation parameter rpcOverrides.
var client = ThirdwebClient.Create(
    clientId: "myepicclientid",
    bundleId: "my.bundle.id", // for native apps
    rpcOverrides: new()
    {
        { 1, "https://eth.llamarpc.com" },
        { 42161, "https://arbitrum.llamarpc.com" }
    }
);
  • Removed some leftover unnecessary logging.

Integration in Unity & WalletConnect Updates

  • Additions from Thirdweb's .NET SDK Release 2.13.0
  • Exposed the ability to override RPC per chain ID in the ThirdwebManager.
  • Exposed the ability to force specific wallet ids into your WalletConnect modal in the ThirdwebManager.
  • Added hover tooltips for all ThirdwebManager options.
7af88a82f42c2f761f63993c46b220bd

Autoconnect Feature

Flag under ThirdwebManager > Preferences.

If enabled, Thirdweb will automatically connect to the last connected wallet on initialization (this behavior does not apply to the WalletConnectWallet provider option).

If a wallet was connected as a non smart wallet, then later upgraded, the smart wallet is saved as the last wallet, and the next session will autoconnect to the smart wallet.

Any failure during this entire flow should not throw.

d90a291c4de48fb3c35e7bec3dfab08f

.NET Release | NuGet Release | Unity Releases

Support | Documentation