Infrastructure Architecture
A high-level view of the technical layers that coordinate wallet ownership, identity, campaigns, products and reporting.
Hazels is designed as a layered system rather than a single application. Each layer has a defined responsibility and can evolve independently while using the same ownership and verification foundation.
Architecture layer | Responsibility | Connected products |
|---|---|---|
Wallet & Ownership Layer | NFT ownership checks, staking status, snapshots, eligibility state | All private Hazels products |
Identity Layer | Creator profile, connected X identity, account-quality inputs | Pulse, Academy |
Campaign Layer | Campaign definitions, submissions, eligibility, scoring context | Pulse |
Launch Layer | Project onboarding, allocation logic, snapshots, mint operations | Drops |
Integrity Layer | Behavioral, engagement, graph, content, audience and wallet risk signals | Pulse, Drops verification |
Learning Layer | Educational content, AI-assisted workflows, access controls | Hazels Academy |
Commerce Layer | Store inventory, physical releases, product identity and retail surfaces | Hazels Store, RWA inputs |
RWA Reporting Layer | Product-cycle accounting, eligibility weights, calculation and records | Hazels RWA |
Community Layer | Private Discord verification and governance participation | Discord, governance, meetups |
Partner Integration Layer | Approved campaign, project and brand connection points | Pulse, Drops, IP collaborations |
Verification boundaries#
A verified wallet state does not automatically authorise every action across the ecosystem. Each product evaluates the minimum data required for its own operation. For example, Pulse requires creator identity and campaign data; Drops requires project-specific staking eligibility; RWA requires cycle-specific ownership and reporting conditions.
This separation reduces the need for one product to depend on unrelated data from another product and creates clearer operational boundaries as the ecosystem expands.
Ownership verification, safety and operational integrity#
A private ownership network is only useful if its access rules can be verified consistently. Hazels therefore treats wallet verification, snapshot integrity, contract review and published campaign terms as operational infrastructure rather than optional community processes.
Restricted products should be accessed only through official Hazels interfaces and published partner routes. A creator, influencer, moderator or partner cannot privately override an ownership requirement. Where a campaign requires a snapshot, the eligible cohort is fixed according to the published rules and invalid, duplicated, restricted or technically ineligible wallets can be excluded before settlement.
Drops project review can include team, contract, supply, metadata, security and disclosure checks. Pulse applies integrity agents to behavioral, engagement, content, audience, graph and wallet signals. RWA reporting is designed around realized revenue, documented deductions and cycle-specific eligibility.