Open Source
RepFi keeps application source code private while publishing full documentation and transparency materials in a public GitHub repository.
Public repository
github.com/repfistreamdev/repfi-public
What’s inside
| Document | Description |
|---|---|
| PROJECT.md | Complete project overview (A → Z) |
| HOW_IT_WORKS.md | User flow, live rooms, AI verification |
| WHY_NOT_A_SCAM.md | Trust, transparency, honest risks |
| TOKENOMICS.md | Pool, $RepFi token, fee routing |
| SECURITY.md | Auth, sessions, key handling |
| ANTI_CHEAT.md | Pose AI anti-cheat model |
| ARCHITECTURE.md | System design (no secrets) |
Screenshots and the RepFi logo are included in the images/ folder.
What’s not inside
- Next.js application source
- API route implementations
- Private keys, env files, or deployment secrets
Private repository
The live website at repfi.stream is built from a private
repository (repfistreamdev/repfi). Only the core team has access.
Why split public / private?
- Transparency — anyone can read how RepFi works and why it’s legitimate.
- Security — payout logic and infrastructure details stay private until audited.
- Community — screenshots and docs can be shared without exposing attack surface.
Contribute
Found a documentation error? Open an issue or pull request on repfi-public .
For product feedback, reach out on X @Repfitnes .
Last updated on