Spec aligned to first-party persistence
Wallet attribution architecture spec
Wallet attribution spec: explicit event records, referrals, and privacy boundaries
This spec defines wallet attribution as a bounded first-party event system, not a stealth identity graph.
- Register a wallet-linked referrer: a partner or contributor opts into a wallet identifier.
- Record a first-party event: the system posts a qualifying action to
/api/v1/attribution-record. - Keep the boundary visible: the record stays first-party and policy-limited.
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.