LogoLogo
  • OpenRank
    • Ranking and Reputation
    • Use Cases
  • The Reputation Stack
    • Data
    • OpenRank Protocol
    • Apps and Clients
  • Integrations
    • Farcaster
      • Openrank Scores Onchain
      • Ranking Strategies on Farcaster
      • Global Profile Ranking
        • 🔵Top Profiles (based on Following)
        • 🔵Top Profiles (based on Engagement)
        • 🟢Profile Rank (based on Following)
        • 🟢Profile Rank (based on Engagement)
      • Channel User Rankings
        • 🔵Top Profiles in Channel
        • 🟢Profile Rank in Channel
      • Personalized Network
        • Direct Network
          • 🟢Get Direct Following
          • 🟢Get Direct Engagement
        • Extended Network
          • 🟢Personalized Following
          • 🟢Personalized Engagement
      • Frames
        • 🔵Top Frames
        • 🟢Personalized Recommended Frames
      • Feeds
        • For You Feed
          • 🔵For You
          • 🔵For You (by Authorship)
        • Channel Feed
          • 🔵Channel Trending Casts
      • Metadata
        • 🟢Get FIDs for Addresses
        • 🟢Get Handles For Addresses
        • 🟢Get Addresses for FIDs
        • 🟢Get Addresses for Handles
      • Ideas to Build using OpenRank APIs
      • Neynar x OpenRank Guides (WIP)
        • Build "For You" Feeds for your Client, using Neynar and OpenRank
        • Build "User Search" using Neynar and OpenRanks' Global Ranking API
        • Build "Suggested follow list" based on OpenRank and Neynar
        • Build Channel Trending Feeds for your Client using Neynar and OpenRank APIs
        • Build "Discover New Users Feed" using Neynar and OpenRanks Global Ranking API
        • Build Power Badges for your Client using Global & Personalized Ranking APIs by OpenRank
        • Build "Sort Replies" on a cast using Neynar and OpenRanks' Global Ranking API
    • Clanker OpenRank Scores
    • Lens Protocol
      • Ranking Strategies on Lens
      • Lens Profile APIs
      • Lens Content APIs
      • Lens Profile Insights
    • Metamask SPD
    • Onchain Graphs and Feeds
    • Upcoming Integrations
    • GitHub Developers & Repo Ranking
  • Reputation Algorithms
    • EigenTrust
    • Hubs and Authorities
    • Latent Semantic Analysis
  • OpenRank SDK
    • Introduction
    • Creating your first reputation graph
    • Publishing Rankings with OpenRank SDK
    • Guides
      • Tipping based User Rankings powered by OpenRank
    • Installation
    • SDK References
      • EigenTrust
        • Installation and Use
        • Examples for using EigenTrust
      • Hubs & Authorities
        • Installation and Use
        • Examples for using Hubs & Authorities (Coming soon)
      • Latent Semantic Analysis (Coming soon)
Powered by GitBook
LogoLogo

SOCIALS

  • Github
  • Farcaster

Copyright 2024

On this page
  1. OpenRank SDK
  2. SDK References

Hubs & Authorities

An alternative reputation algorithm for bipartite graphs

PreviousExamples for using EigenTrustNextInstallation and Use

Last updated 10 months ago

The OpenRank SDK—specifically, its EigenTrust algorithm—uses the notion of local trust, as a graph where one peer expresses its explicit or implied trust to another peer. This assumes that each node in the graph is an actor whose trust can be naturally defined.

In real-life scenarios, trusted entities are not necessarily actors. Other non-actor entities are also trusted, so they can appear in the local trust graph, where they can accept inbound local trust.

Hubs and Authorities (H&A) is a reputation algorithm for bipartite graphs, where edges connect two types of nodes, such as people and books. It defines a good book as one liked by good readers, and a good reader as one who likes good books.

The underlying math is very similar to using eugentrust and hubs and authority so we can reuse the same eigentrust function to also run Hubs and Authorities.

Key Participants:

  1. Hubs: Nodes that point to other nodes (e.g., readers who like books).

  2. Authorities: Nodes that contain useful information (e.g., books liked by readers).

Scores for hubs are based on their links to authorities, and scores for authorities are based on incoming links from hubs. Initially, all nodes have equal importance, with scores set to 1.

Scoring Process:

  1. Hubs' Scores: Derived from outgoing links to authorities.

  2. Authorities' Scores: Derived from incoming links from hubs.

  3. Normalization: Scores are normalized after each iteration to prevent them from becoming excessively large.

Adjacency Matrix: Represents connections between nodes, used to update scores iteratively until convergence.

Outcome: Determines good readers and good books, based on the principle that good books are read by many readers, and good readers read good books.

Limitations: H&A is susceptible to manipulation by sybil actors who can falsely inflate their scores by claiming to like good books. This requires further optimizations for scalable use.

For more information, refer .

There are 3 main flavors for Hubs and Authorities

  1. Fully Convergent Hubs & Authorities (HITS)

  2. Interest and Credit (Inspired by H&A and sybil resistant)

Simplified and Fully Convergent Hubs & Authorities algorithms are both prone to sybil.

Simplified Hubs & Authorities - .

here
explained in the next section