v1.0.0

Breaking Change

Redis is now required because all webhooks are enqueued as Redis jobs now.

Why?
Engine is moving workers to Redis because the queueing capabilities are simpler to maintain and more performant.
Webhooks as worker tasks means they can be retried and are async from the main job processor. This means txs are sent more quickly and webhooks are more reliable!

Expect more of our transaction processing to be moving to Redis workers in the future.

This is a breaking change to documented expectations, hence the major version update.

Upgrade guide (self-hosted)

Deploy a Redis to run alongside your Engine.
Set REDIS_URL to your Redis URL. Make sure your Engine can reach your Redis instance.

Example:

REDIS_URL=redis://<redis_url>:<redis_port>

or if your Redis has a user/password:

REDIS_URL=redis://<redis_user>:<redis_password>@<redis_url>:<redis_port>

See self-host instructions for details.

Upgrade guide (cloud-hosted)

No action is required. thirdweb will be upgrading Engine instances behind the scenes throughout the next week. There should be minimal downtime involved. If you'd like to schedule a specific time, please reach out to support@thirdweb.com.

What's Changed

• feat: Add filters to Contract Subscriptions by @arcoraven in #543
• feat: Move transaction webhooks to Redis by @arcoraven in #549
• Breaking change: Require Redis (for v1.0.0) by @arcoraven in #550

Full Changelog: v0.9.6...v1.0.0