The Insight API now supports automatic decoding of events and transactions. Developers can now receive decoded transaction data by simply adding the decode=true parameter to event and transaction endpoint calls. Insight API will load ABIs directly from it's vast database of contract metadata and return decoded events directly in the response. This significantly simplifies dealing with onchain data for developers by removing the need to 1) manage ABIs for external contracts and 2) write logic for decoding event data from any chain.

Example:

https://1.insight.thirdweb.com/v1/transactions/0xdac17f958d2ee523a2206206994597c13d831ec7?filter_transaction_hash=0xf08df164ed5cff369e3f8016cfd1dc43814d04756ce72b59d1738d1c8760ef21&decode=true&limit=1

Response:

{
 ...
  "decodedData": {
    "name": "transfer",
    "signature": "transfer(address,uint256)",
    "inputs": {
      "_to": "0x7bea8a667815b1e98e6e4badacf1772c89112cfb",
      "_value": 719000000
    }
  }
...
}

Learn more about Insight from our docs or by reviewing the source code on GitHub.

This update brings significant improvements to Nebula, including an upgraded model (t2) for a more engaging and helpful experience—now with added personality and even emojis! 🚀

• More output personality to make Nebula more friendlier and helpful. It even outputs emojis :D
• Improved speed performance and handling about chains (block information) or wallets on common prompts
• Increased memory retention per session by and context holding within session
• Improved accuracy at responding to prompts related to historical blockchain data
• Improve speed performance when fetching wallet balance

• Fixed wallet balances failed to fetch error due to missing sale prices

Nebula is currently in Alpha for a select number of developers. For access to the product, please sign up on the Nebula waitlist.

For any feedback or support inquiries, please visit our support site.

As our customer base continues to grow, we’re enhancing our RPC Edge support process to ensure faster and more efficient assistance.

What’s Changing?

We’re introducing Support IDs to streamline issue resolution. When reporting an RPC Edge issue, you’ll receive a Support ID, which you can share with our team to expedite troubleshooting.

How This Helps You:

✅ Faster response times – No need to repeat details, just share your Support ID.

✅ More efficient issue tracking – Our support team can quickly locate and diagnose your request.

✅ Improved support experience – Ensures every user gets the help they need, faster.

Example:

When reporting an issue, provide your Support ID like this:

🆔 Support ID: d4dea8aa-ad4a-4fe5-968b-24f1927f6f0b

This change ensures that every RPC-related inquiry is handled with greater speed and accuracy. 🚀

What's Changed

TL;DR
Added a new /query/blocks endpoint to retrieve block data with filtering, sorting, and aggregation capabilities.

What changed?

• Created a new /query/blocks endpoint in the API
• Implemented block data retrieval with support for:
  • Filtering by chain ID and other block parameters
  • Sorting and pagination
  • Aggregation functions
  • Group by operations
• Updated the storage interface to return QueryResult for block operations
• Added block scanning functionality to handle database rows

How to test?

1. Start the API server
2. Make GET requests to /query/blocks with optional query parameters:
   • chainId: Specify the blockchain network
   • filter: Apply filters to block data
   • sort_by: Sort results by specific fields
   • sort_order: Choose ascending or descending order
   • page and limit: Control pagination
   • aggregate: Apply aggregation functions
   • group_by: Group results by specific fields

Why make this change?
To provide a standardized way to query and analyze block data from the blockchain, enabling users to retrieve block information with flexible filtering and aggregation options. This enhancement aligns with the existing transaction and event query capabilities of the API.

Why is this useful?
As an example, this feature allows users to easily fetch the earliest block number that meets a specific timestamp criterion. For instance, when constructing block ranges based on timestamps, this can help in determining the precise blocks that fall within certain time windows. This functionality is crucial for tasks such as historical data analysis, event tracking, or aligning blockchain queries with specific real-world dates.

Learn more about Insight and how to use it.
Insight is open source.

