The Sales TravelerIndependent · Reader-funded · A partnership buys reach, never a ratingIndex Desk Live
The Sales TravelerThe decision desk for revenue travel
Open the Index Desk
Implemented · production behavior unverified
Wallet bot prevention · Sybil resistance

Wallet bot prevention and sybil resistance for gated products and communities

Token-gated content, loyalty flows, and community access need anti-abuse controls. The code implements first-party heuristic scoring and documents possible future sybil-resistance signals. It does not claim a universal black-box “trust score.”

My assessment: The code implements bounded first-party heuristic scoring with published policy limits. Production behavior remains unverified, and the score cannot prove that a wallet belongs to a person.

Signals used or planned

  • Implemented: deterministic first-party heuristic scoring for suspicious behavior patterns.
  • Not implemented: deep on-chain social-graph scoring or attestation-registry dependency.
  • Always required: human review and a visible appeal path when a verdict matters.

Read the anti-bot spec →Policy boundaries

Common questions

Is bot prevention verified in production?

No. The code implements a first-party heuristic scoring path, but production behavior still needs independent verification.

Does the system use opaque trust scores for advertising?

No. The published policy explicitly rules out advertising or resale uses of bot-prevention signals.

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

  1. Primary standards: Protocol specifications and standards bodies define what an implementation must do.
  2. Security guidance: Threat-model and identity guidance define controls, failure handling, and recovery expectations.
  3. Deployment evidence: Independent end-to-end checks establish whether a configured production capability is live.
  4. Editorial judgment: I apply those sources to revenue-travel decisions and state where the evidence stops.