Changelog

Arbitrum Stylus brings a second, WebAssembly (WASM) virtual machine to every Arbitrum chain, so you can write contracts in Rust (or C/C++) while staying 100 % interoperable with existing Solidity code.

Under the hood, Stylus executes WASM thousands of times faster than the EVM, so transactions are metered in a new, much-smaller unit called ink rather than gas — translating to dramatic fee savings for compute- or memory-heavy logic.

To take advantage of the interoperability and fee savings, we are working with Arbitrum to bring you thirdweb contract developer tooling to Stylus

• Airdrop tokens pre-built smart contracts available on Explore
  • Airdrop ERC-20
  • Airdrop ERC-721
  • Airdrop ERC-1155
• ERC-20, ERC-721, and ERC-1155 token templates written in Stylus available to deploy through the CLI.

| Learn how to deploy and interact with Stylus contracts through thirdweb documentation

• Deploy contracts written with Stylus through the thirdweb

npx thirdweb deploy-stylus -k <YOUR SECRET KEY>

• Publish Stylus-written contracts through the thirdweb CLI

npx thirdweb publish-stylus -k <YOUR SECRET KEY>

• Interact with Stylus contracts using thirdweb SDKs.

Learn how to do this through the Stylus guide.

Stylus + thirdweb lets you trade Solidity’s familiar syntax for Rust’s performance without losing any of the tooling you love, and simplifies your deployment and tooling integration.

We will be creating additional contracts with Stylus. If you are interested in being notified on release or have any feedback, please join our Telegram community and let us know.

• thirdweb Arbitrum Documentation
• Arbitrum Stylus Documentation
• Stylus Airdrop ERC-721 Template

Need help? Please reach out to our support team.

A cleaner, smarter interface to help you discover features and navigate the Playground more efficiently.

• New home page with Table of Contents
• Updated product grouping in the sidebar
• Clearer titles and descriptions
• A cleaner and more user friendly sidebar
• Added light mode support

Breaking Change: /v1/nfts/transfers Requirements

• Requests to /v1/nfts/transfers now require at least one of the following parameters:
  • block_timestamp_from
  • block_number_from

Status: Read-Only (No New Blocks)

• The following chain IDs have been deprecated and will no longer receive new block updates
• Historical data remains accessible for all deprecated chains
• Affected Chain IDs: 30, 302, 919, 5031, 6283, 9746, 9899, 11690, 16600, 31911, 41455, 42019, 42026, 98865, 555271, 555272, 978658, 4457845, 28122024, 168587773, 531050104, 1660990954, 2734060341882000

• Update any /tokens/transfers paginated requests to include required time or block range parameters
• Consider migrating from deprecated chains to active alternatives where applicable

The Transactions API now supports EIP7702 session key authorization for gasless transaction execution. Server wallets can execute transactions on behalf of user accounts with full gas sponsorship from the infrastructure.

Implementation

curl -X POST "https://engine.thirdweb.com/v1/write/transaction" \
  -H "content-type: application/json" \
  -H "x-secret-key: <your-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EIP7702",
      "chainId": "84532",
      "sessionKeyAddress": "<server-wallet-address>",
      "accountAddress": "<user-account-address>"
    },
    "params": [
      {
        "to": "0x...",
        "data": "0x...",
        "value": "0x0"
      }
    ]
  }'

Parameters

• sessionKeyAddress: Server wallet address with session key authorization
• accountAddress: User account that issued the session key
• type: Must be set to EIP7702 for session key execution
• Gas costs: Fully sponsored by Transactions API infrastructure

Your server wallet must be registered as authorized session key signer on the accountAddress you want to send this transaction on behalf of.

We just enabled batch execution for EOAs, allowing you to execute multiple transactions atomically in a single call.

How to use batch execution

Simply pass multiple items in your params array. All transactions will be executed atomically:

curl -X POST "https://engine.thirdweb.com/v1/write/transaction" \
  -H "content-type: application/json" \
  -H "x-secret-key: <your-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EOA",
      "chainId": "84532",
      "from": "<your-eoa-address>"
    },
    "params": [
      {
        "to": "0x...",
        "data": "0x...",
        "value": "0x0"
      },
      {
        "to": "0x...",
        "data": "0x...",
        "value": "0x0"
      },
      {
        "to": "0x...",
        "data": "0x...",
        "value": "0x0"
      }
    ]
  }'

EOA Upgrade Required

Engine uses EIP7702 internally for batch execution, which requires your EOA to be "upgraded". If your EOA isn't already upgraded, you can send a no-op EIP7702 transaction to upgrade it:

curl -X POST "https://engine.thirdweb.com/v1/write/transaction" \
  -H "content-type: application/json" \
  -H "x-thirdweb-secret-key: <your-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EIP7702",
      "chainId": "84532",
      "from": "<your-eoa-address>"
    },
    "params": [
      { "to": "<your-eoa-address>"}
    ]
  }'

After this upgrade transaction, you can use batching with the same EOA.

Happy building! 🛠️

You can now instantly swap between tokens and chains using any thirdweb wallet with the https://api.thirdweb.com/v1/payments/swap endpoint. Using exact you can toggle between specifying an input and output amount to be received. Learn more and see the full reference here.

We just enabled AWS KMS wallet support for the Transactions API, allowing you to use your AWS KMS-managed keys directly.

How to use AWS KMS wallets

Add the AWS KMS headers to your Engine API calls:

curl -X POST "https://engine.thirdweb.com/v1/write/transaction" \
  -H "content-type: application/json" \
  -H "x-secret-key: <your-secret-key>" \
  -H "x-aws-kms-arn: <your-kms-key-arn>" \
  -H "x-aws-access-key-id: <your-access-key>" \
  -H "x-aws-secret-access-key: <your-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EOA",
      "chainId": "1",
      "from": "<your-kms-wallet-address>"
    },
    "params": [{
      "to": "0x...",
      "data": "0x...",
      "value": "0x0"
    }]
  }'

Migrating from Engine v2?

If you're using AWS KMS wallets with Engine v2, you can now migrate to Engine Cloud seamlessly using the same KMS configuration.

Please avoid using EOA execution on both Engine v2 and Engine Cloud simultaneously with the same wallet on the same chain - this will cause nonce conflicts. Consider testing your integration on a different chain, and them migrating fully.

Happy building! 🛠️

We've made significant changes to how the payment widgets (BuyWidget, CheckoutWidget, and TransactionWidget) generate quotes for every available token. This allows users to find the best possible quote available to them, rather than needing to guess with token to pay with.

Try the improved quote discovery in our playground or on version 5.105.24 or later of the React SDK.

Unreal Engine 5.6 is now supported by thirdweb's Unreal Plugin.

You can download the plugin from our Github Release.

This release is also available on the Fab marketplace!

thirdweb Payments have made it easy to integrate monetization tools into apps with drop-in widgets and SDKs. Now, we're making it even easier with hosted payment links.

You can get paid by anyone, anywhere, and in any token using thirdweb's Payment Links. Links can be created in the dashboard or via the payments API. We've also redesigned our payment's dashboard for easier feature discovery and usage.

Full support for v7 Account Factories and Entrypoints has been added.

Rust static libraries have been updated, and Smart Wallet creation now includes a new advanced EntryPoint parameter.

When using our default v7 Account Factory, or a custom one based on the v7 standard, you can provide the v7 EntryPoint address to override the default v6 behavior.

• v6 Default Factory: 0x85e23b94e7F5E9cC1fF78BCe78cfb15B81f0DF00
• v6 EntryPoint: 0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789
• v7 Default Factory: 0x4bE0ddfebcA9A5A4a617dee4DeCe99E7c862dceb
• v7 EntryPoint: 0x0000000071727De22E5E9d8BAf0edAc6f37da032

You can find the latest release on Github.

We’ve rebuilt the thirdweb developer platform for the AI-native era. You can now build apps 80% faster with our new HTTP API, MCP server and new LLM optimized documentation. We've also re-organized the platform to be simpler and better organized.