Open source version of Insight 0.2.1-beta has been released and focuses on the robustness and reliability of indexing blockchain data.

• Implemented dynamic block range calculations for the reorg handler, allowing both forward and backward scanning based on sync state.
• Improved logic to find specific reorged block numbers rather than ranges, allowing to scan bigger ranges at a time.
• Enhanced error messages for better debugging.
• Updated reorg detection to avoid including non-reorged edge blocks
• Implemented fetching blocks in parallel chunks for performance gains
• Improved test coverage

• Added support for more time functions in aggregations. Added `toDateTime`, `toStartOfMonth`, `toStartOfHour`, and `toStartOfMinute`
• Whitelisted concat function to be used in aggregations and parsing the contract address from raw data

• Improved delete performance in ClickHouse by implementing partition-aware deletes and asynchronous processing. This enhancement minimizes wait times and optimizes resource usage during deletion operations

Learn more about Insight and how to use it.
Insight is open source.

At thirdweb, we empower developers to build decentralized apps effortlessly—and reliable storage is core to that mission. Today, we’re announcing two key upgrades to our IPFS infrastructure: improved resilience and enhanced monitoring, designed to scale your dApps with confidence.

We’ve introduced automated failover and retry mechanisms for IPFS uploads. If a primary node fails, thirdweb instantly switches to a backup, ensuring seamless data storage with minimal downtime. This redundancy safeguards your app’s content against network disruptions, keeping it consistently accessible for users.

Our upgraded monitoring tools now track real-time upload success rates, latency, and node health metrics like bandwidth, storage capacity, and peer connections. Historical data analysis lets us preemptively optimize nodes, addressing issues before they impact your app.

User trust hinges on reliability. With thirdweb’s fortified storage layer, you can build knowing your app withstands real-world challenges—letting you focus on innovation, not infrastructure.

This release focuses on granular configurations for responses to control randomness, limitations, and formats for outputs. Additionally, two new OpenAI compatible endpoints including /chat/completions and /models, and simplified context filter endpoint for an improved developer experience.

• Enable advanced LLM configurations to control output randomness and formatting, including temperature, presence penalty, max tokens, new response formats (JSON object, JSON schema), and nucleus sampling (top-p).

{ 
	"message": "Hello Nebula!",
	// ...
	// advanced llm configuration
	"max_tokens": 100, // integer
    "frequency_penalty": 0.0, // [-2.0, 2.0]
    "presence_penalty": 0.0, // [-2.0, 2.0]
    "temperature": 1.0, // [0.0, 2.0]
    "top_p": 1.0, // [0.0, 1.0]
    "response_format": {}, //{ type: "json_object" } | { "type": "json_schema", "json_schema": { ... } }
 }

• New endpoint for /chat/completions compatible with OpenAI client to process chat history and generate context-aware responses.

POST "https://nebula-api.thirdweb.com/chat/completions" \
  -X POST \
  -H "X-Secret-Key: $THIRDWEB_SECRET_KEY" \
  --data '{
  "messages": [{ "role": "user", "content": "Hello Nebula!"}],
  // (optional) context management
  "context": {
	  "session_id": "...", // optional
	  "wallet_address": "0x...", // optional
	  "chain_ids": ["1", "11155111"], // optional
  },
  // (optional) advanced llm configuration
  "max_tokens": 100,
  "frequency_penalty": 0.0,
  "presence_penalty": 0.0,
  "temperature": 1.0,
  "top_p": 1.0,
  "response_format": { type: "json_object" }
}'

from openai import OpenAI
	
client = OpenAI(
	base_url="<https://nebula-api.thirdweb.com/>",
	api_key="{{THIRDWEB_SECRET_KEY}}",
)
	
chat_completion = client.chat.completions.create(
	model="t0",
	messages=[{"role": "user", "content": "Hello Nebula!"}],
	stream=False,	
    extra_body={ "context": { "wallet_address": "0x..." }}
)
 
