Firewall Records Go Native: Write Security Decisions Directly to Your Chain

Today we’re introducing a meaningful upgrade to Forta Firewall: Firewall records can now be written directly to your chain, instead of being stored on the Forta chain and then bridged out. This change makes Firewall more interoperable and more composable with the rest of your on-chain stack, because the same chain that enforces a policy can now also serve as the canonical home for the record of that decision.

Historically, Firewall decisions and records lived on an isolated Forta chain. If an ecosystem wanted to use those records elsewhere (whether for monitoring, analytics, proofs or integrations with other applications) those records had to be bridged. That approach worked, but it also introduced unnecessary complexity. Bridging adds moving parts, introduces operational overhead and makes it harder for applications and tooling that are chain-native to treat security records as first-class on-chain data.

With this release, Firewall can write records locally on the host chain as an opt-in configuration. In practical terms, this means applications, indexers, explorers and partner systems can access Firewall records where they already operate, without relying on cross-chain delivery. It also means security outcomes can participate more naturally in the ecosystem’s interoperability patterns, because the data is emitted and stored within the same execution environment that apps already trust and integrate with.

This is also an important step forward for composability. When records are available on the host chain, they can be consumed directly by the same kinds of infrastructure that power the rest of DeFi and on-chain finance: indexing pipelines, analytics dashboards, and monitoring systems can read the canonical record without translation. Over time, this also opens the door for richer integrations where security decisions become a native primitive that other systems can reference, reason about, and build on.

Importantly, writing Firewall records to the host chain is an opt-in capability. It is not enabled by default: chains need to explicitly request it as part of their Firewall configuration. This ensures ecosystems can adopt the model intentionally, align it with their operational requirements and roll it out on their own timeline.

Alongside this upgrade, we’re sharing an infrastructure update that follows naturally from the direction Firewall is taking. The Forta chain is being sunset, and it will not store Firewall records any longer. This is not a retreat from the system, it’s a maturation of it. As Firewall records become chain-native by default, a separate record-storage chain becomes unnecessary. Sunsetting the Forta chain reduces complexity, removes an entire layer of bridging overhead, and aligns the architecture with how modern on-chain infrastructure is expected to behave: local, composable, and interoperable.

Same Firewall, Native Records

Forta Firewall helps chains and their protocols enforce policy at runtime while staying compatible with the open, composable nature of on-chain systems. Writing records directly on the host chain is a major step in that direction. It simplifies integration, improves interoperability, and makes Firewall records more useful to the broader ecosystem.

If you’re integrating Firewall and want guidance on enabling the opt-in host-chain records feature (or updating any downstream consumers that previously relied on bridged records) the migration path is straightforward and we’re happy to support. This upgrade is about meeting builders where they are: on their chain, in their tooling, with records that are native, interoperable, and ready to compose.

‍