PublicAI - Cooking Food for AI
  • ๐Ÿš€Overview
  • ๐Ÿ“–The Three Layers of PublicAI
  • ๐Ÿ›๏ธPublicAI Data Hub
    • ๐Ÿง‘โ€๐Ÿ’ปSignup & Login
    • โ›“๏ธBinding for Points
    • ๐Ÿ“ธUploading Data Samples
    • โœ…Voting on Quality
  • ๐ŸนPublicAI Data Hunter
    • โฌ‡๏ธDownload & Connect Account
    • ๐Ÿ‘ทAI Tool for X
  • ๐Ÿ‘จโ€๐Ÿ‘จโ€๐Ÿ‘งโ€๐Ÿ‘งPublicAI Referrals
  • ๐Ÿช™How to Get Airdrop Rewards
  • ๐Ÿ’ฐ$PUBLIC - Tokenomics
    • Revenue Driven Token Issue
    • BFT Data Consensus Algorithm
    • $PUBLIC Token Utility
    • Contribution Rollup
  • โœ…Changelog
Powered by GitBook
On this page
  1. $PUBLIC - Tokenomics

BFT Data Consensus Algorithm

PreviousRevenue Driven Token IssueNext$PUBLIC Token Utility

Last updated 1 day ago

BFT data consensus algorithm is the key mechanism for PublicAI to guarantee the quality of data which consists of two phases:

AI Screening Phase

Once the uploader uploads the data to the platform, our corresponding AI agents will filter it as the first step to mitigate the cost of human verification. Those AI agents are various in terms of data.

Human Voting Phase

After the uploaded data is accepted by AI agents, it will enter the human verification phase. Consensus is the same number of votes in the same direction. Data sample quality is binary: if a data sample is partially good then it's considered overall flawed.

We have three roles in the protocol to verify: scouts, guards, and judges with three hyper-parameters for them respectively as consensus thresholds.

Take an example from the above graph, once a data sample is accepted by the data consensus algorithm there should be at least either 50 votes from scouts, 5 votes from guards, or 1 vote from a judge.

๐Ÿ’ฐ
BFT Data Consensus
Concensus Reach Scenarios