1 00:00:14,230 --> 00:00:20,667 [HOST] Welcome to X1 Report, your source for the latest in blockchain news. Today, we're diving 2 00:00:20,667 --> 00:00:26,811 into the world of X1NS, the decentralized naming system that allows users to own and 3 00:00:26,811 --> 00:00:30,321 manage .x1 domains. Let's start with the basics. 4 00:00:30,321 --> 00:00:37,550 [ANALYST] X1NS operates a public REST API that anyone can use to look up who owns a specific domain 5 00:00:37,550 --> 00:00:43,966 or check if a name is available for registration. The API has no authentication 6 00:00:43,966 --> 00:00:47,945 requirements, making it incredibly user-friendly. 7 00:00:47,945 --> 00:00:55,077 [HOST] To find out who owns a .x1 domain, you simply need to visit the API endpoint with the 8 00:00:55,077 --> 00:01:02,376 domain name. For example, if you want to know who owns 'chris.x1', you would make a GET 9 00:01:02,376 --> 00:01:06,823 request to https://api.x1ns.xyz/api/resolve/chris.x1. 10 00:01:06,823 --> 00:01:12,624 [ANALYST] The response will include both the owner's wallet address and the on-chain domain record. 11 00:01:12,624 --> 00:01:18,164 It's important not to confuse these two keys, as the owner is the human who holds the 12 00:01:18,164 --> 00:01:22,009 domain, while the address is where the domain record lives. 13 00:01:22,009 --> 00:01:29,874 [HOST] Checking if a name is available for registration is just as straightforward. You can use 14 00:01:29,874 --> 00:01:37,651 the /api/available/:domain endpoint. For instance, to check if 'thisnameisfree99.x1' is 15 00:01:37,651 --> 00:01:41,404 available, you would make a GET request to 16 00:01:41,404 --> 00:01:46,320 https://api.x1ns.xyz/api/available/thisnameisfree99.x1. 17 00:01:46,320 --> 00:01:52,439 [ANALYST] The response will indicate whether the domain is available for registration and provide 18 00:01:52,439 --> 00:01:58,628 additional information if it's not. This step is crucial before you commit any resources 19 00:01:58,628 --> 00:02:00,949 or funds to a potential purchase. 20 00:02:00,949 --> 00:02:06,661 [HOST] If you're building an application, the TypeScript SDK can make your life easier by 21 00:02:06,661 --> 00:02:12,721 directly reading from the chain. For example, to resolve a domain, you would import the 22 00:02:12,721 --> 00:02:18,643 `resolveDomain` function from the @x1ns/sdk package and call it with the domain name. 23 00:02:18,643 --> 00:02:24,792 [ANALYST] Similarly, to get the primary domain for a wallet, you would use the `getPrimaryDomain` 24 00:02:24,792 --> 00:02:31,082 function. Both functions take a network argument, allowing you to develop against testnet 25 00:02:31,082 --> 00:02:33,132 without spending mainnet XNT. 26 00:02:33,132 --> 00:02:39,332 [HOST] For those who prefer not to rely on the API or SDK, the X1NS state lives in program- 27 00:02:39,332 --> 00:02:45,606 derived addresses with deterministic seeds. This means any client can compute where a 28 00:02:45,606 --> 00:02:49,223 record lives and read it directly from the chain. 29 00:02:49,223 --> 00:02:56,478 [ANALYST] X1NS is built on the SPL Name Service standard, with an X1NS registrar layer for pricing, 30 00:02:56,478 --> 00:03:03,162 TLD authority, primary records, profiles, and tokenization. This makes integration 31 00:03:03,162 --> 00:03:08,867 familiar for those who have worked with Solana naming services before. 32 00:03:08,867 --> 00:03:15,396 [HOST] Beyond individual names, the API also provides namespace-wide activity data. You can check 33 00:03:15,396 --> 00:03:21,779 listings on the marketplace, recent sales, new registrations, and tokenizations as NFTs. 34 00:03:21,779 --> 00:03:26,422 These endpoints are particularly useful for tracking the market. 35 00:03:26,422 --> 00:03:32,710 [ANALYST] It's worth noting that listing prices on the marketplace can vary significantly from 36 00:03:32,710 --> 00:03:38,400 actual clearing prices, especially in namespaces with fewer than 3,000 total 37 00:03:38,400 --> 00:03:39,448 registrations. 38 00:03:39,448 --> 00:03:45,578 [HOST] In conclusion, X1NS offers a robust and accessible system for managing .x1 domains. 39 00:03:45,578 --> 00:03:52,225 Whether you're a developer looking to integrate the API or a user curious about who owns a 40 00:03:52,225 --> 00:03:57,838 specific domain, there's plenty of information available at your fingertips. 41 00:03:57,838 --> 00:04:04,512 [ANALYST] For more details, visit the X1NS developer documentation. Remember, all responses and 42 00:04:04,512 --> 00:04:11,028 endpoints were read from live X1 mainnet on September 10, 2026, but rate limits and 43 00:04:11,028 --> 00:04:16,995 endpoints may change. Stay tuned for more updates from the blockchain world. 44 00:04:16,995 --> 00:04:22,911 [HOST] That's it for today's episode of X1 Report. Join us next time as we continue to explore 45 00:04:22,911 --> 00:04:28,963 the latest trends and technologies in the blockchain space. Until then, keep your wallets 46 00:04:28,963 --> 00:04:31,275 secure and your investments smart.