Cowrie Research

bandada-primary-sources-2026-05-11

3 min read

Bandada primary sources

Collected: 2026-05-11 UTC

Primary sources reviewed

  • https://bandada.pse.dev/
    • Official homepage
    • Used to confirm the project’s self-description as a dashboard- and application-oriented system for creating and managing onchain and offchain anonymous groups, with invitation-based and credential-based membership paths
  • https://docs.bandada.pse.dev/
    • Official docs landing page
    • Used to confirm the core framing of Bandada as infrastructure for privacy-preserving groups and anti-sybil credential-gated admission
  • https://docs.bandada.pse.dev/faq
    • Official FAQ
    • Used to confirm the explicit split from Semaphore, Bandada’s role in offchain group management and member storage, support for large groups through server-side Merkle-proof generation, and compatibility with Semaphore-style proof systems
  • https://paragraph.com/@privacy-scaling-explorations/bandada-is-live
    • Official launch post by Privacy and Scaling Explorations
    • Used to confirm the project’s intended users, SaaS-versus-self-hosted deployment framing, dashboard/API/client/contracts architecture, manual-versus-credential group types, and example credential providers / use cases
  • https://github.com/bandada-infra/bandada
    • Official source repository
    • Used to confirm the explicit system decomposition into API, dashboard, demo client, verification contracts, SDK/libraries, credential validators, API-key-based admin flows, and self-hosted development/deployment paths

Notes

  • Bandada cleared the bar because it is not just another privacy app, role bot, or generic identity toolkit; it exposes a distinct upstream control layer where anonymous-group membership is defined, stored, administered, and proven before downstream signaling even begins.
  • The single most useful analytical distinction is Bandada versus Semaphore. Semaphore supplies the anonymous membership-proof and signaling primitive, while Bandada supplies the surrounding infrastructure for offchain group administration, eligibility checks, invite flows, and large-group proof generation.
  • This makes Bandada a strong comparison point for several existing corpus clusters at once:
    • against Guild, for programmable community admission and role logic, but with privacy-preserving groups instead of openly visible roles;
    • against Sismo, Human Passport, and other sybil-resistance / credential-aggregation systems, for the narrower question of who gets admitted to a group and through which external proof providers;
    • against Semaphore itself, for the separation between anonymous signaling and group-operations middleware.
  • The dashboard / API / client / contracts / libraries split matters because it prevents the project from being flattened into one generic zk identity bucket. Different actors can control admin UX, hosted APIs, provider integrations, validator logic, proof generation, and downstream application design.
  • The FAQ’s emphasis on server-side Merkle-proof generation is especially useful because it exposes an operational choke point that many anonymous-membership systems hide. In practice, this can determine whether large-group privacy systems remain usable without pushing heavy proof-preparation work onto end users.
  • The launch post also makes Bandada useful as a bridge between privacy and organizational tooling. Its stated use cases include private feedback, whistleblowing, anonymous voting, contributor groups, and credential-gated communities, which means it belongs in the active corpus as middleware rather than as a one-off app.
  • No canonical whitepaper surfaced in this pass, but the official docs and repository were sufficient to recover the project’s mechanism and control surfaces.

Graph View