Hexless Terms of Use
Last updated: July 20, 2026
These terms apply when you access the Hexless website, use the registration app, connect a wallet, or interact with the Hexless contracts. By using the service, you agree to these terms. If you do not agree, do not connect a wallet or submit a transaction.
1. Testnet service
Hexless currently operates on Arc Testnet. Testnet names, balances, fees, metadata, and transactions are experimental test assets. They have no guaranteed monetary value and are not promised to transfer to a future Arc mainnet deployment.
2. Your wallet and security
You control the wallet used with Hexless. You are responsible for protecting private keys, seed phrases, devices, and wallet permissions. Hexless cannot recover a wallet, reverse a signed transaction, restore a transferred NFT, or return assets sent to the wrong address.
3. Registration and renewal
Registering a name requires a private commitment transaction followed by a reveal transaction after the required delay. Names are registered for a selected term and must be renewed before the grace period ends. A name may become available to another wallet after expiry and the applicable grace period.
4. NFT ownership and control
An active .arc name is represented by an ERC-721 token. The wallet holding that token controls the name, its resolved address, and supported records. Transferring the NFT transfers that control. Marketplace support depends on each marketplace and on its support for Arc.
5. Public onchain data
Wallet addresses, names, records, transactions, and NFT metadata may be publicly readable and may remain available through blockchains, indexers, archives, or third-party services. Do not publish confidential, personal, unlawful, or sensitive information in an onchain record.
6. Fees and transactions
Registration and renewal prices are shown by the app from the deployed contract. Arc Testnet uses native test USDC for transaction fees and protocol payments. Network conditions, RPC failures, wallet software, or contract state may cause a transaction to fail or cost more than expected.
7. Third-party services
Hexless may link to wallets, faucets, explorers, RPC providers, marketplaces, or other applications. Those services are operated under their own terms and privacy practices. Hexless does not control their availability, accuracy, security, or continued support for Arc or .arc names.
8. No financial or legal advice
Hexless provides naming and resolution software. Nothing in the website, app, contract, or documentation is investment, financial, tax, or legal advice. An .arc name is not a promise of profit, protocol revenue, governance rights, or future token distribution.
9. Prohibited use
You may not use Hexless to violate law, infringe intellectual-property rights, impersonate another person or organization, register names in bad faith, distribute malware, phish users, steal credentials, evade sanctions, launder funds, manipulate markets, or interfere with the service or its security controls.
10. Software and branding
The Hexless name, visual identity, website, and original interface are protected by their applicable rights. Open-source code is licensed under the license included with its repository. Owning an .arc NFT does not grant rights to the Hexless brand or to third-party trademarks contained in a registered name.
11. Experimental software disclaimer
The testnet website, app, contracts, and integrations are provided as available for experimentation. Bugs, chain reorganizations, contract defects, wallet errors, RPC outages, indexer delays, or incompatible third-party software may cause loss of access, records, test funds, or names. No uninterrupted or error-free operation is guaranteed.
12. Limitation of responsibility
To the maximum extent allowed by applicable law, Hexless contributors are not responsible for indirect, incidental, special, consequential, or punitive losses arising from use of the testnet service, signed transactions, wallet compromise, smart-contract behavior, third-party services, or reliance on displayed data.
13. Changes and mainnet launch
These testnet terms may change as the protocol evolves. A mainnet launch will require updated production terms, a privacy notice, operator and contact information, governing-law and dispute provisions, and review by qualified legal counsel before public release.