Passei a última semana tentando entender como os domínios .night realmente funcionam. Não por uma ficha técnica, mas construindo algo

I spent last week trying to understand how .night domains actually work. Not from a spec sheet, but by building something that touches the chain directly. The result is a small profile viewer. You type in a name like tomin.night, and it resolves the profile straight from the blockchain. No registrar API. No auth wall. Just a smart contract and some JavaScript.

What follows is how it works, what I learned, and the two specific traps that ate my afternoon.

Why On-Chain Names Matter

On Midnight, .night domains are managed by Midnames. Instead of querying a company’s central server, you read directly from a smart contract that lives on the chain. The registry itself holds the domain, the owner, and whatever profile fields the owner attached. Because that data is on-chain, the identity is portable. You are not renting it from a platform that can change terms or pull the plug. If you control the keys, you control the name.

That shift matters for developers too. When you build against a traditional DNS system, you deal with rate limits, API keys, and uptime promises. Here, the contract state is the source of truth. Your application reads it the same way every other application reads it. There is no privileged API tier.

The Code Is Almost Too Simple

The @midnames/sdk handles the heavy lifting. Resolving a domain to an address and profile takes exactly two lines:

const provider = createDefaultProvider({ networkId: "mainnet" });
const result = await resolveDomain(provider, "tomin.night");

That is it. The provider targets the network, and the resolver talks to the contract. The SDK returns a result object that includes a success flag. If the domain does not exist, you do not need layers of error handling or try-catch blocks around RPC failures. The SDK tells you cleanly that nothing is there. This makes building UIs surprisingly pleasant. You can branch on the success flag and show a “not found” state without guessing whether the failure was a missing name or a dead node.

What You Get Back

When the lookup succeeds, the payload contains two pieces that matter.

Target is the wallet address the domain points to. This is the core utility. It turns a long hex address into something a human can read, type, and remember.

Fields hold the profile details. Whatever the owner attached to the domain—social links, avatars, text records—lives inside this structure. These fields are not stored on some company’s MongoDB cluster. They are fields in the contract state, which means any app that knows how to read the registry can render the same profile. No database sync required.

Two Traps That Slowed Me Down

Not everything about the build was two lines and a success flag. I hit two specific hurdles that are worth spelling out so you do not repeat them.

Network Mismatch

The SDK supports both mainnet and preprod environments. I spent a solid chunk of time debugging a domain that “did not exist.” The name was correct. The code looked right. The provider was running. The problem was that my script was querying preprod while the domain itself was registered on mainnet. The error looked like a missing domain, but it was really a missing network context.

If you are resolving a name and getting back a failure, check the provider settings before you debug anything else. Make sure your networkId matches the network where the domain is actually minted. This is the kind of mistake that feels obvious in retrospect but is genuinely hard to spot when you are assuming the contract logic is the issue.

Serialization Pain

The data that comes back from the SDK is not standard JavaScript. It contains BigInt values and Map objects. If you try to pipe that straight into JSON.stringify to send it to a browser, it will throw or silently drop data. BigInt has no native JSON representation, and Map does not serialize the way plain objects do.

I ended up writing a custom serializer. It walks the result object, converts BigInt values to strings, and transforms Map instances into regular objects before the response leaves the server. If you are building an API that serves Midnight data to a frontend, plan for this step early. Do not assume the SDK output is immediately frontend-friendly just because it is JavaScript.

The Architecture

Mantive a stack deliberadamente simples. O backend é um servidor Node rodando Express. Ele importa o @midnames/sdk, executa a lógica de resolução, lida com as acrobacias de serialização e serve um JSON limpo. O frontend é HTML puro e vanilla JavaScript. Sem etapa de build. Sem framework. Sem adaptador de carteira.

Escolhi rodar o SDK no backend em vez do navegador por alguns motivos práticos. Isso mantém qualquer configuração de provedor fora do cliente, me dá um único lugar para corrigir a bagunça da serialização e significa que o frontend só precisa buscar os dados e renderizá-los.

Aqui está a parte que mais me surpreendeu: resolver um nome é uma operação de leitura pública. Você não precisa de uma conexão de carteira. Você não precisa de uma assinatura. Você não precisa que o usuário faça login com nada. Se o domínio existir, o estado do contrato é visível para qualquer pessoa que solicitar. Essa é uma diferença significativa em relação ao fluxo típico de web3, onde cada interação começa com “conectar carteira”. Ler a identidade na Midnight não requer permissão, da mesma forma que ler um site público não requer permissão.

A Principal Lição

Construir este visualizador me lembrou que a parte mais difícil do desenvolvimento de blockchain raramente é a blockchain em si. A Midnight já resolveu o problema difícil: permitir que as pessoas sejam donas de seu nome e perfil sem um banco de dados central. A parte difícil, do ponto de vista de um desenvolvedor, foi lembrar em qual rede eu estava apontando e escrever uma função auxiliar para limpar os tipos de dados.

O protocolo oferece uma identidade portátil. Seu trabalho como desenvolvedor é simplesmente lê-la corretamente e não atrapalhar o usuário. Mantenha a arquitetura simples, separe a lógica voltada para a rede da UI e trate as leituras públicas como o que elas são: consultas comuns de banco de dados que, por acaso, residem em um registro distribuído.

Se você quiser ver o código ou executá-lo você mesmo, o código-fonte completo está disponível em https://github.com/tomiin/midnames-profile-viewer.