Lets White Paper 2026

Status: updated draft
Last updated: 2026-05-21
Source manuscript: primary Russian manuscript
Primary language: RU; EN is a parallel rendering
Audience: users, creators, partners, investors, community participants
Positioning: a social network with a community participation layer and an external protocol layer
Historical bridge: from DAC and a token-first framing — to a social-first Lets, Glints, DAO, and the external LEC protocol layer

This document is informational and describes a direction of product development. It is not an offer to sell tokens, investment advice, a promise of token value, or a commitment that any feature, payout, settlement, wallet, or protocol access will be available in any jurisdiction.

Executive summary
Origins: how Lets began
What we learned while building it
What Lets is today
The mobile layer: social core, Glints, and Decisions
Contribution, reputation, and community participation
The role of LEC and the external protocol layer
DAO, community helpers, and governance
Creator economy, monetization, and settlement
AI-native direction
Public site, White Paper, and Portal
Where we are going next
Closing

1. Executive summary

Lets began as a bet: that a social network can be built more honestly. The first version of this document said it in the language of that moment — LEC, digital value the user has a right to, and a community that shapes the platform. Those ideas are still here. What has changed is the order in which we put them in front of people.

In real product work it quickly became clear: a product that starts with a conversation about a token loses the ordinary person on the first screen. People come back to a social network not for an abstraction, but to read, reply, share, and see what is new with the people close to them. Without that, no economy will hold them. With that, you can build participation, community responsibility, and a deeper layer around it.

So today Lets starts with the social core: feed, stories, chats, profiles, search. That is what a user sees first. As participation grows, Glints open (a way to say thank you when something was actually useful), then Decisions (where every account has one vote), then reports on what we are doing next, then creator tools. Deeper down sits the external LEC layer, where we work on scenarios for creators, partners, and the ecosystem.

The main shift is that we have separated two layers:

Glints live only inside Lets as internal in-app virtual items and exist so a person's contribution does not pass unnoticed. They are not cryptocurrency and not a claim on anything. They have no rate, cannot be sold, withdrawn, exchanged, redeemed, or converted into LEC, and do not create any present or future entitlement to LEC or any other asset.
LEC is a separate external layer for settlements, alignment between creators and the ecosystem, and future web scenarios. It does not appear on the first screen of an ordinary user.

This boundary matters for two reasons. First, it keeps the product understandable: Glints live in ordinary words — "thank you", "useful", "noticed". Second, it gives LEC a precise role — it works where that role is legally, technically, and product-wise appropriate.

This document is about how Lets is built now and where it is going. Social product at the center. Glints as a visible form of participation. Decisions as a voting format. DAO as an accountability frame. LEC as an external layer. The site and the portal as a bridge between the ordinary user and the people who want to look deeper.

2. Origins: how Lets began

Lets grew out of a simple thought: a social network can be built differently. Not as a closed system where the person is only the audience, but as an environment where the user has rights — to know what happens with their data, to see their own contribution, to shape the rules of the community they help build.

In the early edition of the White Paper this was described as a decentralized social network in which content, communication, advertising, and community participation were tied together by a shared economy. That is where LEC came from — as a way to give the user a share in that economy — together with Proof of Contribution as an idea for measuring contribution and DAC as an early frame for community governance.

That document had many ambitious ideas: shared infrastructure for participation, a clear way to distribute digital value, a more honest attention economy. Those ideas have not disappeared. They became more precise once they met real engineering, the rules of App Store and Google Play, the way users actually read an interface, legal constraints, and the need to build a product people use rather than only an architectural description.

So the new edition of the White Paper does not cancel the earlier one. It clarifies it. The goal is the same. The order has changed: first an understandable social product, then participation, economy, and the external layer.

3. What we learned while building it

The main product lesson is simple. If a social product cannot be understood in the first session, no economy and no reward system will save it. Complex architecture has meaning only when there is a product on top of it that people want to come back to.

The early approach — start with a token — carried a strong idea, but it built the entry through explanation. The user had to figure out the system before being able to feel its value. For a mass audience that is too heavy a first step.

The second lesson is about app stores. App Store and Google Play require a careful separation between in-app digital goods, virtual items, payments, blockchain scenarios, and external settlements. So Lets cannot show the same economic layer in every environment. The mobile app has to be understandable, safe, and compatible with the store rules. Deeper scenarios live separately, with legal review of who can access them and the explanations that go with them.

