CUBID primary sources — 2026-05-04

Project status in this pass

• No canonical standalone CUBID whitepaper or litepaper surfaced.
• The clearest current source of truth is the public docs corpus plus the official GitHub repositories, especially the introduction, API reference, terminology glossary, and Cubid Passport materials.
• The project is best understood as proof-of-personhood and sybil-resistance identity middleware with an app-scoped wallet and credential layer rather than as a simple login SDK or reputation dashboard.

Primary-source snapshots

1) Introduction docs

• URL: https://raw.githubusercontent.com/Cubid-Me/cubid-docs/main/introduction.md
• Key excerpt:
  • The introduction says CUBID is a decentralized identity management and Sybil attack prevention protocol.
  • It says the system uses cryptographic techniques, zero-knowledge proofs, and collaboration between apps so users can prove they are real without exposing unnecessary personal data.
  • It emphasizes reusable identity, selective disclosure, developer APIs, and a collaborative cross-app ecosystem.

2) Cross-app scoring model in the introduction

• URL: https://docs.cubid.me/
• Key excerpt:
  • The docs frame CUBID as a cross-app scoring protocol where a shared identity across many apps can strengthen trust, security, and privacy simultaneously.
  • They say apps exchange updates through APIs and webhooks and that the CUBID scoring algorithm estimates the likelihood that a user is a unique alive human.
  • They also describe blacklist and recovery dynamics when duplicate accounts are detected and later merged.

3) API v2 reference

• URL: https://raw.githubusercontent.com/Cubid-Me/cubid-docs/main/api-reference.md
• Key excerpt:
  • The POST /api/v2/create_user endpoint creates an app-scoped user, associates that user with a credential such as email or phone, and returns is_new_app_user, is_sybil_attack, and is_blacklisted.
  • The docs explicitly recommend using the returned CUBID user_id as the app’s core identifier when proof-of-personhood or bot defense is central to business logic.
  • The same reference also documents POST /api/v2/pk/fetch_evm_public_key, which generates one EVM public key per user per app.

4) Terminology glossary

• URL: https://raw.githubusercontent.com/Cubid-Me/cubid-docs/main/terminology.md
• Key excerpt:
  • The glossary defines app-scoped user IDs as a privacy feature intended to prevent cross-site tracking.
  • It defines “stamps” as identity-bearing proofs such as email, phone, social accounts, blockchain accounts, and proof-of-personhood credentials.
  • It also says proof-of-personhood scores quantify the trustworthiness of the user’s identity and that CUBID can act as a wallet by generating and managing keypairs for users.

5) Cubid Passport repository

• URL: https://raw.githubusercontent.com/Cubid-Me/cubid-passport/main/README.md
• Key excerpt:
  • The README describes a demo flow with passwordless login, Gitcoin Passport stamp collection, walletless NEAR account creation, minting a score-derived SBT, and private-key export.
  • This is strong evidence that the team is experimenting with identity-plus-wallet onboarding flows, not merely static identity verification.

6) Official GitHub organization

• URL: https://github.com/Cubid-Me
• Key excerpt:
  • The org surface exposes multiple first-party repositories including docs, passport, SDK, and starter-project material.
  • Even when individual repos are sparse, the org footprint helps confirm that CUBID is being built as an integration platform rather than a one-off demo.

Working conclusion

CUBID is best cataloged as a cross-app proof-of-personhood and sybil-resistance control plane. The deciding evidence in this pass was the combination of reusable identity stamps, app-scoped IDs, webhook-propagated trust changes, explicit blacklist/sybil signals in the core API, and an adjacent wallet/account-generation layer for app onboarding.