Product definition
Aura Protocol is a Solana-native decentralized physical infrastructure protocol for WiFi connectivity. Hosts contribute internet access, consumers use connectivity, operators manage deployments, buyers purchase capacity, and developers build on verified network primitives.
Core architecture
The system follows a strict boundary: physical internet traffic remains off-chain, while Solana coordinates economic ownership and settlement. Aura Gateway devices sign service telemetry; the verification layer scores useful contribution; reward epochs are published as compact state for claims.
Participants
- Consumers discover access, build a profile, complete quests, and participate in rewards.
- WiFi hosts register venues and gateways, prove service, and become eligible for settlement.
- Network operators manage multi-location deployments and service quality.
- Connectivity buyers purchase or sponsor access capacity for events, brands, campuses, or mobility use cases.
- Developers consume protocol data, build apps, and integrate verified connectivity primitives.
On-chain design
Aura's program shape includes protocol configuration, operator authority, network registry state, reward epoch roots, claim receipts, and governance-ready controls. Token settlement and staking should use audited SPL-token flows and multisig-controlled authorities.
Backend and smart-contract readiness
The working backend exposes local API flows, signed gateway verification, local chain receipts, and chain sync endpoints. Contract source now covers protocol setup, operators, WiFi networks, reward epochs, profile claims, quest receipts, staking positions, and campaign claim receipts. Run npm run chain:check to inspect Solana readiness.
Quest economy
The growth system borrows a market-dashboard model: users have profile positions, quests behave like earnable markets, staking locks earned points for signal, claims create receipts, and leaderboards rank contribution. Real social login should use OAuth or wallet-native attestations before production.
Privacy and security
Aura should never publish browsing history, DNS activity, packet payloads, router passwords, raw MAC addresses, or exact private-home coordinates to public chain state.
Production readiness requires audited contracts, gateway firmware signing, replay protection, rate limits, abuse detection, event indexing, observability, incident response, and legal/compliance review for each operating region.
Private console
The private Console and Arena are available through login.html for operator workflows, host onboarding, signed gateway telemetry, user quests, staking, claiming, and leaderboard testing.