thirdweb TypeScript SDK v5.85.0 release notes

Joaquim Verges

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