Skip to content

Latest commit

 

History

History
40 lines (24 loc) · 2.86 KB

README.md

File metadata and controls

40 lines (24 loc) · 2.86 KB
Raw

👋 Introduction

Overview

Verax is a shared, public attestation registry that can deployed to EVM chains. It can be used by dApps to store data that is of public interest, aka "attestations", that can be easily accessed and composed together by anyone that's interested. It is designed to be deployed as a single instance per network, so that all dApps on that network can issue their attestations to the same place, so that they can be easily discovered and consumed.

Attestations are usually statements made by an attestation issuer about something specific. They are also sometimes known as claims or credentials. Examples of attestations could include:

  • Owner of address 0xbabe1999… has completed a course on Solidity
  • Contract at address 0x666bea5f… is a malicious erc-20 token
  • Owner of address 0xd00daa… is a human being (i.e. not a bot)
  • Owner of address 0xdeadbeef… is a member of DimSumDAO
  • Attestation 0xa2345 is an (in)valid attestation
  • Attestation 0x98765 is a “like” for content stored at 0xa1b2c3d4…

How is Verax used?

For issuers of attestations:

If you are a dApp that offers credentials / attestations, you can choose to issue them to an existing Verax instance on a network. Issuing to Verax gives access to your attestations to any dApp that reads from Verax. Your attestation data becomes widely discoverable and easily consumed, as well as being easily composed with other attestations. Your attestations can start receiving attestations themselves, allowing you to add to your reputation as a trusted datasource.

For consumers of attestations:

Your dApp can now compose attestations from multiple sources, meaning you no longer have to choose between issuer A or issuer B. You can be sure that users of dApp can prove they are not a bot without being tied to a specific provider. You can start to discover what kind of users are interacting with your dApp, and start incentivizing them to onboard with your dApp through issuing attestations yourself!

For reputation protocols:

Start leveraging linked data and shared ontologies to easily create rich and powerful semantic graphs to provide your users with valuable insights and information. Cut down hours of development of scraping data from disparate heterogeneous sources and give your users fine-grained, nuanced and holistic reputation scores that have real meaning.

Dive in to the relevant section or go through the High Level Overview section to start learning more.

You can find out more information or contact any of the contributors on any of these channels: