Project Description

K-pop voting suffers from two core problems: lack of transparency and severe fragmentation. Today, fans are forced to move across many competing apps and regional restrictions, while centralized operators continue to face manipulation controversies that damage trust. Blockchain can solve the trust problem, but existing solutions often introduce new friction through gas fees and complex identity tools.

VESTAr solves both issues at once. Built on Status Network, VESTAr provides a unified, mobile-first voting platform where users can create and participate in K-pop votes with gasless transactions. It also uses Karma, a non-transferable reputation system, to provide sybil resistance without requiring heavy identity verification. As a result, voting becomes both verifiable and easy to use.

To support private live voting, VESTAr introduces a commitment-verified key reveal system. The public key is published onchain, while the private key remains offchain during the voting period. After voting ends, the backend automatically reveals the private key onchain through gasless execution, allowing anyone to decrypt and verify the final result. This design preserves temporary privacy during live voting while guaranteeing full transparency afterward.

All core voting logic runs onchain, while an indexer makes the data fast and user-friendly to query in the app. In the end, VESTAr creates a win-win ecosystem for voters, organizers, and advertisers by turning transparency into a scalable and sustainable business model. Our vision is simple: to make VESTAr the standard for K-pop voting, where transparency is no longer optional, but expected.

Architecture

Frame 2608638.png

VESTAr is built around a hybrid Web3 architecture that combines on-chain trust with a user-friendly application layer.

The frontend, built with React, provides both the main voting experience and a public verification portal.

Core voting logic lives in VESTAr election contracts on Status Network, which handle vote state, tallying, commitment-verified key reveal, karma-based sybil resistance, and paid voting settlement. Metadata and images are stored on IPFS, while a NestJS + PostgreSQL backend indexes contract events, synchronizes election state, and delivers indexed metadata to the app.