print(chat_completion)

• New OpenAI compatible endpoint to list out models used by Nebula

from openai import OpenAI
 
# https://nebula-api.thirdweb.com/models
 
client = OpenAI(
    base_url="https://nebula-api.thirdweb.com/",
    api_key="",
)
 
models = client.models.list()
print(models)

• Simplified context_filter and execute_config into context for /chat, /execute, and /chat/completions endpoints.

Before:

{
  "message": "Hello Nebula!",
  "session_id": "...",
  "context_filter": {
    "wallet_addresses": [],
    "chain_ids": [],
    "contract_addresses": []
  },
  "execute_config": {
    "type": "client",
    "signer_wallet_address": "0x0000..."
  }
}

New:

{
  "message": "Hello Nebula!",
  "context": { 
    "session_id": "...",
    "wallet_address": "0x...",
    "chain_ids": ["1", "11155111"]
  },
}

Nebula is currently in Alpha for a select number of developers. For access to the product, please sign up on the Nebula waitlist.

For any feedback or support inquiries, please visit our support site.

With the thirdweb SDK, all smart wallets maintain the same address across any EVM chain. Account factories and wallet deployments are managed for you from within the thirdweb SDK unless overridden with your own factory. If you need a different wallet address for any reason, you can provide an optional account salt to the wallet.

Create a smart wallet on your default chain:

import { smartWallet } from "thirdweb/wallets";
 
const mySmartWallet = smartWallet({
  chain: sepolia,
  sponsorGas: true,
});

Send your transaction on any chain:

const sendTx = prepareTransaction({
  to: receiver.address,
  value: 100000n,
  chain: baseSepolia,
  client,
});
 
const sendResult = await sendAndConfirmTransaction({
  account: sender,
  transaction: sendTx,
});

If you need to create a wallet using the same admin account but a different address, use an account salt:

const mySmartWallet = smartWallet({
  chain: sepolia,
  sponsorGas: true,
  overrides: {
    accountSalt: "123",
  },
});

Check out the video for more:

.NET 2.17.0 Release

The last piece of the puzzle required to create .NET apps and games leveraging a blockchain-powered AI assistant or NPC that also has the power to fully execute transactions. Further enhanced when combined with Server Wallets and Account Abstraction.

Read, Write, Reason.
The best way to understand is to look at examples.

We'll prepare some context for the AI - here, we'll generate a basic PrivateKeyWallet and upgrade it to a SmartWallet on Sepolia.

// Prepare some context
var myChain = 11155111; // Sepolia
var mySigner = await PrivateKeyWallet.Generate(client);
var myWallet = await SmartWallet.Create(mySigner, myChain);
var myContractAddress = "0xe2cb0eb5147b42095c2FfA6F7ec953bb0bE347D8"; // DropERC1155
var usdcAddress = "0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238"; // Sepolia USDC

A one liner creates a Nebula session.

// Create a Nebula session
var nebula = await ThirdwebNebula.Create(client);

You can Chat with Nebula. The Chat method accepts any IThirdwebWallet as an optional parameter, context will automatically be updated.

// Chat, passing wallet context
var response1 = await nebula.Chat(message: "What is my wallet address?", wallet: myWallet);
Console.WriteLine($"Response 1: {response1.Message}");

You may also pass it smart contract context.

// Chat, passing contract context
var response2 = await nebula.Chat(
    message: "What's the total supply of token id 0 for this contract?",
    context: new NebulaContext(contractAddresses: new List<string> { myContractAddress }, chainIds: new List<BigInteger> { myChain })
);
Console.WriteLine($"Response 2: {response2.Message}");

You can have a full on conversation with it with our Chat override accepting multiple messages.

