Engine v0.0.26 - Improved error messages, gas spike reliability, throughput + more
thirdweb Engine is an open-source server for your web3 app to read, write, and deploy contracts to the blockchain.
The team is working hard to continuously improve stability and developer experience.
Summary
- Clear error messages for onchain failures
- Improved reliability during gas spikes
- Higher read/write throughput
- Updated dashboard timeline
- Version indicator with update prompt
- Deploy contracts on behalf of other users
- New endpoints
Clear error messages for onchain failures
Engine now return the onchain error from the contract if the call is expected to fail. Bonus: since the transaction is simulated, gas funds are not spent!
Previous: An obscure, low-level error indicating the transaction will fail ("execution reverted").
Now: A clear error returned the contract.
Improved reliability during gas spikes
We've fixed numerous bugs that may occur during gas volatility. These cases occasionally caused nonce desync issues in the past.
- Removing a global "max gas price" limit. We'll re-introduce this limit per-chain or per-transaction in the future.
- Ensuring retries attempt with at least 10% higher gas (handles error ).
- Slightly increasing a transaction's gas limit to handle inaccuracies with the RPC provider's estimation.
Higher read/write throughput
Our goal is for Engine with 1 vCPU / 1GB memory* to handle the majority of apps' use cases. (*Costs $0.27 / day on AWS!)
We've made a handful of improvements to allow Engine to better handle traffic bursts:
- Configured server timeouts.
- Cached consistent auth computation (no impact to behavior).
- Improved underlying RPC latency.
- Improved underlying Contract metadata resolution latency.
- Scaled up load balancers for cloud-hosted Engine customers.
- Improved extension resolution in the thirdweb SDK.
- Improved batching behavior in the thirdweb SDK.
As a result, a single Engine on minimal infrastructure can handle 100-200 read requests per second and process 500 write requests per second. And throughput scales linearly by adding more Engine instances. Or get a cloud-hosted Engine for thirdweb to manage the infrastructure + scaling.
Bonus: most of these changes were made to thirdweb's infrastructure and SDK, so you'll see improvements across the thirdweb stack!
Updated dashboard timeline
The timeline in the dashboard shows where in the lifecycle the current transaction is. Select Cancel transaction to cancel any transactions not yet mined.
Version indicator with update prompt
The version badge in the dashboard now shows your current version.
And if it's out of date, cloud-hosted Engine customers can request a version update. The Engine team will update your host during low traffic (within 2 business days).
Deploy contracts on behalf of other users
The prebuilt contract deployment endpoints now accept a defaultAdmin
field which overrides the admin for a deployed contract.
This means your app can sponsor contract deployments and the contract admin will be a different wallet address. Your backend wallet that paid the gas will not have any permissions on the deployed contract.
New endpoints
- Sign typed data (EIP-712):
POST /backend-wallet/sign-typed-data
- Prepare a signature to sign for ERC721 signature mints:
- Returns the typed data to be signed by an external wallet.
Conclusion
The team is continuously iterating based on feedback. Please let us know in Discord if you have feature requests or encounter issues.
Want to contribute? thirdweb Engine is fully open-source and we welcome contributions.
We're also hiring!