Describe the push-based outbound oracle pattern: its problem, solution, and main trade-off.

The oracle continuously watches the chain and, when a relevant event fires, pushes that change out to an off-chain system to trigger an action. Initiated on-chain; slowest of the four because it waits for a block.

• Problem: Knowledge on the chain must reach the outside world, but the closed chain can't push information out on its own.
• Solution: The oracle monitors the chain for relevant changes and then triggers or performs activities off-chain in response.
• Benefit: By constantly monitoring, it can automate off-chain tasks — take real-world action the moment a chain state updates.
• Drawback: It must run continuously or it misses events, and — crucially — the triggering event only exists once a transaction is mined into a block, so it inherits full block latency (measured ~16 s mean, high variance). That makes it the slowest pattern and risky for time-sensitive interactions.

Go deeper:

• Foundational Oracle Patterns (Mühlberger et al., arXiv) — the push-based outbound pattern and why waiting on a mined block makes it the slowest.