The third lesson is about DAO. Community governance should not start with terminology. For an ordinary person, the important questions are simpler: what are we choosing, why now, what happens next, and who is responsible. So the first interface layer talks about Decisions, Contribution, and Community helpers. The user experience does not require knowing the word DAO — that word stays in the language of strategy and the protocol layer.

The main conclusion: Lets becomes stronger not because it gives up depth, but because it stops showing all of that depth at once.

4. What Lets is today

Today Lets is first of all a social product. The main value is not in the token and not in the governance system, but in the fact that inside Lets people have a feed, stories, chats, profiles, and search — enough to stay in touch and come back every day.

The basic social core includes:

the feed — for everyday reading and returning;
stories — a short format;
the profile — identity and a history of activity;
search and collections — a way to find people and topics;
chats — personal one-to-one conversations and group chats;
notifications — one place where you see what happened;
the social circle — follows, friends, and privacy settings.

On top of that foundation a second layer appears: Glints, Decisions, reports on next steps, creator support, and the link to the external layer. That layer strengthens the social core but does not replace it.

If you have to describe Lets in one line:

Lets is a social network where ordinary conversation sits at the center, and a person's contribution does not disappear in the feed.

This wording matters because it can be explained without blockchain vocabulary. A person comes to Lets as a social app. If they stay, Glints, contribution history, Decisions, community helpers, creator tools, and — later — the external LEC layer gradually open up.

The mobile Lets has to stay simple for a first encounter. So in the public beta we build only the layer that fits inside the rules of App Store and Google Play:

Glints — a sign of thanks and attention inside Lets;
Contribution — what you have done in the community;
Decisions — community votes;
Support — where to write when something has gone wrong;
Community helpers — people who carry topics and gather discussion;
activity history — where you can see what you did inside the app.

Glints are internal in-app virtual items that live inside the Lets beta. You can use them to thank a person for a useful post, support a reply, or notice a contribution in a discussion. They are not money or cryptocurrency, have no in-app market price, and are not sold, withdrawn, exchanged, redeemed, or converted into LEC. Beta Glints do not create any present or future entitlement to LEC or any other asset.

This choice is made both for legal reasons and for the sake of clarity. To use Glints, a person does not need crypto terminology — ordinary words are enough: "thank you", "useful", "noticed".

Decisions are a short voting format inside Lets. They work as a social and product process:

what we are discussing;
what the options are;
how to vote;
what the community chose;
what we are doing next;
who is responsible for it.

In Decisions every account has one vote. You can place Glints next to a topic to show that it matters to you, but Glints do not change the outcome, vote weight, percentages, quorum, or access to features. This is a basic boundary: support does not buy influence.

In the mobile Lets we do not start with financial language. We start with the social experience. Glints and Decisions open as a continuation of participation, not as a separate financial layer.

6. Contribution, reputation, and community participation

One of the central ideas of the next stage of Lets is to make a person's contribution visible.

Contribution in a social network is not only publishing. A person can answer someone's question, support a friend, help moderate a discussion, vote in a Decision, or report a problem. All of that is participation that today usually disappears in the feed.

Lets gathers that picture into something readable:

what you did;
which Glints you received and for what;
which Decisions you took part in;
which discussions you led or supported;
which ideas you helped move forward.

For the user, this should not look like a financial statement or a governance dashboard. It should read as a simple personal story:

Here you can see how you take part in Lets: what you wrote, what you replied to, who you supported, and how you voted in Decisions.

Inside the system this can develop further: measure the quality of contribution, defend against farming, tie into future distribution mechanics. But the first layer has to stay human. You do not need to explain ledger logic, scoring, or tokenomics where a person only wants to understand why their action was noticed.

This model matters strategically. It separates Lets from projects where participation is mechanical farming for points. In Lets, contribution is tied to real value for people: a real conversation, a useful answer, a notable idea, calm moderation.

7. The role of LEC and the external protocol layer

LEC keeps an important role in Lets, but that role has become more precise.

In the early model LEC tried to describe almost the whole system of participation and value distribution — from an ordinary user action to deep ecosystem coordination. In the current model LEC does not have to cover the whole product. It lives in the external layer, where the work is about settlements, alignment between participants, and scenarios that need a separate frame:

settlements with creators and partners;
distribution logic and treasury operations;
external operations through third-party wallets;
access to web scenarios that need legal review;
cryptographic protocol proofs;
future DAO and ecosystem coordination;
alignment between creators, participants, operators, and the network.