// Chat, passing multiple messages and context
var response3 = await nebula.Chat(
    messages: new List<NebulaChatMessage>
    {
        new($"Tell me the name of this contract: {myContractAddress}", NebulaChatRole.User),
        new("The name of the contract is CatDrop", NebulaChatRole.Assistant),
        new("What's the symbol of this contract?", NebulaChatRole.User),
    },
    context: new NebulaContext(contractAddresses: new List<string> { myContractAddress }, chainIds: new List<BigInteger> { myChain })
);
Console.WriteLine($"Response 3: {response3.Message}");

Chatting is cool, but what if I just want it to do things and stop talking so much?

You can Execute transactions directly with a simple prompt.

// Execute, this directly sends transactions
var executionResult = await nebula.Execute("Approve 1 USDC to vitalik.eth", wallet: myWallet, context: new NebulaContext(contractAddresses: new List<string>() { usdcAddress }));
if (executionResult.TransactionReceipts != null && executionResult.TransactionReceipts.Count > 0)
{
    Console.WriteLine($"Receipt: {executionResult.TransactionReceipts[0]}");
}
else
{
    Console.WriteLine($"Message: {executionResult.Message}");
}

Similarly, Execute can take in multiple messages.

// Batch execute
var batchExecutionResult = await nebula.Execute(
    new List<NebulaChatMessage>
    {
        new("What's the address of vitalik.eth", NebulaChatRole.User),
        new("The address of vitalik.eth is 0xd8dA6BF26964aF8E437eEa5e3616511D7G3a3298", NebulaChatRole.Assistant),
        new("Approve 1 USDC to them", NebulaChatRole.User),
    },
    wallet: myWallet,
    context: new NebulaContext(contractAddresses: new List<string>() { usdcAddress })
);
if (batchExecutionResult.TransactionReceipts != null && batchExecutionResult.TransactionReceipts.Count > 0)
{
    Console.WriteLine($"Receipts: {JsonConvert.SerializeObject(batchExecutionResult.TransactionReceipts, Formatting.Indented)}");
}
else
{
    Console.WriteLine($"Message: {batchExecutionResult.Message}");
}

Full Reference

We've added transaction and connection analytics that will show up on your thirdweb dashboard and give you a better sense of your users' activities - make sure you grab this version to get the benefits!

If you've read this far, access Nebula and start building cool things. You're early - a full stack blockchain integration powered by AI is not something you see in .NET land too often, make use of thirdweb to build next-gen applications, and reach out to us!

Unity 5.17.0 Release

• Additions from Thirdweb's .NET SDK Release 2.17.0
  • Includes Thirdweb Nebula AI Integration.
  • Combine with Backend Wallets & Account Abstraction to create truly unique experiences.
• Moved analytics to the .NET SDK (DLL), removed from ThirdwebManagerBase.
• MetaMaskWallet.Disconnect now calls wallet_revokePermissions allowing you to fully disconnect the extension - thanks @tulfix !

You now have all the tools to be the first to build the best interactive NPCs to ever accompany your players - contact us if you run into any issues!

Links

.NET Release | NuGet Release | Unity Release

Documentation | Support

We just added a new section on your project overviews showing how your users are transacting from your apps!

These stats will show all transactions initiated from the client side by day/week/month, as well as the most interacted chains and contracts with direct links.

Check out your own stats by navigating to your project overview, and make sure to use the latest version of the thirdweb SDKs.

We're continuously improving our analytics to better help you monitor the growth of your apps, let us know what you'd like to see next!

At Thirdweb, we’ve been hard at work implementing significant improvements to our infrastructure, and we’re thrilled to share the results of these efforts. This update represents a major leap forward in scalability, performance, and resilience, ensuring we’re better equipped to serve our users now and in the future. Here's what we’ve achieved:

One of the key drivers of this overhaul was the need to reduce latency and improve response times. Our engineering team has:

