Funder Guide
Evaluate projects and milestones, understand evidence, and make more informed funding decisions.
BBOXX helps funders compare project claims with public evidence. It does not provide investment advice or guarantee delivery, refunds, security, or future value.
Start with the project record
Confirm that the website, repository, publisher profile, and release channels refer to the same project. Look for ongoing maintenance, issue handling, tagged releases, a clear license, and documentation that a new contributor can follow.
Treat ratings and verification as inputs rather than conclusions. A small project can be valuable without many reviews, while a popular project can still contain risk.
Evaluate the proposed work
For each milestone, identify:
- Outcome: What observable capability or artifact will exist?
- Acceptance criteria: What must be true for the work to count as complete?
- Evidence: Which release, source, test, demonstration, or report will be inspected?
- Scope: What is explicitly excluded?
- Dependencies: Which external services, protocols, or upstream changes could block delivery?
- Funding mechanics: Who controls funds and how is a payout authorized?
If two reasonable reviewers could interpret completion differently, the milestone needs more detail.
Match evidence to the claim
A screenshot may demonstrate interface progress but not code quality. A merged pull request demonstrates code changes but not a released product. A build hash identifies an artifact but does not prove source equivalence. Ask for evidence appropriate to the promised outcome.
Follow delivery over time
Compare submitted evidence with the original acceptance criteria. Note scope changes publicly and evaluate whether delays are explained by previously disclosed dependencies. Prefer a sequence of smaller, inspectable milestones over a single large promise.
Understand registry boundaries
BAR can show a publisher-authorized history of metadata changes, but it does not escrow funds, audit code, or enforce a milestone. BBOXX can display funding and community context, but the exact custody and payout mechanism must be evaluated separately.
A compact review checklist
- Project identity and links corroborate one another
- Repository and license are accessible
- Milestone outcome is observable
- Acceptance criteria are unambiguous
- Evidence matches the promised result
- Dependencies and risks are disclosed
- Fund custody and payout conditions are understood
- No badge or rating is treated as a guarantee