SPACE ID

What is SPACE ID?

SPACE ID is a multichain Web3 naming and identity protocol that lets users replace blockchain addresses with human-readable domains and Payment IDs, while giving developers a single resolution layer through its Web3 Name SDK and API.

The problem it addresses is not base-layer settlement but identity fragmentation: a user may hold assets across Ethereum, BNB Chain, Arbitrum, Solana, Sei, Injective, and other networks, while wallets and applications often require chain-specific address formats.

SPACE ID’s competitive argument is aggregation rather than exclusivity; instead of operating only one namespace, it attempts to serve as a registry, marketplace, and resolution middleware for multiple TLDs, including its own .bnb service and third-party or ecosystem-specific domains.

Its market position is therefore closer to application-layer infrastructure than to a Layer 1 or DeFi primitive. As of early September 2026, market-data providers placed ID in the mid-cap crypto segment, with CoinMarketCap showing a market-cap rank around the high 300s and CoinGecko using a different methodology that ranked it lower. TVL is not a meaningful primary metric for SPACE ID because the protocol is not a lending, exchange, or liquid-staking system that accumulates user deposits; its more relevant indicators are registered domains, owners, resolution integrations, renewal behavior, marketplace liquidity, and SDK adoption. Public materials indicate broad integration claims, including 300-plus partners on SPACE ID’s own platform page, but domain counts and “owners” should be treated as cumulative stock metrics rather than proof of sustained daily active users.

Who Founded SPACE ID and When?

SPACE ID launched publicly in 2022, during the post-Terra and post-Three Arrows “crypto winter,” when infrastructure projects were still raising capital but speculative metaverse and NFT identity narratives had already compressed sharply. The project’s early public milestone was the launch of the .bnb Name Service on BNB Chain in September 2022, followed by a seed round led by Binance Labs. Binance Research later profiled SPACE ID as its 30th Launchpad project and described the protocol as a Web3 identity platform with .bnb, .arb, marketplace, SDK, and DAO components in its project report. Public documentation has generally emphasized the SPACE ID team, DAO, and ecosystem rather than a founder-led personality structure, which is common among some Asian-market infrastructure projects but creates less transparency than founder-identified protocols such as ENS.

The project’s narrative has evolved from a BNB Chain naming product into a broader identity middleware stack. In 2022 and early 2023, the main story was .bnb registration growth, Binance ecosystem distribution, and the addition of .arb through collaboration with the ARB ID team. By 2023, the project repositioned around SPACE ID 2.0 as a one-stop platform to discover, register, trade, and manage Web3 domains, and later around SPACE ID 3.0 as a permissionless name-service toolkit for communities launching their own TLDs. As of the more recent roadmap, the project has also framed “AI Agents Domains” as a 2025-era expansion path through its official roadmap, although that thesis remains early and less empirically validated than simple wallet-address resolution.

How Does the SPACE ID Network Work?

SPACE ID is not a sovereign blockchain and does not run an independent proof-of-work, proof-of-stake, or DAG consensus system. It is better understood as an application-layer naming protocol deployed across existing chains, with the ID token issued as ERC-20 and BEP-20 at the same contract address, 0x2dff88a56767223a5529ea5960da7a3f5f766406, on Ethereum and BNB Smart Chain. Security for token transfers and many domain interactions depends on the underlying networks: Ethereum uses proof-of-stake validators as described in ethereum.org’s PoS documentation, while BNB Smart Chain uses Proof-of-Staked-Authority according to BNB Chain’s staking documentation. This means SPACE ID inherits the finality, censorship-resistance, bridge assumptions, and validator-set risks of the chains on which its registries and token contracts are deployed.

Technically, the naming system follows a registry-and-resolver pattern similar to ENS. Binance Oracle’s integration guide explains that SPACE ID resolution relies mainly on a SID Registry and Public Resolver: a domain is converted into a node hash, the registry identifies the relevant resolver, and the resolver returns the mapped address or contract record. The SDK and API abstract this workflow for developers, supporting domain-to-address resolution, reverse resolution, metadata records, avatars, IPFS links, and chain-specific primary names through the Web3 Name API. The more recent Payment ID product extends the same usability thesis to exchange and wallet transfers, with SPACE ID’s MetaMask Snap page describing human-readable identifiers, CEX-to-wallet deposits, and Gmail-based onboarding using zkEmail. The trade-off is that easier resolution can introduce middleware and UI dependencies: if users rely on SPACE ID-hosted APIs, front ends, or curated TLD verification, some practical trust shifts away from pure contract-level self-custody.

What Are the Tokenomics of ID?

ID has a capped maximum supply of 2 billion tokens, so its terminal supply is fixed by design, but its circulating supply has been inflationary during the vesting period because locked allocations continue to enter the market. SPACE ID’s official ID token documentation describes ID as the ecosystem governance token and lists a 2 billion maximum supply, with allocations to seed investors, strategic investors, Binance Launchpad, the team, advisors, marketing, foundation, airdrops, and ecosystem incentives. As of early September 2026, public market pages showed circulating supply around the 1.47 billion ID range, while an Upbit-published circulating-supply schedule indicated scheduled month-end circulation moving from roughly 1.48 billion ID at the end of August 2026 toward roughly 1.55 billion ID by the end of September 2026. The asset therefore combines a hard cap with meaningful unlock risk, especially because private-investor, team, advisor, foundation, and ecosystem allocations remain economically relevant until the vesting schedule is substantially complete.