• Reduced P99 Latency: We’ve slashed P99 latency from upwards of 20 seconds to just 2 seconds. This improvement means even the slowest requests now complete faster than ever.
• Optimized Average Response Time: The average response time is now just 250ms, providing a snappier, smoother experience for our users.
• Expanded Regional Coverage in Europe and Asia Pacific: We have introduced new regions in Europe and Asia Pacific, allowing us to provide more localized services to meet the growing demands of our global customer base. Additionally, these new regions enhance our disaster recovery capabilities, ensuring greater resiliency and reliability.

These enhancements ensure that our platform is not only faster but also more consistent under varying workloads.

To handle ever-increasing traffic demands, we’ve rolled out improved autoscaling capabilities. These dynamic systems allow us to:

• Respond to peak load surges without sacrificing performance.
• Maintain cost efficiency by scaling resources up or down as needed.

This ensures that no matter how much demand our platform faces, we’re ready to deliver resilient service.

Reliability is critical, especially as we scale. To validate our infrastructure’s ability to handle increasing demand, we conducted resilience testing at over 6,000 Requests Per Second (RPS). The system performed admirably, solidifying confidence in its ability to handle extreme loads.

Our load testing focused on the RPC router, which efficiently routed requests to over 2,000 nodes globally over a 6-hours period. The screenshots below provides a sample measurement of the aggregated P90 latency across all RPC calls in all regions.

We’re expanding our global footprint with the rollout of Regional RPC services in Asia Pacific (SEA), Europe (EU), and Americas (US). This regionalization improves latency by up to 60% for users across the globe and ensures a more localized and reliable service experience.

Security and collaboration are critical, and our updated authentication system now integrates seamlessly with teams. This allows:

• Enhanced access control for better security.
• Simplified management of team-based workflows.

This update ensures that working as a team on our platform is both secure and effortless.

These improvements mark a significant milestone in our ongoing commitment to delivering a fast, reliable, and scalable platform for our users. But we’re not stopping here. Our team is already planning the next wave of enhancements to stay ahead of the curve and continue providing the best experience possible.

Thank you for being a part of our journey. We’re excited about these changes and can’t wait for you to experience them. Let us know your thoughts and stay tuned for more updates!

thirdweb v5.85.0 has been released with new features a breaking change for the beta nebula API as well as notable bug fixes.

The following property names have been updated in Nebula.chat() and Nebula.execute() to align with the HTTP API:

• prompt is now message
• context is now contextFilter

Before:

Nebula.chat({
  client,
  prompt:
    "What's the total supply of this contract: 0xe2cb0eb5147b42095c2FfA6F7ec953bb0bE347D8",
  context: {
    chains: [sepolia],
  },
});

After:

Nebula.chat({
  client,
  message:
    "What's the total supply of this contract: 0xe2cb0eb5147b42095c2FfA6F7ec953bb0bE347D8",
  contextFilter: {
    chains: [sepolia],
  },
});

Both Nebula.chat() and Nebula.execute() now support multiple input messages through the new messages property, enabling more complex conversation flows.

Nebula.chat({
  client,
  messages: [
    {
      role: "user",
      content:
        "Tell me the name of this contract: 0xe2cb0eb5147b42095c2FfA6F7ec953bb0bE347D8",
    },
    {
      role: "assistant",
      content: "The name of the contract is My NFT Collection",
    },
    {
      role: "user",
      content: "What's the symbol of this contract?",
    },
  ],
  contextFilter: {
    chains: [sepolia],
  },
});

Nebula.execute({
  client,
  account,
  messages: [
    { role: "user", content: "What's the address of vitalik.eth" },
    {
      role: "assistant",
      content:
        "The address of vitalik.eth is 0xd8dA6BF26964aF8E437eEa5e3616511D7G3a3298",
    },
    { role: "user", content: "Send them 0.0001 ETH" },
  ],
  contextFilter: {
    chains: [sepolia],
  },
});

Each message in the array requires a role ("user" or "assistant") and content string.

• Fixed NFT components incorrectly displaying metadata when multiple contracts with the same token ID are rendered due to caching issues
• Fixed MarketplaceV3 deployment for Xsolla testnet

