Kubera

Verifiable OnChain Credit Score providing criteria selection for Permissioned DeFi Protocols

  • 1,825 Raised
  • 218 Views
  • 1 Judges

Tags

  • DeFi
  • ZKP

Categories

  • Ora
  • Linea
  • Ten Protocol
  • Morpheus Labs
  • OpSec
  • ETHTaipei Community Finalist
  • Optimism
  • ThunderCore
  • Scroll
  • Zircuit

Gallery

Description

Project Description

Kubera - a verifiable on-chain credit score system. Kubera is specifically designed to tackle the criteria selection for permissioned DeFi protocols. These types of protocols require users to meet certain checkpoints to be eligible for whitelisting. Kubera provides a trust minimized solution for these protocols to verify if a user meets their required threshold.

Links

Github - https://github.com/Kubera-ETHTaipei

Presentation - https://pitch.com/v/kubera-snyix2

Demo Video - https://www.loom.com/share/ccb3125dc22e4e0fa0b45f6511ddf062?sid=87c86de9-8eda-4b67-ae58-4cd15d1cde46

Blog Post- https://happys1ngh.hashnode.dev/leveraging-opsecs-vps-to-deploy-a-node-server-up-and-running 

Problem it Solves

Permissioned Defi platforms require a trusted source of information about the users joining the problem. This poses a centralisation threat and many eligible users are unable to join the protocol and the Protocol also loses the potential consumer base.

Impact

Kubera provides a zk verifiable source of information about credit worthiness without revealing the sensitive information about the users themselves.

Integrations

  • Utilized ORA's ZKGraph CLE for Verifiable Indexing.
  • Used OpenSec VLS for hosting a node on the Backend and a Blog
  • Used Ten Protocol to deploy encrypted contracts.
  • Deployed on Scroll, Linea, Optimism, Thundercore, Zircuit and Sepolia.   

Challenges we Faced

  • We had to debug the zk-graph cle since we were experiencing verification errors , but it was later solved by the team by fixing a bugs in their codebase.
  • We tried implementing TLS Notary to include offchain credit score but the verification backend was not working from the tutorials of TLS Notary.
  • We tried implementing the halo-2 library to aggregate all the proofs instead of iterating over >60k blocks.
  • We tried implementing ZK email but it was not feasible since its hard to get credit scores in mail.

Deployed Contract Addresses     

SCROLL_ADD=0x6641126700308379cdb602b4e8dc1afc13d6c088

OPTIMISM_ADD=0xd9276777548d4b1e7b35b87d1ED9F8bA6FFcBfC6

THUNDERCORE_ADD=0xd9276777548d4b1e7b35b87d1ED9F8bA6FFcBfC6

LINEA_ADD=0xd9276777548d4b1e7b35b87d1ED9F8bA6FFcBfC6

ZIRCUIT_ADD= 0xd9276777548d4b1e7b35b87d1ED9F8bA6FFcBfC6

SEPOLIA = 0x6B394c412568cd628964709bbdBfe5FFa3d6Ba23                                                             

TEN PROTOCOL- 0x790823a2ba1D662E24E18737E21ccDefa025bBB0

Attachments