• New HTTP API → We created a new API which combines all services with a simplified interface. Optimized for humans and agents.
• New MCP server → Interact with the thirdweb platform from your favorite LLM client.
• New LLM-optimized documentation → inject these into your prompts to instruct coding agents to build with thirdweb
• New Project and documentation organization → Projects and docs are now organized to follow the new product structure

• Manage user and server wallets
• Transact gasless-ly with highly performant EIP7702 execution
• Query any blockchain data both indexed and real time
• Monitor all your transactions on your project dashboard

Check out the full api reference.

The entire thirdweb platform is now available as a remote MCP server: https://api.thirdweb.com/mcp. Perfect for building agents, or directly interacting with the thirdweb platform from your favorite LLM client.

Check out our new MCP documentation for more details.

Inject knowledge into your coding agent by copying our new llms.txt into your project or your prompts. Example prompt:

Add a login screen that lets the user enter the email and confirm a verification code, then display their email and wallet address in the header. Docs: https://api.thirdweb.com/llms.txt

Check out our available llm optimized doc files.

We've organized the dashboard and documentations around our new main categories: Wallets, Transactions, Contracts, Payments, Tokens and Marketplace.

You'll see this grouping reflected all across the product for a more cohesive and predictable experience.

1. Create a new or use an existing project in the thirdweb dashboard
2. Discover the new API: authenticate using your project’s secret key and start exploring the new endpoints for Wallets, Contracts, Payments, etc. See the documentation reference.
3. Work with AI: test the MCP server in your favorite LLM client, or inject our new llms.txt and build apps in minutes

If you’re already using our APIs or SDKs, no action is required.

• You can continue using your existing setup
• Gradual adoption is supported, if desired, and you can migrate endpoint-by-endpoint if you like
• Your current auth keys and project still work and nothing is changing on your current build.

If you use the upgraded API, all actions — whether client-side or server-side — show up in the dashboard. That means better monitoring, logs, transaction lifecycle tracking, and visibility across your app.

Q: Will the old APIs or SDKs be deprecated?

No. SDKs and dedicated service APIs are here to stay and will continue to evolve as before towards the new product simplification without any breaking changes.

Q: How are the upgraded services priced?

Services are priced as they are currently- no changes. Requests will be charged based on usage to the underlying infrastructure. See our pricing page for more details.

Q: Will portal docs change?

Yes. We’re gradually reorganizing our portal to match the new interfaces. You will see a lot of changes coming up daily. We will still ensure users on existing services have relevant documentation available.

If you need help on finding anything please let us know.

And as always, we are here for support. Our team will be on standby for support around the upgraded API. Please join us for any feedback or questions in our community Telegram channel.

What’s New

• Support Tab: A new “Support” tab is now available on the team sidebar
• AI Agent: Get quick answers with our built-in AI support chat
• Case Management: Create, track, and manage support cases directly from your dashboard

How It Works

• Open a new case for the thirdweb team to review
• View the status and history of existing cases
• Use the AI agent for instant guidance on common issues

Next Steps

• Go to your team in the dashboard and click on the Support tab
• For support SLAs by plan, visit: thirdweb.com/pricing
• For general response time expectations, see: portal.thirdweb.com/knowledge-base#3-response-time-expectations

We just enabled EOA execution for server wallets, allowing you to self fund your own server wallets, and directly executing onchain transactions from them.

Set type: "EOA" in your executionOptions and pass your server wallet EOA address (signer).

Remember to fund the EOA with some native currency on that chain!

curl -X POST "https://engine.thirdweb.com/v1/write/contract" \
  -H "Content-Type: application/json" \
  -H "x-secret-key: <your-project-secret-key>" \
  -d '{
    "executionOptions": {
      "type": "EOA",
      "from": "<your-EOA-server-wallet-address>",
      "chainId": "84532"
    },
    "params": [
      {
        "contractAddress": "0x...",
        "method": "function mintTo(address to, uint256 amount)",
        "params": ["0x...", "100"]
      }
    ]
  }'

If your EOA runs out of funds, the transactions will be paused until you send some funds to it, then all transactions will resume automatically.

Happy building! 🛠️

