How to Use INOH for Tezos Event

Introduction

INOH provides a standardized framework for triggering, routing, and verifying event notifications on the Tezos blockchain. Developers and bakers use INOH to build responsive applications that react to on-chain state changes without constant polling. This guide explains how INOH works within Tezos and how to implement it for your next project.

Key Takeaways

• INOH enables push-based event notifications on Tezos, reducing network load compared to polling
• The protocol supports smart contract state transitions, delegation changes, and governance triggers
• Implementation requires Michelson contract integration and off-chain listener configuration
• Risks include relay centralization and callback reliability issues
• INOH differs from Tezos FA2 token standards by focusing on event propagation rather than asset management

What is INOH

INOH stands for Inter‑Blockchain Notification Handler, a lightweight protocol designed for the Tezos ecosystem. It creates a standardized channel for smart contracts to emit structured events that external applications can subscribe to and process in real time. The specification defines event schemas, delivery guarantees, and callback formats that work across different Tezos execution environments. According to the Tezos developer documentation, event-driven architectures improve application responsiveness and reduce unnecessary on-chain computations.

Why INOH Matters

Traditional Tezos applications rely on polling to detect state changes, which wastes resources and introduces latency. INOH eliminates this inefficiency by pushing notifications directly to subscribers when conditions are met. Bakers benefit from faster response times during critical events like missed blocks or reward distributions. DApp developers can create more engaging user experiences without maintaining expensive indexing infrastructure. The BIS has highlighted event-driven designs as a key trend in blockchain interoperability, making INOH a timely addition to the Tezos toolkit.

How INOH Works

The INOH framework operates through three interconnected components: Event Emission, Relay Network, and Subscriber Handlers.

Event Emission Phase:

Smart contracts invoke the INOH entrypoint with a structured payload containing event_type, timestamp, and payload_hash. The contract calculates a deterministic event_id using:

event_id = H(contract_address + entrypoint + block_level + payload_hash)

Relay Verification Phase:

INOH relayers observe Tezos blocks and filter events matching registered subscriptions. Each relay validates the event signature and creates a delivery receipt stored off-chain. The relay prioritizes events using:

priority_score = weight(contract_trust) * urgency(event_type) / distance(relay_node)

Subscriber Delivery Phase:

Registered subscribers receive events via webhook or WebSocket with the original payload and cryptographic proof. Subscribers verify proof against the Tezos block where the event originated, ensuring authenticity without re-processing the entire chain.

Used in Practice

A Tezos-based prediction market uses INOH to notify traders when new markets resolve. The smart contract emits a RESOLUTION event containing market_id and outcome data. Traders who subscribed receive instant notifications and can withdraw winnings without manually checking the contract state.

Bakers implement INOH to monitor delegation changes across their baker operations. When a wallet shifts delegation, INOH delivers the DEL_CHANGE event within seconds. This enables proactive customer retention actions rather than reacting to reduced stake after the fact.

Governance dApps leverage INOH for proposal state transitions. Voting applications subscribe to PROPOSAL_ACTIVE and VOTING_ENDED events, automatically updating UI dashboards and sending email digests to token holders.

Risks and Limitations

Relay centralization poses the primary concern. If few entities operate INOH relayers, they become attack vectors or single points of failure. Subscribers must implement fallback mechanisms and verify relay receipts independently.

Callback reliability varies across implementations. Network failures or subscriber downtime can result in missed events. INOH supports event replay within a configurable window, but extended outages may cause permanent notification loss.

Smart contract complexity increases when integrating INOH entrypoints. Developers must carefully design event schemas to avoid front-running attacks where malicious actors observe pending events and react before legitimate subscribers.

The protocol does not guarantee exactly-once delivery semantics. Subscribers should implement idempotency checks using event_id deduplication to prevent processing duplicate notifications.

INOH vs Traditional Tezos Indexing

Traditional Tezos indexers like TzKT or Badger scan every block and store parsed data in external databases. Applications query these databases for state information, introducing polling overhead and database dependencies.

INOH inverts this model by pushing data only when events occur. This reduces storage requirements and improves latency for subscription-based use cases. However, indexers offer richer query capabilities and historical analysis that INOH does not replace.

Indexers excel at complex data aggregations across multiple contracts, while INOH focuses on real-time event distribution. Most production applications benefit from combining both approaches: INOH for immediate notifications and indexers for historical reporting and complex filtering.

What to Watch

The Tezos core development team has discussed native event support in future protocol updates, which could reduce reliance on external relay networks. Monitor the Tezos improvement proposals repository for updates that may enhance INOH integration capabilities.

Cross-chain INOH extensions are under development, potentially enabling Tezos events to trigger actions on other Layer 1 networks. This expansion would significantly increase the protocol’s utility for decentralized bridge applications.

Standardization efforts are underway to create统一的INOH event schema library. A common taxonomy would improve interoperability between Tezos dApps and reduce custom integration work for developers.

FAQ

What programming languages support INOH integration?

Official INOH SDKs exist for Python, JavaScript, and OCaml. Community-maintained libraries cover Rust, Go, and Java. The Tezos sandbox environment includes test fixtures for all major SDKs.

How much does INOH relay service cost?

Public testnet relays operate free of charge. Mainnet relay services typically charge per-event fees ranging from 0.001 to 0.01 XTZ depending on urgency and delivery guarantees. Self-hosted relays eliminate per-event costs but require infrastructure management.

Can INOH events trigger on-chain smart contract callbacks?

INOH delivers events off-chain only. To execute on-chain actions, you must implement a separate transaction signing workflow that responds to received notifications. Chainlink oracles provide alternative on-chain callback solutions if trustless execution is required.

What is the maximum event payload size in INOH?

INOH supports payloads up to 4KB per event. Larger data sets should use IPFS or decentralized storage, with only the content hash included in the INOH payload. This keeps on-chain event data minimal while preserving off-chain data availability.

How do I test INOH locally before mainnet deployment?

Use the Flextesa sandbox with the INOH development plugin enabled. The plugin simulates relay behavior and includes a webhook inspector for debugging notification flows. Test contracts should emit events at each state transition to verify delivery.

Does INOH work with FA2 token contracts?

Yes, INOH integrates with FA2 contracts through standard event emission. You can subscribe to transfer events, operator updates, and metadata changes. Many Tezos NFT marketplaces use INOH to power real-time listing and sale notifications.

What happens if my subscriber server goes offline?

INOH relayers store undelivered events for a configurable retention period, typically 24 to 72 hours. When your server reconnects, it receives buffered events automatically. You should implement event ordering logic since network delays may cause out-of-sequence delivery.

Are INOH events considered legally binding on Tezos?

INOH events are informational notifications, not cryptographic proofs of contractual obligations. Any business logic dependent on INOH events should include on-chain verification steps. Legal agreements should reference smart contract state, not relay-delivered notifications.