Project wallets now send for you

TLDR: The thirdweb API from fields when transacting are now optional - this is powered by the newly launched Project Wallets - go set one up!

What’s new

When you’re orchestrating transactions from your backend, repeating the same sender address in every payload is the definition of busywork. Starting today, you can skip it. Authenticate with your project’s secret key, leave off the from field, and we’ll launch those transactions straight from your project wallet.

• Automatic sender fallback for server-side flows that use your project secret key.
• Works everywhere you submit encoded calls, trigger wallet actions, deploy or write contracts, mint tokens, process payments, or swap via the bridge API.
• Still honors explicit from values when you need to override the default.

Why you’ll love it

Removing boilerplate means less room for typos, quicker prototyping, and cleaner shared helpers. Your integrations stay lean while every transaction still resolves to the right wallet.

Try it now

curl https://api.thirdweb.com/v1/transactions \
  -H "Content-Type: application/json" \
  -H "x-secret-key: <your-secret-key>" \
  -d '{
    "chainId": 421614,
    "transactions": [
      {
        "data": "0x",
        "to": "vitalik.eth",
        "value": "0"
      }
    ]
  }'

No from required—just the secret key that unlocks your project wallet.