Notification gateways

• Accept notification events from the protocol and deliver them over any transport
• Return delivery receipts
• Verify user contact endpoints through one-time codes or bot challenges
• Register supported channels, regions and pricing in the service registry

5,000 OPEN, enforced by the staking program when you stake against the notification-gateway role. It buys economic accountability and Sybil resistance rather than preferential treatment: nothing routes notification traffic by stake today, so meeting the minimum makes a gateway eligible, not favoured.

Nothing yet. The intended model is a share of a small fixed OPEN fee a participant pays to enable notifications on a trade, with the remainder split between treasury and ecosystem allocations — but no such fee exists anywhere in the protocol today and no gateway rewards are paid. Treat it as design intent, not income.

• →Implement the published notification specification
• →Register gateway metadata: channels, protocol version, pricing, endpoints
• →Accept that gateways receive only the minimum information needed to deliver — never balances, dispute evidence or unrelated marketplace state

• OFS-6000OpenFiat Notification Protocol (ONP)
• OFS-1500Service Registry Protocol (SRP)