From fefaa24269216ba47dd037985986c3e850dfb1a1 Mon Sep 17 00:00:00 2001 From: Juampi Date: Thu, 5 Feb 2026 12:26:26 -0300 Subject: [PATCH 01/10] feat: update Builder Score to Builder Ranks across documentation - Update main Builder Score page to Builder Ranks framework - Change Builder Score Levels to Builder Rank Tiers with percentile-based system - Update tier names to match new ranking system (Novice, Apprentice, etc.) - Update API documentation to clarify /score endpoint returns ranking data - Update all protocol concept pages (Profile, Account, User, Event) - Update scoring systems index to reference Builder Ranks - Update sidebar category label from 'Builder Score' to 'Builder Ranks' - Maintain technical references to internal scoring while emphasizing user-facing ranks This change reflects the transition from a score-based system to a more intuitive rank-based system, making it easier for users to understand their position relative to other builders in the ecosystem. --- docs/get-started.mdx | 4 +- docs/protocol-concepts/account.mdx | 6 +- docs/protocol-concepts/event.mdx | 2 +- docs/protocol-concepts/profile.mdx | 2 +- .../builder-score/_category_.json | 2 +- .../builder-score/builder-score-levels.mdx | 61 ++++++----- .../scoring-systems/builder-score/index.mdx | 40 +++---- .../scoring-systems/creator-score.mdx | 102 +++--------------- .../scoring-systems/index.mdx | 16 +-- docs/protocol-concepts/user.mdx | 4 +- docs/talent-api/api-reference/index.mdx | 10 +- docs/talent-api/index.mdx | 2 +- 12 files changed, 86 insertions(+), 165 deletions(-) diff --git a/docs/get-started.mdx b/docs/get-started.mdx index 43c6f5c..3b2dc71 100644 --- a/docs/get-started.mdx +++ b/docs/get-started.mdx @@ -28,7 +28,7 @@ Use our API to add reputation-based context and authentication to your app, like 2. Explore our [API Reference](/docs/talent-api/api-reference) 3. Jump into specific guides: - [Authentication](/docs/talent-api/authentication) - - [Builder Score](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier) + - [Builder Ranks](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier) - [Credentials](/docs/talent-api/api-reference/get-the-score-and-the-credentials-using-wallet-scorer-slug-talent-id-or-account-identifier) ## Core Concepts @@ -42,7 +42,7 @@ Talent is built around the following core concepts to create a comprehensive rep - [**Account**](/docs/protocol-concepts/account): A connection to a third-party data source (wallet, GitHub, X, etc.) that provides reputation data. - [**Data Point**](/docs/protocol-concepts/data-point): A specific verified fact about a builder (GitHub stars, wallet transactions, etc.). - [**Events**](/docs/protocol-concepts/event): Historical records of reputation changes -- [**Score**](/docs/protocol-concepts/scoring-systems): A numerical measure of reputation calculated from Data Points using a specific Scoring System. +- [**Ranking Systems**](/docs/protocol-concepts/scoring-systems): A ranking system that evaluates reputation based on Data Points. Builder Ranks are our primary ranking system for identifying top builders. ## Support diff --git a/docs/protocol-concepts/account.mdx b/docs/protocol-concepts/account.mdx index cfc77bd..26366b2 100644 --- a/docs/protocol-concepts/account.mdx +++ b/docs/protocol-concepts/account.mdx @@ -8,7 +8,7 @@ An Account represents a connection with a third-party data provider. An **Account** represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. -A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and increase their [Builder Score](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** ## Key Attributes: @@ -16,8 +16,8 @@ A [**User**](/docs/protocol-concepts/user) represents an individual that signed - `talentprotocol.com/address/0xbd…23d4` - `talentprotocol.com/github/filmacedo` - If linked to a user, the account URL will automatically redirect to the user’s profile URL. Otherwise, it will show the data from that imported account independently. -- Once linked to a user, an account loses its independent profile and redirect to the user’s profile. The account also loses its [Builder Score](/docs/protocol-concepts/scoring-systems/builder-score), and its data feeds into the user’s aggregated reputation. -- Accounts display their own [Builder Score](/docs/protocol-concepts/scoring-systems/builder-score) unless linked to a user, at which point their data integrates into the user’s aggregated [Builder Score](/docs/protocol-concepts/scoring-systems/builder-score). +- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), and its data feeds into the user's aggregated reputation. +- Accounts display their own [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score). - Users can claim an imported account by verifying ownership (e.g., signing a wallet message, connecting GitHub). ## Types of Accounts: diff --git a/docs/protocol-concepts/event.mdx b/docs/protocol-concepts/event.mdx index ff89202..f49f702 100644 --- a/docs/protocol-concepts/event.mdx +++ b/docs/protocol-concepts/event.mdx @@ -6,7 +6,7 @@ sidebar_position: 5 An Event is a historical record of changes to a user’s reputation data over time. -Events track how reputation changes over time, giving users better insights into their progress. Think of it like Etherscan for the Builder Score: users will be able to see not just their current reputation state, but the complete history of how they got there. +Events track how reputation changes over time, giving users better insights into their progress. Think of it like Etherscan for Builder Ranks: users will be able to see not just their current reputation state, but the complete history of how they got there. Every change to reputation data is recorded as an Event with its old value, new value, and timestamp. diff --git a/docs/protocol-concepts/profile.mdx b/docs/protocol-concepts/profile.mdx index f07a8a7..49941df 100644 --- a/docs/protocol-concepts/profile.mdx +++ b/docs/protocol-concepts/profile.mdx @@ -42,7 +42,7 @@ The [API](/docs/talent-api/api-reference) provides advanced search capabilities - Identity information (names, ENS domains, usernames) - Connected accounts (GitHub, wallet addresses, etc.) - Human verification status -- Builder Score values and score credentials +- Builder Rank values and ranking credentials - Tags and interests See the [API Reference](/docs/talent-api/api-reference) for detailed examples of profile search queries. diff --git a/docs/protocol-concepts/scoring-systems/builder-score/_category_.json b/docs/protocol-concepts/scoring-systems/builder-score/_category_.json index dc23b72..9123c21 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/_category_.json +++ b/docs/protocol-concepts/scoring-systems/builder-score/_category_.json @@ -1,3 +1,3 @@ { - "label": "Builder Score" + "label": "Builder Ranks" } diff --git a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx b/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx index 5ef3700..8a38de8 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx +++ b/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx @@ -1,48 +1,47 @@ -# Builder Score Levels +# Builder Rank Tiers -Breakdown of the 6 Builder Score Levels and implementation guidelines for developers. +Understanding Builder Rank tiers and implementation guidelines for developers. -Builder Score Levels provide a structured way to understand and interpret Builder Score values in the Talent ecosystem. These levels help both developers integrating our API and individual builders track progress and set goals. +Builder Rank Tiers provide a structured way to understand and interpret Builder Ranks in the Talent ecosystem. These tiers help both developers integrating our API and individual builders track progress and set goals. -## Understanding Builder Score Levels +## Understanding Builder Rank Tiers -Builder Score is an uncapped scoring system that measures a builder's verified reputation data across multiple categories. To make these scores more intuitive and actionable, we've established six distinct levels that represent increasing degrees of building activity and impact. +Builder Ranks are a ranking system that measures a builder's verified reputation data across multiple categories. To make these rankings more intuitive and actionable, we've established distinct tiers based on percentile rankings that represent increasing degrees of building activity and impact. -Each level corresponds to a specific Builder Score range: +Each tier corresponds to a specific rank range: -| Level | Name | Score | Range | -| ----- | ------------ | ------- | ---------------------------------------------------------------------------------------------------------------------------- | -| 1 | Novice | 0-39 | Just getting started with the basics. They've connected some accounts and taken their first steps as a builder. | -| 2 | Apprentice | 40-79 | They're building sporadically and starting to make their mark. Their contributions are starting to get noticed. | -| 3 | Practitioner | 80-119 | They've established themselves as serious builders with real impact. Their work speaks for itself across multiple platforms. | -| 4 | Advanced | 120-169 | They've built some impressive things and contributed to notable projects. Their reputation is solid and growing. | -| 5 | Expert | 170-249 | They're among the top builders with an exceptional track record. People look to their work as an example. | -| 6 | Master | 250+ | They're one of the most accomplished builders in the ecosystem with contributions that have made a real difference. | +| Tier | Name | Rank Range | Description | +| ---- | ------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| 1 | Novice | Top 100,000 | Just getting started with the basics. They've connected some accounts and taken their first steps as a builder. | +| 2 | Apprentice | Top 50,000 | They're building sporadically and starting to make their mark. Their contributions are starting to get noticed. | +| 3 | Practitioner | Top 10,000 | They've established themselves as serious builders with real impact. Their work speaks for itself across multiple platforms. | +| 4 | Advanced | Top 5,000 | They've built some impressive things and contributed to notable projects. Their reputation is solid and growing. | +| 5 | Expert | Top 1,000 | They're among the top builders with an exceptional track record. People look to their work as an example. | +| 6 | Master | Top 100 | They're one of the most accomplished builders in the ecosystem with contributions that have made a real difference. | ## Use Cases -- **Base**: Offers discounted Basename registrations for builders at Level 3 (Practitioner) or higher -- **Hackathons:** Prioritizes hackathon applications from builders at Level 4 (Advanced) or higher -- **Communities**: Automatically approves membership for builders at Level 2 (Apprentice) or higher +- **Hackathons:** Prioritizes hackathon applications from builders ranked in the top 5,000 (Distinguished tier) or higher +- **Communities**: Automatically approves membership for builders ranked in the top 50,000 (Rising tier) or higher ## Implementation Guide -When integrating Builder Score into your app or protocol, you can use these levels to: +When integrating Builder Ranks into your app or protocol, you can use these tiers to: -- **Access Control**: Gate specific features or capabilities based on Builder Score Levels +- **Access Control**: Gate specific features or capabilities based on Builder Rank Tiers - **User Segmentation**: Create targeted experiences for different builder segments -- **Reward Distribution**: Allocate rewards or incentives proportionally to builder levels -- **Interface Design**: Visually represent levels with badges or other UI elements +- **Reward Distribution**: Allocate rewards or incentives proportionally to builder tiers +- **Interface Design**: Visually represent tiers with badges or other UI elements - **Governance Rights**: Allocate voting weight or proposal rights -- **Recommended Level Requirements:** +- **Recommended Tier Requirements:** -- General access and basic features: Level 1 (Novice) -- Premium features and moderate incentives: Level 3 (Practitioner) -- Exclusive access and significant incentives: Level 5 (Expert) +- General access and basic features: Tier 1 (Emerging - Top 100,000) +- Premium features and moderate incentives: Tier 3 (Established - Top 10,000) +- Exclusive access and significant incentives: Tier 5 (Elite - Top 1,000) -## Onchain Level Badges +## Onchain Tier Badges -Builders will be able to mint achievement badges for each Builder Score Level they reach. These badges: +Builders will be able to mint achievement badges for each Builder Rank Tier they reach. These badges: - Serve as permanent proof of achievement - Can be displayed on profiles across the web3 ecosystem @@ -51,7 +50,7 @@ Builders will be able to mint achievement badges for each Builder Score Level th ## Important Notes -- **Absolute Values**: Builder Score Levels are based on absolute score values, not percentile ranks. -- **Forward Evolution**: As our protocol adds more data points and users, the distribution of levels will naturally evolve. -- **Periodic Review**: We review and may adjust level ranges periodically to maintain meaningful separation between tiers. -- **Non-Decay**: Once you've minted a level badge, it remains in your collection even if your Builder Score temporarily decreases. +- **Percentile-Based**: Builder Rank Tiers are based on percentile rankings, meaning your position relative to other builders in the ecosystem. +- **Dynamic Rankings**: As more builders join the ecosystem and contribute, rankings will naturally shift. Maintaining your tier requires continued engagement and contributions. +- **Periodic Review**: We review and may adjust tier thresholds periodically to maintain meaningful separation between tiers as the ecosystem grows. +- **Badge Permanence**: Once you've minted a tier badge, it remains in your collection even if your Builder Rank temporarily changes. diff --git a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx b/docs/protocol-concepts/scoring-systems/builder-score/index.mdx index 0bb0961..6f4346d 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx +++ b/docs/protocol-concepts/scoring-systems/builder-score/index.mdx @@ -1,22 +1,22 @@ -# Builder Score +# Builder Ranks ============= -A scoring system to recognize real onchain builders. +A ranking system to recognize real onchain builders. -## What is the Builder Score? +## What are Builder Ranks? -Builder Score is a numerical value that represents a user's reputation as an onchain builder. +Builder Ranks are a ranking system that represents a user's reputation as an onchain builder based on verified activity and impact. -The Builder Score aims to distinguish builders from other types of crypto users, by valuing both the quantity and quality of their contributions. It reflects both "potential" (future growth) and "achievements" (proven track record). +Builder Ranks aim to distinguish builders from other types of crypto users, by valuing both the quantity and quality of their contributions. They reflect both "potential" (future growth) and "achievements" (proven track record). -Users can leverage their Builder Score within Talent's growing partner ecosystem, while developers can easily add the Builder Score to their apps. +Users can leverage their Builder Rank within Talent's growing partner ecosystem, while developers can easily add Builder Ranks to their apps. -Apps like [Basenames](https://x.com/TalentProtocol/status/1825995151275434439) or [Etherscan](https://x.com/TalentProtocol/status/1830974248363622607) already integrate with the Builder Score to bring more context to their users and to curate the best builders in crypto. +Apps like [Basenames](https://x.com/TalentProtocol/status/1825995151275434439) or [Etherscan](https://x.com/TalentProtocol/status/1830974248363622607) already integrate with Builder Ranks to bring more context to their users and to curate the best builders in crypto. -## The "Builder Score" Scoring Framework +## The "Builder Ranks" Framework -All Talent scoring systems are composed of a selection of [Data Points](/docs/protocol-concepts/data-point). While we don't disclose the exact formula to prevent gaming, we can share that each Data Point is evaluated based on: +All Talent ranking systems are composed of a selection of [Data Points](/docs/protocol-concepts/data-point). While we don't disclose the exact formula to prevent gaming, we can share that each Data Point is evaluated based on: 1. value conversion (when applicable) 2. signal strength @@ -25,12 +25,12 @@ All Talent scoring systems are composed of a selection of [Data Points](/docs/pr ### 1. Value Conversion -For some Data Points it's helpful to normalized their numerical value before applying the scoring function, but this is an optional step. +For some Data Points it's helpful to normalized their numerical value before applying the ranking algorithm, but this is an optional step. Examples: - Convert `twitter_account_age` from a `timestamp` to the `number of years` the account has. -- Normalize `base_out_transactions` with a `sqrt` function to reduce the impact of large values, making the scoring system more balanced and fair, and ensuring big contributors don’t completely overpower smaller ones. This means that your first contributions matter more than later ones. +- Normalize `base_out_transactions` with a `sqrt` function to reduce the impact of large values, making the ranking system more balanced and fair, and ensuring big contributors don't completely overpower smaller ones. This means that your first contributions matter more than later ones. - Invert `farcaster_social_capital_rank` value, so that the #1 ranked user has a higher value (and more points) than the last ranked user. ### 2. Signal Strength @@ -44,7 +44,7 @@ Examples: ### 3. Max Score -Defines the maximum amount of points each Data Point can contribute to the overall Builder Score. We use the signal strength to help define the max score of each Data Point: +Defines the maximum amount of points each Data Point can contribute to the overall ranking calculation. We use the signal strength to help define the max score of each Data Point: - strong (up to 40 points) - medium (up to 20 points) @@ -54,7 +54,7 @@ The mapping between signal strength and max score is just a framework for human ### 4. Multiplier -In the Builder Score, we use multipliers to convert the numerical value of a Data Point into a score measured in "points." These multipliers help standardize very different scales of Data Point values into a consistent scoring system. +In the Builder Rank algorithm, we use multipliers to convert the numerical value of a Data Point into a score measured in "points." These multipliers help standardize very different scales of Data Point values into a consistent scoring system that feeds into the final ranking. Although we don't disclose the exact multipliers used for each Data Point, users can understand the relative importance of each Data Point through the signal strength and max score values we provide. @@ -76,13 +76,13 @@ Although we don't disclose the exact multipliers used for each Data Point, users :::warning -Builder Score is still experimental, so expect regular updates to its scoring formula. +Builder Ranks are still experimental, so expect regular updates to the ranking algorithm. ::: ## Transparency and Formula Disclosure -At Talent, we believe in transparency while maintaining the integrity of our scoring system. We disclose the general framework of our Builder Score calculation, including: +At Talent, we believe in transparency while maintaining the integrity of our ranking system. We disclose the general framework of our Builder Rank calculation, including: - The Data Points we consider relevant - The signal strength classification for each Data Point @@ -94,16 +94,16 @@ However, to prevent gaming or artificial optimization of the system, we do not p - Exact conversion functions applied to normalize values - Detailed thresholds for achieving maximum scores -This approach allows us to maintain the integrity of the Builder Score while still providing users with clear guidance on how to improve their scores through genuine contributions. +This approach allows us to maintain the integrity of Builder Ranks while still providing users with clear guidance on how to improve their ranking through genuine contributions. ## Summary -The Builder Score represents 3 core decisions: +Builder Ranks represent 3 core decisions: 1. What Data Points are relevant to assess the reputation of a builder. 2. How strongly does each Data Point signal that the user is a real builder. -3. What should be the multiplier to convert each Data Point value into Builder Score points. +3. What should be the multiplier to convert each Data Point value into points for the ranking algorithm. -The final Builder Score is the sum of all the points. +The ranking algorithm calculates positions based on verified contributions across key data points. -Builder Score doesn’t have a maximum cap, so it’s likely to increase over time, as we add more integrations and possible credentials to the protocol. +Builder Ranks don't have a maximum cap, so rankings are likely to evolve over time as we add more integrations and possible credentials to the protocol. diff --git a/docs/protocol-concepts/scoring-systems/creator-score.mdx b/docs/protocol-concepts/scoring-systems/creator-score.mdx index 6889001..9a184e3 100644 --- a/docs/protocol-concepts/scoring-systems/creator-score.mdx +++ b/docs/protocol-concepts/scoring-systems/creator-score.mdx @@ -1,100 +1,22 @@ # Creator Score -A scoring system that identifies talent in content creation and creative contribution. +The Creator Score is a scoring system available through the Talent API that evaluates content creation activity and creative contributions. -## What is the Creator Score? +## Overview -Creator Score is a numerical value that represents a user's reputation as a content creator based on verified data across multiple platforms. Unlike traditional metrics that only consider follower count, Creator Score evaluates both quantity AND quality of creative output through verifiable signals. +Creator Score is one of several scoring systems available in the Talent Protocol ecosystem. It provides a numerical representation of a user's creative activity based on verified data from connected platforms and accounts. -The Creator Score is designed to: +The score takes into account various aspects of content creation, including: -- Help authentic creators gain recognition based on their actual contributions -- Provide protocols, brands, and platforms with reliable data to identify top creative talent -- Create a standardized measurement for creative impact and consistency -- Reward consistent, high-quality content creation over mere popularity +- **Creation activity**: Content publishing frequency and consistency +- **Engagement metrics**: Audience size and interaction across platforms +- **Economic signals**: Monetization and earnings from creative work -## Who is a Creator? +## Accessing Creator Score Data -While Builder Score focuses on software development, Creator Score targets those who share original content consistently. A creator is someone that produces creative output (text, image, video, audio, interactive) that provides value to others by informing, educating, entertaining, or inspiring. +Creator Score data is available through the Talent API: -The Creator Score supports various creator types: +- **[Advanced Search endpoint](/docs/talent-api/api-reference/search-for-profiles)**: Filter and search profiles with Creator Score data +- **[Score endpoint](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier)**: Retrieve specific scoring information for profiles -- **Visual Artists**: Illustrators, photographers, painters, graphic designers, animators -- **Writers**: Bloggers, journalists, essayists, poets, newsletter authors -- **Audio Creators**: Musicians, podcasters, sound designers, voice artists -- **Video Creators**: Filmmakers, vloggers, streamers, YouTube content producers -- **Community & Memes**: KOLs, meme artists, community builders - -## Use Cases - -Creator Score serves multiple purposes in the ecosystem: - -- **For creators**: Objective verification of creative impact that can be shared across platforms -- **For protocols**: Reliable method to identify authentic creators for rewards, grants, and partnerships -- **For brands**: Data-driven discovery of talent for collaborations and sponsorships -- **For apps**: Enhanced context about users' creative contributions and reputation - -## The "Creator Score" Scoring Framework - -The Creator Score uses the same technical framework as the [Builder Score](/docs/protocol-concepts/scoring-systems/builder-score) but with [data points](/docs/protocol-concepts/data-point) specifically relevant to creators. The final score is the sum of all data point scores with no maximum cap, and each data point is evaluated based on: signal strength, max score, multiplier (not publicly disclosed), value conversion (optional). - -### **Signal Strength** - -- The first step is defining how strongly a given data point signals someone is a real creator -- There's 3 possible levels: - - **Strong**: Up to 40 points (e.g., zora rewards earned) - - **Medium**: Up to 20 points (e.g., farcaster followers) - - **Weak**: Up to 8 points (e.g., twitter account age) - -### **Max Score** - -- Maximum amount of points each data point can contribute to the Creator Score, based on the signal strength - -### **Multiplier** - -- Each data point has a multiplier to convert its readable value into points -- The multiplier is not publicly disclosed to prevent gaming (same approach as Builder Score) -- Example: for twitter followers, if the multiplier is 0.01 and I have 1,000 followers, I will receive 10 points - -### **Value Conversion** - -- Some data point original values are converted to normalized metrics. -- Example: We us a square root function for metrics like total followers or NFT earnings to prevent large creators from completely dominating - -## Creator Score Levels - -Similar to Builder Score, Creator Score is organized into levels to help users understand their standing: - -| Level | Score Range | Description | -| ----- | ----------- | -------------------------------------------------------------------------------------- | -| 1 | 0-39 | Just getting started. Has created some content and taken first steps as a creator. | -| 2 | 40-79 | Creating content regularly with growing engagement. Beginning to build an audience. | -| 3 | 80-119 | Established creator with consistent output and meaningful engagement across platforms. | -| 4 | 120-169 | Accomplished creator with significant audience and proven monetization. | -| 5 | 170-249 | Top-tier creator with substantial influence and recognition in their domain. | -| 6 | 250+ | Elite creator with exceptional impact, audience, and earnings. | - -## Key Metrics - -The Creator Score considers various metrics organized into three categories: - -### 1. Creation Metrics - -- Content Published - total number of content pieces published -- Content Frequency - number of unique pieces published per week/month -- Publishing Streak - consecutive weeks/months with published content -- Creative Longevity - time since first published content - -### 2. Engagement Metrics - -- Followers and subscriber counts across platforms -- Follower-to-following ratio -- Engagement rates and interactions with content - -### 3. Economic Metrics - -- Total earnings and rewards -- Unique holders/collectors/paid subscribers -- NFT mints, coin purchases or price -- Secondary market activity (NFT/coin trading) -- Collector loyalty/repeat engagement +For more information about the Talent API and how to access scoring data, see the [API Reference](/docs/talent-api/api-reference). diff --git a/docs/protocol-concepts/scoring-systems/index.mdx b/docs/protocol-concepts/scoring-systems/index.mdx index fb38b5d..7d27b12 100644 --- a/docs/protocol-concepts/scoring-systems/index.mdx +++ b/docs/protocol-concepts/scoring-systems/index.mdx @@ -6,19 +6,19 @@ A Scoring System assigns numerical scores (measured in "points") to a selection Talent intentionally separates Data Points (objective data) from Scoring Systems (subjective data). Both are autonomous and composable protocol primitives. -## Different Scores +## Different Ranking Systems -Multiple scoring systems can exist in parallel, with each designed to evaluate talent in a specific domain: +Multiple ranking systems can exist in parallel, with each designed to evaluate talent in a specific domain: -- [Builder Score](/docs/protocol-concepts/scoring-systems/builder-score) identifies people creating software +- [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score) identifies and ranks people creating software - [Creator Score](/docs/protocol-concepts/scoring-systems/creator-score) recognizes content and community builders -- Other scores coming soon +- Other ranking systems coming soon -Each scoring system operates independently with its own set of relevant Data Points and scoring logic, tailored to what matters for their specific persona. +Each ranking system operates independently with its own set of relevant Data Points and scoring logic, tailored to what matters for their specific persona. This modular approach allows Talent to serve different communities with metrics that genuinely reflect their unique contributions, rather than forcing diverse talents into the same box. -Reach out if you want to create a custom scoring system. +Reach out if you want to create a custom ranking system. ## Scoring Framework @@ -55,10 +55,10 @@ A Score Credential is the connection between a [Data Point](/docs/protocol-conce For the Data Point "GitHub Stars": -- In the Builder Score system, this might be worth up to 15 points (strong signal) +- In the Builder Ranks system, this might be worth up to 15 points (strong signal) - In the Creator Score system, this might be worth only 2 points (weak signal) Similarly, for the Data Point "Zora Earnings": - In the Creator Score system, this might be worth up to 30 points (strong signal) -- In the Builder Score system, this might be worth only 5 points (weak signal) +- In the Builder Ranks system, this might be worth only 5 points (weak signal) diff --git a/docs/protocol-concepts/user.mdx b/docs/protocol-concepts/user.mdx index b27766a..efc165a 100644 --- a/docs/protocol-concepts/user.mdx +++ b/docs/protocol-concepts/user.mdx @@ -6,7 +6,7 @@ sidebar_position: 1 A User represents an individual that signed up on talentprotocol.com -A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and increase their [Builder Score](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** An [**Account**](/docs/protocol-concepts/account) represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. @@ -16,7 +16,7 @@ An [**Account**](/docs/protocol-concepts/account) represents a connection with a - Users have a single profile URL aggregating data from all associated accounts. - `talentprotocol.com/UUID` - A user can connect multiple [accounts](/docs/protocol-concepts/account), but an account can only be linked to one user at a time. -- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Score](/docs/protocol-concepts/scoring-systems/builder-score). +- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score). - A user is able to sign-in to the Talent App with any account that they connected. - For now, only the Talent app can create, update or delete users from the database. Ecosystem apps can only read data. diff --git a/docs/talent-api/api-reference/index.mdx b/docs/talent-api/api-reference/index.mdx index 2f6bfd8..488e1a2 100644 --- a/docs/talent-api/api-reference/index.mdx +++ b/docs/talent-api/api-reference/index.mdx @@ -6,9 +6,9 @@ The Talent API provides comprehensive access to verified builder reputation data ## Key Improvements -- **Advanced Search**: Filter profiles by multiple criteria including tags, scores, and human verification status +- **Advanced Search**: Filter profiles by multiple criteria including tags, ranks, and human verification status - **Profile-Centric Design**: Streamlined endpoints organized around Profiles as the central entity -- **Multiple Scoring Systems**: Support for Builder Score and other upcoming scores +- **Multiple Ranking Systems**: Support for Builder Ranks and other upcoming ranking systems - **Consistent Responses**: Standardized response formats across all endpoints - **Improved Pagination**: Options for both page-based and cursor-based pagination @@ -22,9 +22,9 @@ Base URL: `https://api.talentprotocol.com/` - [**Profile Search**](/docs/talent-api/api-reference/search-for-profiles): `/search/advanced/profiles` - Find profiles matching specific criteria - [**Profile Data**](/docs/talent-api/api-reference/get-a-profile-using-wallet-talent-id-or-account-identifier): `/profile` - Get profile information by ID or account identifier -- [**Score Data**](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier): `/score` - Get Builder Score and other scoring information -- [**Farcaster Scores**](/docs/talent-api/api-reference/get-the-score-of-farcaster-accounts): `/farcaster/scores` - Get the Builder Score of Farcaster users -- [**Credentials Data**](/docs/talent-api/api-reference/get-the-score-and-the-credentials-using-wallet-scorer-slug-talent-id-or-account-identifier): `/credentials` - Get the points each data point contributed to the Builder Score +- [**Score Data**](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier): `/score` - Get Builder Rank and other ranking information (endpoint returns ranking data including rank position) +- [**Farcaster Scores**](/docs/talent-api/api-reference/get-the-score-of-farcaster-accounts): `/farcaster/scores` - Get the Builder Rank of Farcaster users +- [**Credentials Data**](/docs/talent-api/api-reference/get-the-score-and-the-credentials-using-wallet-scorer-slug-talent-id-or-account-identifier): `/credentials` - Get the points each data point contributed to the ranking calculation - [**Data Points**](https://talent.app/~/data): `/data_points` - Get the data points providing a list of slugs and for a Talent profile - [**Account Data**](/docs/talent-api/api-reference/get-account-using-wallet-talent-id-or-account-identifier): `/accounts` - Get connected accounts information - [**Social Data**](/docs/talent-api/api-reference/get-socials-using-wallet-talent-id-or-account-identifier): `/socials` - Get connected social media information diff --git a/docs/talent-api/index.mdx b/docs/talent-api/index.mdx index 7485d83..3028469 100644 --- a/docs/talent-api/index.mdx +++ b/docs/talent-api/index.mdx @@ -6,5 +6,5 @@ slug: /talent-api # Talent API -Our API provides Builder Scores, identity verification, and hundreds of other [data points](https://talent.app/~/data) +Our API provides Builder Ranks, identity verification, and hundreds of other [data points](https://talent.app/~/data) through simple, reliable endpoints. From ee56c8eff822bf184a40c132f1873efe0fb67212 Mon Sep 17 00:00:00 2001 From: Juampi Date: Thu, 5 Feb 2026 16:24:48 -0300 Subject: [PATCH 02/10] fix: change singular 'Builder Rank' to plural 'Builder Ranks' for consistency --- docs/protocol-concepts/account.mdx | 6 +++--- docs/protocol-concepts/profile.mdx | 2 +- .../builder-score/builder-score-levels.mdx | 16 ++++++++-------- .../scoring-systems/builder-score/index.mdx | 6 +++--- docs/protocol-concepts/user.mdx | 4 ++-- docs/talent-api/api-reference/index.mdx | 4 ++-- 6 files changed, 19 insertions(+), 19 deletions(-) diff --git a/docs/protocol-concepts/account.mdx b/docs/protocol-concepts/account.mdx index 26366b2..5b94e76 100644 --- a/docs/protocol-concepts/account.mdx +++ b/docs/protocol-concepts/account.mdx @@ -8,7 +8,7 @@ An Account represents a connection with a third-party data provider. An **Account** represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. -A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** ## Key Attributes: @@ -16,8 +16,8 @@ A [**User**](/docs/protocol-concepts/user) represents an individual that signed - `talentprotocol.com/address/0xbd…23d4` - `talentprotocol.com/github/filmacedo` - If linked to a user, the account URL will automatically redirect to the user’s profile URL. Otherwise, it will show the data from that imported account independently. -- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), and its data feeds into the user's aggregated reputation. -- Accounts display their own [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score). +- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score), and its data feeds into the user's aggregated reputation. +- Accounts display their own [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score). - Users can claim an imported account by verifying ownership (e.g., signing a wallet message, connecting GitHub). ## Types of Accounts: diff --git a/docs/protocol-concepts/profile.mdx b/docs/protocol-concepts/profile.mdx index 49941df..f7df22b 100644 --- a/docs/protocol-concepts/profile.mdx +++ b/docs/protocol-concepts/profile.mdx @@ -42,7 +42,7 @@ The [API](/docs/talent-api/api-reference) provides advanced search capabilities - Identity information (names, ENS domains, usernames) - Connected accounts (GitHub, wallet addresses, etc.) - Human verification status -- Builder Rank values and ranking credentials +- Builder Ranks values and ranking credentials - Tags and interests See the [API Reference](/docs/talent-api/api-reference) for detailed examples of profile search queries. diff --git a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx b/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx index 8a38de8..0c1c863 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx +++ b/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx @@ -1,10 +1,10 @@ -# Builder Rank Tiers +# Builder Ranks Tiers -Understanding Builder Rank tiers and implementation guidelines for developers. +Understanding Builder Ranks tiers and implementation guidelines for developers. -Builder Rank Tiers provide a structured way to understand and interpret Builder Ranks in the Talent ecosystem. These tiers help both developers integrating our API and individual builders track progress and set goals. +Builder Ranks Tiers provide a structured way to understand and interpret Builder Ranks in the Talent ecosystem. These tiers help both developers integrating our API and individual builders track progress and set goals. -## Understanding Builder Rank Tiers +## Understanding Builder Ranks Tiers Builder Ranks are a ranking system that measures a builder's verified reputation data across multiple categories. To make these rankings more intuitive and actionable, we've established distinct tiers based on percentile rankings that represent increasing degrees of building activity and impact. @@ -28,7 +28,7 @@ Each tier corresponds to a specific rank range: When integrating Builder Ranks into your app or protocol, you can use these tiers to: -- **Access Control**: Gate specific features or capabilities based on Builder Rank Tiers +- **Access Control**: Gate specific features or capabilities based on Builder Ranks Tiers - **User Segmentation**: Create targeted experiences for different builder segments - **Reward Distribution**: Allocate rewards or incentives proportionally to builder tiers - **Interface Design**: Visually represent tiers with badges or other UI elements @@ -41,7 +41,7 @@ When integrating Builder Ranks into your app or protocol, you can use these tier ## Onchain Tier Badges -Builders will be able to mint achievement badges for each Builder Rank Tier they reach. These badges: +Builders will be able to mint achievement badges for each Builder Ranks Tier they reach. These badges: - Serve as permanent proof of achievement - Can be displayed on profiles across the web3 ecosystem @@ -50,7 +50,7 @@ Builders will be able to mint achievement badges for each Builder Rank Tier they ## Important Notes -- **Percentile-Based**: Builder Rank Tiers are based on percentile rankings, meaning your position relative to other builders in the ecosystem. +- **Percentile-Based**: Builder Ranks Tiers are based on percentile rankings, meaning your position relative to other builders in the ecosystem. - **Dynamic Rankings**: As more builders join the ecosystem and contribute, rankings will naturally shift. Maintaining your tier requires continued engagement and contributions. - **Periodic Review**: We review and may adjust tier thresholds periodically to maintain meaningful separation between tiers as the ecosystem grows. -- **Badge Permanence**: Once you've minted a tier badge, it remains in your collection even if your Builder Rank temporarily changes. +- **Badge Permanence**: Once you've minted a tier badge, it remains in your collection even if your Builder Ranks temporarily changes. diff --git a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx b/docs/protocol-concepts/scoring-systems/builder-score/index.mdx index 6f4346d..c494bc8 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx +++ b/docs/protocol-concepts/scoring-systems/builder-score/index.mdx @@ -10,7 +10,7 @@ Builder Ranks are a ranking system that represents a user's reputation as an onc Builder Ranks aim to distinguish builders from other types of crypto users, by valuing both the quantity and quality of their contributions. They reflect both "potential" (future growth) and "achievements" (proven track record). -Users can leverage their Builder Rank within Talent's growing partner ecosystem, while developers can easily add Builder Ranks to their apps. +Users can leverage their Builder Ranks within Talent's growing partner ecosystem, while developers can easily add Builder Ranks to their apps. Apps like [Basenames](https://x.com/TalentProtocol/status/1825995151275434439) or [Etherscan](https://x.com/TalentProtocol/status/1830974248363622607) already integrate with Builder Ranks to bring more context to their users and to curate the best builders in crypto. @@ -54,7 +54,7 @@ The mapping between signal strength and max score is just a framework for human ### 4. Multiplier -In the Builder Rank algorithm, we use multipliers to convert the numerical value of a Data Point into a score measured in "points." These multipliers help standardize very different scales of Data Point values into a consistent scoring system that feeds into the final ranking. +In the Builder Ranks algorithm, we use multipliers to convert the numerical value of a Data Point into a score measured in "points." These multipliers help standardize very different scales of Data Point values into a consistent scoring system that feeds into the final ranking. Although we don't disclose the exact multipliers used for each Data Point, users can understand the relative importance of each Data Point through the signal strength and max score values we provide. @@ -82,7 +82,7 @@ Builder Ranks are still experimental, so expect regular updates to the ranking a ## Transparency and Formula Disclosure -At Talent, we believe in transparency while maintaining the integrity of our ranking system. We disclose the general framework of our Builder Rank calculation, including: +At Talent, we believe in transparency while maintaining the integrity of our ranking system. We disclose the general framework of our Builder Ranks calculation, including: - The Data Points we consider relevant - The signal strength classification for each Data Point diff --git a/docs/protocol-concepts/user.mdx b/docs/protocol-concepts/user.mdx index efc165a..29661b3 100644 --- a/docs/protocol-concepts/user.mdx +++ b/docs/protocol-concepts/user.mdx @@ -6,7 +6,7 @@ sidebar_position: 1 A User represents an individual that signed up on talentprotocol.com -A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** An [**Account**](/docs/protocol-concepts/account) represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. @@ -16,7 +16,7 @@ An [**Account**](/docs/protocol-concepts/account) represents a connection with a - Users have a single profile URL aggregating data from all associated accounts. - `talentprotocol.com/UUID` - A user can connect multiple [accounts](/docs/protocol-concepts/account), but an account can only be linked to one user at a time. -- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score). +- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score). - A user is able to sign-in to the Talent App with any account that they connected. - For now, only the Talent app can create, update or delete users from the database. Ecosystem apps can only read data. diff --git a/docs/talent-api/api-reference/index.mdx b/docs/talent-api/api-reference/index.mdx index 488e1a2..c9bec21 100644 --- a/docs/talent-api/api-reference/index.mdx +++ b/docs/talent-api/api-reference/index.mdx @@ -22,8 +22,8 @@ Base URL: `https://api.talentprotocol.com/` - [**Profile Search**](/docs/talent-api/api-reference/search-for-profiles): `/search/advanced/profiles` - Find profiles matching specific criteria - [**Profile Data**](/docs/talent-api/api-reference/get-a-profile-using-wallet-talent-id-or-account-identifier): `/profile` - Get profile information by ID or account identifier -- [**Score Data**](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier): `/score` - Get Builder Rank and other ranking information (endpoint returns ranking data including rank position) -- [**Farcaster Scores**](/docs/talent-api/api-reference/get-the-score-of-farcaster-accounts): `/farcaster/scores` - Get the Builder Rank of Farcaster users +- [**Score Data**](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier): `/score` - Get Builder Ranks and other ranking information (endpoint returns ranking data including rank position) +- [**Farcaster Scores**](/docs/talent-api/api-reference/get-the-score-of-farcaster-accounts): `/farcaster/scores` - Get the Builder Ranks of Farcaster users - [**Credentials Data**](/docs/talent-api/api-reference/get-the-score-and-the-credentials-using-wallet-scorer-slug-talent-id-or-account-identifier): `/credentials` - Get the points each data point contributed to the ranking calculation - [**Data Points**](https://talent.app/~/data): `/data_points` - Get the data points providing a list of slugs and for a Talent profile - [**Account Data**](/docs/talent-api/api-reference/get-account-using-wallet-talent-id-or-account-identifier): `/accounts` - Get connected accounts information From 5e992551af2009a1b49a7bb9fb4a8e2a4d73a175 Mon Sep 17 00:00:00 2001 From: Juampi Date: Sun, 8 Feb 2026 11:44:47 -0300 Subject: [PATCH 03/10] fix: change plural 'Builder Ranks' back to singular 'Builder Rank' throughout documentation --- docs/get-started.mdx | 4 +-- docs/protocol-concepts/account.mdx | 6 ++--- docs/protocol-concepts/event.mdx | 2 +- docs/protocol-concepts/profile.mdx | 2 +- .../builder-score/_category_.json | 2 +- .../builder-score/builder-score-levels.mdx | 20 +++++++------- .../scoring-systems/builder-score/index.mdx | 26 +++++++++---------- .../scoring-systems/index.mdx | 6 ++--- docs/protocol-concepts/user.mdx | 4 +-- docs/talent-api/api-reference/index.mdx | 6 ++--- docs/talent-api/index.mdx | 2 +- 11 files changed, 40 insertions(+), 40 deletions(-) diff --git a/docs/get-started.mdx b/docs/get-started.mdx index 3b2dc71..f694573 100644 --- a/docs/get-started.mdx +++ b/docs/get-started.mdx @@ -28,7 +28,7 @@ Use our API to add reputation-based context and authentication to your app, like 2. Explore our [API Reference](/docs/talent-api/api-reference) 3. Jump into specific guides: - [Authentication](/docs/talent-api/authentication) - - [Builder Ranks](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier) + - [Builder Rank](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier) - [Credentials](/docs/talent-api/api-reference/get-the-score-and-the-credentials-using-wallet-scorer-slug-talent-id-or-account-identifier) ## Core Concepts @@ -42,7 +42,7 @@ Talent is built around the following core concepts to create a comprehensive rep - [**Account**](/docs/protocol-concepts/account): A connection to a third-party data source (wallet, GitHub, X, etc.) that provides reputation data. - [**Data Point**](/docs/protocol-concepts/data-point): A specific verified fact about a builder (GitHub stars, wallet transactions, etc.). - [**Events**](/docs/protocol-concepts/event): Historical records of reputation changes -- [**Ranking Systems**](/docs/protocol-concepts/scoring-systems): A ranking system that evaluates reputation based on Data Points. Builder Ranks are our primary ranking system for identifying top builders. +- [**Ranking Systems**](/docs/protocol-concepts/scoring-systems): A ranking system that evaluates reputation based on Data Points. Builder Rank is our primary ranking system for identifying top builders. ## Support diff --git a/docs/protocol-concepts/account.mdx b/docs/protocol-concepts/account.mdx index 5b94e76..26366b2 100644 --- a/docs/protocol-concepts/account.mdx +++ b/docs/protocol-concepts/account.mdx @@ -8,7 +8,7 @@ An Account represents a connection with a third-party data provider. An **Account** represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. -A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** ## Key Attributes: @@ -16,8 +16,8 @@ A [**User**](/docs/protocol-concepts/user) represents an individual that signed - `talentprotocol.com/address/0xbd…23d4` - `talentprotocol.com/github/filmacedo` - If linked to a user, the account URL will automatically redirect to the user’s profile URL. Otherwise, it will show the data from that imported account independently. -- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score), and its data feeds into the user's aggregated reputation. -- Accounts display their own [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score). +- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), and its data feeds into the user's aggregated reputation. +- Accounts display their own [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score). - Users can claim an imported account by verifying ownership (e.g., signing a wallet message, connecting GitHub). ## Types of Accounts: diff --git a/docs/protocol-concepts/event.mdx b/docs/protocol-concepts/event.mdx index f49f702..14045b9 100644 --- a/docs/protocol-concepts/event.mdx +++ b/docs/protocol-concepts/event.mdx @@ -6,7 +6,7 @@ sidebar_position: 5 An Event is a historical record of changes to a user’s reputation data over time. -Events track how reputation changes over time, giving users better insights into their progress. Think of it like Etherscan for Builder Ranks: users will be able to see not just their current reputation state, but the complete history of how they got there. +Events track how reputation changes over time, giving users better insights into their progress. Think of it like Etherscan for Builder Rank: users will be able to see not just their current reputation state, but the complete history of how they got there. Every change to reputation data is recorded as an Event with its old value, new value, and timestamp. diff --git a/docs/protocol-concepts/profile.mdx b/docs/protocol-concepts/profile.mdx index f7df22b..49941df 100644 --- a/docs/protocol-concepts/profile.mdx +++ b/docs/protocol-concepts/profile.mdx @@ -42,7 +42,7 @@ The [API](/docs/talent-api/api-reference) provides advanced search capabilities - Identity information (names, ENS domains, usernames) - Connected accounts (GitHub, wallet addresses, etc.) - Human verification status -- Builder Ranks values and ranking credentials +- Builder Rank values and ranking credentials - Tags and interests See the [API Reference](/docs/talent-api/api-reference) for detailed examples of profile search queries. diff --git a/docs/protocol-concepts/scoring-systems/builder-score/_category_.json b/docs/protocol-concepts/scoring-systems/builder-score/_category_.json index 9123c21..3a8d94c 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/_category_.json +++ b/docs/protocol-concepts/scoring-systems/builder-score/_category_.json @@ -1,3 +1,3 @@ { - "label": "Builder Ranks" + "label": "Builder Rank" } diff --git a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx b/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx index 0c1c863..af479fe 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx +++ b/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx @@ -1,12 +1,12 @@ -# Builder Ranks Tiers +# Builder Rank Tiers -Understanding Builder Ranks tiers and implementation guidelines for developers. +Understanding Builder Rank tiers and implementation guidelines for developers. -Builder Ranks Tiers provide a structured way to understand and interpret Builder Ranks in the Talent ecosystem. These tiers help both developers integrating our API and individual builders track progress and set goals. +Builder Rank Tiers provide a structured way to understand and interpret Builder Rank in the Talent ecosystem. These tiers help both developers integrating our API and individual builders track progress and set goals. -## Understanding Builder Ranks Tiers +## Understanding Builder Rank Tiers -Builder Ranks are a ranking system that measures a builder's verified reputation data across multiple categories. To make these rankings more intuitive and actionable, we've established distinct tiers based on percentile rankings that represent increasing degrees of building activity and impact. +Builder Rank is a ranking system that measures a builder's verified reputation data across multiple categories. To make these rankings more intuitive and actionable, we've established distinct tiers based on percentile rankings that represent increasing degrees of building activity and impact. Each tier corresponds to a specific rank range: @@ -26,9 +26,9 @@ Each tier corresponds to a specific rank range: ## Implementation Guide -When integrating Builder Ranks into your app or protocol, you can use these tiers to: +When integrating Builder Rank into your app or protocol, you can use these tiers to: -- **Access Control**: Gate specific features or capabilities based on Builder Ranks Tiers +- **Access Control**: Gate specific features or capabilities based on Builder Rank Tiers - **User Segmentation**: Create targeted experiences for different builder segments - **Reward Distribution**: Allocate rewards or incentives proportionally to builder tiers - **Interface Design**: Visually represent tiers with badges or other UI elements @@ -41,7 +41,7 @@ When integrating Builder Ranks into your app or protocol, you can use these tier ## Onchain Tier Badges -Builders will be able to mint achievement badges for each Builder Ranks Tier they reach. These badges: +Builders will be able to mint achievement badges for each Builder Rank Tier they reach. These badges: - Serve as permanent proof of achievement - Can be displayed on profiles across the web3 ecosystem @@ -50,7 +50,7 @@ Builders will be able to mint achievement badges for each Builder Ranks Tier the ## Important Notes -- **Percentile-Based**: Builder Ranks Tiers are based on percentile rankings, meaning your position relative to other builders in the ecosystem. +- **Percentile-Based**: Builder Rank Tiers are based on percentile rankings, meaning your position relative to other builders in the ecosystem. - **Dynamic Rankings**: As more builders join the ecosystem and contribute, rankings will naturally shift. Maintaining your tier requires continued engagement and contributions. - **Periodic Review**: We review and may adjust tier thresholds periodically to maintain meaningful separation between tiers as the ecosystem grows. -- **Badge Permanence**: Once you've minted a tier badge, it remains in your collection even if your Builder Ranks temporarily changes. +- **Badge Permanence**: Once you've minted a tier badge, it remains in your collection even if your Builder Rank temporarily changes. diff --git a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx b/docs/protocol-concepts/scoring-systems/builder-score/index.mdx index c494bc8..bdc6d71 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx +++ b/docs/protocol-concepts/scoring-systems/builder-score/index.mdx @@ -1,20 +1,20 @@ -# Builder Ranks +# Builder Rank ============= A ranking system to recognize real onchain builders. -## What are Builder Ranks? +## What is Builder Rank? -Builder Ranks are a ranking system that represents a user's reputation as an onchain builder based on verified activity and impact. +Builder Rank is a ranking system that represents a user's reputation as an onchain builder based on verified activity and impact. -Builder Ranks aim to distinguish builders from other types of crypto users, by valuing both the quantity and quality of their contributions. They reflect both "potential" (future growth) and "achievements" (proven track record). +Builder Rank aims to distinguish builders from other types of crypto users, by valuing both the quantity and quality of their contributions. It reflects both "potential" (future growth) and "achievements" (proven track record). -Users can leverage their Builder Ranks within Talent's growing partner ecosystem, while developers can easily add Builder Ranks to their apps. +Users can leverage their Builder Rank within Talent's growing partner ecosystem, while developers can easily add Builder Rank to their apps. -Apps like [Basenames](https://x.com/TalentProtocol/status/1825995151275434439) or [Etherscan](https://x.com/TalentProtocol/status/1830974248363622607) already integrate with Builder Ranks to bring more context to their users and to curate the best builders in crypto. +Apps like [Basenames](https://x.com/TalentProtocol/status/1825995151275434439) or [Etherscan](https://x.com/TalentProtocol/status/1830974248363622607) already integrate with Builder Rank to bring more context to their users and to curate the best builders in crypto. -## The "Builder Ranks" Framework +## The "Builder Rank" Framework All Talent ranking systems are composed of a selection of [Data Points](/docs/protocol-concepts/data-point). While we don't disclose the exact formula to prevent gaming, we can share that each Data Point is evaluated based on: @@ -54,7 +54,7 @@ The mapping between signal strength and max score is just a framework for human ### 4. Multiplier -In the Builder Ranks algorithm, we use multipliers to convert the numerical value of a Data Point into a score measured in "points." These multipliers help standardize very different scales of Data Point values into a consistent scoring system that feeds into the final ranking. +In the Builder Rank algorithm, we use multipliers to convert the numerical value of a Data Point into a score measured in "points." These multipliers help standardize very different scales of Data Point values into a consistent scoring system that feeds into the final ranking. Although we don't disclose the exact multipliers used for each Data Point, users can understand the relative importance of each Data Point through the signal strength and max score values we provide. @@ -76,13 +76,13 @@ Although we don't disclose the exact multipliers used for each Data Point, users :::warning -Builder Ranks are still experimental, so expect regular updates to the ranking algorithm. +Builder Rank is still experimental, so expect regular updates to the ranking algorithm. ::: ## Transparency and Formula Disclosure -At Talent, we believe in transparency while maintaining the integrity of our ranking system. We disclose the general framework of our Builder Ranks calculation, including: +At Talent, we believe in transparency while maintaining the integrity of our ranking system. We disclose the general framework of our Builder Rank calculation, including: - The Data Points we consider relevant - The signal strength classification for each Data Point @@ -94,11 +94,11 @@ However, to prevent gaming or artificial optimization of the system, we do not p - Exact conversion functions applied to normalize values - Detailed thresholds for achieving maximum scores -This approach allows us to maintain the integrity of Builder Ranks while still providing users with clear guidance on how to improve their ranking through genuine contributions. +This approach allows us to maintain the integrity of Builder Rank while still providing users with clear guidance on how to improve their ranking through genuine contributions. ## Summary -Builder Ranks represent 3 core decisions: +Builder Rank represents 3 core decisions: 1. What Data Points are relevant to assess the reputation of a builder. 2. How strongly does each Data Point signal that the user is a real builder. @@ -106,4 +106,4 @@ Builder Ranks represent 3 core decisions: The ranking algorithm calculates positions based on verified contributions across key data points. -Builder Ranks don't have a maximum cap, so rankings are likely to evolve over time as we add more integrations and possible credentials to the protocol. +Builder Rank doesn't have a maximum cap, so rankings are likely to evolve over time as we add more integrations and possible credentials to the protocol. diff --git a/docs/protocol-concepts/scoring-systems/index.mdx b/docs/protocol-concepts/scoring-systems/index.mdx index 7d27b12..8779c8f 100644 --- a/docs/protocol-concepts/scoring-systems/index.mdx +++ b/docs/protocol-concepts/scoring-systems/index.mdx @@ -10,7 +10,7 @@ Talent intentionally separates Data Points (objective data) from Scoring Systems Multiple ranking systems can exist in parallel, with each designed to evaluate talent in a specific domain: -- [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score) identifies and ranks people creating software +- [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score) identifies and ranks people creating software - [Creator Score](/docs/protocol-concepts/scoring-systems/creator-score) recognizes content and community builders - Other ranking systems coming soon @@ -55,10 +55,10 @@ A Score Credential is the connection between a [Data Point](/docs/protocol-conce For the Data Point "GitHub Stars": -- In the Builder Ranks system, this might be worth up to 15 points (strong signal) +- In the Builder Rank system, this might be worth up to 15 points (strong signal) - In the Creator Score system, this might be worth only 2 points (weak signal) Similarly, for the Data Point "Zora Earnings": - In the Creator Score system, this might be worth up to 30 points (strong signal) -- In the Builder Ranks system, this might be worth only 5 points (weak signal) +- In the Builder Rank system, this might be worth only 5 points (weak signal) diff --git a/docs/protocol-concepts/user.mdx b/docs/protocol-concepts/user.mdx index 29661b3..efc165a 100644 --- a/docs/protocol-concepts/user.mdx +++ b/docs/protocol-concepts/user.mdx @@ -6,7 +6,7 @@ sidebar_position: 1 A User represents an individual that signed up on talentprotocol.com -A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** An [**Account**](/docs/protocol-concepts/account) represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. @@ -16,7 +16,7 @@ An [**Account**](/docs/protocol-concepts/account) represents a connection with a - Users have a single profile URL aggregating data from all associated accounts. - `talentprotocol.com/UUID` - A user can connect multiple [accounts](/docs/protocol-concepts/account), but an account can only be linked to one user at a time. -- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Ranks](/docs/protocol-concepts/scoring-systems/builder-score). +- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score). - A user is able to sign-in to the Talent App with any account that they connected. - For now, only the Talent app can create, update or delete users from the database. Ecosystem apps can only read data. diff --git a/docs/talent-api/api-reference/index.mdx b/docs/talent-api/api-reference/index.mdx index c9bec21..a4d443a 100644 --- a/docs/talent-api/api-reference/index.mdx +++ b/docs/talent-api/api-reference/index.mdx @@ -8,7 +8,7 @@ The Talent API provides comprehensive access to verified builder reputation data - **Advanced Search**: Filter profiles by multiple criteria including tags, ranks, and human verification status - **Profile-Centric Design**: Streamlined endpoints organized around Profiles as the central entity -- **Multiple Ranking Systems**: Support for Builder Ranks and other upcoming ranking systems +- **Multiple Ranking Systems**: Support for Builder Rank and other upcoming ranking systems - **Consistent Responses**: Standardized response formats across all endpoints - **Improved Pagination**: Options for both page-based and cursor-based pagination @@ -22,8 +22,8 @@ Base URL: `https://api.talentprotocol.com/` - [**Profile Search**](/docs/talent-api/api-reference/search-for-profiles): `/search/advanced/profiles` - Find profiles matching specific criteria - [**Profile Data**](/docs/talent-api/api-reference/get-a-profile-using-wallet-talent-id-or-account-identifier): `/profile` - Get profile information by ID or account identifier -- [**Score Data**](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier): `/score` - Get Builder Ranks and other ranking information (endpoint returns ranking data including rank position) -- [**Farcaster Scores**](/docs/talent-api/api-reference/get-the-score-of-farcaster-accounts): `/farcaster/scores` - Get the Builder Ranks of Farcaster users +- [**Score Data**](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier): `/score` - Get Builder Rank and other ranking information (endpoint returns ranking data including rank position) +- [**Farcaster Scores**](/docs/talent-api/api-reference/get-the-score-of-farcaster-accounts): `/farcaster/scores` - Get the Builder Rank of Farcaster users - [**Credentials Data**](/docs/talent-api/api-reference/get-the-score-and-the-credentials-using-wallet-scorer-slug-talent-id-or-account-identifier): `/credentials` - Get the points each data point contributed to the ranking calculation - [**Data Points**](https://talent.app/~/data): `/data_points` - Get the data points providing a list of slugs and for a Talent profile - [**Account Data**](/docs/talent-api/api-reference/get-account-using-wallet-talent-id-or-account-identifier): `/accounts` - Get connected accounts information diff --git a/docs/talent-api/index.mdx b/docs/talent-api/index.mdx index 3028469..bc2ff88 100644 --- a/docs/talent-api/index.mdx +++ b/docs/talent-api/index.mdx @@ -6,5 +6,5 @@ slug: /talent-api # Talent API -Our API provides Builder Ranks, identity verification, and hundreds of other [data points](https://talent.app/~/data) +Our API provides Builder Rank, identity verification, and hundreds of other [data points](https://talent.app/~/data) through simple, reliable endpoints. From 6a527793bd5c29cebb8b05ca80daf342b36f2472 Mon Sep 17 00:00:00 2001 From: Juampi Date: Sun, 8 Feb 2026 12:01:27 -0300 Subject: [PATCH 04/10] fix: correct tier description from percentile-based to rank-based Tiers use fixed rank thresholds (top 100, top 1,000, etc.) rather than percentiles. Updated documentation to accurately reflect this approach. --- .../scoring-systems/builder-score/builder-score-levels.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx b/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx index af479fe..eedb137 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx +++ b/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx @@ -6,7 +6,7 @@ Builder Rank Tiers provide a structured way to understand and interpret Builder ## Understanding Builder Rank Tiers -Builder Rank is a ranking system that measures a builder's verified reputation data across multiple categories. To make these rankings more intuitive and actionable, we've established distinct tiers based on percentile rankings that represent increasing degrees of building activity and impact. +Builder Rank is a ranking system that measures a builder's verified reputation data across multiple categories. To make these rankings more intuitive and actionable, we've established distinct tiers based on absolute rank positions that represent increasing degrees of building activity and impact. Each tier corresponds to a specific rank range: @@ -50,7 +50,7 @@ Builders will be able to mint achievement badges for each Builder Rank Tier they ## Important Notes -- **Percentile-Based**: Builder Rank Tiers are based on percentile rankings, meaning your position relative to other builders in the ecosystem. -- **Dynamic Rankings**: As more builders join the ecosystem and contribute, rankings will naturally shift. Maintaining your tier requires continued engagement and contributions. +- **Rank-Based Tiers**: Builder Rank Tiers are based on absolute rank positions (e.g., top 100, top 1,000), meaning your position relative to other builders in the ecosystem. +- **Fixed Thresholds**: Tier thresholds are fixed numbers, so as more builders join the ecosystem, it becomes more competitive to reach and maintain higher tiers. - **Periodic Review**: We review and may adjust tier thresholds periodically to maintain meaningful separation between tiers as the ecosystem grows. - **Badge Permanence**: Once you've minted a tier badge, it remains in your collection even if your Builder Rank temporarily changes. From fc6e134dc056403596a5d453d426f1970d60701a Mon Sep 17 00:00:00 2001 From: Juampi Date: Sun, 8 Feb 2026 12:02:22 -0300 Subject: [PATCH 05/10] docs: clarify that ranks are based on scores calculated from data points MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Added explanation in the Builder Rank Framework section to show the relationship: Data Points → Scores → Ranks --- .../scoring-systems/builder-score/index.mdx | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx b/docs/protocol-concepts/scoring-systems/builder-score/index.mdx index bdc6d71..9826153 100644 --- a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx +++ b/docs/protocol-concepts/scoring-systems/builder-score/index.mdx @@ -16,7 +16,14 @@ Apps like [Basenames](https://x.com/TalentProtocol/status/1825995151275434439) o ## The "Builder Rank" Framework -All Talent ranking systems are composed of a selection of [Data Points](/docs/protocol-concepts/data-point). While we don't disclose the exact formula to prevent gaming, we can share that each Data Point is evaluated based on: +Builder Rank is determined by your position relative to other builders based on an underlying score. This score is calculated from verified [Data Points](/docs/protocol-concepts/data-point) that measure your onchain activity and contributions. + +**How it works:** +1. **Data Points** are collected from your connected accounts (GitHub contributions, onchain transactions, etc.) +2. **Scores** are calculated by evaluating each Data Point and converting them into points +3. **Ranks** are assigned based on your total score compared to all other builders in the ecosystem + +While we don't disclose the exact formula to prevent gaming, we can share that each Data Point is evaluated based on: 1. value conversion (when applicable) 2. signal strength From 081995aeadc52e0ff24ee3b7158a881c6f6fa42d Mon Sep 17 00:00:00 2001 From: Juampi Date: Sun, 8 Feb 2026 12:17:09 -0300 Subject: [PATCH 06/10] refactor: rename directory from builder-score to builder-rank - Renamed docs/protocol-concepts/scoring-systems/builder-score/ to builder-rank/ - Updated all internal references to use the new path - Maintains git history through git mv --- docs/protocol-concepts/account.mdx | 6 +++--- .../{builder-score => builder-rank}/_category_.json | 0 .../builder-score-levels.mdx | 0 .../{builder-score => builder-rank}/index.mdx | 0 docs/protocol-concepts/scoring-systems/index.mdx | 2 +- docs/protocol-concepts/user.mdx | 4 ++-- 6 files changed, 6 insertions(+), 6 deletions(-) rename docs/protocol-concepts/scoring-systems/{builder-score => builder-rank}/_category_.json (100%) rename docs/protocol-concepts/scoring-systems/{builder-score => builder-rank}/builder-score-levels.mdx (100%) rename docs/protocol-concepts/scoring-systems/{builder-score => builder-rank}/index.mdx (100%) diff --git a/docs/protocol-concepts/account.mdx b/docs/protocol-concepts/account.mdx index 26366b2..969c470 100644 --- a/docs/protocol-concepts/account.mdx +++ b/docs/protocol-concepts/account.mdx @@ -8,7 +8,7 @@ An Account represents a connection with a third-party data provider. An **Account** represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. -A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** ## Key Attributes: @@ -16,8 +16,8 @@ A [**User**](/docs/protocol-concepts/user) represents an individual that signed - `talentprotocol.com/address/0xbd…23d4` - `talentprotocol.com/github/filmacedo` - If linked to a user, the account URL will automatically redirect to the user’s profile URL. Otherwise, it will show the data from that imported account independently. -- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), and its data feeds into the user's aggregated reputation. -- Accounts display their own [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score). +- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank), and its data feeds into the user's aggregated reputation. +- Accounts display their own [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank). - Users can claim an imported account by verifying ownership (e.g., signing a wallet message, connecting GitHub). ## Types of Accounts: diff --git a/docs/protocol-concepts/scoring-systems/builder-score/_category_.json b/docs/protocol-concepts/scoring-systems/builder-rank/_category_.json similarity index 100% rename from docs/protocol-concepts/scoring-systems/builder-score/_category_.json rename to docs/protocol-concepts/scoring-systems/builder-rank/_category_.json diff --git a/docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx b/docs/protocol-concepts/scoring-systems/builder-rank/builder-score-levels.mdx similarity index 100% rename from docs/protocol-concepts/scoring-systems/builder-score/builder-score-levels.mdx rename to docs/protocol-concepts/scoring-systems/builder-rank/builder-score-levels.mdx diff --git a/docs/protocol-concepts/scoring-systems/builder-score/index.mdx b/docs/protocol-concepts/scoring-systems/builder-rank/index.mdx similarity index 100% rename from docs/protocol-concepts/scoring-systems/builder-score/index.mdx rename to docs/protocol-concepts/scoring-systems/builder-rank/index.mdx diff --git a/docs/protocol-concepts/scoring-systems/index.mdx b/docs/protocol-concepts/scoring-systems/index.mdx index 8779c8f..09e6c02 100644 --- a/docs/protocol-concepts/scoring-systems/index.mdx +++ b/docs/protocol-concepts/scoring-systems/index.mdx @@ -10,7 +10,7 @@ Talent intentionally separates Data Points (objective data) from Scoring Systems Multiple ranking systems can exist in parallel, with each designed to evaluate talent in a specific domain: -- [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score) identifies and ranks people creating software +- [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank) identifies and ranks people creating software - [Creator Score](/docs/protocol-concepts/scoring-systems/creator-score) recognizes content and community builders - Other ranking systems coming soon diff --git a/docs/protocol-concepts/user.mdx b/docs/protocol-concepts/user.mdx index efc165a..251b6a2 100644 --- a/docs/protocol-concepts/user.mdx +++ b/docs/protocol-concepts/user.mdx @@ -6,7 +6,7 @@ sidebar_position: 1 A User represents an individual that signed up on talentprotocol.com -A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** An [**Account**](/docs/protocol-concepts/account) represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. @@ -16,7 +16,7 @@ An [**Account**](/docs/protocol-concepts/account) represents a connection with a - Users have a single profile URL aggregating data from all associated accounts. - `talentprotocol.com/UUID` - A user can connect multiple [accounts](/docs/protocol-concepts/account), but an account can only be linked to one user at a time. -- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-score). +- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank). - A user is able to sign-in to the Talent App with any account that they connected. - For now, only the Talent app can create, update or delete users from the database. Ecosystem apps can only read data. From b473ff5e2a2ecc86cb48b6fd6792d3b5a35b2c36 Mon Sep 17 00:00:00 2001 From: Juampi Date: Sun, 8 Feb 2026 12:18:35 -0300 Subject: [PATCH 07/10] refactor: rename builder-score-levels.mdx to builder-rank-levels.mdx Renamed the file to match the new Builder Rank terminology --- .../{builder-score-levels.mdx => builder-rank-levels.mdx} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/protocol-concepts/scoring-systems/builder-rank/{builder-score-levels.mdx => builder-rank-levels.mdx} (100%) diff --git a/docs/protocol-concepts/scoring-systems/builder-rank/builder-score-levels.mdx b/docs/protocol-concepts/scoring-systems/builder-rank/builder-rank-levels.mdx similarity index 100% rename from docs/protocol-concepts/scoring-systems/builder-rank/builder-score-levels.mdx rename to docs/protocol-concepts/scoring-systems/builder-rank/builder-rank-levels.mdx From ec74113e023b3e70dad16b073cac932cae992305 Mon Sep 17 00:00:00 2001 From: Juampi Date: Sun, 8 Feb 2026 12:20:03 -0300 Subject: [PATCH 08/10] chore: hide Creator Score page from documentation - Renamed creator-score.mdx to _creator-score.mdx (underscore prefix hides it) - Removed Creator Score references from scoring systems index - Updated examples to use generic 'other scoring systems' instead - File is preserved but not visible in the documentation --- .../{creator-score.mdx => _creator-score.mdx} | 0 docs/protocol-concepts/scoring-systems/index.mdx | 5 ++--- 2 files changed, 2 insertions(+), 3 deletions(-) rename docs/protocol-concepts/scoring-systems/{creator-score.mdx => _creator-score.mdx} (100%) diff --git a/docs/protocol-concepts/scoring-systems/creator-score.mdx b/docs/protocol-concepts/scoring-systems/_creator-score.mdx similarity index 100% rename from docs/protocol-concepts/scoring-systems/creator-score.mdx rename to docs/protocol-concepts/scoring-systems/_creator-score.mdx diff --git a/docs/protocol-concepts/scoring-systems/index.mdx b/docs/protocol-concepts/scoring-systems/index.mdx index 09e6c02..9bdd9eb 100644 --- a/docs/protocol-concepts/scoring-systems/index.mdx +++ b/docs/protocol-concepts/scoring-systems/index.mdx @@ -11,7 +11,6 @@ Talent intentionally separates Data Points (objective data) from Scoring Systems Multiple ranking systems can exist in parallel, with each designed to evaluate talent in a specific domain: - [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank) identifies and ranks people creating software -- [Creator Score](/docs/protocol-concepts/scoring-systems/creator-score) recognizes content and community builders - Other ranking systems coming soon Each ranking system operates independently with its own set of relevant Data Points and scoring logic, tailored to what matters for their specific persona. @@ -56,9 +55,9 @@ A Score Credential is the connection between a [Data Point](/docs/protocol-conce For the Data Point "GitHub Stars": - In the Builder Rank system, this might be worth up to 15 points (strong signal) -- In the Creator Score system, this might be worth only 2 points (weak signal) +- In other scoring systems, this might be worth only 2 points (weak signal) Similarly, for the Data Point "Zora Earnings": -- In the Creator Score system, this might be worth up to 30 points (strong signal) +- In other scoring systems, this might be worth up to 30 points (strong signal) - In the Builder Rank system, this might be worth only 5 points (weak signal) From f41aa8e1529d5ea31efa351719e816df45313e5f Mon Sep 17 00:00:00 2001 From: Juampi Date: Mon, 9 Feb 2026 08:29:33 -0300 Subject: [PATCH 09/10] Simplify docs: remove scoring formula internals, tiers, and rename to Ranking Systems - Remove scoring formula details (value conversion, signal strength, max score, multipliers) - Delete builder-rank-levels.mdx (tier system: names, table, badges) - Simplify Builder Rank page to: what it is, what data feeds it, how to access via API - Simplify Scoring Systems page and rename to Ranking Systems - Move files from scoring-systems/ to ranking-systems/ --- .../ranking-systems/_category_.json | 4 + .../_creator-score.mdx | 0 .../builder-rank/_category_.json | 0 .../ranking-systems/builder-rank/index.mdx | 39 ++++++ .../ranking-systems/index.mdx | 20 +++ .../scoring-systems/_category_.json | 2 +- .../builder-rank/builder-rank-levels.mdx | 56 --------- .../scoring-systems/builder-rank/index.mdx | 116 ------------------ .../scoring-systems/index.mdx | 63 ---------- 9 files changed, 64 insertions(+), 236 deletions(-) create mode 100644 docs/protocol-concepts/ranking-systems/_category_.json rename docs/protocol-concepts/{scoring-systems => ranking-systems}/_creator-score.mdx (100%) rename docs/protocol-concepts/{scoring-systems => ranking-systems}/builder-rank/_category_.json (100%) create mode 100644 docs/protocol-concepts/ranking-systems/builder-rank/index.mdx create mode 100644 docs/protocol-concepts/ranking-systems/index.mdx delete mode 100644 docs/protocol-concepts/scoring-systems/builder-rank/builder-rank-levels.mdx delete mode 100644 docs/protocol-concepts/scoring-systems/builder-rank/index.mdx delete mode 100644 docs/protocol-concepts/scoring-systems/index.mdx diff --git a/docs/protocol-concepts/ranking-systems/_category_.json b/docs/protocol-concepts/ranking-systems/_category_.json new file mode 100644 index 0000000..be899dd --- /dev/null +++ b/docs/protocol-concepts/ranking-systems/_category_.json @@ -0,0 +1,4 @@ +{ + "label": "Ranking Systems", + "position": 7 +} diff --git a/docs/protocol-concepts/scoring-systems/_creator-score.mdx b/docs/protocol-concepts/ranking-systems/_creator-score.mdx similarity index 100% rename from docs/protocol-concepts/scoring-systems/_creator-score.mdx rename to docs/protocol-concepts/ranking-systems/_creator-score.mdx diff --git a/docs/protocol-concepts/scoring-systems/builder-rank/_category_.json b/docs/protocol-concepts/ranking-systems/builder-rank/_category_.json similarity index 100% rename from docs/protocol-concepts/scoring-systems/builder-rank/_category_.json rename to docs/protocol-concepts/ranking-systems/builder-rank/_category_.json diff --git a/docs/protocol-concepts/ranking-systems/builder-rank/index.mdx b/docs/protocol-concepts/ranking-systems/builder-rank/index.mdx new file mode 100644 index 0000000..c9707dd --- /dev/null +++ b/docs/protocol-concepts/ranking-systems/builder-rank/index.mdx @@ -0,0 +1,39 @@ +# Builder Rank + +A ranking system to recognize real onchain builders. + +## What is Builder Rank? + +Builder Rank is a ranking system that represents a user's position relative to other builders, based on verified activity and impact. + +Builder Rank aims to distinguish builders from other types of crypto users, by valuing both the quantity and quality of their contributions. It reflects both "potential" (future growth) and "achievements" (proven track record). + +Users can leverage their Builder Rank within Talent's growing partner ecosystem, while developers can easily add Builder Rank to their apps. + +Apps like [Basenames](https://x.com/TalentProtocol/status/1825995151275434439) or [Etherscan](https://x.com/TalentProtocol/status/1830974248363622607) already integrate with Builder Rank to bring more context to their users and to curate the best builders in crypto. + +## How Builder Rank Works + +Builder Rank is determined by your position relative to other builders. It is calculated from verified [Data Points](/docs/protocol-concepts/data-point) collected from your connected accounts, such as: + +- GitHub contributions and repositories +- Onchain transactions and contract deployments +- Hackathon participation and wins +- Social presence (Farcaster, Twitter/X) + +Each Data Point is evaluated based on how strongly it signals real building activity. The exact formula is not disclosed to prevent gaming. + +:::warning + +Builder Rank is still experimental, so expect regular updates to the ranking algorithm. + +::: + +## Accessing Builder Rank + +You can retrieve a builder's rank via the Talent API: + +- [**Rank endpoint**](/docs/talent-api/api-reference/get-a-specific-score-using-wallet-scorer-slug-talent-id-or-account-identifier): Get a builder's rank by wallet address, Talent ID, or account identifier +- [**Profile search**](/docs/talent-api/api-reference/search-for-profiles): Search and filter profiles by rank + +Builder Rank doesn't have a maximum cap, so rankings evolve over time as more builders join and more data sources are added. diff --git a/docs/protocol-concepts/ranking-systems/index.mdx b/docs/protocol-concepts/ranking-systems/index.mdx new file mode 100644 index 0000000..9fd5c56 --- /dev/null +++ b/docs/protocol-concepts/ranking-systems/index.mdx @@ -0,0 +1,20 @@ +# Ranking Systems + +A Ranking System evaluates verified [Data Points](/docs/protocol-concepts/data-point) to determine a user's position relative to others in a specific domain. + +Under the hood, each ranking system uses an internal scoring algorithm to convert Data Points into a final rank. The scores themselves are not exposed — only the resulting rank is made available through the API. + +Talent intentionally separates Data Points (objective data) from Ranking Systems (subjective evaluation). Both are autonomous and composable protocol primitives. + +## Available Ranking Systems + +Multiple ranking systems can exist in parallel, each designed to evaluate talent in a specific domain: + +- [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank) identifies and ranks people creating software +- Other ranking systems coming soon + +Each ranking system operates independently with its own set of relevant Data Points, tailored to what matters for their specific persona. + +This modular approach allows Talent to serve different communities with metrics that genuinely reflect their unique contributions, rather than forcing diverse talents into the same box. + +Reach out if you want to create a custom ranking system. diff --git a/docs/protocol-concepts/scoring-systems/_category_.json b/docs/protocol-concepts/scoring-systems/_category_.json index e076b7c..be899dd 100644 --- a/docs/protocol-concepts/scoring-systems/_category_.json +++ b/docs/protocol-concepts/scoring-systems/_category_.json @@ -1,4 +1,4 @@ { - "label": "Scoring Systems", + "label": "Ranking Systems", "position": 7 } diff --git a/docs/protocol-concepts/scoring-systems/builder-rank/builder-rank-levels.mdx b/docs/protocol-concepts/scoring-systems/builder-rank/builder-rank-levels.mdx deleted file mode 100644 index eedb137..0000000 --- a/docs/protocol-concepts/scoring-systems/builder-rank/builder-rank-levels.mdx +++ /dev/null @@ -1,56 +0,0 @@ -# Builder Rank Tiers - -Understanding Builder Rank tiers and implementation guidelines for developers. - -Builder Rank Tiers provide a structured way to understand and interpret Builder Rank in the Talent ecosystem. These tiers help both developers integrating our API and individual builders track progress and set goals. - -## Understanding Builder Rank Tiers - -Builder Rank is a ranking system that measures a builder's verified reputation data across multiple categories. To make these rankings more intuitive and actionable, we've established distinct tiers based on absolute rank positions that represent increasing degrees of building activity and impact. - -Each tier corresponds to a specific rank range: - -| Tier | Name | Rank Range | Description | -| ---- | ------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| 1 | Novice | Top 100,000 | Just getting started with the basics. They've connected some accounts and taken their first steps as a builder. | -| 2 | Apprentice | Top 50,000 | They're building sporadically and starting to make their mark. Their contributions are starting to get noticed. | -| 3 | Practitioner | Top 10,000 | They've established themselves as serious builders with real impact. Their work speaks for itself across multiple platforms. | -| 4 | Advanced | Top 5,000 | They've built some impressive things and contributed to notable projects. Their reputation is solid and growing. | -| 5 | Expert | Top 1,000 | They're among the top builders with an exceptional track record. People look to their work as an example. | -| 6 | Master | Top 100 | They're one of the most accomplished builders in the ecosystem with contributions that have made a real difference. | - -## Use Cases - -- **Hackathons:** Prioritizes hackathon applications from builders ranked in the top 5,000 (Distinguished tier) or higher -- **Communities**: Automatically approves membership for builders ranked in the top 50,000 (Rising tier) or higher - -## Implementation Guide - -When integrating Builder Rank into your app or protocol, you can use these tiers to: - -- **Access Control**: Gate specific features or capabilities based on Builder Rank Tiers -- **User Segmentation**: Create targeted experiences for different builder segments -- **Reward Distribution**: Allocate rewards or incentives proportionally to builder tiers -- **Interface Design**: Visually represent tiers with badges or other UI elements -- **Governance Rights**: Allocate voting weight or proposal rights -- **Recommended Tier Requirements:** - -- General access and basic features: Tier 1 (Emerging - Top 100,000) -- Premium features and moderate incentives: Tier 3 (Established - Top 10,000) -- Exclusive access and significant incentives: Tier 5 (Elite - Top 1,000) - -## Onchain Tier Badges - -Builders will be able to mint achievement badges for each Builder Rank Tier they reach. These badges: - -- Serve as permanent proof of achievement -- Can be displayed on profiles across the web3 ecosystem -- May unlock special perks from ecosystem partners -- Create a collection that visually represents a builder's journey - -## Important Notes - -- **Rank-Based Tiers**: Builder Rank Tiers are based on absolute rank positions (e.g., top 100, top 1,000), meaning your position relative to other builders in the ecosystem. -- **Fixed Thresholds**: Tier thresholds are fixed numbers, so as more builders join the ecosystem, it becomes more competitive to reach and maintain higher tiers. -- **Periodic Review**: We review and may adjust tier thresholds periodically to maintain meaningful separation between tiers as the ecosystem grows. -- **Badge Permanence**: Once you've minted a tier badge, it remains in your collection even if your Builder Rank temporarily changes. diff --git a/docs/protocol-concepts/scoring-systems/builder-rank/index.mdx b/docs/protocol-concepts/scoring-systems/builder-rank/index.mdx deleted file mode 100644 index 9826153..0000000 --- a/docs/protocol-concepts/scoring-systems/builder-rank/index.mdx +++ /dev/null @@ -1,116 +0,0 @@ -# Builder Rank - -============= - -A ranking system to recognize real onchain builders. - -## What is Builder Rank? - -Builder Rank is a ranking system that represents a user's reputation as an onchain builder based on verified activity and impact. - -Builder Rank aims to distinguish builders from other types of crypto users, by valuing both the quantity and quality of their contributions. It reflects both "potential" (future growth) and "achievements" (proven track record). - -Users can leverage their Builder Rank within Talent's growing partner ecosystem, while developers can easily add Builder Rank to their apps. - -Apps like [Basenames](https://x.com/TalentProtocol/status/1825995151275434439) or [Etherscan](https://x.com/TalentProtocol/status/1830974248363622607) already integrate with Builder Rank to bring more context to their users and to curate the best builders in crypto. - -## The "Builder Rank" Framework - -Builder Rank is determined by your position relative to other builders based on an underlying score. This score is calculated from verified [Data Points](/docs/protocol-concepts/data-point) that measure your onchain activity and contributions. - -**How it works:** -1. **Data Points** are collected from your connected accounts (GitHub contributions, onchain transactions, etc.) -2. **Scores** are calculated by evaluating each Data Point and converting them into points -3. **Ranks** are assigned based on your total score compared to all other builders in the ecosystem - -While we don't disclose the exact formula to prevent gaming, we can share that each Data Point is evaluated based on: - -1. value conversion (when applicable) -2. signal strength -3. max score -4. multiplier (not publicly disclosed) - -### 1. Value Conversion - -For some Data Points it's helpful to normalized their numerical value before applying the ranking algorithm, but this is an optional step. - -Examples: - -- Convert `twitter_account_age` from a `timestamp` to the `number of years` the account has. -- Normalize `base_out_transactions` with a `sqrt` function to reduce the impact of large values, making the ranking system more balanced and fair, and ensuring big contributors don't completely overpower smaller ones. This means that your first contributions matter more than later ones. -- Invert `farcaster_social_capital_rank` value, so that the #1 ranked user has a higher value (and more points) than the last ranked user. - -### 2. Signal Strength - -Defines how strongly a given data point proves that the user is a real builder, and can have 3 possible values: `weak`, `medium`, `strong.` - -Examples: - -- Winning a ETHGlobal hackathon is a strong signal that someone is a real builder. -- Simply having a GitHub account is a weak signal that someone is a real builder. - -### 3. Max Score - -Defines the maximum amount of points each Data Point can contribute to the overall ranking calculation. We use the signal strength to help define the max score of each Data Point: - -- strong (up to 40 points) -- medium (up to 20 points) -- weak ( to 8 points) - -The mapping between signal strength and max score is just a framework for human decision, not enforced at the code level. - -### 4. Multiplier - -In the Builder Rank algorithm, we use multipliers to convert the numerical value of a Data Point into a score measured in "points." These multipliers help standardize very different scales of Data Point values into a consistent scoring system that feeds into the final ranking. - -Although we don't disclose the exact multipliers used for each Data Point, users can understand the relative importance of each Data Point through the signal strength and max score values we provide. - -
- Examples - -- Data Point: Base Contracts Deployed (Mainnet) - - Value: 7 (number of contracts deployed) - - Multiplier: 0.2 - - Max Score: 2 - - Points: 1.4 (7\*0.2) -- Data Point: GitHub Total Contributions - - Value: 1734 - - Multiplier: 0.001 - - Max Score: 15 - - Points: 1.734 (1734\*0.001) - -
- -:::warning - -Builder Rank is still experimental, so expect regular updates to the ranking algorithm. - -::: - -## Transparency and Formula Disclosure - -At Talent, we believe in transparency while maintaining the integrity of our ranking system. We disclose the general framework of our Builder Rank calculation, including: - -- The Data Points we consider relevant -- The signal strength classification for each Data Point -- The maximum score potential for each Data Point - -However, to prevent gaming or artificial optimization of the system, we do not publicly disclose: - -- Specific multipliers for each Data Point -- Exact conversion functions applied to normalize values -- Detailed thresholds for achieving maximum scores - -This approach allows us to maintain the integrity of Builder Rank while still providing users with clear guidance on how to improve their ranking through genuine contributions. - -## Summary - -Builder Rank represents 3 core decisions: - -1. What Data Points are relevant to assess the reputation of a builder. -2. How strongly does each Data Point signal that the user is a real builder. -3. What should be the multiplier to convert each Data Point value into points for the ranking algorithm. - -The ranking algorithm calculates positions based on verified contributions across key data points. - -Builder Rank doesn't have a maximum cap, so rankings are likely to evolve over time as we add more integrations and possible credentials to the protocol. diff --git a/docs/protocol-concepts/scoring-systems/index.mdx b/docs/protocol-concepts/scoring-systems/index.mdx deleted file mode 100644 index 9bdd9eb..0000000 --- a/docs/protocol-concepts/scoring-systems/index.mdx +++ /dev/null @@ -1,63 +0,0 @@ -# Scoring Systems - -A Scoring System is a set of rules that convert Data Points into numerical reputation scores. - -A Scoring System assigns numerical scores (measured in "points") to a selection of [Data Points](/docs/protocol-concepts/data-point). - -Talent intentionally separates Data Points (objective data) from Scoring Systems (subjective data). Both are autonomous and composable protocol primitives. - -## Different Ranking Systems - -Multiple ranking systems can exist in parallel, with each designed to evaluate talent in a specific domain: - -- [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank) identifies and ranks people creating software -- Other ranking systems coming soon - -Each ranking system operates independently with its own set of relevant Data Points and scoring logic, tailored to what matters for their specific persona. - -This modular approach allows Talent to serve different communities with metrics that genuinely reflect their unique contributions, rather than forcing diverse talents into the same box. - -Reach out if you want to create a custom ranking system. - -## Scoring Framework - -A Scoring System is composed of: - -1. a **selection of Data Points** to be considered for this particular score -2. a **value conversion** (optional) to normalize Data Point values (ex.`timestamp_to_year` or `sqrt)` -3. a **signal strength** (strong, medium, or weak) attributed to each Data Point -4. a **maximum score** (in "points") that each Data Point can contribute to the overall score -5. a **scoring function** or **condition** that converts the current value of a Data Point into a numerical score (measured in "points") - -Scoring systems are absolute, meaning they don’t include any form of normalization or percentile-based approach. The final score should be a simple sum of all Data Point individual scores. - -This framework intends to keep every scoring system simple, transparent and scalable. - -## Calculating a Score - -To calculate a score, Talent will follow the steps below: - -1. Fetch new data for each account and store them in the respective Data Point. -2. If the Data Point value changed, we create an [Event](/docs/protocol-concepts/event) (coming soon). -3. We then apply the scoring framework to all Data Points with a value change. -4. If there are multiple sources for the same data point (example: a user with multiples wallet addresses), we pick the one with the highest value. - -## Score Credentials - -A Score Credential is the connection between a [Data Point](/docs/protocol-concepts/data-point) and a Scoring System. It defines: - -1. How much a specific Data Point contributes to a given score -2. The criteria for evaluating the Data Point's value -3. The maximum points this credential can add to the total score - -## Example - -For the Data Point "GitHub Stars": - -- In the Builder Rank system, this might be worth up to 15 points (strong signal) -- In other scoring systems, this might be worth only 2 points (weak signal) - -Similarly, for the Data Point "Zora Earnings": - -- In other scoring systems, this might be worth up to 30 points (strong signal) -- In the Builder Rank system, this might be worth only 5 points (weak signal) From 44205e7cde2658752775a66899e0dd556f162f54 Mon Sep 17 00:00:00 2001 From: Juampi Date: Mon, 9 Feb 2026 08:43:04 -0300 Subject: [PATCH 10/10] Fix broken links: update scoring-systems paths to ranking-systems --- docs/get-started.mdx | 2 +- docs/legal/creator-rewards-terms-conditions.mdx | 2 +- docs/protocol-concepts/account.mdx | 6 +++--- docs/protocol-concepts/data-point.mdx | 2 +- docs/protocol-concepts/ranking-systems/index.mdx | 2 +- docs/protocol-concepts/user.mdx | 4 ++-- 6 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/get-started.mdx b/docs/get-started.mdx index f694573..be3037d 100644 --- a/docs/get-started.mdx +++ b/docs/get-started.mdx @@ -42,7 +42,7 @@ Talent is built around the following core concepts to create a comprehensive rep - [**Account**](/docs/protocol-concepts/account): A connection to a third-party data source (wallet, GitHub, X, etc.) that provides reputation data. - [**Data Point**](/docs/protocol-concepts/data-point): A specific verified fact about a builder (GitHub stars, wallet transactions, etc.). - [**Events**](/docs/protocol-concepts/event): Historical records of reputation changes -- [**Ranking Systems**](/docs/protocol-concepts/scoring-systems): A ranking system that evaluates reputation based on Data Points. Builder Rank is our primary ranking system for identifying top builders. +- [**Ranking Systems**](/docs/protocol-concepts/ranking-systems): A ranking system that evaluates reputation based on Data Points. Builder Rank is our primary ranking system for identifying top builders. ## Support diff --git a/docs/legal/creator-rewards-terms-conditions.mdx b/docs/legal/creator-rewards-terms-conditions.mdx index 674e03a..e2e642a 100644 --- a/docs/legal/creator-rewards-terms-conditions.mdx +++ b/docs/legal/creator-rewards-terms-conditions.mdx @@ -38,7 +38,7 @@ Top 200 creators share the reward pool, proportionally to their Creator Score. ## 5. Evaluation Criteria -For more information about Creator Score please visit [this page](https://docs.talentprotocol.com/docs/protocol-concepts/scoring-systems/creator-score). +For more information about Creator Score please visit [this page](https://docs.talentprotocol.com/docs/protocol-concepts/ranking-systems/creator-score). The specific weights and formulas used to calculate rankings are proprietary and subject to change at the sole discretion of Talent. diff --git a/docs/protocol-concepts/account.mdx b/docs/protocol-concepts/account.mdx index 969c470..448f6ca 100644 --- a/docs/protocol-concepts/account.mdx +++ b/docs/protocol-concepts/account.mdx @@ -8,7 +8,7 @@ An Account represents a connection with a third-party data provider. An **Account** represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. -A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A [**User**](/docs/protocol-concepts/user) represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/ranking-systems/builder-rank), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** ## Key Attributes: @@ -16,8 +16,8 @@ A [**User**](/docs/protocol-concepts/user) represents an individual that signed - `talentprotocol.com/address/0xbd…23d4` - `talentprotocol.com/github/filmacedo` - If linked to a user, the account URL will automatically redirect to the user’s profile URL. Otherwise, it will show the data from that imported account independently. -- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank), and its data feeds into the user's aggregated reputation. -- Accounts display their own [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank). +- Once linked to a user, an account loses its independent profile and redirect to the user's profile. The account also loses its [Builder Rank](/docs/protocol-concepts/ranking-systems/builder-rank), and its data feeds into the user's aggregated reputation. +- Accounts display their own [Builder Rank](/docs/protocol-concepts/ranking-systems/builder-rank) unless linked to a user, at which point their data integrates into the user's aggregated [Builder Rank](/docs/protocol-concepts/ranking-systems/builder-rank). - Users can claim an imported account by verifying ownership (e.g., signing a wallet message, connecting GitHub). ## Types of Accounts: diff --git a/docs/protocol-concepts/data-point.mdx b/docs/protocol-concepts/data-point.mdx index 28c025d..3bb7bac 100644 --- a/docs/protocol-concepts/data-point.mdx +++ b/docs/protocol-concepts/data-point.mdx @@ -37,7 +37,7 @@ Explore data indexed by Talent at [https://talent.app/~/data](https://talent.app ## Scoring Tags -- We use a **tag-based system** that determines how data points are used in [Scoring Systems](/docs/protocol-concepts/scoring-systems): +- We use a **tag-based system** that determines how data points are used in [Ranking Systems](/docs/protocol-concepts/ranking-systems): - Initial tags: `human`, `builder`, `creator` - Data points can have multiple tags - Scoring systems use tags to determine which data points to include diff --git a/docs/protocol-concepts/ranking-systems/index.mdx b/docs/protocol-concepts/ranking-systems/index.mdx index 9fd5c56..9a8435f 100644 --- a/docs/protocol-concepts/ranking-systems/index.mdx +++ b/docs/protocol-concepts/ranking-systems/index.mdx @@ -10,7 +10,7 @@ Talent intentionally separates Data Points (objective data) from Ranking Systems Multiple ranking systems can exist in parallel, each designed to evaluate talent in a specific domain: -- [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank) identifies and ranks people creating software +- [Builder Rank](/docs/protocol-concepts/ranking-systems/builder-rank) identifies and ranks people creating software - Other ranking systems coming soon Each ranking system operates independently with its own set of relevant Data Points, tailored to what matters for their specific persona. diff --git a/docs/protocol-concepts/user.mdx b/docs/protocol-concepts/user.mdx index 251b6a2..ca5d6d9 100644 --- a/docs/protocol-concepts/user.mdx +++ b/docs/protocol-concepts/user.mdx @@ -6,7 +6,7 @@ sidebar_position: 1 A User represents an individual that signed up on talentprotocol.com -A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** +A **User** represents an individual that signed up on talentprotocol.com to verify their reputation data and improve their [Builder Rank](/docs/protocol-concepts/ranking-systems/builder-rank), by connecting multiple [**accounts**](/docs/protocol-concepts/account)**.** An [**Account**](/docs/protocol-concepts/account) represents a connection with a third-party entity (e.g., Wallet Address, GitHub, X, LinkedIn) that feeds reputation data into Talent. Accounts can exist independently or be linked to a user. @@ -16,7 +16,7 @@ An [**Account**](/docs/protocol-concepts/account) represents a connection with a - Users have a single profile URL aggregating data from all associated accounts. - `talentprotocol.com/UUID` - A user can connect multiple [accounts](/docs/protocol-concepts/account), but an account can only be linked to one user at a time. -- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Rank](/docs/protocol-concepts/scoring-systems/builder-rank). +- A user aggregates reputation data from all its connected [accounts](/docs/protocol-concepts/account) into a unified [Builder Rank](/docs/protocol-concepts/ranking-systems/builder-rank). - A user is able to sign-in to the Talent App with any account that they connected. - For now, only the Talent app can create, update or delete users from the database. Ecosystem apps can only read data.