Changelog

about 5 hours ago

Toomas Oosalu

Native Balance Support In Insight

Insight API adds a new token balances endpoint that also supports native token balances. It will replace the current ERC-20 balance endpoint which is being deprecated.

ERC-20 Balance Endpoint Deprecation

This endpoint is being deprecated in favor of v1/tokens to be better aligned with the NFT endpoints and make it easier to expand the capabilities of the new endpoint in the future.

New Tokens Endpoint

v1/tokens has full parity with the ERC-20 balances endpoint but also adds support for native token balances and also returns the owner_address in the response.

Native balances are always returned at the beginning of the response. If they are not needed, they can be removed from the response by setting the include_native query param to false.

The native token address is 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

The new endpoint is available in our playground.

📖 Learn more about Insight - it’s open source and ready to power your applications!

5 days ago

Arsenii

Insight API: Unified Token Transfers with Metadata

We’ve improved the Insight API to support unified access to all token transfers — both NFTs (ERC721/ERC1155) and fungible tokens (ERC20) — through a single, consistent endpoint 🚀

Highlights:

You can now fetch NFT and ERC20 transfers in one call.
Transfer responses include metadata for both NFTs and ERC20 tokens.
Added support for a new "burn" transfer type when tokens are sent to the zero address.
Introduced filtering by token type (erc20, erc721, erc1155) via query parameters.

This change simplifies integration and improves performance when querying mixed token transfers — especially useful for clients who need a single endpoint to track all token activity.

7 days ago

Joaquim Verges

thirdweb SDK 5.100.0 - Universal Bridge improvements

The thirdweb TypeScript SDK was just updated with significant updates to the universal bridge component and APIs.

Installation


pnpm add thirdweb@5.100.0

Highlights

No more insufficient funds walls

When you do a transaction in a react environment (useSendTransaction or TransactionButton), and the user does not have enough funds in their wallet, we now by default always show them a flow to top up their wallet:

Pay with another wallet
Pay with another token
Pay with fiat
Deposit funds (for testnets and unsupported routes) with balance auto refresh

PayEmbed improvements

The PayEmbed component has been improved across the board to load routes, quotes and status faster than ever before. No code changes required.

Bridge.Transfer – token transfers in one call


import { Bridge, NATIVE_TOKEN_ADDRESS, toWei } from "thirdweb";
 
const quote = await Bridge.Transfer.prepare({
  chainId: 1,
  tokenAddress: NATIVE_TOKEN_ADDRESS,
  amount: toWei("0.01"),
  sender: "0xSender",
  receiver: "0xReceiver",
  client,
});
 
// quote.transactions → execute sequentially with sendAndConfirmTransaction

Bridge.Onramp – fiat‑to‑crypto


import { Bridge } from "thirdweb";
import { ethereum } from "thirdweb/chains";
import { NATIVE_TOKEN_ADDRESS, toWei } from "thirdweb/utils";
 
const session = await Bridge.Onramp.prepare({
  client,
  onramp: "stripe",
  chainId: ethereum.id,
  tokenAddress: NATIVE_TOKEN_ADDRESS,
  amount: toWei("10"),
  receiver: "0xReceiver",
});
 
window.location.href = session.link;
 
// Later
const status = await Bridge.Onramp.status({ id: session.id, client });

Upgrade for smoother cross‑chain and on‑ramp experiences!

8 days ago

Cillian Berragan

Nebula v0.0.16: Advanced Contract Tools & Cross-Chain Improvements

Nebula 0.0.16 brings significant improvements to contract interactions, introduces a new token burn capability, and enhances cross-chain support.

Features

New Token Burn Tool: Permanently remove tokens from circulation with smart fallbacks. Supports both ERC20 tokens and native currencies, with automatic detection of burn methods.
Contract Type Detection: Automatically identify contract types (ERC20, ERC721, ERC1155, marketplace, proxy, multisig, etc.) to provide more context-aware interactions.
Enhanced Contract Metadata: Contract analysis now includes token-specific data (decimals, total supply), NFT-specific features (tokenURI support), and better handling of EOA addresses.
Improved Universal Bridge: Cross-chain transfers now work seamlessly across all supported chains with improved validation and confirmation.
Tool Consolidation: Combined similar tools (wallet address/token balance, transaction lookups) for more streamlined interactions and consistent responses.
Token-Specific Wallet Queries: Added support for querying specific token balances in a wallet, enabling more focused blockchain data retrieval.
Human-Readable Values: All token amounts now use human-readable formats with proper decimal handling across all contract tools.

Improvements

