Identity: The Trust Layer of the TON Ecosystem

Version 0.2 — 8 February 2026

Abstract

Blockchain ecosystems rely on small committees to coordinate growth — allocating grants, evaluating projects, deciding who gets access. This works at small scale but breaks down as ecosystems grow. The process becomes opaque, subjective, and impossible to maintain.

Identity is an open platform that replaces manual gatekeeping with transparent, automated evaluation built on verifiable signals. It reverses the traditional model: contribute first, earn access second. The result is a trust layer for the TON ecosystem — where reputation is portable, rules are public, and every decision is auditable.

1. The Problem

Blockchain ecosystems grow faster than the institutions that govern them. Most rely on small committees as the central point of coordination — reviewing projects, allocating grants, making introductions. If a project wants to build something, it goes to the committee. If a contributor seeks recognition, they need a personal connection. When the ecosystem is small, this works: the committee can hold one-on-one meetings with developers, track progress, give advice, and distribute resources.

But this model breaks down at scale. When a wave of new developers, projects, and communities enters the ecosystem, the committee simply cannot keep up. There is no time to evaluate every project from scratch, no capacity to monitor how each one evolves, and no way to provide personalized guidance to hundreds of teams. Core processes — discovery, evaluation, support — stop working.

This creates several critical bottlenecks:

• Subjectivity at scale. When a handful of people decide who receives grants, marketing, or recognition, the process is inherently opinion-driven. Quality contributors get overlooked.
• Lack of transparency. Contributors rarely understand why they were accepted or rejected. There is no audit trail, no clear criteria. Worse, even strong projects suffer: a committee may recognize their results and allocate resources fairly, but because the evaluation process is private, the community sees only the outcome — and assumes it was driven by connections, not merit. This breeds resentment toward the very projects that earned their support, eroding both their reputation and ecosystem trust.
• Cannot scale. Manual review requires headcount. As the ecosystem grows 10x, you cannot grow committees 10x.
• Single point of failure. Centralized gatekeeping concentrates power. A small group controls access for everyone.

These are not edge cases — they are structural limitations of how ecosystems operate today.

2. The Vision

Identity is an open platform that automates the pipelines of working with projects, contributors, and communities — removing the need for manual participation from ecosystem committees.

But automation alone is not enough. The rules must be transparent. When a project receives an endorsement, funding, or visibility, the community should have no questions about why or how. Clear criteria, fair access, open evaluation, verifiable outcomes.

This approach shifts the role of ecosystem committees from gatekeepers to governance designers. Instead of making individual decisions on which projects to select or support, committees interact directly with the process itself — defining rules, setting criteria, tuning evaluation. The platform executes; the community verifies.

Beyond automation and transparency, Identity unites all ecosystem participants — developers, projects, KOLs, community builders, and users — around a shared goal: technology adoption. Every participant has a portable reputation that reflects their real impact. Access to opportunities follows from verifiable criteria, not personal connections.

Reputation also unlocks a voice in ecosystem governance. The ecosystem allocates resources for project support, and contributors with verified track records choose the best recipients — through a transparent, community-agreed process. This creates a feedback loop: the people who contribute the most have the greatest influence over where the ecosystem goes next.

Identity reverses the traditional model. In most ecosystems, you first need access — an introduction, an approval, a slot — and only then can you start building. Identity flips this: you arrive, demonstrate results, the platform evaluates them, and you earn access to ecosystem resources. Contribution comes first. Recognition follows.

The result: a platform that defines clear rules for ecosystem development, distributes resources and attention to the best projects, and drives adoption — all without manual gatekeeping.

Identity aims to build a world where contribution is verifiable, and selection is too.

Core principles

1. Rules, not opinions. Access follows verifiable criteria, not committee discretion.
2. Auditable by default. Every signal, score, and outcome is public. Anyone can verify how decisions are made.
3. Scales without headcount. Automated evaluation replaces manual review. Growing ecosystems don't need growing committees.
4. No single gatekeeper. Community-driven and independent. No organization controls who qualifies.

3. How Identity Works

Identity operates as a five-step pipeline from raw signals to ecosystem access:

Step 1: Connect

Users link their public accounts — Telegram, GitHub, TON wallets, and other platforms — to create a unified identity. Only public data is read. Identity never requests private credentials or repository access.

