BitDNS Technical Specifications

Defines the structure of $BitDNS names, supported DNS record types, and the process by which these names are resolved to their corresponding data via the chosen blockchain and the BitDNS Resolver Network.

• Name syntax and hierarchy (e.g., `.bitdns` TLD, character limitations).
• Supported DNS record types (A, AAAA, CNAME, MX, TXT, NS, SRV, custom types).
• Blockchain data structures for storing domain tokens and DNS records.
• Resolver Network query protocol and response formats.
• Interaction with the $BitDNS token for specific protocol operations (if any beyond staking).

Details the on-chain representation of BitDNS domains as tokens and the flexible addressing model designed for enhanced user privacy and control.

• Token standard used (e.g., NFT-like, specifying metadata for DNS records).
• Multi-address control: A BitDNS domain token can be controlled by or associated with one or many public blockchain addresses.
• Compatibility with Hierarchical Deterministic (HD) wallet principles to encourage unique address usage per interaction.
• Mechanisms for updating DNS record data associated with the domain token.
• Implications for privacy: How the multi-address system helps mitigate address reuse and improve transaction graph obfuscation.

Specifications for how users interact with the BitDNS platform via blockchain wallets, with a focus on secure and user-friendly operations.

• Primary recommended integration (e.g., HandCash for the BSV ecosystem, detailing specific API usage if applicable).
• Generic wallet interaction patterns (e.g., Web3Modal-like approach for broader compatibility on EVM chains, or specific standards for other chains).
• Authentication mechanisms: Using wallet signatures for login ('Sign-in with Wallet').
• Transaction signing process for domain registration, updates, transfers, and $BitDNS token interactions.
• Secure handling of private keys (client-side only) and transaction payloads.

Ensuring that BitDNS records can be verified and trusted within the existing global DNS infrastructure through DNSSEC.

• Method for associating DNSSEC-specific records (e.g., DS, DNSKEY, RRSIG) with BitDNS domain tokens.
• Process for signing zones or individual records on the blockchain or by resolvers.
• Integration points with traditional DNS resolvers that are DNSSEC-aware.
• Trust chain establishment from the root DNS zone to BitDNS domains.

Defines how paid services, such as premium resolver lookups or advanced API access, are signaled and processed using the HTTP 402 (Payment Required) status code.

• Identifying services that require payment.
• Structure of the HTTP 402 response, including necessary headers or body content to guide payment (e.g., payment address, amount, currency).
• Supported payment methods (e.g., native blockchain tokens, stablecoins, $BitDNS token).
• Workflow for clients to complete payment and gain access to the service.
• Rate limiting and access tiers for different payment levels.

Specifications for the BitDNS Resolver Network, including node requirements, query handling, and the Proof-of-Service mechanism for incentivizing operators.

• Minimum hardware and software requirements for running a resolver node.
• Communication protocol between clients and resolvers, and between resolvers themselves (if applicable for distributed resolution).
• Query processing logic and caching strategies.
• Proof-of-Service (PoSe) algorithm: Metrics for measuring service quality (uptime, response time, successful resolutions).
• $BitDNS token staking requirements and reward distribution mechanism based on PoSe.