New Block Tool: New unified tool replaces separate block retrieval methods with support for block numbers, hashes, and special tags ('latest', 'earliest', 'pending').
Arbitrary Contract Output: Enhanced with additional metadata to support Nebula's response.
Link Formatting: Better formatting of transaction hashes and wallet addresses in responses for improved readability.

Bug Fixes

Fixed transaction data formatting in contract preparation tools
Corrected decimals handling in token operations
Improved URI formatting for NFT collections
Enhanced wallet address handling in transaction tools

12 days ago

Jake Loo

Nebula v0.0.15: Enhanced Contract Analysis & Improved Streaming

Overview

Nebula v0.0.15 focuses on enhancing contract metadata analysis and fixing core functionality issues. This release significantly improves contract metadata output, making it easier to understand smart contract functions and capabilities. It also fixes critical issues with address prediction and streaming responses.

Features

Enhanced Contract Metadata Tool: Completely revamped output format with better function categorization and improved contract type detection
Support for Code Block Streaming: Better handling of code snippets with proper formatting
Address and Transaction Links: Automatically creates clickable blockchain explorer links

Bug Fixes

Deploy Address Prediction: Fixed CREATE2 address calculation for cross-chain deployments
Streaming Response Buffering: Improved text streaming with better handling of code blocks
Transaction History: Re-added transaction lookup by hash to support transaction analysis
Image Rendering: Fixed generated images not showed up as an event

Try it out today at https://nebula.thirdweb.com!

12 days ago

Firekeeper

Expanding EIP-7702 Chain Support

As soon as the Pectra Ethereum Upgrade was released, so were our next-gen 7702 smart accounts - read more about them here!

Today, we introduce support for more chains that upgraded to Pectra!

TypeScript / React


// plain TypeScript
import { inAppWallet } from "thirdweb/wallets";
 
const wallet = inAppWallet({
  executionMode: {
    mode: "EIP7702",
    sponsorGas: true,
  },
});


// React (e.g. Next.js)
import { inAppWallet } from "thirdweb/wallets";
import { ConnectButton } from "thirdweb/react";
 
<ConnectButton
  client={client}
  wallets={[
    inAppWallet({
      executionMode: {
        mode: "EIP7702",
        sponsorGas: true,
      },
    }),
  ]}
/>;

.NET / Unity


// .NET (server, Godot C#, MAUI, etc.)
var smartEoa = await InAppWallet.Create(
    client: thirdwebClient,
    authProvider: AuthProvider.Google,
    executionMode: ExecutionMode.EIP7702Sponsored
);


// Unity (C#)
var wallet = await ConnectWallet(
    new WalletOptions(
        provider: WalletProvider.InAppWallet,
        chainId: 11155111,
        inAppWalletOptions: new InAppWalletOptions(
            authprovider: AuthProvider.Google,
            executionMode: ExecutionMode.EIP7702Sponsored
        )
    )
);

12 days ago

Arsenii

Insight Webhooks Just Got More Reliable

We’ve re-architected how Insight webhooks are delivered — introducing a durable execution model that improves reliability, observability, and resilience.

🔂 Durable by Design

Webhook delivery is now handled through a stateful, retry-capable execution engine. This means:

Delivery persists through failures – Webhooks won’t silently fail or get lost due to transient issues.
Exponential backoff retries – Prevents overwhelming client systems while still ensuring delivery.

📈 Better Observability & Tracking

Every webhook delivery is now monitored and logged with structured metadata, giving us (and soon, you) much more insight into what’s happening:

Full delivery history and error context for each webhook delivery
Fine-grained attribution by webhook/project/team for improved debugging

⚙️ Configurable & Flexible

We've introduced configuration options that make it easier to tune webhook behavior per environment, including retry policies and timeouts.

🔮 What’s Next

This is just the beginning. Next up:

Durable storage for visualising webhook execution history and efficient retrieval of executions for a specific webhook
Improved webhook suspension management with visibility into paused endpoints
Self-serve observability tools so teams can view delivery status, retry logic, and failure patterns directly

If you rely on Insight webhooks to power workflows, this upgrade makes them more dependable and transparent.

Let us know what you'd like to see next → we're building this with you in mind.

13 days ago

Cillian Berragan

Nebula v0.0.14: Code Agent & Real-time Streaming

We're excited to announce a major upgrade to Nebula that introduces powerful new capabilities through the implementation of a code generation agent and real-time response streaming.

These changes are live now at nebula.thirdweb.com!

Overview

This release transforms Nebula with the integration of an agent that can generate code, enabling significantly more complex reasoning and multi-stage task processing. We've also added word-by-word streaming for a more responsive user experience, alongside numerous tool enhancements to support these new capabilities.