• Added mode as a predefined chain
• Added overrides for Lumia Testnet to use pre-EIP1559 gas values

This chart shows a breakdown of transactions sent by your Engine's backend wallets by their status. This gives you an insight into the transaction volume and success/error rate trend at a glance

Pagination and Status filters added in Transaction history table. Pagination UI also has an input field that allows you quickly jump to a page - allowing you to quickly comb through a large list of transactions

We've added new chains to the platform this week!

Sei Testnet: RPC and Chain Settings

Use the best Sei Testnet RPC and add to your wallet. Discover the chain ID, native token, explorers, and faucet options.

Sei Network: RPC and Chain Settings

Use the best Sei Network RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

Viction Testnet: RPC and Chain Settings

Use the best Viction Testnet RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

Eclipse Testnet: RPC and Chain Settings

Use the best Eclipse Testnet RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

EVM on Flow Testnet: RPC and Chain Settings

Use the best EVM on Flow Testnet RPC and add to your wallet. Discover the chain ID, native token, explorers, and faucet options.

Rivalz: RPC and Chain Settings

Use the best Rivalz RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

Rivalz2: RPC and Chain Settings

Use the best Rivalz2 RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

Ouroboro: RPC and Chain Settings

Use the best Ouroboro RPC and add to your wallet. Discover the chain ID, native token, explorers, and more.

Every chain comes out of the box with SDK support RPC, Engine and Account Abstraction capabilities. All you need is the chain id to get going.

const wallet = smartWallet({
  chain: defineChain(388), // just need the chainId!
  sponsorGas: true,
});

For testnets, you'll also find a faucet in each chain page.

Happy building! 🛠️

.NET v2.16.0 Release

Depending on the framework, or on the external wallet platform support, you may not have direct access to every single wallet out there.
This new AuthProvider allows you to login to otherwise native-unavailable wallets such as Abstract Wallet & Coinbase Smart Wallet through a flow similar to OAuth, using SIWE.

It'll redirect you to static.thirdweb.com and use our React SDK and other wallet SDKs as needed, unlocking the ability to login (or link) with any wallet thirdweb supports on web, from runtime platforms that would otherwise be unsupported by said wallet, and create an In-App or Ecosystem Wallet out of it.

Windows Console Example:

var inAppWalletSiweExternal = await InAppWallet.Create(client: client, authProvider: AuthProvider.SiweExternal);
var address = await inAppWalletSiweExternal.LoginWithSiweExternal(
    isMobile: false,
    browserOpenAction: (url) =>
    {
        var psi = new ProcessStartInfo { FileName = url, UseShellExecute = true };
         _ = Process.Start(psi);
    },
    forceWalletIds: new List<string> { "io.metamask", "com.coinbase.wallet", "xyz.abs" }
);

This is useful when you want your guest mode to be tied to a unique device identifier, and depending on your framework there may be various APIs to fetch such identifiers that you may want to use.

Example:

var guestWallet = await EcosystemWallet.Create(
    ecosystemId: "ecosystem.the-bonfire",
    client: client,
    authProvider: AuthProvider.Guest
);
var address = await guestWallet.LoginWithGuest(SomeSystemInfoAPI.deviceUniqueIdentifier);

Unity 5.16.0 Release

• Additions from Thirdweb's .NET SDK Release 2.16.0
• Integrated AuthProvider.SiweExternal in ThirdwebManager.
  • Work around your favorite external wallet not having Unity support.
  • OAuth style linking variant of AuthProvider.Siwe, but using wallets and SIWE in a static React environment.

var walletOptions = new WalletOptions(
    WalletProvider.InAppWallet,
    421614,
    new InAppWalletOptions(authprovider: AuthProvider.SiweExternal)
);
var wallet = await ConnectWallet(walletOptions);
ThirdwebDebug.Log("Connected to InAppWallet with SiweExternal auth provider." + await wallet.GetAddress());

