Engine Cloud: Now Generally Available

Engine Cloud exits beta with a complete architectural overhaul powered by our new Rust-based Engine Core. This update introduces simplified APIs, comprehensive transaction monitoring, and significant performance improvements.

🚀 What's New

Rust-Based Engine Core

Engine Cloud is now built on Engine Core, our new open-source Rust-based blockchain transaction infrastructure. The Engine Core repository is now public.

Key improvements include:

• Sub-second API response times (< 40ms server latency for transactions, < 10ms for status)
• Horizontal scaling through Redis-backed job queues with configurable worker pools
• Memory safety and zero-cost abstractions from Rust
• Improved nonce management and transaction batching
• Enhanced error handling with detailed context

Changed Signing API

Signature endpoints now use a new signingOptions parameter that replaces the previous executionOptions structure across all signature routes.

Before:

{
  "executionOptions": {
    "from": "0x...",
    "chainId": 137
  }
}

After:

{
  "signingOptions": {
    "type": "eoa",
    "from": "0x...",
    "chainId": 137
  }
}

ERC-4337 Smart Accounts support intelligent defaults with minimal configuration:

{
  "signingOptions": {
    "type": "ERC4337",
    "signerAddress": "0x...",
    "chainId": 137,
    "entrypointVersion": "v0.7"
    // Optional: smartAccountAddress, accountSalt, entrypointAddress, factoryAddress
  }
}

When using thirdweb's default account factory, specifying entrypointVersion automatically configures the appropriate entrypoint and factory addresses:

• v0.6: 0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789 (entrypoint), 0x85e23b94e7F5E9cC1fF78BCe78cfb15B81f0DF00 (factory)
• v0.7: 0x0576a174D229E3cFA37253523E645A78A0C91B57 (entrypoint), 0x4bE0ddfebcA9A5A4a617dee4DeCe99E7c862dceb (factory)

The system automatically infers missing values when not explicitly provided, supporting both v0.6 and v0.7 standards.

Cleaner Response Format

Response handling is now more intuitive for single fallible operations like signMessage:

Before:

{
  "result": {
    "results": [
      {"success": true, "data": "0x..."},
      {"success": false, "error": "Invalid signature"}
    ]
  }
}

After:

{
  "result": [
    {"result": "0x..."},
    {"error": "Invalid signature"}
  ]
}

Activity Logs System

The new Activity Logs system provides visibility into transaction lifecycle and Engine operations:

• Real-time status tracking from submission to confirmation
• Detailed error context for failed transactions
• Performance metrics including gas usage and timing
• Debug information for troubleshooting

Access via dashboard or API:

GET /transactions/activity-logs?transactionId={queueId}

🔄 Migration Guide

TypeScript SDK Users

No breaking changes. Existing ServerWallet implementations continue working—simply upgrade your SDK version:

npm install thirdweb@5.105.2

const serverWallet = Engine.serverWallet({
  address: "0x...", // your wallet address
  chain: sepolia, // or your target chain
  client: thirdwebClient,
  vaultAccessToken: "your_vault_token"
});

// All existing methods work identically
const result = await serverWallet.sendTransaction(tx);

Direct API Users

Update signature endpoints to use the new signingOptions parameter. Most use cases only require changing the parameter name while keeping the same values.

Getting Started

Engine Cloud is now generally available:

1. Create a thirdweb project
2. Complete Transactions API onboarding to create server wallets and vault access tokens
3. Start making API calls!

Engine Documentation → | API Reference →