Powerful Multi-stage Processing

Replacing Nebula's main agent with a code-generation agent brings a revolutionary approach to how Nebula processes blockchain requests:

Code-first approach allows Nebula to write and execute Python code snippets for complex tasks
Enhanced reasoning capabilities for multi-stage blockchain operations
30% more efficient processing compared to traditional tool-calling approaches
Improved problem decomposition for handling complex user requests

Now Nebula can automatically break down multi-stage operations like "Deploy a new ERC-721 contract, mint an NFT, and send it to cjber.eth" into logical steps with appropriate parameter validation at each stage.

Improved Thought Process Visibility

With Code Agent, Nebula now exposes more of its thinking process:

Watch as Nebula reasons through complex blockchain operations
See the logical steps it takes to solve multi-part problems
Better understand why specific approaches or parameters are used

This transparency helps users learn from Nebula's analytical approach while providing greater confidence in the recommended actions.

Word-by-word Response Generation

One of the most visible improvements in this release is the addition of real-time, word-by-word streaming:

Responses begin appearing immediately, eliminating long wait times
Thoughts and reasoning are streamed as they're generated
See Nebula work through complex problems in real-time

This creates a much more interactive experience, similar to watching an expert think through blockchain challenges.

Comprehensive Tool Enhancements

To support the new Code Agent architecture, we've made extensive improvements to Nebula's tool system:

Standardized Framework

Unified output formatting across all blockchain tools
Consistent validation patterns for blockchain parameters
Improved error handling with more descriptive messages

Enhanced Blockchain Operations

Consolidated related tools for more intuitive interactions
Better validation for blockchain addresses, amounts, and parameters
Improved handling of token standards and contract interactions

Performance Optimizations

More efficient tool execution for faster responses
Better handling of blockchain data pagination
Optimized resource usage for complex operations

What This Means For Users

These improvements deliver several key benefits:

More Complex Tasks: Nebula can now handle significantly more complex, multi-stage blockchain operations
Faster Responses: Start seeing results immediately with word-by-word streaming, and more efficient tool calling through code means overall response times are reduced

3. Better Reasoning Transparency: More visible reasoning helps users understand blockchain operations

More Reliable Interactions: Enhanced validation ensures operations are checked thoroughly before execution

We're excited for you to experience the power of Code Agent and real-time streaming in Nebula. These improvements represent a significant leap forward in making blockchain interactions more intuitive, responsive, and powerful.

Ready to try out all these new features? Give it a spin at nebula.thirdweb.com!

14 days ago

Greg

Onramp to Any Token from 160+ Countries

We've added Transak to our suite of supported onramp providers in the Universal Bridge. Along with Coinbase and Stripe, Transak brings the total supported countries to over 160, and supported direct onramp tokens to over 170. Explore all the countries and tokens Transak supports.

When used with Universal Bridge, our onchain routing allows you to onramp to thousands of tokens. Some of the notable countries the Universal Bridge now supports:

Philippines
South Korea
Brazil
Japan
Indonesia
Hong Kong

Onramping with the API

To get an onramp link and quote using the Universal Bridge API, use the following:


const res = await fetch(
  "https://bridge.thirdweb.com/v1/onramp/prepare",
  {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "x-secret-key": process.env.THIRDWEB_SECRET_KEY,
    },
    body: JSON.stringify({
      onramp: "transak",
      chainId: 4337,
      tokenAddress: "0xAFf7314Bc869f4AB265ec7EfA8E442F1D978d7a",
      maxSteps: 2,
      amount: "200000000000000000",
      currency: "USD",
      receiver: "0x2a4f24f935eb178e3e7ba9b53a5ee6d8407c0709",
    }),
  },
);
 
const data = await res.json();

The returned quote will look something like this:


{
  "data": {
    "id": "3179cf89-e915-4103-b61e-991bf3a33e93",
    "link": "https://global.transak.com/...",
    "destinationAmount": "2000010000000000",
    "timestamp": 1747165958956,
    "expiration": 1747169558945,
    "intent": {
      "chainId": 4337,
      "tokenAddress": "0xAff7314Bc869ff4AB265ec7Efa8E442F1D978d7a",
      "amount": "2000010000000000",
      "receiver": "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
      "onramp": "transak",
      "currency": "USD",
      "maxSteps": 2
    },
    "steps": [
      {
        "originToken": {
          "chainId": 4337,
          "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
          "symbol": "BEAM",
          "name": "Beam",
          "decimals": 18,
          "priceUsd": 0.00974066,
          "iconUri": "https://coin-images.coingecko.com/coins/images/32417/large/chain-logo.png?1698114384"
        },
        "destinationToken": {
          "chainId": 4337,
          "address": "0xAff7314Bc869ff4AB265ec7Efa8E442F1D978d7a",
          "symbol": "FP",
          "name": "Forgotten Playland",
          "decimals": 18,
          "priceUsd": 0.0006662,
          "iconUri": "https://coin-images.coingecko.com/coins/images/35339/small/FP-Token-Icon_%281%29.png?1744266332"
        },
        "transactions": [
          {
            "type": "eip1559",
            "to": "0xF8Ab2dBE6c43bf1a856471182290f91D621Ba76d",
            "from": "0x2a4f24F935Eb178e3e7BA9B53A5Ee6d8407C0709",
            "value": "142478928995176",
            "data": "...",
            "chainId": 4337,
            "action": "buy",
            "id": "0xb15a4e9999fc5504e64085dd812b33090e33e3b3b84f4d1adbaf52e6587af8f1",
            "spender": "0x965B104e250648d01d4B3b72BaC751Cde809D29E"
          }
        ],
        "originAmount": "142478928995176",
        "destinationAmount": "2000010000000000",
        "estimatedExecutionTimeMs": 12000
      }
    ],
    "currency": "USD",
    "currencyAmount": 1.06
  }
}

You can then use the top-level id to get the onramp's status:


const res = await fetch(
  "https://bridge.thirdweb.com/v1/onramp/status?id=3179cf89-e915-4103-b61e-991bf3a33e93",
  {
    method: "GET",
    headers: {
      "Content-Type": "application/json",
      "x-secret-key": process.env.THIRDWEB_SECRET_KEY,
    },
  },
);
 
const data = await res.json();

The returned status:


{
  "data": {
    "status": "COMPLETED",
    "transactions": [
      {
        "chainId": 4337,
        "transactionHash": "0xd36a649a23044e980446a3183c6cfe9016d539a6ff88f31b611a1614b1d265aa"
      }
    ],
    "purchaseData": null
  }
}

To learn more about how to use thirdweb's Universal Bridge for onramping, bridging, or swapping, check out the API reference or docs.

14 days ago

Greg

Instant Token Balances in the Universal Bridge Embed

We've improved token balance fetching in the PayEmbed for near-instant balance display. We check thousands of tokens for possible routes and return any the user can use to perform their desired transaction in less than a second.

The improved performance is available as of TypeScript SDK v5.99.0. Try it out for yourself on the thirdweb playground.

0:00

/0:26

16 days ago

Joaquim Verges

Improved EIP-5792 support

Version 5.99.0 of the TypeScript thirdweb SDK brings first-class support for EIP-5792. The new implementation streamlines how you batch calls, sponsor gas and track confirmations, while aligning our API with the final EIP-5792 spec.

Highlights:

New React hooks – useSendAndConfirmCalls, useWaitForCallsReceipt
Simpler useSendCalls / sendCalls signatures – no more explicit client prop, aligned return types with v2.0.0 of the EIP
Decoupled receipt handling for flexible UI handling of receipts
Easy wallet-capability detection

Live Demo

As usual, you can try out the integration on the live playground:

0:00

/3:03

Usage

TypeScript (node / backend)


import { sendCalls, waitForCallsReceipt } from "thirdweb";
 
// Build your calls array (tx1, tx2 … conforming to EIP-5792 structure)
const result = await sendCalls({
  calls: [tx1, tx2],
  sponsorGas: true, // optional gas sponsorship
});
 
// Later - or in a different process
const receipt = await waitForCallsReceipt(result.id);
 
console.log("First tx hash:", receipt.receipts[0].transactionHash);

React (front-end)

1 – Fire-and-forget, then wait for the receipt


const { mutate: sendCalls } = useSendCalls();
const { data: result } = await sendCalls({ calls: [tx1, tx2] });
 
// later, or in another component
const { data: receipt, isLoading } = useWaitForCallsReceipt(
  result.id,
);

2 – One-liner helper


const { mutate: sendAndConfirmCalls, data: receipt } =
  useSendAndConfirmCalls();
 
await sendAndConfirmCalls({ calls: [tx1, tx2] });
console.log("Bundle confirmed:", receipt.bundleHash);

Breaking changes

The previous version of the SDK had beta support for 5792, which got some breaking changes in this version, listed below:

React

Before	After
useSendCalls({ client }) returned string bundleId	useSendCalls() returns { id, client, chain, wallet }
useSendCalls({ waitForBundle: true }) returned receipts	Waiting is now decoupled; use useWaitForCallsReceipt
N/A	New helper useSendAndConfirmCalls combines both steps

TypeScript / non-React

