Frequently Asked Questions

Atlas is a peer-to-peer protocol for publishing, discovery, identity, trust, and governance — shared infrastructure instead of rented land.

No single company owns your account, audience, or ranking logic. Atlas splits those into open layers that any app can build on.

Identity lock-in, invisible content, fake accounts, platform-controlled discovery, weak security, and extreme centralization — the internet still bundles all of these together.

Atlas makes accounts, data, discovery, trust, and governance contestable instead of privately controlled.

No. Atlas avoids forcing all data through one global chain.

It is a structured P2P protocol with typed envelopes, specialized registries, trust, governance, and incentives — built around real application needs.

No. Atlas solves infrastructure problems first: identity, discovery, trust, storage, and governance.

FairShares coordinate usage, visibility, and incentives — not speculation.

No. There is no global mining race.

Atlas can use bounded proof-of-work for anti-abuse, but that is very different from chain-wide competition that secures the whole system through continuous waste.

The internet's core data problem has three inseparable parts: gate-keeping, lack of interoperability, and lack of user ownership. Solving only two of three is useless — the unsolved part undoes the other two.

Each Atlas pillar exists because the dependency chain demands it. Anti-gate-keeping needs incentives and user-centric storage. Interoperability needs shared semantic schemas. Ownership needs local or trusted hosting. Trust needs governance. Fair governance needs decentralization. Decentralization needs cryptography and sybil resistance. Remove any piece and the whole structure collapses.

It may seem like too much, but it is actually the minimum viable scope to solve internet enshittification — split into decomposable, understandable parts.

• Gate-keeping — needs incentives, punishment for non-compliance, and user-centric storage
• Interoperability — needs Schema.org semantics and JSON-schemas as standard data skeletons
• Ownership — needs local hosting or trusted redundant shelters
• Trust and economy — need governance; fair governance needs decentralization
• Decentralization — needs cryptography, signatures, and registries collecting proofs to derive objective truths
• Neutral discovery — needs identity verification, sybil resistance, and rate-limiting

Read the full argument →

No. Your strongest key stays in secure hardware or with a custodian.

Apps receive delegated keys with limited permissions and expirations — temporary power, not permanent control.

Much less damage than with classic wallet-style access. Delegated keys are short-lived, narrow, and revocable.

A leak is still bad, but not the same as losing full authority over your identity.

Multiple layers, not one trick. Transport friction stops cheap abuse; identity and trust layers make mass attacks easy to filter.

Delegated keys reduce phishing pressure — apps never need your strongest secret.

• Bounded proof-of-work and rate limits for cheap abuse
• Identity verification and trust signals for distinguishing real participants
• Delegated permissions so leaked app credentials are less catastrophic

No. Atlas supports strong identity context without a public real-name system.

Identity verification reduces abuse and duplication — it does not force you to expose your offline life.

For every legitimate user online, there are potentially thousands or millions of malicious or spammy ones — and distinguishing them is inherently hard. Only the most competent peers can do it well, which means some centralization of competence and some data retention is unavoidable.

The alternatives are worse: fully decentralized spam-fighting re-centralizes into whoever coordinates the signals, or you end up with opaque, incoherent moderation. Atlas accepts the trade-off and makes it legible — who verifies, what proofs are worth, and how much data is retained, all decided by the network.

How identity verification works →

No. Most users just use apps without becoming operators.

Running a node gives you more control over storage, reads, and discovery.

Stronger data control, storage contribution, network availability, and protocol-native rewards for useful work.

Infrastructure is not charity — nodes earn real reasons to stay online.

Specialized registries and storage roles — not one giant company database. Different parts of the network store and serve different kinds of data.

Useful data stays online because nodes have trust and economic reasons to keep it.

By not forcing all data through one global chain. The network specializes by data type.

Less translation, less custom indexing, less app-side reconstruction than typical decentralized systems.

Atlas is not tied to one networking transport forever.

The protocol defines data shape, meaning, and verification — so transport can evolve without restarting the system.

No single platform. Discovery, indexing, and ranking come from competing registries — not one invisible global feed.

Users choose who they trust, and the rules are inspectable instead of black-box.

Partially. Clients can implement their own moderation policies, while registries can choose not to store certain envelopes — although that comes at the cost of smaller reach (due to lower accumulated totalBurn, which is the primary driver of discovery).

Verified users may also spend FairShares to counter-weight total burn spent on content promotion, while clients may choose to interpret that as moderation.

Lastly, users may allocate negative trust on bad actors, marking them as untrusted on a given topic for the long term.

By separating identity, data, discovery, and trust into competing roles instead of letting them collapse into one owner.

Discovery is a protocol concern, not a private app feature — so visibility cannot depend on one operator's invisible choices.

Not blind popularity. Atlas captures competence, reliability, and human legitimacy in a way software can use.

The network can weigh whose judgments matter for verification, discovery, and expertise — without pretending all opinions are equal.

FairShares are access credits — closer to a postage allowance than a financial asset. Everyone receives the same weekly amount, they decay when unused, although they can be traded within the network.

There's no investment thesis — just a resource-allocation mechanism that keeps the network running without ads or subscriptions.

A network with no friction gets filled by whoever can spam it hardest. Costs tie attention to real tradeoffs.

Mass abuse becomes expensive; creators and operators get clearer signals about what the network values.

Two layers. Hard rules live in code and are expensive to change. Softer rules live in signed Legislation that communities adopt, update, or fork.

The base protocol stays coherent without hard-coding every economic or social rule.

Money, visibility, and infrastructure control cannot stack into the same actor by default. Trust, discovery, governance, and storage are separable roles.

Equal FairShares issuance, explicit trust, and forkable governance make permanent monopolies harder to sustain.

The equal split of 100 trust allocations per cycle is not a mechanism to prevent centralization or to force it — it is a balance between the two. If the community feels stronger checks are needed and should be done by a few highly competent peers, they allocate trust to reflect that.

When a process drifts too far and the same names accumulate power across cycles, participants allocate negative trust on the top trusted peers. That starves concentrated authority and forces the process to decentralize again. The same tool that enables centralization provides the lever to reverse it.

How trust allocation works →

Social apps, marketplaces, identity tools, directories, knowledge graphs, moderation services, storage providers, and domain-specific registries.

Anything that needs durable identity, structured records, inspectable discovery, or contestable governance.

Much less than in most decentralized stacks. Protocol data stays close to what apps need — no rebuilding the read layer just to show a profile.

App-specific logic still exists, but repetitive infrastructure work is cut significantly.

Yes. Apps can bridge web experiences, import data, and integrate with legacy systems.

The core identity, data, and trust model does not stay trapped inside one company's database.

Only if the experience is meaningfully better — Atlas does not bet on ideology alone.

Safer identity, less phishing, fairer discovery, durable audiences, and apps that do not erase your digital life when you leave.