The key principle:

LEC is not the first language in which the mobile app speaks to a user. It is the external layer for scenarios where that role is legally, technically, and product-wise appropriate.

This boundary makes the structure clearer. LEC no longer carries the whole meaning of the product. It stays as an external protocol asset that works where there is a reviewed context.

So Glints and LEC stay separated:

Glints — the internal participation layer of the mobile app;
LEC — the external protocol layer;
there is no automatic conversion between them;
the public beta does not create expectations of withdrawal, market price, or a claim on a token.

In the future LEC may matter for the creator economy, protocol governance, settlements, treasury, external wallets, cryptographic proofs, and ecosystem access. But these scenarios open through a separate web / protocol layer, not through hidden complexity in the mobile app.

8. DAO, community helpers, and governance

Community participation has been part of Lets from the very start. At the early stage that idea was described through DAC. In the current and future model we use DAO, but it matters how.

DAO in Lets is not a decorative term, and it is not a way to turn the interface into a voting console. It is a set of clear ways to formulate proposals, discuss changes, vote, see accountability, and track execution.

In the mobile and public layer this idea opens through simpler concepts:

Decisions;
Suggest an idea;
What happens next;
Public history;
Community helpers;
Reports.

In the beta, the DAO of Lets works as a flexible consultative model of participation. That means:

the community discusses and votes;
the result is an important signal for the team and for the community itself;
execution during the beta stays with the operator where safety, resources, legal review, or infrastructure access are required;
every action leaves a public trail: what was decided, who is responsible, when it was updated, what has been completed.

Before a vote, a proposal passes a readiness check: what is changing, why now, what resources are needed, who is responsible, what the expected outcome is, what risks and trade-offs are involved, and how we plan to do it. Without that, the proposal stays a topic for discussion, not a full Decision.

Community helpers are an important part of this model. They do not replace voting and do not get an automatic right to govern the platform. Their job is to help ideas become understandable, support discussion, check readiness, prepare reports, and make sure the result of a vote does not dissolve without explanation.

This DAO layer does not promise, in the beta, automatic execution through smart contracts, token-weighted voting, or treasury management without the team. It builds a more mature institutional model of participation: understandable for people, verifiable for the team, and extendable for the future protocol layer.

Operator-only and future protocol governance paths may contain staking, snapshots, weighted voting, and other technical mechanics, but they live outside the store-safe mobile Decisions model and must not leak into vote weight, quorum, or vote outcomes visible to a user.

9. Creator economy, monetization, and settlement

The economy of Lets should not start with a token. It should be built around sustainable product value.

The first task of the economy is not to create a speculative story around a token, but to build sustainable flows inside the product:

creator tools;
paid distribution for publications;
promotion and boost;
advertising;
support and subscription tiers;
a history of earnings;
settlements and payouts;
review, holds, anti-fraud, and reversals.

Any paid digital services inside the mobile app — boost, promotion, subscriptions, creator perks — use Apple and Google billing, unless a separately approved program or a jurisdictional exception applies. External web settlements and creator payouts must not be advertised from the mobile app as a way around store rules.

Creators have to understand what they receive and why. Advertisers have to understand what they pay for. Users have to understand that Glints inside the public beta are not money, a claim on a token, or a way around store rules.

In the working model we separate:

internal participation signals;
creator income;
advertising budgets;
platform income;
treasury and ecosystem distributions;
external settlements.

Any future payouts, earnings, and settlements go through a ledger, review, holds, and legal-compliance checks. That is required for trust, safety, anti-fraud, and long-term resilience.

For paid promotion and boost, the working economy counts value not by the gross payment, but by the verified net amount after store fees, taxes, refunds, chargebacks, and reserve holds. Mobile digital payments go through app-store billing with explicit rules for merchant-of-record, country availability, and reconciliation.

In this model LEC may be tied to participant alignment, settlements, creator and ecosystem participation, and protocol coordination. But the launch must not depend on speculative growth of a token price. Lets has to earn as a product, not as a promise of a future market price.

10. AI-native direction

AI in Lets is not decoration but a product instrument.

The first clear scenario is automatic translation of posts into the language of the user's device. For a social network this is not just a convenience. It is a way to remove the language barrier, broaden who a person can read, link local communities, and make publications reachable beyond one language environment.

AI can also strengthen other parts of the product:

short summaries of long discussions;
help with drafting proposals for Decisions;
translation and adaptation of public community reports;
moderation assistance;
detection of spam, farming, and reward abuse;
a clear explanation of why an action was counted as contribution.

But AI must not replace the social experience. It should help a person understand what they are reading, take part more safely, and move more easily between languages, formats, and the contexts of different communities.

For Lets, the AI direction is tied not to marketing fashion but to reach across languages, accessibility, and quality of participation.

11. Public site, White Paper, and Portal

The next web layer of Lets has to do three different jobs.

The public site is for orientation and conversion. It quickly explains Lets as an understandable social product with a deeper ecosystem layer:

what Lets is;
why this is not just one more social network;
what Glints are;
how contribution works;
what Decisions are;
the role of the community;
where the protocol layer appears;
why LEC exists;
how to read the White Paper;
how to join the beta.

The White Paper is for depth: it explains the strategy, the history of changes, the role of Glints, LEC, DAO, the creator economy, the AI direction, and the web / protocol layer.

The Portal is for role-based operations and public accountability. It is not a presentation page. Inside the Portal separate surfaces may appear:

Creator Portal — for creators and monetization;
Decisions Hub — for Decisions, contribution, and the public execution history;
Operator Area — for workflows, support, and reporting;
LEC Zone — for verified participants and future scenarios with settlement and external wallets.

The Portal opens in stages. v0 is read-only: a creator panel, a history of contribution, a Decisions execution tracker, and community-helper reports. v1 adds creator and community panels. v2 opens role-checked operations. Deeper scenarios (LEC, wallets, settlements, treasury, cryptographic protocol proofs) live in a separate zone with legal review.

Access checks may include the role of the participant, jurisdiction, legal compliance, and specific features. By default an ordinary user sees explanatory, read-only content.

It matters that the mobile app does not become a door into crypto operations. The mobile side stays simple and store-safe. The site and the Portal explain and reveal the depth for the people who need it.

Mobile builds distributed through app stores must not contain calls to action, deep links, web views, redirects into an external browser, or sign-in scenarios that take the user to LEC, external wallets, settlements, token purchase, or off-platform digital purchases.

This web layer becomes the bridge between the mass-user product and the long-term protocol intent.

12. Where we are going next

The next stage of Lets is not a return to the old token-first framing. It is a movement towards a mature system in which the social core, Glints, contribution, Decisions, the creator economy, DAO, and the protocol layer work together.

The near-term directions are:

Strengthen the mobile social core — feed, stories, profile, search, chats, notifications, privacy, and safety.
Finish public-beta QA so that the product is stable, understandable, and store-safe.
Bring the product to a state ready for a public launch: reliability, moderation, safety, analytics, user support, operating processes, and clear release criteria.
Develop Glints as an internal participation layer — without mixing them with LEC.
Make the user's contribution visible through the profile, the activity history, and the contribution pages.
Strengthen Decisions through an execution tracker: what was decided, what we are doing next, what is already done.
Bring community helpers and working groups into a clear layer of public accountability.
Prepare the public site and the White Paper as the main project presentation.
Build the web Portal for creators, communities, and role-based scenarios.
Develop LEC as an external protocol layer for settlements and participant alignment.
Add AI features, starting with automatic translation.

The goal of this stage is to make Lets understandable for a broad audience and deep enough for the people who want to take part in the development of the network at a higher level.

13. Closing

Lets began as an attempt to assemble a new kind of social network: more honest towards a person, clearer in how participation works, and more serious in how it handles digital value.

The goal has not changed. What has changed is the maturity of the project. Lets no longer explains itself only through a token or abstract decentralization. Its strength is that there is a social core around which Glints, contribution, Decisions, community helpers, the creator economy, AI features, and the external protocol layer gradually appear.

The new model does not abandon the original intent. It makes that intent buildable.

The ambition remains large — not simply to add a layer of rewards to a social app, but to change the very link between a publication, participation, trust, and digital value. The difference is that this ambition now starts not with an abstract economy, but with a product people actually use.

First a person discovers an understandable social product. Then they notice their own contribution. Then they vote in Decisions. Then public reports appear: who is responsible, what has been updated, what has been done. And only after that does a deeper level open up: creators, settlements, LEC, treasury, cryptographic proofs, and access to the protocol.

That is how Lets can become not yet another app and not another token story, but a mature social environment where people's participation gradually turns into a visible, verifiable, and useful part of a shared system.