Before	After
type SendCallsResult = string;	type SendCallsResult = { id: string; client: ThirdwebClient; chain: Chain; wallet: Wallet }
getCallsStatus(bundleId)	getCallsStatus(id) (field renamed)

Any existing code that relies on the old return type must now read result.id and call waitForCallsReceipt (or the React hook) to obtain transaction receipts.

We recommend upgrading as soon as possible to leverage gas sponsorship and the simplified developer experience. For a full diff, see PR #7003 on GitHub.

17 days ago

Firekeeper

Expanding EIP-7702 In-App Wallet Support

As soon as the Pectra Ethereum Upgrade was released, so were our next-gen 7702 smart accounts - read more about them here!

Today, we introduce support for more chains that upgraded to Pectra!

TypeScript / React


// plain TypeScript
import { inAppWallet } from "thirdweb/wallets";
 
const wallet = inAppWallet({
  executionMode: {
    mode: "EIP7702",
    sponsorGas: true,
  },
});


// React (e.g. Next.js)
import { inAppWallet } from "thirdweb/wallets";
import { ConnectButton } from "thirdweb/react";
 
<ConnectButton
  client={client}
  wallets={[
    inAppWallet({
      executionMode: {
        mode: "EIP7702",
        sponsorGas: true,
      },
    }),
  ]}
/>;

.NET / Unity


// .NET (server, Godot C#, MAUI, etc.)
var smartEoa = await InAppWallet.Create(
    client: thirdwebClient,
    authProvider: AuthProvider.Google,
    executionMode: ExecutionMode.EIP7702Sponsored
);


// Unity (C#)
var wallet = await ConnectWallet(
    new WalletOptions(
        provider: WalletProvider.InAppWallet,
        chainId: 11155111,
        inAppWalletOptions: new InAppWalletOptions(
            authprovider: AuthProvider.Google,
            executionMode: ExecutionMode.EIP7702Sponsored
        )
    )
);

19 days ago

Jake Loo

Nebula API v0.0.13: Image & Transaction Message

Overview

This release includes significant improvements to the Nebula agent's architecture, entity memory management, error handling, and documentation search capabilities. Key updates focus on simplifying blockchain entity handling, improving transaction management, supporting more content types in chat, and enhancing error messaging for a better user experience.

Features

New Content Support in Chat
- Add support for image and transaction content types in chat messages


{
  "messages": [
     { 
       "role": "user", 
       "content": [
         { "type": "image", "image_url": "ipfs://Qmefr67P2qZS5BS9KBbZVgVXAYCdeezkN4je4tnd6xib4c" }, 
         { "type": "text", "text": "Please describe the image" }
       ]
     }],
     "stream": "true", 
}

Enable transaction hash messages for blockchain status checks


{
  "messages": [
     { 
       "role": "user", 
       "content": [
          { "type": "transaction", "transaction_hash": "0x112c7d127dbd1fef1006aa6211462a2635b504fc42f71aad0cae4b1e7ddba32a", "chain_id": 1 }
        ]
     }],
     "stream": "true", 
}

Enhanced Entity Management
- Simplify loading entities by type with a cleaner implementation
- Improve entity memory formatting for better readability
- Reduce database operations for improved performance
- Add user wallet as parsed entity for better context
Documentation and Search Improvements
- Implement new LLMs documentation search with better context retrieval
- Add URL to web search results for better source attribution
- Format blockchain entities as links in responses
Improved Error Handling
- Better error messaging for deployment and payment issues
- Add instructions to help users correct chain context issues
- Support graceful error handling in streaming responses

API Changes

New agent action types for better request handling
Support for image and transaction inputs in chat messages
More structured error responses with helpful suggestions
Revised agent action structure to use more specific types
Updated event streaming format for better client compatibility

Bug Fixes

Fix undefined behavior when no routes found in Universal Bridge
Handle payment required errors from storage service
Fix wallet balance formatting and improve entity display
Ensure price and token supply data is displayed correctly

Ready to try out all these new features? Give it a spin at https://nebula.thirdweb.com!

19 days ago

Greg

$HONEY is now Available on Universal Bridge

We just added Universal Bridge support for $HONEY, Berachain's stablecoin. You can now pay with or accept HONEY for any transaction on any chain.

0:00

/0:34

19 days ago

Joaquim Verges

Prithvish Baidya

Introducing Engine Cloud

Introducing Engine Cloud — read and write to the blockchain at scale, without the cost or complexity of traditional blockchain API setups.

Why we built Engine Cloud

Engine Cloud is our answer to lowering the barrier to developing high volume applications onchain- with fully-hosted, scalable APIs that let you perform on-chain actions from your backend. No upfront costs. Only pay-as-you-go.