We just enabled EIP7702 for server wallets, resulting in 4x faster sponsored transactions from sending to confirming when compared to ERC4337 execution.

Simply pass your server wallet EOA address (signer), execution will automatically default to EIP7702 execution and sponsor gas for the transaction.

curl -X POST "https://engine.thirdweb.com/v1/write/contract" \
  -H "Content-Type: application/json" \
  -H "x-secret-key: <your-project-secret-key>" \
  -d '{
    "executionOptions": {
      "from": "<your-EOA-server-wallet-address>",
      "chainId": "84532"
    },
    "params": [
      {
        "contractAddress": "0x...",
        "method": "function mintTo(address to, uint256 amount)",
        "params": ["0x...", "100"]
      }
    ]
  }'

You can also explicitly enable it by passing type: "EIP7702" in the execution options. Other execution types are "ERC4337" and "EOA".

If you pass your smart contract wallet address, by default engine will use ERC4337 execution like before, no changes needed.

Take advantage of EIP7702 for your server wallets and let us know about your experience!

We've made significant improvements to the Payments (Universal Bridge) API's performance, improving average latency from 900ms to under 300ms. You can now get quotes, routes, token prices, and more in a third of the time. Our Payments API powers advanced user-centric UIs using our Payments Widgets, try them out here.

We’ve redesigned the ERC20 contract page to improve usability, shareability, and conversion. This update is live for all ERC20 contracts - including the ones you deploy from thirdweb dashboard

The Buy Token section is now placed at the top, making it easier for users to purchase tokens immediately. This also makes the page ideal for sharing with your community or end users.

The Token Price Chart has been moved further down to prioritize key actions and reduce visual clutter.

Several visual enhancements offer a cleaner, more user-friendly experience.

Checkout the updated layout for some popular tokens

• USDC on Base
• USDC on ethereum
• Shiba Inu on ethereum

Breaking Change: The Nebula API now requires a paid subscription plan. Free usage is limited to essential testing purposes.

• Free Tier: Limited to 1 RPS and 3 RPM (for testing only)
• Paid Plans Required: Production usage now requires one of the following plans:
  • Starter: 1 RPS, 10 RPM
  • Growth: 5 RPS, 100 RPM
  • Scale: 10 RPS, 500 RPM
  • Pro: 30 RPS, 1500 RPM
  • Custom: Reach out!

• Review your current Nebula API usage and update your integration to handle the new rate limits
• Select an appropriate plan on your team account on the dashboard

For questions about plan selection or enterprise needs, contact the thirdweb team.

You can now use the Transaction API with just your project secret key.

When you create a new project, we now initialize a secure Vault automatically for you which lets you create server wallets and transact immediately with just your project secret key.

curl -X POST "https://engine.thirdweb.com/v1/write/contract" \
  -H "Content-Type: application/json" \
  -H "x-secret-key: <your-project-secret-key>" \
  -d '{
    "executionOptions": {
      "from": "<your-server-wallet-address>",
      "chainId": "84532"
    },
    "params": [
      {
        "contractAddress": "0x...",
        "method": "function mintTo(address to, uint256 amount)",
        "params": ["0x...", "100"]
      }
    ]
  }'

• Before: Performing transactions with your server wallets required BOTH a project secret key (x-secret-key) AND a vault access token (x-vault-access-token).
• After: You can now do server wallet transactions with ONLY your project secret key

Your project secret key is now all you need to access thirdweb infrastructure and your server wallets from your backends.

If you've already created a vault for your project, nothing changes, you can continue using your vault access tokens normally.

When you create a project, we generate a secret key that only you have access to. We do not store that secret key only a hash of it. At project creation time, we now generate a Vault access token, encrypt with your project secret key, and store it.

This lets you now interact with your vault as long as you pass your secret key to the thirdweb transaction API.

At any point, you can choose to take control of your own Vault keys by revoking the Vault keys from the vault tab. This will invalidate any previous keys and generate new ones that you can store those yourself.

Happy building!

You can now search users by email, phone, id or address in your project or ecosystem by navigating to the Users tab.

Select the search criteria, type a value and hit search. Great for quickly finding user associated addresses or emails.

Happy building!