Solana Frontier Hackathon MVP

Proof of Unique Humanity for Solana.

HumanPulse proves the presence of a unique living human at a specific moment in time — instantly, privately, and on-chain.

HPP
Current MVPWebcam hand-detection challenge-response and live Devnet proof-consumption transaction.
Solana Integration$HPP Devnet token, deployed Anchor burn-on-use program, and public transaction proof.
Privacy-first positioningDesigned around proof consumption, not centralized identity storage.
Problem

The internet cannot reliably tell humans from machines.

AI agents, Sybil farms, airdrop abuse, and governance manipulation create a growing need for privacy-preserving human presence verification.

Sybil resistance

DAO votes, airdrops, token launches, and access gates need stronger protection against duplicated wallets and bot farms.

Privacy risk

Centralized identity systems and biometric databases introduce custody, friction, and trust assumptions.

Solana-native need

Verification events should be fast, low-cost, composable, and usable directly by on-chain applications.

Live Demo Preview

Verification in under 10 seconds.

The user completes a webcam-based hand challenge. HumanPulse demonstrates a verification flow and returns a proof-consumption signal that can be used by a dApp.

Camera-based challengeMVP browser challenge-response using local hand detection.
Local processingCamera frames are processed in-browser for this MVP demo and are not uploaded or stored.
On-chain proof consumptionLive Devnet transaction available in the section below.
Active Challenge
Raise your hand
● Hand challenge
Verification preview complete 100%
Verified HumanNo biometric identity stored in this preview.

MVP note: this visual section is a verification-flow preview. The live webcam and Solana Devnet transaction demo is available below.

Live Devnet Demo

Complete a webcam hand challenge and consume a proof on Solana Devnet

This MVP uses browser-based hand detection for challenge-response. After the hand challenge is completed locally, the proof-consumption event is recorded through a real Solana Devnet transaction.

1. Connect Wallet

Connect Phantom on Solana Devnet.

2. Start Camera

Load local browser hand detection.

3. Raise Your Hand

Complete the hand challenge locally.

4. Verify On-Chain

Sign a real Devnet proof-consumption transaction.

Wallet not connected
Camera not started. Connect wallet, then start the hand challenge.
Challenge: Raise one hand in front of the camera
Hand detector idle.
Status: waiting for wallet connection.

MVP note: camera frames are processed locally in the browser for this demo and are not uploaded or stored. The demo uses MediaPipe-based browser hand detection to unlock a real Solana Devnet proof-consumption transaction using the Solana Memo program. The deployed HumanPulse Anchor burn-on-use program represents the protocol’s burn-based verification fee mechanism.

Architecture

MVP now, protocol roadmap next.

HumanPulse separates the current hackathon implementation from longer-term research modules. The MVP demonstrates webcam challenge-response and live proof consumption on Solana Devnet.

Current MVP

Webcam-oriented verification preview, local hand-detection challenge-response, live Devnet proof-consumption transaction, demo website, and public demo video.

Solana components

Deployed $HPP Devnet token, deployed Anchor burn-on-use program, and example proof-consumption transaction on Solana Explorer.

Technical roadmap

Validator / aggregator architecture, recursive zk-STARK aggregation, TEE-based local proof generation, and optional advanced sensing modules.

Business Model

Proof consumption as a usage event.

HumanPulse can charge applications per verification event. DAOs, launchpads, airdrop platforms, DePIN networks, and gated applications consume HumanPulse proofs to reduce Sybil abuse. In the MVP, this is represented by a proof-consumption transaction and a deployed burn-on-use program.

Who pays?

Applications that need Sybil-resistant access, eligibility, governance, or reward distribution.

When?

When a user consumes a verification proof for a gated action or eligibility check.

Why?

To significantly increase the cost of bot farms, duplicated wallets, and automated participation abuse.