I spent last week trying to understand how .night domains actually work. Not from a spec sheet, but by building somethin

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

Nilifanya mfumo (stack) uwe wa kawaida kabisa kwa makusudi. Upande wa nyuma (backend) ni seva ya Node inayotumia Express. Inaimporiti @midnames/sdk, inatekeleza mantiki ya utatuzi (resolution logic), inashughulikia mambo magumu ya ubadilishaji wa data (serialization gymnastics), na kutoa JSON safi. Upande wa mbele (frontend) ni HTML ya kawaida na vanilla JavaScript. Hakuna hatua ya ujenzi (build step). Hakuna framework. Hakuna wallet adapter.

Nilichagua kuendesha SDK kwenye backend badala ya kivinjari (browser) kwa sababu kadhaa za kiutendaji. Inazuia mipangilio yoyote ya mtoa huduma (provider configuration) isiingie kwenye upande wa mteja (client), inaniwezesha kuwa na sehemu moja ya kurekebisha vurugu za ubadilishaji wa data (serialization mess), na inamaanisha kuwa frontend inahitaji tu kuchukua data na kuionyesha.

Hapa ndipo sehemu iliyonishangaza zaidi: kutatua jina (resolving a name) ni operesheni ya kusoma hadharani. Huhitaji kuunganisha pochi (wallet connection). Huhitaji saini. Huhitaji mtumiaji kuingia (log in) kwa kitu chochote. Ikiwa domain ipo, hali ya mkataba (contract state) inaonekana kwa yeyote anayeuliza. Hiyo ni tofauti kubwa kutoka kwa mtiririko wa kawaida wa web3 ambapo kila mwingiliano huanza na “unganisha pochi” (connect wallet). Kusoma utambulisho kwenye Midnight hakuhitaji ruhusa (permissionless), sawa na jinsi kusoma tovuti ya umma kunavyokuwa bila kuhitaji ruhusa.

Funzo Halisi

Kujenga programu hii ya kuonyesha (viewer) ilinikumbusha kuwa sehemu ngumu zaidi ya maendeleo ya blockchain mara nyingi si blockchain yenyewe. Midnight tayari imetatua tatizo gumu: kuwaruhusu watu kumiliki jina na wasifu wao bila kuhitaji kanzi data (database) kuu. Sehemu ngumu, kwa mtazamo wa mjenzi, ilikuwa ni kukumbuka ni mtandao upi nilikuwa unauelekeza na kuandika kazi msaidizi (helper function) ili kusafisha aina za data (data types).

Itifaki (protocol) inakupa utambulisho unaoweza kubebeka (portable identity). Kazi yako kama mendelezaji (developer) ni kusoma tu kwa usahihi na kutoingilia njia ya mtumiaji. Weka usanifu (architecture) uwe rahisi, tenganisha mantiki inayohusiana na mnyororo (chain-facing logic) kutoka kwenye UI, na chukulia kusoma kwa hadharani kama ilivyo: maswali ya kawaida ya kanzi data (database queries) ambayo tu yanapatikana kwenye daftari lililosambazwa (distributed ledger).

Ikiwa unataka kuona kodi au kuijaribu mwenyewe, chanzo kamili kinapatikana hapa https://github.com/tomiin/midnames-profile-viewer.