• AuthProvider.Guest now uses a unique device identifier, making it a little more persistent than the previous implementation.
  • Guest mode is meant as an ephemereal login method, you should allow users to link additional auths later in the flow.
  • This update makes Guest mode a little more persistent in cases where users delete something by mistake.
• Fixed edge case where Application.identifier being an empty string with some build configs would cause an empty bundle id to be used as the fallback instead of com.company.product.

Links

.NET Release | NuGet Release | Unity Release

Documentation | Support

• Nebula TypeScript SDK now available in Beta, integrate /chat and /execute calls easily or be able to plug into any framework
  • View the full reference documentation
• New example template on how to create specialized AI agents that can interact with blockchain data while maintaining a distinct personality and purpose
  • View template

• Read and write contracts with better function argument extraction
  • Improved understanding and parsing for array function arguments related to reading or executing contract functions

• ENS resolver not parsing correctly in select cases
• Query wallet balance improvements handling wallet addresses with multiple tokens or NFTs
• Add improved read support for chains with block extraData including Polygon

The thirdweb TypeScipt SDK v5.84.0 release adds support for Nebula, our new AI model designed interact with real time blockchain data and execute transactions with natural language.

Simply install the thirdweb package on your frontend or backend to get started.

npm install thirdweb

Nebula enables developers to query real-time blockchain data using simple natural language prompts. From checking contract symbols to analyzing on-chain metrics, Nebula provides human-readable responses to your blockchain queries.

import { Nebula } from "thirdweb/ai";
 
const response = await Nebula.chat({
  client,
  prompt:
    "What's the symbol of this contract: 0xe2cb0eb5147b42095c2FfA6F7ec953bb0bE347D8",
  context: {
    chains: [sepolia],
  },
});
 
console.log("chat response:", response.message);

Nebula goes beyond just querying data - it can now execute blockchain transactions based on natural language instructions. Simply connect your wallet and describe the transaction you want to perform.

import { Nebula } from "thirdweb/ai";
 
const wallet = createWallet("io.metamask");
const account = await wallet.connect({ client });
 
const result = await Nebula.execute({
  client,
  prompt: "send 0.0001 ETH to vitalik.eth",
  account,
  context: {
    chains: [sepolia],
  },
});
 
console.log("executed transaction:", result.transactionHash);

• Natural language processing for blockchain queries
• Real-time data access across 2000+ chains
• Transaction execution through simple prompts
• Works with 300+ wallet providers, in-app wallets, smart wallets and engine
• Context-aware responses and actions with multi step sessions

This addition to the SDK marks a significant step forward in making blockchain technology more accessible and user-friendly. Nebula's natural language capabilities greatly reduce the complexity of doing complex actions on the blockchain.

For detailed documentation and examples, please visit our documentation portal or join our Discord community for support and discussions.

Happy Building! 🛠️

The thirdweb TypeScript sdk v5.84.0 introduces the new engineAccount() function, enabling seamless backend integration with your thirdweb Engine instance. This addition allows developers to leverage the full power of the thirdweb SDK and contract extensions functions in backend environments while benefiting from Engine's performance, reliability, and monitoring capabilities.

• Create Engine-powered accounts for backend transaction handling with nonce and fund management
• Full access to thirdweb SDK functions and extensions from the backend
• Built-in transaction monitoring and reliability features

// Initialize engine account with your instance credentials
const engine = engineAccount({
  engineUrl: process.env.ENGINE_URL,
  authToken: process.env.ENGINE_AUTH_TOKEN,
  walletAddress: process.env.ENGINE_WALLET_ADDRESS,
});
 
// Prepare transactions like usual
const tx = await claimTo({
  contract: getContract({ client, chain, address: "0x..." }),
  to: "0x...",
  tokenId: 0n,
  quantity: 1n,
});
 
// Send transaction through engine
const result = await sendTransaction({
  account: engine,
  transaction: tx,
});
 
