Testnet only (Arkiv Tiramisu). OpenTrigger 0.1 has not had an outside audit.
OpenTrigger

Examples

The dashboard and four example apps, all built on the published SDK.

The dashboard

The dashboard is the website for creating rules and watching receipts. It is a static app: it reads Arkiv from the browser and writes through your wallet, so it has no backend of its own. See Use the dashboard.

Example apps

Four small Next.js apps in examples/.

Canary landing page
Canary
Trigger Scope landing page
Trigger Scope
Private Pager landing page
Private Pager
Cron Hooks landing page
Cron Hooks
AppWhat it shows
Canary (examples/keepalive)A warrant canary: the publisher checks in by extending an entity; if they stop, a rule fires publicly. Each check-in extends the canary and its rule in one transaction. Anyone can open a canary's public page by its rule key.
Trigger Scope (examples/trigger-scope)A read-only explorer of the open worker network: workers and their versions, a receipt feed, any rule's audit trail, and how to run your own worker. No wallet.
Private Pager (examples/lease-alarm)Telegram reminders where the chat code is sealed to one worker in the browser, with a side-by-side view of what goes on Arkiv and what stays private.
Cron Hooks (examples/cron-hooks)Scheduled webhooks with no cron server, and a receiver that verifies the worker's signature against an allowlist and drops replays.

All four use arkiv-triggers@0.1.0 from npm, read Arkiv from the browser with an optional read-only relay for rate-limited visitors. Apps that write offer MetaMask or a testnet session wallet.

The example apps pass type checks, lint and production builds, and load against Tiramisu (live block, workers and socket). Writing rules from them has not been tested in a browser yet.

On this page