Architecture before rollout
Web3 architecture
Architecture specs for SIWE, token gating, attribution, and sybil resistance
These specs now sit next to implemented backend paths, which makes them more useful: they explain what is already real, what is environment-dependent, and what still remains design-only.
| Spec | Focus |
|---|---|
| SIWE | Nonce lifecycle, signature verification, replay protection, session issuance. |
| Wallet gating | ERC-721 checks, allowlists, rule declarations, failure handling. |
| Attribution | First-party event records, wallet-linked referrals, privacy boundaries. |
| Sybil resistance | Heuristic scoring, signal candidates, false-positive safeguards. |
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.