It includes a non-custodial way to manage your wallets and ready-to-go API calls that do things like mint NFTs, transfer tokens, airdrops, sponsor gas for users — on any contract, across any EVM chain.

Engine Cloud includes:

Server Wallets managed via Vault (our new key management system)
New Transaction Gateway with retry logic, nonce management, and sub-second speed
New transaction API improved DX, new typescript SDK integration, and more
Secure, granular access tokens to work with multiple wallets and teams via vault access tokens and permissions
No more manual gas top-ups or alerts— we handle that for you by topping through our paymasters from your payment on file.

Learn more about use cases and benefits of using Engine Cloud.

Get Started

Create a thirdweb project — this will include a ready-to-go Engine server for you to start making API calls on.
Get your Vault Admin Key + Access Tokens — via the dashboard. Learn more about Vault.
Create a server wallet — for secure, granular signing and management. You can create one or multiple server wallets.
Start calling the API — write and send transactions from your backend using the simple API endpoints. All API endpoints can be accessed via the dashboard or through the API reference.

Engine will be free during beta without charging for any requests until May 19th. You can integrate it to your application today.

For any questions or feedback, please reach out to our support team.

19 days ago

Samina Kabir

🚀 Introducing Engine Cloud – Now in Beta!

Say hello to Engine Cloud, the easiest way to send blockchain transactions from your backend at scale — no monthly fees, just pay-as-you-go.

Non-custodial wallet management - Manage through Vault, thirdweb's new Key Management Service
Avoid Transaction Failures – Resubmits stuck transactions with built-in retry logic
Wallet Management – No gas top-ups required; handle payments through your account
Abstract Blockchain Complexity – Sponsor gas + sign on behalf of users
Programmatic Deployments – Launch NFTs, tokens, accounts, marketplaces, and more

Get started by creating a project or try it out live on playground.

Learn more about Engine Cloud.

20 days ago

Joaquim Verges

Next-gen Smart Accounts with EIP-7702

EIP-7702 unlocks a new capability for externally-owned accounts (EOAs): the ability to behave like smart contract accounts. The latest SDK let you enable 7702 on any of your in-app wallets with one line of code, giving your users gas-sponsored, batched and automated transactions faster and more efficiently than ever before.

Why you’ll care

Once an in-app wallet is running in EIP-7702 mode you can:

• Sponsor gas so users can sign transactions with zero ETH in their balance.
• Batch transactions so multiple contract calls clear in a single signature.
• Add session keys to automate on-chain actions safely (think scheduled mints, subscription based payments or game loops).
• …and any other capability you’d expect from smart accounts—all while your user keeps their familiar EOA address.

All it takes is a tiny config change.

But what about EIP-4337 smart wallets?
In our testing, using 7702 is up to twice as fast and orders of magnitude cheaper than using 4337 smart contract wallets!

Try it for yourself

Don't take our word for it, try it yourself on the live playground:

https://playground.thirdweb.com/connect/account-abstraction/7702

Using 7702 with In-App Wallets

In-app wallets lets you create wallets for your users based on standard logins like email, passkey or Google. Below are drop-in examples to turn those wallets into 7702 smart accounts for every stack the thirdweb SDK supports today.

TypeScript / React


// plain TypeScript
import { inAppWallet } from "thirdweb/wallets";
 
const wallet = inAppWallet({
  executionMode: {
    mode: "EIP7702",
    sponsorGas: true,
  },
});


// React (e.g. Next.js)
import { inAppWallet } from "thirdweb/wallets";
import { ConnectButton } from "thirdweb/react";
 
<ConnectButton
  client={client}
  wallets={[
    inAppWallet({
      executionMode: {
        mode: "EIP7702",
        sponsorGas: true,
      },
    }),
  ]}
/>;

. NET / Unity


// .NET (server, Godot C#, MAUI, etc.)
var smartEoa = await InAppWallet.Create(
    client: thirdwebClient,
    authProvider: AuthProvider.Google,
    executionMode: ExecutionMode.EIP7702Sponsored
);


// Unity (C#)
var wallet = await ConnectWallet(
    new WalletOptions(
        provider: WalletProvider.InAppWallet,
        chainId: 11155111,
        inAppWalletOptions: new InAppWalletOptions(
            authprovider: AuthProvider.Google,
            executionMode: ExecutionMode.EIP7702Sponsored
        )
    )
);

Heads-up EIP-7702 only works on chains that enable it. Ethereum mainnet and Sepolia already support it, with more coming soon; keep an eye on the thirdweb blog for other chain activation dates.

Using EIP-7702 with External Wallets (EIP-5792)

