The problem Quinty solves

Quinty solves the trust and payment issues commonly found in freelance, bounty, and funding platforms.

In traditional Web2 platforms, users must trust centralized intermediaries that:

• Charge high platform fees
• Control payouts and dispute resolution
• Store reputation off-chain and can modify or revoke it

This creates real risks:

• Creators may not get paid after completing work
• Solvers can be unfairly judged or face fraudulent tasks
• Reputation systems are opaque and easy to manipulate

Quinty makes collaboration safer and trustless by moving the entire workflow on-chain. People can use Quinty to:

• Create and fund bounties or grants with guaranteed escrowed payments
• Submit work transparently with verifiable on-chain actions
• Build permanent, non-transferable reputation through Soulbound NFTs
• Resolve disputes via community-based governance instead of centralized control

By using smart contracts, Quinty removes the need for intermediaries and ensures that payments, decisions, and reputation updates are transparent, verifiable, and immutable.

Challenges I ran into

One major challenge was coordinating state changes across multiple smart contracts — especially between the Bounty, Reputation, and NFT modules. Without careful design, this could lead to race conditions, duplicated updates, or inconsistent reputation states.

To solve this, we implemented an event-driven architecture. Each contract emits standardized events for key actions (submission, approval, payout, reputation minting), which the frontend listens to and processes in real time. This ensured consistent state synchronization without tightly coupling contracts.

Another challenge was protecting IPFS-based submission data while maintaining on-chain verification. Since IPFS data is publicly accessible, sensitive solution files could be exposed too early.

We addressed this by using blinded submissions combined with hash-based encryption, allowing submissions to be verified on-chain without revealing the actual content until the appropriate stage. This preserved privacy while keeping the process trustless.