The token’s value-accrual model is indirect. ID is used for governance, payments within the SPACE ID ecosystem, SDK-related integrations, and staking benefits such as marketplace-fee and registration-fee discounts, according to the official token documentation. SPACE ID DAO materials also describe a quarterly buyback-and-burn policy in which 50% of net platform revenue from registrations, renewals, gift cards, and marketplace fees is allocated to buy and burn ID through the DAO revenue-distribution mechanism. This does not make ID a gas token in the way ETH or BNB are gas tokens; users still pay underlying network fees in the native assets of the chains they use. The economic question is whether domain registrations, renewals, marketplace volume, and Payment ID usage generate enough recurring revenue to offset dilution from unlocks and to make staking discounts more than a marginal utility feature.

Who Is Using SPACE ID?

SPACE ID usage should be separated into three categories: token trading, domain speculation, and functional identity resolution. Token volume on centralized exchanges can be large relative to the protocol’s market capitalization, but that says little about the number of users resolving names or renewing domains. Domain registrations are also imperfect because low-cost names can be bulk-registered or held speculatively, particularly for short words, brand-like strings, and numeric clubs. The stronger on-chain utility case is where wallets, explorers, DeFi interfaces, NFT marketplaces, social applications, and payment flows resolve names into addresses. SPACE ID’s documentation and public pages emphasize support for .eth, .bnb, .arb, .sol, .crypto, .lens, and many newer ecosystem TLDs through one SDK/API layer, which positions the protocol primarily in identity, wallet UX, social, and infrastructure rather than in RWA, lending, or gaming-specific verticals.

Legitimate adoption examples include integrations or collaborations with BNB ecosystem infrastructure, wallet providers, and analytics products. Binance Research cited earlier integrations with more than 100 projects, including BscScan and Trust Wallet, in its SPACE ID profile. The project later launched Payment ID in connection with MetaMask and Binance through an April 2025 announcement, and DappRadar added support for SPACE ID domain names in user accounts in a 2025 integration note. Enkrypt also announced Payment ID and SDK support in 2025 through a wallet integration release. These are credible distribution channels, but they should not be confused with institutional balance-sheet adoption or enterprise procurement; the actual use case remains retail and developer-facing identity abstraction.

What Are the Risks and Challenges for SPACE ID?

Regulatory risk is unresolved rather than uniquely adverse. As of early September 2026, there was no widely reported SPACE ID-specific SEC lawsuit, CFTC action, spot ETF filing, or explicit U.S. commodity classification for ID, but that absence should not be read as regulatory certainty. ID was distributed through Binance Launchpad and trades on centralized exchanges, which creates generic exposure to securities-law analysis around fundraising, promoter efforts, governance claims, and secondary-market expectations. The broader exchange-litigation environment remains relevant: in June 2023, the SEC filed charges against Binance entities and Changpeng Zhao alleging unregistered exchange, broker-dealer, and clearing-agency activity in its press release, and although ID was not central to that action, tokens with launchpad histories can still face listing, market-access, and disclosure scrutiny. Centralization risk also exists at the operational level: SPACE ID depends on hosted interfaces, curated integrations, DAO processes, and underlying chain validator sets, including BNB Smart Chain’s PoSA model.

The competitive risk is substantial because naming systems have strong network effects. ENS remains the most recognized Ethereum-native naming layer and advertises tens of millions of names through its official ENS website, while Unstoppable has moved aggressively toward hybrid Web2/Web3 domain distribution and ICANN-aligned infrastructure through its official registrar materials. Other competitors include chain-native naming services, wallet-native address books, exchange whitelisting systems, account-abstraction wallets, Farcaster and Lens identity handles, and conventional DNS domains connected to crypto profiles. SPACE ID’s aggregation strategy reduces dependence on any one TLD, but it also means the project must convince developers that its middleware is neutral, reliable, and worth integrating over direct ENS, Unstoppable, or chain-specific resolution. The biggest economic threat is not a single rival token but commoditization: if wallets and exchanges build native multichain contact layers, third-party naming fees and marketplace spreads could compress.

What Is the Future Outlook for SPACE ID?

SPACE ID’s future depends less on speculative identity narratives and more on whether its resolution layer becomes embedded in wallets, exchanges, explorers, and consumer payment flows.

The verified roadmap has moved from .bnb and multichain TLD expansion toward SPACE ID 3.0’s community TLD toolkit and the 2025 “AI Agents Domains” theme described in the official roadmap. The Payment ID initiative is the more concrete near-term test because it targets a persistent UX problem: reducing address-copying errors across wallets and centralized exchanges.

The structural hurdles are clear: public active-user data remains less transparent than token-market data, domain registration counts can overstate organic demand, token unlocks continue to matter through the vesting cycle, and the project must defend relevance against ENS, Unstoppable, wallet-native identity systems, and traditional DNS. A durable bull case would require evidence of recurring renewals, rising resolver calls, sticky developer integrations, and measurable payment usage, not merely more TLD launches or exchange volume.