OtterFi

Developers

OtterFi is built as two independent products sharing a common platform. This page explains the architecture and design principles at a high level without diving into implementation details.

Two products, one platform

Verify and Notify are built and run independently, sharing only the top-level account a community belongs to. Neither one depends on the other's data or uptime - Verify reads chain state directly for its own needs rather than relying on Notify's own event pipeline, since the two products have different correctness requirements.

This separation allows each product to evolve independently while sharing a consistent experience for community owners.

Notify Architecture

Verify Architecture

Verification Engine

The Verification Engine is a small, pluggable registry of ownership-proof methods (today: connect-wallet and self-transfer). Whatever triggers a re-check - a schedule, a manual command, or an on-chain event via Live Membership - always funnels into the exact same evaluation logic.

The Verification Engine guarantees every access decision follows the exact same evaluation path, regardless of what triggered it.

Event Pipeline

Both products are built around domain events rather than direct calls between components - an event is persisted, and whatever needs to react to it (a notification formatter, a dirty-membership check) does so independently.

This approach keeps components independent, easier to maintain, and simpler to extend as OtterFi grows.

Platform Adapters

Telegram and Discord are each implemented as an adapter behind a common interface, for both message delivery and access-granting.

This architecture makes adding future platforms significantly easier without changing Verify or Notify themselves.

Design Principles

  • Product independence
  • No custody
  • Platform abstraction
  • Event-driven architecture
  • Blockchain as the source of truth
  • Automation over manual administration

Technology Philosophy

OtterFi favors simple, composable architecture over unnecessary complexity. Components communicate through well-defined interfaces, allowing products and platforms to evolve independently.

Looking Ahead

A public API is planned to allow communities to integrate OtterFi with their own tools and workflows.

See the Roadmap for future platform and developer features.

Next steps