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
Spec aligned to the implemented gate-check path
Wallet gating architecture spec

Wallet gating spec: ERC-721 access checks, allowlists, and failure-safe responses

This spec documents implemented backend logic and its explicit failure behavior when on-chain configuration is missing.

  1. Declare a rule: local allowlist, ERC-721 balance, or hybrid rule.
  2. Submit the request: client calls /api/v1/gate-check.
  3. Return a safe result: granted, denied, or unavailable — never a fabricated pass.

Open token-gating page →

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.