// Transaction hash is returned once engine submits it onchain
console.log(result.transactionHash);

This update helps backend development workflows by opening up the large catalog of extensions functions available in the SDK. The engineAccount() function serves as a bridge between your backend services and the blockchain, handling transaction preparation, submission, and confirmation in a reliable manner.

For more information about this release, please visit our documentation or join our Discord community for support and discussions.

The SDK now exposes the autoConnect function for use outside of React environments. This allows developers to implement wallet auto-connection functionality in any JavaScript/TypeScript environment.

import { autoConnect } from "thirdweb/wallets";
 
const autoConnected = await autoConnect({
  client,
  onConnect: (wallet) => {
    console.log("wallet", wallet);
  },
});
console.log("isAutoConnected", isAutoConnected); // true or false

For more information about this release, please visit our documentation or join our Discord community for support and discussions.

Happy building! 🛠️

We're excited to introduce powerful new batching capabilities in Engine v2.1.25, enabling you to execute multiple operations atomically and efficiently read from multiple contracts in a single call.

New Endpoint: /backend-wallet/{chainId}/send-transaction-batch-atomic

Send multiple transactions that will be executed together in a single atomic operation. Perfect for operations that need to happen in a specific order, like token approvals followed by transfers. Check out the API Reference for more details.

• Guaranteed order of execution
• All transactions succeed or fail together
• Single queue ID for tracking the entire batch
• Compatible with all smart account setups:
  • Smart backend wallets (no additional headers needed)
  • Regular backend wallets using x-smart-account-address header

curl --request POST \
  --url http://localhost:3005/backend-wallet/84532/send-transaction-batch-atomic \
  --header 'Authorization: Bearer {{authToken}}' \
  --header 'x-backend-wallet-address: {{walletAddress}}' \
  --data '{
  "transactions": [
    {
      "toAddress": "0x...",
      "value": "0",
      "data": "0x..." // First transaction (e.g., approval)
    },
    {
      "toAddress": "0x...",
      "value": "0",
      "data": "0x..." // Second transaction (e.g., transfer)
    }
  ]
}'

• Previous: Each transaction got its own queue ID, executed independently
• New: Single queue ID for entire batch, guaranteed atomic execution

New Endpoint: /contract/{chainId}/read-batch

Execute multiple read operations across different contracts in a single call, with guaranteed consistency of data from the same block. Check out the API Reference for more details.

• All reads executed in the same block
• Reduced RPC calls using multicall3
• Perfect for getting related data across contracts
• Consistent state snapshot across all reads

curl --request POST \
  --url http://localhost:3005/contract/421614/read-batch \
  --header 'Authorization: Bearer {{authToken}}' \
  --data '{
  "calls": [
    {
      "contractAddress": "0x...",
      "functionName": "balanceOf"
    },
    {
      "contractAddress": "0x...",
      "functionName": "allowance"
    }
  ]
}'

The transaction status object now includes a batchOperations field that provides details about all operations in an atomic batch. This field will be null for non-batch transactions:

{
  batchOperations: [
    {
      to: string | null,
      data: string | null,
      value: string,
    },
  ] | null;
}

thirdweb Engine is an open-source server for your app to read, write, and deploy contracts at production scale. Self-host for free or get a cloud-hosted Engine for $99/month.

Contract Analytics on thirdweb dashboard is now powered by thirdweb Insight

You can select a date range and see various analytics for the contract such as

• Unique wallets that have sent transactions
• Total Transactions & Events
• Breakdown of unique Functions calls & emitted Events

View this contract analytics on dashboard

Insight is a powerful tool that lets you retrieve blockchain data from any EVM chain, enrich it with metadata, and transform it using custom logic.

Whether you're building a gaming inventory system, tracking DeFi metrics, or analyzing NFT collections, Insight makes it easy to get the data you need with simple API calls. Learn more about thirdweb insight to use in your projects!