This is by design: public data can be independently verified by any community member, ensuring trust without reliance on a central authority. It also incentivizes open-source development — the more open your work, the more visible and verifiable your contribution.

Step 2: Contribute

Participants contribute to the ecosystem in any way they choose — building open-source software, growing communities, creating educational content, mentoring newcomers, or launching projects.

Identity can also suggest ways to contribute: based on a participant's skills, activity, and current ecosystem needs, the platform surfaces relevant opportunities — open tasks, projects seeking contributors, or areas where support is most needed.

Step 3: Verify

Identity continuously analyzes contributions across the ecosystem. Raw signals pass through a network of validators that confirm relevance, authenticity, and quality. The evaluation engine then aggregates validated signals and applies rule-based scoring to produce a transparent assessment.

Step 4: Gain Visibility

A contributor's impact becomes visible across the ecosystem. Verified profiles surface real achievements, not self-reported claims.

People, committees, and communities can understand each other's contributions and track records at a glance. This is especially valuable as the ecosystem scales — the platform automates discovery and introduction that would otherwise require personal networking. Instead of asking "who is this person?", anyone can see a verified, data-backed answer.

Participants can also indicate in their profiles how they can help others — development, mentorship, marketing, design, community building — making it easy to find not just who has contributed, but who is available and willing to contribute next.

Step 5: Unlock

Verified reputation unlocks tangible outcomes: jobs, grants, event access, introductions, mentorship, and recognition. The score acts as a portable credential across the ecosystem.

4. Validators

Not every signal that enters the platform can be trusted at face value. A new repository appears on GitHub — how does the system determine whether it is related to TON? A contributor claims ecosystem activity — how is that confirmed? This is where validators come in.

A validator is any entity that verifies the relevance, authenticity, or quality of a signal. Validators are the layer between raw data collection and reputation scoring — they ensure that only meaningful, verified signals feed into the evaluation engine.

Validator types

Identity supports an open architecture of validator types:

• Code-based validators. Automated rules and scripts that check verifiable facts — scanning a repository's dependencies for TON libraries, verifying that a smart contract is deployed on the TON blockchain, or confirming that a GitHub account is linked to a specific wallet.
• AI-based validators. Models that analyze content, code, and context at scale — classifying whether a repository is TON-related based on its structure and documentation, or detecting anomalous contribution patterns that may indicate gaming.
• Human validators. Community members with verified reputation who review cases that automated systems cannot resolve with confidence — evaluating the quality of an educational article, or confirming that a community event actually took place.

This architecture is deliberately extensible. New validator types can be introduced as the ecosystem evolves, and existing validators can be refined or replaced without changing the core protocol.

Validation as contribution

Validators are not passive infrastructure — they are active participants. Community members who perform validation earn reputation points for accurate, timely assessments. Conversely, incorrect or negligent validation carries penalties: validators who consistently misclassify signals lose reputation, reducing their influence and validation privileges. This creates a self-reinforcing cycle with built-in accountability — contributors with strong track records validate signals, earn further reputation, and strengthen the integrity of the entire system.

Example: classifying a new repository

A new repository appears on GitHub. Code-based validators scan its dependencies and detect TON SDK imports. An AI-based validator analyzes the README and confirms TON-related functionality. If the automated confidence score is high, the repository is classified immediately. If it falls below a threshold, a human validator with relevant expertise reviews and makes the final determination. Every step is logged and auditable.

5. Reputation Score

The Identity reputation score is a composite metric calculated from public, verifiable signals. Importantly, reputation applies not only to individuals but also to projects and communities — each with its own signal profile.

Who has a reputation score

• People. Individual contributors — developers, creators, community builders, mentors. A person's score reflects their direct impact across the ecosystem.
• Projects. Applications, protocols, and tools building on TON. A project's reputation is derived from its ecosystem contribution: new users brought in, audience engagement, product metrics, on-chain activity, developer growth, and community support.
• Communities. Groups and channels within the ecosystem. A community's reputation reflects the aggregate activity and impact of its members — the stronger the participants, the stronger the community's standing.

Signal sources

Identity aggregates signals from multiple domains of ecosystem participation:

• GitHub activity. Commits, pull requests, code reviews, and issues in TON-related repositories. Repository creation, maintenance, and community contributions.
• Telegram communities. Activity and standing in TON-related groups — discussions, support, moderation, and community building.
• On-chain activity. Smart contract deployment, blockchain interactions, protocol usage, DeFi participation, and other verifiable on-chain actions on the TON network.
• Marketing and social media. Publishing posts, threads, and announcements about TON projects across social platforms.
• Educational content. Creating tutorials, guides, courses, and video content that helps others learn about the ecosystem.
• Evangelism. Speaking at conferences, representing the ecosystem publicly, and advocating for TON adoption.
• Events. Organizing and participating in hackathons, meetups, workshops, and community gatherings.
• Mentorship and support. Helping newcomers, reviewing projects, and providing expertise to other contributors.

The list of signal sources is not fixed — it expands as the ecosystem grows and new forms of contribution emerge.

Scoring principles

• Deterministic. The same inputs always produce the same score. No human judgment in the loop.
• Transparent. Every component of the score is visible to the user. You can see exactly what contributed to your result.
• Evolving. New signal sources and scoring algorithms are introduced as the ecosystem grows.
• Not a ranking. The score reflects individual impact, not competition. It highlights how you have been involved.

6. SBT Integration

What are SBTs

Soulbound Tokens (SBTs) are non-transferable tokens permanently bound to a wallet. Unlike regular NFTs, they cannot be sold or moved — they represent personal achievements, credentials, and participation history. Think of them as on-chain certificates: proof that you attended an event, completed a course, contributed to a project, or received a grant.

The role of SBTs in the ecosystem today

In the TON ecosystem, SBTs already serve as verifiable proof of participation. Several ecosystem programs, events, and communities issue SBTs to mark contributions and milestones. In theory, this creates a rich on-chain history of what a person has done.

The problem with SBTs today

In practice, SBTs remain underutilized. Issuing them requires technical knowledge — not every organizer can deploy a collection and distribute tokens. There is no unified standard for how SBTs are structured or discovered. Most sit idle in wallets with no practical use beyond proof of ownership. No platform aggregates them into a meaningful picture, and no tooling makes issuance accessible to non-technical participants. The result: a powerful primitive that has not yet reached its potential.

How Identity changes this

Identity reads SBT collections from connected wallets to incorporate on-chain credentials into the reputation score. But it goes beyond reading existing tokens — it aims to transform how SBTs are issued and used across the ecosystem.

SBT issuance platform

Identity will provide a platform and a mobile application that make issuing SBTs simple and accessible. Event organizers, for example, can distribute attendance SBTs to participants by tapping phones via NFC — no complex setup, no manual address collection, no friction. This turns every meetup, hackathon, and conference into a verifiable on-chain credential with minimal effort from both organizers and attendees.

Identity without registration forms

When a participant arrives at an event or joins a program, organizers can instantly see their verified Identity profile — contributions, reputation, skills — without requiring lengthy registration forms or questionnaires. The SBT and the profile work together: the token proves attendance, the profile provides context about who the person is and what they bring to the ecosystem.

Expanding SBT utility

By making SBT issuance effortless and connecting tokens to rich identity data, Identity creates a practical adoption path for SBTs across the ecosystem — from event attendance and course completion to grant milestones and community recognition.

7. What Identity Unlocks

Identity creates value for every layer of the ecosystem — from individual contributors to the governance structures that guide its development.

For people

A portable, verifiable reputation that opens doors. Contributors gain access to grants, jobs, mentorship, and recognition based on what they have actually done — not who they know. The platform suggests relevant opportunities based on skills and activity. Participants with strong track records earn a voice in ecosystem governance, voting on which projects receive support. Reputation becomes a credential that travels with you across the ecosystem.

For projects

Transparent evaluation without pitch decks and personal introductions. Projects are assessed on real signals — users, engagement, product metrics, on-chain activity, developer growth — and gain access to ecosystem resources automatically when they meet clear criteria. Verified project profiles give communities and investors a data-backed picture of what is being built and how it is progressing.

For communities

Recognition of collective impact. A community's reputation reflects the aggregate contribution of its members, giving active groups visibility and influence. Strong communities can participate in resource allocation, helping direct ecosystem attention to where it matters most.

For committees