Don’t want to embed an in-app wallet? No problem. EIP-5792 lets you tap into the same 7702 capabilities from any external wallet—like Metamask and Coinbase Wallet —via the sendCalls RPC method.

Sponsoring Gas & Batching Transactions

The useSendCalls React hook (or the plain sendCalls function in vanilla TypeScript) lets you bundle multiple calls into one and attach a paymaster so your dApp covers the gas:


import { useSendCalls } from "thirdweb/react";
 
const { mutate: sendCalls, data: bundleId } = useSendCalls();
await sendCalls({
  client,
  calls: [sendTx1, sendTx2],
  capabilities: {
    paymasterService: {
      url: `https://${CHAIN.id}.bundler.thirdweb.com/${client.clientId}`,
    },
  },
});

Thie enabled single signature, gas-free, batched execution on exernal wallets like Metamask!

Documentation links: React API | TypeScript API

Ready to ship?

Upgrade your thirdweb SDK to the latest version, flip on executionMode: "EIP7702" or use EIP5792's sendCalls, and your users instantly level-up to smart-account features—no new wallets, no migrations, just better UX.

Got questions or feedback? Jump into the thirdweb Discord and let us know what you’re building!

22 days ago

Greg

Universal Bridge: Advanced Filters

With the latest release of Universal Bridge, we've added a number of new filters to make building advanced payment UIs more convenient. These are available starting in v5.97.0 of the TypeScript SDK.

The `sortBy` Filter

The /routes endpoint (API) and Bridge.routes function (SDK) now have an optional sortBy option to determine how the returned routes will be ordered. The first option we've made available is sortBy: "popularity", which will ordered the returned routes based on the number of times they've been used. The following will return the 10 most popular routes originating from ETH on mainnet:


import { Bridge } from "thirdweb";
 
const routes = await Bridge.routes({
  originChainId: 1,
  originTokenAddress: "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
  limit: 10,
  offset: 0,
  sortBy: "popularity",
  client: thirdwebClient,
});


[
  {
    "originToken": {
      "chainId": 8453,
      "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "iconUri": "https://coin-images.coingecko.com/coins/images/6319/large/usdc.png?1696506694",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6
    },
    "destinationToken": {
      "chainId": 466,
      "address": "0x675C3ce7F43b00045a4Dab954AF36160fb57cB45",
      "iconUri": "https://coin-images.coingecko.com/coins/images/6319/large/usdc.png?1696506694",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6
    }
  },
  {
    "originToken": {
      "chainId": 42161,
      "address": "0xaf88d065e77c8cC2239327C5EDb3A432268e5831",
      "iconUri": "https://ethereum-optimism.github.io/data/USDC/logo.png",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6
    },
    "destinationToken": {
      "chainId": 466,
      "address": "0x675C3ce7F43b00045a4Dab954AF36160fb57cB45",
      "iconUri": "https://coin-images.coingecko.com/coins/images/6319/large/usdc.png?1696506694",
      "symbol": "USDC",
      "name": "USD Coin",
      "decimals": 6
    }
  },
  {
    "originToken": {
      "chainId": 1,
      "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
      "iconUri": "https://assets.relay.link/icons/1/light.png",
      "symbol": "ETH",
      "name": "Ether",
      "decimals": 18
    },
    "destinationToken": {
      "chainId": 8453,
      "address": "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
      "iconUri": "https://assets.relay.link/icons/1/light.png",
      "symbol": "ETH",
      "name": "Ether",
      "decimals": 18
    }
  },
  ...
]

The `maxSteps` Filter

The maxSteps filter already allows you to filter routes based on the number of steps required to fulfill a routes. With this update, we've added this same option to the Buy.quote, Buy.prepare, Sell.quote, and Sell.prepare functions, as well as their corresponding API endpoints. You can now guarantee the quote returned uses a certain number of steps or fewer:


import { Bridge } from "thirdweb";
 
const quote = await Bridge.Buy.quote({
  originChainId: 1,
  originTokenAddress: "0x...",
  destinationChainId: 137,
  destinationTokenAddress: "0x...",
  amount: 1000000n,
  maxSteps: 2,
});
 
const preparedQuote = await Bridge.Buy.prepare({
  originChainId: 1,
  originTokenAddress: "0x...",
  destinationChainId: 137,
  destinationTokenAddress: "0x...",
  amount: 1000000n,
  sender: "0x...",
  receiver: "0x...",
  maxSteps: 2,
});
 
const quote = await Bridge.Sell.quote({
  originChainId: 1,
  originTokenAddress: "0x...",
  destinationChainId: 137,
  destinationTokenAddress: "0x...",
  amount: 1000000n,
  maxSteps: 3,
});
 
