Who decides the status of a disputed .sol name?

Primary question: Who decides the status of a .sol name that has been reported or marked as stolen, suspicious, frozen, blacklisted, or disputed, and where can holders read that process?

One of the affected names used as the primary public example in this record is chris.sol, previously held by Chris McNicholas. Publisher disclosure is in the status panel.

This record asks for process clarity, not liability decisions or individual dispute resolution.

Relevant parties: SNS for the current .sol process. Solana Foundation and D3 for future namespace clarification.

Record status

Record ID: QFS-001
Record state: Open
Subject: Disputed .sol name status
Published: 4 June 2026
Last updated: 6 June 2026
Days open: —
Public answer status: Awaiting public answer
Public answer: No substantive public answer listed
Publisher disclosure: The publisher, Chris McNicholas, is known in the Solana ecosystem as Chris.sol / @chrisdotsol and has a disclosed personal and financial interest in this record. The record is framed as a public process question and remains open to correction, clarification, right of reply, or public answer.

TL;DR

Some .sol names have been reported or marked as stolen, suspicious, frozen, blacklisted, or disputed.
One public example is chris.sol, visible on SNS at sns.id/domain/chris. As observed on 4 June 2026, the operator label read "Blacklisted: Suspicious behavior detected."
No published process for deciding or resolving that status was found in public SNS, marketplace, or Foundation-facing sources reviewed for this record.
D3 has publicly stated that it and Solana Foundation are applying for .SOL and .SOLANA. The public record does not say what, if any, relationship existing .sol names have to that route.
Record state: open. Public answer status: awaiting public answer. No published process identified.

What would count as an answer?

A substantive answer would clarify: the current forum and published process for disputed or blacklisted .sol names; who holds authority over those status labels; how affected users and later buyers are treated; whether there is any review or appeal route; and whether existing .sol names have any planned relationship to future .SOL or .SOLANA routes.

Public record / finding

Solana Name Service, or SNS, operates the existing .sol identity layer.
Sources reviewed for this record included public SNS domain pages, marketplace-facing status information, public Solana Foundation-facing materials, and the public sources listed below. No published disputed-name process was identified as of 4 June 2026.
The question is narrow: who is the forum for disputed .sol names, what process applies, and how status-affected names are treated if any future namespace route relies on existing names?

Namespace uncertainty

The relationship between existing .sol names and any future .SOL or .SOLANA route is not stated publicly. If there is no relationship, holders should be told existing names carry no rights into it. If there may be one, status-affected names need a readable process before that relationship affects holders. If the plan is undecided, that can be said.

Scope and limits

This record does not claim that Solana Foundation is responsible for SNS or for current .sol status decisions. It does not ask the Foundation or D3 to decide an individual dispute.

The current .sol status-process question is first for SNS. The Solana Foundation / D3 question is limited to future-route clarification: whether existing .sol names have any intended relationship to any future .SOL or .SOLANA route.

Strongest contrary view

The strongest contrary view is that SNS and any future .SOL / .SOLANA application are separate systems; that SNS alone controls current .sol status decisions; and that neither Solana Foundation nor D3 has any present duty to address an SNS-operated status dispute. This record does not ask readers to reject that possibility. It asks whether the relevant parties will clarify the current process and, separately, whether any future relationship exists or is planned.

What resolution would look like

First, identify the correct forum for disputed .sol names today. If that forum is SNS or another operator, say so and publish or point to the process.

Second, if Solana Foundation and D3 have no role in current .sol disputes, say so and, if known, point users to the correct forum.

Third, if a future .SOL or .SOLANA route proceeds, state whether existing .sol names are unrelated to it, whether the relationship is undecided, or whether some relationship is planned.

Sources

The claims above rest on public sources and dated observations. Public items are linked where available.

SNS public domain page: chris.sol was visible on SNS at sns.id/domain/chris. As observed on 4 June 2026, the operator label read "Blacklisted: Suspicious behavior detected."

D3 / Solana Foundation namespace announcement: D3 publicly stated that D3 and Solana Foundation are together building infrastructure to bridge Web2 and Web3 domains on Solana, including applying for .SOL and .SOLANA. Public source: PRNewswire

Doma Protocol source: Doma describes its protocol as bridging Web2 domains with Web3 and tokenized domains across Web2 DNS infrastructure and Web3 ecosystems including Solana. Public source: doma.xyz/protocol

SOLANA trademark reference: public trademark records list SOLANA as a Solana Foundation mark. Public source: Justia trademark record

ICANN 2026 New gTLD Program application round: application submission period opened 30 April 2026 and closes 12 August 2026. Public source: ICANN

Update log

4 June 2026: QFS-001 published as first release.
5 June 2026: TL;DR and answer criteria added. No change to the substantive question.
6 June 2026: Layout and navigation updates. No change to the substantive question or finding.

Right of reply / corrections

This record remains open to response.

Any party referenced in a published question is invited to respond. Corrections, clarifications, and substantive replies will be reflected accurately where appropriate.

Email and the Respond page are both available for corrections, clarifications, and right of reply.

Project updates are distributed through X and the Telegram channel.

Suggest an update to this record. You do not need to be named in this record to suggest an update. If you have seen a public answer, correction, source, or material development, you can send it for review.

Watch this record

Get notified if a public answer, correction, right of reply, or material update is added to this record.