Skip to main content

Glossary

Last updated on June 17, 2024 · Jean-Loïc M.

TermDefinition
Firewall Smart ContractA Firewall Smart Contract (or Contract Firewall) is the software component executed by the Decentralized Firewall at the end of a transaction. Its purpose is to analyze the transaction traces and safeguard the application.
IPSProtocolThe Layer 2 ecosystem that has devised and implemented hack prevention using decentralized firewall technology. The ecosystem comprises its decentralized autonomous organization (DAO), core developers, partners, and dApps.
IPSChainThe blockchain within the IPSProtocol ecosystem.
Decentralized Firewall (DF)The engine implemented within the execution client, responsible for executing Firewall Smart Contracts.
Firewall ClientA blockchain client module, run alongside the execution client, that validates transactions during block building and consensus by executing the Firewall Contracts associated with each affected dApp.
Firewall ContractAn on-chain smart contract that declares and enforces a dApp's intended behavior. Each Firewall Contract is mapped to exactly one business-logic smart contract.
IPS EVMA specialized EVM that powers the Decentralized Firewall, executing Firewall Contracts deterministically and producing reproducible security analyses.
Firewall LayerA logical network layer composed of node operators running the Firewall Client. The Firewall Layer is the long-term architectural target for IPSProtocol — analogous to how the Consensus Layer evolved alongside the Execution Layer.
Firewall Deposit ContractAn on-chain contract deployed to mainnet that holds dApp deposits, maps dApps to their Firewall Contracts, and pays node operators after Firewall Layer consensus.
Execution Gap (IntentGuard)The discrepancy between what a transaction was intended to achieve at signing time and what actually settles on-chain. IntentGuard, the user-facing application of the IPSProtocol model, closes this gap with a Protection Transaction declaring expected outcomes.
Protection Transaction (IntentGuard)A second signed transaction declaring the outcome constraints the original transaction must satisfy (expected balance changes, recipient set, allowed contract-state mutations). The original transaction is included only if execution matches the declared constraints.