const preparedQuote = await Bridge.Sell.prepare({
  originChainId: 1,
  originTokenAddress: "0x...",
  destinationChainId: 137,
  destinationTokenAddress: "0x...",
  amount: 1000000n,
  sender: "0x...",
  receiver: "0x...",
  maxSteps: 3,
});

The Chains Endpoint

We've added a new endpoint and SDK function to get all chains supported by Universal Bridge along with their name, icon, and native currency.


import { Bridge } from "thirdweb";
 
const chains = await Bridge.chains({
  client: thirdwebClient,
});

This will return:


[
  {
    "chainId": 1868,
    "name": "Soneium Mainnet",
    "icon": "ipfs://QmPSGdP5WKe2bC5JCo43JjWff8Agw7dg6WQpmUktyW7sat",
    "nativeCurrency": {
      "name": "Ethereum",
      "symbol": "ETH",
      "decimals": 18
    }
  },
  {
    "chainId": 466,
    "name": "AppChain",
    "icon": "ipfs://bafybeigx76uxvcvet7365sjdzuxxcgl5auzck6vbbigu2jeg6ixl5k3tya",
    "nativeCurrency": {
      "name": "Ether",
      "symbol": "ETH",
      "decimals": 18
    }
  },
  {
    "chainId": 42161,
    "name": "Arbitrum One",
    "icon": "ipfs://QmcxZHpyJa8T4i63xqjPYrZ6tKrt55tZJpbXcjSDKuKaf9/arbitrum/512.png",
    "nativeCurrency": {
      "name": "Ether",
      "symbol": "ETH",
      "decimals": 18
    }
  },
  ...
]

Bug Fixes

Fixed an issue where Coinbase onramps were not returning the associated transaction hash
Fixed routes returning the zero address rather than the native token address

25 days ago

Jonas Daniels

Introducing Verified Domains

You can now verify a domain for your team!

What’s new:

Teams can verify their domain (e.g. @yourcompany.com)
→ When logged in, navigate to Settings`→ General and scroll down Domain Verification to verify your domain.
To complete the verification, you'll need to add a DNS TXT record to your domain. This part must be completed through your domain provider's dashboard.
Please note you may only verify one domain per team.

Perks of verifying your domain:

Verified badge: Your team gets a special badge, so it’s easier to confirm you're in the right place.
Recommended team members: On the Settings → Members page, you’ll see users with emails that match your domain but aren’t in the team yet — making it super easy to invite everyone on the team.

Coming Soon:

Instant invite alerts: Team owners will get a notification (in the dashboard and optionally via email) when someone signs up with your verified domain — with a 1-click invite option.
Recommended teams for users: New users with a matching email domain will see teams they can request to join, giving team owners control to approve or deny.

For any questions or support please reach out to our support team.

25 days ago

Yash Kumar

Samina Kabir

Pack Contract Deprecation

In preparation for Ethereum’s upcoming Pectra upgrade this May, the thirdweb Pack contract has been officially deprecated and is no longer deployable via the dashboard, SDK, or CLI.

Important: Existing Pack contracts are not compatible with the Pectra upgrade.

We strongly recommend that users abandon or conclude any unopened packs as soon as possible to avoid potential issues once the upgrade goes live.

For any questions or support, please reach out to the official thirdweb team support channel.

Changelog

ERC-20 Balance Endpoint Deprecation

New Tokens Endpoint

Highlights:

Installation

Highlights

No more insufficient funds walls

PayEmbed improvements

Bridge.Transfer – token transfers in one call

Bridge.Onramp – fiat‑to‑crypto

Features

Improvements

Bug Fixes

Overview

Features

Bug Fixes

🔂 Durable by Design

📈 Better Observability & Tracking

⚙️ Configurable & Flexible

🔮 What’s Next

Overview

Powerful Multi-stage Processing

Improved Thought Process Visibility

Word-by-word Response Generation

Comprehensive Tool Enhancements

Standardized Framework

Enhanced Blockchain Operations

Performance Optimizations

What This Means For Users

Onramping with the API

Live Demo

Usage

Breaking changes

Overview

Features

API Changes

Bug Fixes

Why we built Engine Cloud

Get Started

Why you’ll care

Try it for yourself

Using 7702 with In-App Wallets

Using EIP-7702 with External Wallets (EIP-5792)

Ready to ship?

The sortBy Filter

The maxSteps Filter

The Chains Endpoint

Bug Fixes

What’s new:

Perks of verifying your domain:

Coming Soon:

The `sortBy` Filter

The `maxSteps` Filter