RepCheck Protocol
Trust Your Chain, Build Your Name Real-time streaming of your web3 contributions— stake PYUSD, boost your reputation and earn credibility from every DeFi action. Build your on-chain legacy today!
Demo
About
The problem it solves **RepCheck** is a Web3 reputation protocol deployed on **RepChain**, a custom **Avail-powered rollup**, that quantifies and rewards user engagement across DeFi protocols. Leveraging **Quicknode's Streams** technology, RepCheck captures granular protocol interactions in real-time, tracking **Uniswap swaps** and **Aave lending activities** (supply, borrow, repay) with millisecond precision. [Demo Link here](https://www.canva.com/design/DAGVBYOOMGc/7vq59HbiJJfpNSjYlZyZqg/watch?utm_content=DAGVBYOOMGc&utm_campaign=designshare&utm_medium=link&utm_source=editor) The protocol's architecture integrates **Quicknode Functions** for trustless on-chain execution with a unique **PYUSD staking** mechanism that acts as a reputation multiplier. When users stake PYUSD, they unlock **multipliers** that enhance their reputation accrual from DeFi interactions. This creates a composable reputation layer where both protocol engagement and capital commitment contribute to a user’s **on-chain credibility score**. RepCheck uses **Quicknode's serverless infrastructure** to process complex DeFi transaction data and trigger point attribution via automated function calls. Its modular design allows for seamless protocol integration, while maintaining atomic transaction guarantees on RepChain. All reputation points and multiplier calculations are stored **on-chain**, creating an immutable record of user activity that can be queried and verified by any external protocol. By leveraging **Avail's data availability layer**, RepCheck achieves horizontal scalability and low gas costs, creating an accessible reputation system that rewards active DeFi participants. The result is a transparent, game-theoretically sound mechanism for measuring and incentivizing protocol engagement across the DeFi ecosystem.
How it's made
Challenges we ran into - Avail integration was a bit trick - Quicknode function code debugging was a bit tiresome - Handling between different chains These were the difficulties but I'm happy to say we have overcome every one of them!