A shift from gatekeeping to governance design. Instead of reviewing every project and making individual decisions, committees define the rules, criteria, and thresholds — and the platform executes. This frees committees to focus on strategy, policy, and ecosystem direction while ensuring that every decision is transparent and auditable.

For the ecosystem

Automated pipelines that scale without headcount. Frictionless SBT issuance that turns every event and milestone into a verifiable credential. A unified trust layer that connects people, projects, and communities around a shared goal — technology adoption. Resources and attention flow to the best contributors and projects, transparently and effectively.

8. Architecture Overview

Identity is designed as a modular, open platform with seven layers:

Signal Layer

Collects data from external sources — GitHub, Telegram, TON blockchain, social platforms, event systems, and other integrations. Normalizes raw signals into a unified format for downstream processing.

Validation Layer

Validators — code-based, AI-based, and human — review and verify the quality and relevance of incoming signals before they enter scoring. (See Section 4: Validators for details.)

Evaluation Engine

Applies rule-based scoring to validated signals. Determines the reputation score for each person, project, and community according to transparent, versioned algorithms.

Identity Layer

Verified profiles for people, projects, and communities. Public information about contributions, reputation scores, and credentials — accessible to anyone in the ecosystem.

Access Layer

Connects reputation to ecosystem benefits — grants, support programs, jobs, mentorship, and recognition. Access is determined by contribution and reputation, not personal connections.

Governance Layer

Community-driven decision-making powered by reputation. Contests, hackathons, community votes — such as "project of the month" — where contributors select the best using reputation as a weight. Enables the ecosystem to allocate resources through transparent, collective judgment.

API Layer

Open APIs and SDKs that make platform data transferable and verifiable by external products and services. Identity also provides an MCP (Model Context Protocol) interface, making the platform AI-friendly and enabling developers to build intelligent tools, agents, and applications on top of Identity data. The goal: an open, digitalized platform that others can extend.

9. Platforms

Identity will be available across multiple platforms to meet users where they already are.

Web

The primary interface — a full-featured website for managing profiles, exploring the ecosystem, viewing reputation scores, and accessing all platform functionality. Available at identityhub.app.

Telegram Mini App

A lightweight application inside Telegram, where most of the TON community already communicates. Users can check their reputation, browse projects, vote in governance programs, and interact with key platform features — without leaving the messenger.

Mobile Apps (iOS & Android)

Native mobile applications focused on event experiences. Designed for organizers and attendees: distribute and collect SBTs via NFC, check in with your Identity profile, and discover who is at the event — all from your phone. A companion for conferences, hackathons, and meetups.

10. Use Cases

Identity enables concrete applications that address real gaps in the ecosystem today.

Job Portal

Projects need experienced people from the ecosystem — developers, designers, marketers — but discovery is fragmented and relies on personal networks. Identity replaces this with a talent platform where projects search for contributors by verified skills and track record, and candidates apply using their Identity profile. Instead of a resume, you show what you have actually built, contributed, and achieved.

Freelance Marketplace

Many people with ideas and resources lack the technical skills to evaluate blockchain developers. Without understanding smart contract development, it is difficult to assess quality, experience, or reliability — and the market has no shortage of bad actors. Identity solves this by surfacing verified development track records. Clients can review a developer's contribution history, reputation score, and peer endorsements before engaging — reducing risk and building trust.

Product Launch Program

A Product Hunt-style program for the TON ecosystem. Contributors with verified reputation vote on the best new projects — for example, in a recurring "Launch of the Month" format. Winners receive endorsement and marketing support from ecosystem partners, including the TON Foundation. This gives quality projects a transparent path to visibility, driven by community judgment rather than committee selection.

KOL Discovery

Projects frequently ask: "Who are the best KOLs in the ecosystem? Can you connect us?" Today, this requires personal introductions from ecosystem teams. Identity makes KOL profiles discoverable — sorted by reputation, reach, and verified activity. Projects can find relevant KOLs directly, understand their strengths, and connect without intermediaries.

Mentorship Matching

The ecosystem has many experienced mentors, but their capacity is limited — they cannot help everyone. At the same time, many projects do not even know that someone could help them with a specific challenge. Identity bridges this gap by matching projects with mentors based on reputation, expertise, and relevance. Mentors choose where to invest their time based on verified project data, and projects find the right guidance without relying on luck or connections.

Telegram Verification

