Spec aligned to heuristic bot scoring
Sybil resistance architecture spec
Wallet bot prevention spec: heuristic scoring, signal candidates, and human review
This spec shows where the implemented first-party scoring path stops and where stronger reputation or attestation signals would begin.
- Implemented baseline: first-party heuristic scoring.
- Candidate upgrades: rate-limiting, wallet-age signals, attestation membership.
- Required safeguard: human review and a visible appeal path.
Evidence, freshness, and corrections
- Written and edited by
- Rachel Julian, founder and editor
- Last reviewed
- 2026-08-13
- Readiness rule
- Scaffold means designed, not implemented. Beta means implemented with production verification pending. Live means independently verified end to end. Source code, ABI files, endpoints, or configuration never prove production availability.
- Correction path
- Report a correction or compare the capability changelog.
Source hierarchy
- Primary standards: Protocol specifications and standards bodies define what an implementation must do.
- Security guidance: Threat-model and identity guidance define controls, failure handling, and recovery expectations.
- Deployment evidence: Independent end-to-end checks establish whether a configured production capability is live.
- Editorial judgment: I apply those sources to revenue-travel decisions and state where the evidence stops.