f.fomodeveloper docsopen app →

.fomo developer platform

build with names
the family remembers.

Resolve human-readable .fomo identities, read the public registry, surface marketplace listings and verify every paid claim with its Solana transaction proof.

NETWORKmainnet-beta RPC checking
LATEST SLOT—protected server RPC
REGISTRY— names database checking
CLAIM PRICE0.1 SOLone time · no renewal

01 · QUICK START

resolve a name in seconds.

The resolver is public, read-only and CORS-enabled. No API key or wallet connection is required.

cURL
curl https://dotfomo-names.oversmart.chatgpt.site/api/resolve/explorer.fomo
JavaScript
const response = await fetch(
  "https://dotfomo-names.oversmart.chatgpt.site/api/resolve/explorer.fomo"
);

if (!response.ok) throw new Error("Name not found");

const record = await response.json();
console.log(record.targets.solana);
200 RESPONSE
{
  "domain": "explorer.fomo",
  "ownerWallet": "AiV...8ZPj",
  "targets": {
    "solana": "AiV...8ZPj",
    "base": null,
    "bnb": null,
    "monad": null
  }
}

02 · ARCHITECTURE

onchain settlement. signed ownership. fast resolution.

.fomo is a hybrid registry. Registration and marketplace payments settle in SOL on Solana mainnet and are verified from RPC transaction data. Name records resolve from the registry database. Transfers and listing changes require an Ed25519 message signed by the current wallet owner.

01reserve

A unique 10-minute reservation and memo are created.

→
02settle

The wallet sends the exact SOL amount with that memo.

→
03verify

The server checks signer, recipient, amount, memo and time.

→
04record

Ownership is written once; the transaction cannot be reused.

Important

.fomo names are registry records, not NFTs or Solana Name Service domains. The onchain transaction is the payment proof; resolution and ownership state are served by this independent registry.

03 · RESOLVE NAMES

one endpoint, chain-aware responses.

GET/api/resolve/:name

Return the full owner and address-target record.

GET/api/resolve/:name?chain=solana

Return only the requested chain target.

OPTIONS/api/resolve/:name

CORS preflight for browser integrations.

React hook
import { useEffect, useState } from "react";

export function useFomoName(name) {
  const [record, setRecord] = useState(null);

  useEffect(() => {
    if (!name) return;
    fetch("https://dotfomo-names.oversmart.chatgpt.site/api/resolve/" + encodeURIComponent(name))
      .then((response) => response.ok ? response.json() : null)
      .then(setRecord);
  }, [name]);

  return record;
}

04 · REGISTRY API

search public registrations and proof.

GET/api/registrations?page=1

Paginated registrations, 18 records per page.

GET/api/registrations?q=explorer

Prefix-search names and return transaction proof URLs.

GET/api/availability/:name

Check registered and temporary-reservation state.

GET/api/status

Live Solana RPC and registry health.

TypeScript
type FomoRegistration = {
  name: string;
  domain: string;
  owner: string;
  createdAt: string;
  proofType: "solana" | "admin";
  proofUrl: string | null;
};

const { registrations } = await fetch(
  "https://dotfomo-names.oversmart.chatgpt.site/api/registrations?page=1"
).then((response) => response.json());

05 · REGISTRATION FLOW

build a verifiable claim transaction.

  1. 1
    POST /api/reserve

    Send the normalized name and connected wallet. The response contains the treasury, exact lamports and unique memo.

  2. 2
    GET /api/solana/blockhash

    Fetch a fresh mainnet blockhash through the protected server connection.

  3. 3
    Sign and send

    Create one System Program transfer plus one Memo Program instruction.

  4. 4
    POST /api/register

    Submit the reservation, wallet and transaction signature. Only verified payments create a record.

@solana/web3.js
import { Buffer } from "buffer";
import {
  PublicKey,
  SystemProgram,
  Transaction,
  TransactionInstruction,
} from "@solana/web3.js";

const transaction = new Transaction({
  feePayer: ownerPublicKey,
  blockhash,
  lastValidBlockHeight,
});

transaction.add(SystemProgram.transfer({
  fromPubkey: ownerPublicKey,
  toPubkey: new PublicKey(reservation.payment.recipient),
  lamports: reservation.payment.lamports,
}));