Telegram supports third-party verification badges for accounts. Identity can act as a verification provider — automatically granting a verified badge to ecosystem participants who reach a certain reputation threshold. This brings trust signals directly into the communication layer where most of the TON community already operates, making reputation visible without leaving the messenger.

These are just a few examples. The beauty of a trust layer is that it can solve a wide range of problems across the ecosystem — many of which we have not yet imagined. As the platform matures and the community grows, new use cases will emerge naturally on top of Identity's open infrastructure. This list alone makes clear that a verifiable reputation platform is not a nice-to-have — it is essential for the ecosystem to scale.

11. Roadmap

Identity is built around four major phases. There is no strict timeline or fixed order for launching individual features — the product evolves organically as the ecosystem demands. The general direction is from foundational infrastructure to applications and governance.

Identity Phase (In Progress)

A working trust layer that produces meaningful, verifiable scores. Verified profiles for people, account linking (GitHub, Telegram, TON wallets), signal collection, validator infrastructure, and the initial reputation scoring engine.

Project & Community Phase

Extend reputation to projects and communities. Launch the SBT issuance platform — enabling frictionless credential distribution. Expand signal sources to cover on-chain activity, community engagement, marketing, and events.

Access Phase

Bring the platform to life through concrete applications built on top of the Identity and Project & Community Phases: ecosystem jobs marketplace, Project Launch Program, verified developer marketplace, KOL discovery, and mentorship matching.

Governance Phase

Community votes, contests, and resource allocation driven by reputation. Open API and SDK for ecosystem partners. MCP integration for AI-native applications. The end state: an open, digitalized platform that anyone can build on.

12. Why Now

Building a system like Identity has historically been impractical. Meaningful reputation requires processing a large volume of heterogeneous signals — code, on-chain activity, community participation, content, events — and weighting them in a consistent, reproducible way. Until recently, this would have required large teams, significant funding, and continuous manual oversight.

The emergence of AI changes this constraint. Modern models make it possible to classify, validate, and contextualize ecosystem signals at scale — dramatically reducing the cost and complexity of evaluation. Tasks that once required human review can now be automated, audited, and versioned, without sacrificing accuracy or transparency.

At the same time, the ecosystem itself has matured. There is now sufficient activity, signal density, and demand for fair resource allocation for a trust layer to be meaningful. As ecosystems grow, expectations shift: contributors expect transparent criteria, projects expect efficient access to resources, and communities expect decisions to be explainable and auditable.

Identity emerges at the intersection of these shifts. AI makes large-scale evaluation feasible; ecosystem maturity makes it necessary. Together, they enable a trust layer that was previously too expensive, too complex, or too early to build.

13. Open Questions

Identity is an evolving platform. Several important questions remain open:

• Privacy vs. transparency. How much data should be public by default? How do we balance verifiability with the right to control what is shared? Not every participant will be willing to publicly link their wallets — yet on-chain activity is critical for accurate reputation scoring.
• Reputation token. Should the platform introduce a token that represents reputation on-chain? How would it relate to the reputation score — and how do we prevent it from becoming a tradable commodity that undermines the integrity of the system?
• Relationship with TON ID. Should Identity replace TON ID as the ecosystem's identity layer? If the community supports this direction, a governance vote could formalize a proposal to the TON Foundation for transferring TON ID assets and branding to the Identity platform.
• Decentralization path. Which components — scoring, validation, governance — should move on-chain, open-source, and at what stage of platform maturity?

These are not obstacles — they are design challenges we are actively working through with the community.

Conclusion

Ecosystems grow when trust scales with them. Identity builds the infrastructure to make that possible — replacing opaque, manual processes with transparent evaluation, verifiable reputation, and open governance.

The core principle is simple: contribute first, earn access second. Let the work speak for itself. Let the community verify it. Let the platform direct resources to those who have earned them — not to those who know the right people.

Identity is not just a scoring system. It is an open platform — for people, projects, and communities — with validators, SBTs, governance, and an API layer that anyone can build on. It is designed to grow with the ecosystem and to be extended by it.

The TON ecosystem deserves a trust layer that is open, auditable, and fair.

Identity is that layer.

This document is a living whitepaper. It will evolve as the protocol develops and the community provides feedback. For the latest updates, visit identityhub.app.