How Tempo Domains works.
A concise explanation of the onchain architecture, uniqueness model, NFT-bound ownership, transfer-safe resolver behavior, and the public pathUSD mint flow behind Tempo Domains.
Architecture
Tempo Domains combines an ERC-721 NFT, a canonical registry, a resolver, and a registrar. The app checks availability and ownership from deployed contracts directly instead of relying on explorer data, and v1 minting uses pathUSD approvals plus a registrar mint transaction rather than native-value pricing.
Uniqueness And Ownership
Each normalized full domain such as `wolf.tmp` or `wolf.tempo` maps to exactly one token id. Ownership always follows `ownerOf(tokenId)`, so transferring the NFT transfers the domain automatically.
Transfer Reset And Roadmap
Resolver settings reset whenever a domain NFT changes hands so old owners lose payment/profile control immediately. Wallet support includes injected wallets plus WalletConnect, and the roadmap includes richer public profiles, invoices, payment pages, and subscriptions on top of the current pathUSD mint rail.
Marketplace
Marketplace is where Tempo domain NFTs can be presented for sale, discovered by buyers, and used for direct domain trading. Listing is currently closed, so public sale actions are not active yet.
Dashboard Actions
The dashboard is where users manage wallet-owned Tempo domain NFTs and view their owned identities in one place. Transfer sends the NFT to another wallet, while List is reserved for marketplace sale actions and remains disabled while listing is closed.