Skip to content

bitrep-core/primary

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

62 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

BitRep — Verifiable, Portable Binary Attestations

BitRep is a protocol and reference implementation for verifiable trust built on cryptographic identity, binary attestations, and decentralized governance. It provides a trust layer that is portable, auditable, and independent of any single platform.

Features

  • self‑sovereign identity — RSA keypairs with verification endpoints
  • binary attestations — signed, anchored trust statements (issuer → subject)
  • governance — one-identity-one-vote proposals and voting
  • privacy layer — ZK framework and selective disclosure of attestations
  • integrations — import attestations from GitHub, eBay, LinkedIn, StackOverflow
  • security — RSA signatures, validation, CodeQL clean
  • testing — full FastAPI test suite

Why BitRep Exists

Online trust is fragmented across platforms. BitRep provides a shared attestation layer that applications can adopt without centralizing trust or locking users into a single ecosystem.

How It Works

  • Identity: users generate RSA keypairs; public keys act as decentralized identifiers.
  • Attestations: identities issue signed, binary statements about others. Each attestation carries: {issuer, subject, attestation_type, signature, timestamp, anchor}.
  • Governance: proposals use one-identity-one-vote rather than tokens or weighted scores.
  • Privacy: users can prove they meet attestation-count thresholds without revealing raw data.

Attestation Model

BitRep attestations are binary, signed, anchored statements. There is no numeric reputation score, no aggregation, and no scoring formula. Each attestation contains:

Field Description
issuer Identity issuing the attestation
subject Identity the attestation is about
attestation_type Type of attestation (e.g., "peer_verified")
signature Cryptographic signature from issuer
timestamp When the attestation was created
anchor Optional anchor (e.g., transaction hash, mutual validation)

Quick Start

  • install dependencies
  • run the FastAPI server
  • generate an identity
  • issue an attestation
  • query attestations

API Overview

  • identity endpoints — create, verify, rotate keys
  • attestation endpoints — issue, validate, list
  • governance endpoints — proposals, votes, tallies

Security Notes

  • RSA signatures
  • input validation
  • documented threat model
  • experimental ZK framework (not production‑grade)

Contributing

Contributions are welcome in:

  • cryptography
  • backend engineering
  • governance design
  • privacy systems

Open an issue, start a discussion, or submit a PR.

About

Minimal implementation of the BitRep attestation graph (Phase 1)

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages