Changelog

Here are this week's highlights:

• Builder Codes

• User Alerts

• Improvements and Fixes

Builder Codes

Formo now automatically detects and extracts ERC-8021 Builder Codes from transaction calldata.

• Builder codes are an onchain attribution standard that lets apps identify themselves in transactions. When a transaction includes an ERC-8021 data suffix, Formo parses it and includes the builder_codes field in the transaction event.

• For example, a transaction with the builder code "uniswap" would include "builder_codes": "uniswap" in the event properties.

This works automatically — no additional configuration is needed. If your app appends builder codes to transactions, Formo will detect and attribute them.

You can now query your transaction data by builder_codes property in the dashboard, charts, and the query explorer to get instant attribution based on builder codes.

User Alerts

Get notified on Slack or webhooks in real time when high-value whales visit your app with the new User Alerts.

You can now receive notifications whenever users that fit a certain criteria visit your DeFi app, such as:

• Users with a minimum net worth (minnows, dolphins, whales),

• Users with specific wallet labels (Coinbase Verified, OFAC Sanctioned, Merkl Campaigns),

• Users from a specific country, or

• All of the above!

Improvements and Fixes

• Fixed duplicate alerts being sent for the same trigger condition

• Fixed mismatched MAU counts that caused inaccurate usage reporting for some projects

• Allowed project domain changes without rotating the write key

• Synced usage metering with billing periods so usage metrics now align with your subscription cycle

• Wallets that exceed the MAU limit are now hidden

• Fixed 404s for form and sidebar links