Docs

Forward Resolution

Maps a human-readable .bot domain to its owner address and token ID. Delegates directly to the DomainNFT contract — always reflects current on-chain state.

alice.bot  ──resolve()──►  { owner: "0xAlice...", tokenId: 42, fullDomain: "alice.bot" }

Reverse Resolution

Maps a wallet address to its self-designated primary .bot domain. Ownership is re-verified on every call — stale data is never returned.

0xAlice...  ──reverseResolve()──►  { tokenId: 42, domainName: "alice", fullDomain: "alice.bot" }

If ownership transferred since setPrimaryDomain() was called:
0xAlice...  ──reverseResolve()──►  { tokenId: 0, domainName: "", fullDomain: "" }

Primary Domains

When a wallet owns multiple .bot domains it can designate one as its Primary Domain. This is the domain shown in wallets and block explorers via reverse resolution.

// Set primary — caller must own tokenId
resolver.setPrimaryDomain(42);

// Clear primary
resolver.clearPrimaryDomain();

// Check primary
resolver.hasPrimaryDomain(wallet);          // → true/false
resolver.getPrimaryDomain(wallet);          // → "alice"
resolver.getPrimaryToken(wallet);           // → 42
resolver.isPrimaryOwner(wallet, 42);        // → true

Future Record Types

The botResolver storage layout reserves space for ENS-compatible record types. These are read-only stubs today — they return safe defaults without reverting.

What It Is

Encrypted Forms allows any Bot Domains holder to publish custom forms — questionnaires, applications, surveys, event registrations, and more — where every response is end-to-end encrypted. Responses are stored via IPFS and are inaccessible to the platform, third parties, or anyone without the owner's decryption key.

Why It Exists

Traditional form tools store responses in centralised databases that are accessible to the platform operator, subject to data breaches, and governed by third-party privacy policies. Encrypted Forms removes the platform from the trust equation: responses are encrypted before leaving the respondent's device, stored on IPFS, and can only be decrypted by the wallet that created the form.

How Encryption Works

When a respondent submits a form, the response data is encrypted client-side in their browser using the form owner's public key before being sent to storage. Only the form owner — the holder of the corresponding private wallet key — can derive the decryption key and read the plaintext responses. The platform handles only ciphertext at all times.

Wallet Verification

Every respondent must sign a message with their wallet before submitting a form. This cryptographically proves that the submission came from the wallet that signed it — no accounts, no passwords, no email addresses. Wallet verification also enables the one-submission-per-wallet rule (see below).

One Submission Per Wallet

Because every submission is signed by a wallet, duplicate submissions from the same address are automatically rejected. This makes Encrypted Forms ideal for scenarios where fairness matters — whitelists, raffles, voting registrations, and community allocations — without requiring any third-party identity verification.

Response Limits

When creating a form, you can optionally set a maximum number of responses. Once the limit is reached, the form automatically stops accepting new submissions. This is useful for limited-spot applications, NFT whitelist registrations, and capacity-constrained events.

Expiration Dates

Forms can be configured with an expiration date and time. After the deadline, the form closes and no further submissions are accepted. Existing responses remain stored and decryptable by the owner. This is useful for time-sensitive campaigns, beta access windows, and event registrations.

IPFS Storage

Both the form definition and the encrypted responses are stored on IPFS via Pinata. This means there is no traditional database backend storing your form data. Content is addressable by its IPFS CID (Content Identifier) and accessible from any IPFS gateway. The form owner's Workspace fetches and decrypts responses directly from IPFS.

Public Sharing

Each published form receives a unique shareable URL. You can distribute this link anywhere — social media, Discord, email, QR code — and anyone with the link can submit a response. The form itself (field labels, descriptions) is public, but all responses are encrypted and visible only to the owner.

Duplicate Forms

You can duplicate any form you have created to use it as a template for a new campaign. The duplicated form is treated as a new, independent form with its own responses, limits, and expiration settings. Previously collected responses are not copied to the duplicate.

Export Responses

From your Workspace dashboard, you can export all decrypted responses to a CSV file for offline analysis, record-keeping, or importing into other tools. Responses are decrypted client-side in your browser at export time — no plaintext ever leaves your device to a server.

Decryption Process

When you open your form responses in Workspace, your connected wallet is used to derive the decryption key. The encrypted responses are fetched from IPFS, decrypted entirely inside your browser, and displayed in plaintext. The decryption key is never transmitted to any server — the entire process happens locally on your device.

Why Only the Owner Can Read Responses

The encryption scheme uses the form owner's wallet public key to encrypt each response at submission time. Only the private key of that wallet can derive the corresponding decryption key. Because private keys never leave a user's wallet, the platform has no cryptographic ability to decrypt responses — even if it wanted to. This is a mathematical guarantee, not a policy promise.

Real-World Examples

What It Is

The Collection Factory is a smart contract that verifies your .bot domain ownership and then deploys a new ERC-721 contract configured with your chosen name, symbol, supply, mint price, and metadata. All collection records are stored on-chain in the factory contract — no off-chain database is involved.

ERC-721 Standard

Every collection deployed through the factory is a fully compliant ERC-721 contract. This means the NFTs are transferable, hold standard metadata, and are compatible with any wallet, explorer, or marketplace that supports the ERC-721 standard on BOT Chain.

Domain-Gated Access

The factory verifies .bot domain ownership on-chain before allowing deployment. This links every collection to a real on-chain identity and prevents anonymous or unverified actors from spamming the factory. If you transfer your domain, access to create new collections under that domain transfers with it.

Free to Deploy

There are no platform fees to create a collection. You pay only the gas cost of the deployment transaction on BOT Chain Chain. You can deploy as many collections as you want — there is no cap.

Workspace Builder

The Workspace builder walks you through configuring your collection step by step: name, symbol, description, supply, mint price, and start/end dates. Once you review and confirm, the factory deploys your contract and it appears in your Collections dashboard immediately.

Real-World Examples

What It Is

The Token Factory is a smart contract that verifies your .bot domain ownership and then deploys a new ERC20 contract with your chosen name, symbol, total supply, logo, and description. All token metadata and ownership records are stored on-chain in the factory — no off-chain database is involved.

OpenZeppelin Standard

Every token deployed through the factory inherits from OpenZeppelin's battle-tested ERC20 implementation. This means your token is fully standard-compliant, transferable, and supported by any wallet, DEX, or tool that works with ERC20 tokens on BOT Chain. The contracts are not upgradeable or pauseable — what you deploy is what exists.

Supply to Creator

The entire token supply — exactly the amount you set — is minted to your connected wallet at the moment of deployment. There is no vesting, no platform reserve, and no future minting capability. Once deployed, the total supply is fixed forever.

Domain-Gated Access

The factory verifies .bot domain ownership on-chain before deployment. Every token is permanently linked to a real on-chain identity, giving token holders a verifiable creator record. Unverified wallets cannot use the factory.

Free to Deploy

There are no platform fees to create a token. You pay only the gas cost of the deployment transaction on BOT Chain. You can create as many tokens as you want — there is no limit.

Workspace Builder

The Workspace builder collects your token name, ticker symbol, logo URL, description, and total supply. A review step shows you a summary before you sign the deployment transaction. Once confirmed, your token contract is live on BOT Chain and appears in your Tokens dashboard with the contract address and an explorer link.

Real-World Examples