transaction.add(new TransactionInstruction({
  keys: [],
  programId: new PublicKey("MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr"),
  data: Buffer.from(reservation.reservation.memo, "utf8"),
}));

06 · MARKETPLACE

owner-listed names with direct settlement.

Owners choose any custom price from 0.001 to 10,000 SOL and can update it with a new wallet signature. Marketplace SOL moves directly from buyer to seller. The registry changes owner only after the exact payment and unique sale memo verify.

GET/api/listings

Active listings, market stats and recent verified sales.

POST/api/listings/:name/reserve

Lock a listing for one buyer for ten minutes.

POST/api/listings/:name/buy

Verify the payment and atomically move ownership.

Read listings
const market = await fetch(
  "https://dotfomo-names.oversmart.chatgpt.site/api/listings"
).then((response) => response.json());

console.log(market.stats.floorSol);
console.table(market.listings);

// Every listing includes its domain profile.
const { avatarUrl, bannerUrl, displayName, fomoUrl, profileUrl } =
  market.listings[0].profile;

07 · DOMAIN PROFILES

pictures and social identity, owned by the name.

Every registered name has a public profile route. The current domain owner can add an avatar, wide banner, display name, bio, public fomo.family link, X, Telegram, and website with a wallet-signed update. Profiles also expose registry activity, owned-name collections, and verified sale proofs. Profile data is cleared when the domain changes hands.

GET/api/profiles/:name

Read the public profile, listing state, owner wallet, and registration proof.

GET/api/profiles/:name/avatar

Serve the validated profile picture from object storage.

GET/api/profiles/:name/banner

Serve the validated profile banner from object storage.

PUT/api/profiles/:name

Save a multipart profile update after an Ed25519 ownership challenge.

GET/:name.fomo

Open the shareable public trader profile.

Read a profile
const { profile } = await fetch(
  "https://dotfomo-names.oversmart.chatgpt.site/api/profiles/explorer"
).then((response) => response.json());

console.log(profile.domain);               // explorer.fomo
console.log(profile.ownerWallet);          // full Solana address
console.log(profile.avatarUrl);            // same-origin image URL
console.log(profile.bannerUrl);            // same-origin banner URL
console.log(profile.stats.marketSales);     // registry-verified sales
console.log(profile.registrationProofUrl); // Solscan transaction
FOMO account linking

A fomo.family URL is supplied and signed by the .fomo domain owner. It is displayed as “linked by domain owner,” not as official fomo.family OAuth verification.

08 · WALLET ACTIONS

prove ownership without spending SOL.

Transfers, listings and unlistings use short-lived, single-use challenges. The message includes the wallet, action, normalized payload, nonce and expiry.

Challenge + signature
const challenge = await fetch("https://dotfomo-names.oversmart.chatgpt.site/api/auth/challenge", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    wallet,
    purpose: "transfer",
    name: "explorer",
    recipientWallet,
  }),
}).then((response) => response.json());

const { signature } = await provider.signMessage(
  new TextEncoder().encode(challenge.message),
  "utf8"
);

09 · SECURITY MODEL

checks that prevent free or replayed claims.

SIGNERWallet must sign

The payer must be a signer in the parsed Solana transaction.

AMOUNTExact lamports

Registration and sale amounts must exactly match the reservation.

MEMOUnique intent

Every reservation has an unguessable ID bound to its name.

REPLAYOne signature once

Verified payment signatures are unique and cannot be reused.

OWNEREd25519 approval

Non-payment mutations require the current wallet's signature.

MEDIAValidated uploads

Pictures are size-limited, magic-byte checked, isolated, and never accepted as SVG.

SECRETSServer-only RPC

Provider credentials never ship to browser JavaScript.

10 · ERRORS & LIMITS

predictable JSON errors.

400

Invalid input or unconfirmed paymentValidate the name, wallet, signature and retry confirmation.

403

Ownership proof failedThe wallet signature or current owner did not match.

404

Name not foundThe requested registry record does not exist.

409

State changedName, reservation, listing or payment is no longer usable.

429

Rate limitedWait before repeating high-frequency requests.

502/503

Temporary upstream issueRetry with the same reservation and transaction signature.