White Paper: Personal Oracle

Concept Author: cleverat.tea
Official Project Web Resources: web3chance.com , web3chance.personaloracle
Document Status: Official Formulation (Conception)
Publication Date: September 2, 2026
Target Audience: Private individuals, ambitious personal brand creators, and corporate structures (entities).

Legal Disclaimer: This document constitutes an architectural and strategic conception for building decentralized systems. The described mechanisms for smart contract interaction, identity verification, and sovereign domain management (SI TLD/SLD) are software-technical and organizational in nature and do not represent financial or investment advice.

All names, domain examples, and use cases provided in this document are fictitious and for educational and illustrative purposes only. No affiliation, sponsorship, or endorsement by any real-world individual or organization is implied. Any resemblance to actual persons, online aliases, or entities is entirely coincidental.

Section 1. The SITLD concept: Imaging and registration of a Web3 domain.

1.1 The SITLD concept (Semantic Identity Top-Level Domain)

1.2 Web3 domain architecture and customization: Implementation options

1.3 Expert infrastructure recommendation

1.4 Phase culmination: Registration, ownership

Section 2. Ownership verification and cybersquatting protection.

2.1 Identity Verification Acts

2.2 The verification culmination: Writing to the domain metadata (NFT)

Section 3. Deploying a Web3 website.

3.1 The space map (The digital locations to visit)

3.2 Step-by-Step Deployment Workflow

3.3 Fault tolerance protocol in the event of the registrar's operational cessation

Section 4. Oracle interacts with the external environment.

4.1 Inbound interaction protocols (External world access to the Oracle)

4.2 Outbound interaction protocols (Oracle integration with external systems)

4.3 Privacy modes and access management (Token/Address gating)

Section 5. Legal framework and liability disclaimer.

Section 6. Conclusion: Digital legacy as an act of sovereignty.

Section 1. The SITLD conception: Imaging and registration of a Web3 domain.

1.1 The SITLD conception (Semantic Identity Top-Level Domain).

The foundation of the Personal Oracle architecture is the SITLD—a semantic top-level domain that defines personal identity. Unlike traditional, meaningless extensions of the Web2 space, the SITLD inherently establishes a global context. It directly indicates the owner's first and last name or the company name. It defines the status, field of activity, and category of a sovereign digital entity within a decentralized environment.

The SITLD establishes a semantic granularity that simultaneously evokes both utilitarian (functional) associations and a distinct emotional resonance. It is not merely a network address, but the immutable root of digital longevity and a personal brand.

1.2 Web3 domain architecture and customization: Implementation options.

When shaping digital identity, we have fundamentally rethought existing approaches to defining TLD value. We have chosen meaningful TLDs of arbitrary length over short, abstract ones. The more comprehensive and substantial the name, the stronger the foundation it creates for brand capitalization and the subsequent integration of practical utilities (Loyalty 2.0 programs, asset tokenization, and decentralized marketing).

Examples: .FirstnameLastname , .CompanyName , .MasterOfMiracle , . YourTroubleShooter , .RetiredPilot , .MemorialNFT , .AsEasyAsPie , .IntegralApproach, etc..

Based on the technical standards of Web3 registries, specific rules apply to character strings and punctuation marks within second-level domains (SLDs): hyphens (-) are fully supported for word separation, while dots (.) are reserved exclusively for the hierarchical creation of subdomains and cannot be purchased as part of a single string.

To accommodate these principles, two fundamental implementation options have been developed:

Option A (User Profile): FirstnameLastname.SITLD or CompanyName.SITLD
- Format: The optimal solution for individuals and smaller structures (entities) utilizing an established, third-party semantic TLD of their choice.

The gold standard here is either the seamless concatenation of one's First Name and Last Name (e.g., JaneDoe . PlanetOfPeople ), or their separation with a hyphen for enhanced readability (e.g., Jane-Doe . pilot ). An optional patronymic middle initial can also be integrated (e.g., Jane-U-Doe.pilot ), ensuring an ideal balance between address uniqueness and a premium perception. For businesses, the standard format is the company name (e.g., SpaceExploration.PlanetOfPeople ).

Section Mechanics: For most users, the standard single-string format (concatenated or hyphenated) is perfectly sufficient and ready to use out of the box. If a user strictly prefers to separate their first and last name with a dot (e.g., John.Smith ), this requires deploying a custom subdomain infrastructure. In this case, the user first secures the base domain ( Smith.pilot ) and then manually and independently creates the subdomain ( John ) within their account dashboard with the domain registrar. Step-by-step guidelines for this process are detailed in our educational resources.

Otherwise, the structuring of Oracle sections ( Archive, Heritage, Marketing ) for Option A is executed purely at the internal software level—via linked smart contracts, decentralized data directories, and hash paths tied to a single domain ID.

Option B (Sovereign Registry): SLD.FirstnameLastname or SLD.CompanyName
- Format: A premium-tier solution for large-scale, ambitious individuals and major corporate structures (entities). In this scenario, the sovereign TLD (the root) becomes the user's own First Name and Last Name or the Company Name. Examples: .JeffFink or .SpaceExploration .
- Section Mechanics: Owning a proprietary TLD eliminates technical constraints. The sections of the Personal Oracle are projected into the external domain space and deployed as legitimate second-level domains (SLDs) separated by the single, valid dot before the root. Section Examples: heritage.JeffFink ; loyalty.SpaceExploration ; archive.SpaceExploration . This delivers 100% brand recognition and limitless customization of the digital ecosystem.

1.3 Expert infrastructure recommendation.

When selecting a registrar, it is critically important to evaluate the economic model of asset ownership. Certain platforms, which charge an annual maintenance fee of $50 to $100 per TLD, rely on the legacy Web2 model of recurring renewal fees. This approach fundamentally contradicts the long-term objectives and philosophy of the Personal Oracle: it introduces a systemic risk of losing one's digital identity in the future. It imposes an unnecessary burden of constant financial oversight on the user or their heirs.

Within this conception, Freename.com is recognized as the most adaptive and technologically sound infrastructure partner. Its defining advantage is the complete absence of renewal fees. You purchase the domain once, and it remains yours forever—secured as an unconditional private-asset NFT (Non-Fungible Token) in your non-custodial wallet.

1.4 Phase culmination: Registration, ownership.

This phase culminates in the legal and technical act of domain registration. A Web3 domain is a full-fledged digital asset issued in the format of an NFT (Non-Fungible Token). At the moment of purchase, the domain (NFT) must be minted and transferred to the user's personal, non-custodial wallet (e.g., MetaMask, Trust Wallet, etc.). No one can confiscate or freeze this domain. The absolute right of ownership (the NFT) permanently belongs to your wallet.

A Web3 domain lives on the blockchain, but transforming this complex cryptographic address into content readable by ordinary browsers (DNS resolution) requires specialized technical gateways. This is precisely the function performed by the registrar. Within the registrar dashboard, you manage the domain settings, configure its routing, and link it to your future website.

Section 2. Ownership verification and cybersquatting protection.

2.1 Identity verification acts.

In an environment of free and decentralized access to Web3 domain registration, the issue of cybersquatting—the intentional interception of personal names or company brands by third parties—inevitably arises.

The Personal Oracle conception completely mitigates this issue. The mere fact of owning a Web3 domain (NFT) does not automatically turn it into a legitimate source of information. The authenticity of the Oracle is anchored in an inseparable Identity Verification Act, which is published to the immutable distributed file system IPFS (InterPlanetary File System) and cryptographically linked to the domain's smart contract. Even if an original name is intercepted, a malicious actor can never duplicate the verifiable cryptographic footprint of the true owner.

To deploy this protection, two complementary verification options have been engineered:

Option 1 (Legal): Notarized attestation.

A traditional path providing maximum legal clarity. The domain owner verifies their identity, either in person or digitally, before a licensed notary public. The notary attests a legal document (manifesto) that officially links the individual's passport data to their specific Web3 domain address and wallet hash. This document is digitized, secured with the notary's qualified electronic signature, and uploaded to IPFS.

Option 2 (Technological): Remote KYC protocol (eKYC).

A modern, streamlined method of decentralized verification that uses automated identity-verification procedures similar to those used on centralized crypto exchanges (CEX). The user undergoes biometric liveness checks and government ID scanning via a specialized eKYC protocol. Upon successful processing, an immutable cryptographic certificate of conformity is generated. This digital passport is cryptographically bound to the Web3 domain and permanently anchored in the IPFS network, proving that a verified, living individual stands behind the Oracle.

Option 3 (Decentralized / Anonymous): World ID (Proof of Personhood).

A privacy-preserving alternative designed for users seeking Sybil resistance without disclosing personal identity data. Utilizing zero-knowledge proofs (ZK-SNARKs) via the World ID protocol (including Orb biometric verification), this tier generates a cryptographic proof confirming that a unique, living human operates the Oracle. This prevents bot-automated spoofing and identity duplication while maintaining absolute data anonymity.

2.2 The verification culmination: Writing to the domain metadata (NFT).

Once the Verification Act (Notarized, eKYC, or World ID attestation is generated, it is uploaded to the distributed IPFS storage. The system then issues a unique, immutable file address—the IPFS link (CID hash).

To complete the legal anchoring of authenticity, you execute the final step: copy this IPFS link and paste it directly into your domain's metadata via the Registrar dashboard. You sign the transaction in your wallet, and this hash becomes permanently embedded into the body of your NFT domain at the blockchain level.

From this moment on, any search engine, Web3 browser, or smart contract interacting with your domain instantly reads this link and displays the verified status: “Identity Confirmed. Verification Act CID: ...” This renders any attempt to spoof your digital profile technically impossible.

Verification status: The eKYC and notarization protocols (Verification Acts) anchored within the domain metadata serve strictly to validate identity within the Web3 ecosystem cryptographically. These cryptographic records are committed to the metadata upon successful completion of the verification procedure. They are dynamically updated throughout the Personal Oracle's lifecycle as legal certificates are renewed or upgraded.

These procedures do not substitute for official sovereign state identification documents in the physical world (Web2/offline environments) and operate strictly within the Personal Oracle ecosystem.

Note: Detailed step-by-step instructions for completing the verification procedures are regularly published and updated on the official project websites ( web3chance.com , web3chance.personaloracle) and across its official social media channels.

Section 3. Deploying a Web3 website.

The geography and route of deploying your sovereign website. For most users, transitioning from the familiar Web2 model to a Web3 architecture presents a psychological barrier. To eliminate disorientation, we divide the process into two distinct components: space (where exactly you are) and action (what specifically you do there).

3.1 The space map (The digital locations to visit).

To successfully deploy a Web3 website, you only need to check in at three core locations across the digital landscape:

3.1.1 Your non-custodial wallet (e.g., MetaMask, Trust Wallet, etc.): your personal digital signature, main control panel, and asset vault. It exists as a browser extension or a mobile application.
3.1.2 The registrar dashboard of Freename.com : The destination where your domain (NFT) is physically managed and configured to link with your upcoming website.
3.1.3 The decentralized Web3 content builder/hosting platform: A specialized visual builder (such as Fleek for decentralized hosting or Framer for interface design), where the website structure is assembled and from which data is deployed to the InterPlanetary File System (IPFS) distributed network.

3.2 Step-by-Step Deployment Workflow.

3.2.1 Location 1: Your Web3 wallet
- Action: Open your wallet application and ensure it is connected to the correct network where your domain will reside. Before initiating the minting process, this wallet address must be added to your account profile on the Registrar platform and selected as the designated self-custody address for receiving the NFT domain asset.

The wallet serves as your master key for all subsequent deployment stages, requiring no passwords, only your cryptographic signature.

3.2.2 Location 2: The Freename.com dashboard
- Action: You navigate to the platform and click "Connect Wallet". Your wallet instantly authenticates you without requiring an email address. In your profile dashboard, you select your registered domain ( FirstnameLastname.SITLD or your proprietary SITLD). Here, you initiate the domain-to-content routing function.
3.2.3 Location 3: The Web3 development platform (Website builder like Fleek or Framer)
- Action 1 (Content assembly): You authenticate on the development platform using the same wallet. Inside an intuitive visual editor, you populate the Oracle: placing your manifesto, uploading verified IPFS acts, and linking social graphs.
- Action 2 (Minting & publication): You click the "Publish" button. Your wallet interface will prompt you to sign the transaction. You approve it with a single click. The platform processes the assembled content, digitizes it, and permanently distributes it across the independent nodes of the Web3 network.

Crucial Addition: To eliminate any technical friction, we have prepared a comprehensive walkthrough. It visually demonstrates, step by step, this exact process—from the initial wallet connection to the final website minting —using a live project as an example.

3.3 Fault tolerance protocol in the event of the registrar's operational cessation.

The technical routing associated with the registrar's dashboard does not create a critical dependency or pose a risk of losing content management capabilities. The Web3 architecture delivers end-to-end autonomy through the following protocols:

3.3.1 Direct smart contract execution: The domain NFT and its configuration records (including the website's IPFS hash and verification CID keys) are deposited directly into the blockchain ledger (Polygon/Ethereum). The registrar's dashboard serves strictly as a graphical user interface (frontend).

In the event of the registrar's web platform liquidation, metadata management and content routing updates are executed by the owner directly via blockchain explorers (e.g., Polygonscan) or alternative integration gateways by authenticating a non-custodial wallet (MetaMask/Trust Wallet).

3.3.2 Decentralized hosting: The Web3 website data and Oracle archives are physically distributed across independent nodes of the IPFS network. Website resolution and availability within Web3-enabled browsers remain fully operational, completely independent of the operational status or legal existence of the Registrar company.

Section 4. Oracle interacts with the external environment.

To maintain seamless interaction with the external environment, you will simultaneously utilize two distinct links that are automatically generated within your registrar dashboard, from which they must be copied:

Option A (User Profile)
- FirstnameLastname.SITLD (or CompanyName.SITLD ) — your sovereign direct link for the decentralized environment (Web3 browsers and blockchain-native systems).
- FirstnameLastname.SITLD.limo (or CompanyName.SITLD.limo ) — your adaptive bridge link for the traditional internet infrastructure (legacy Web2 browsers).
Option B (Sovereign Registry)
- SLD.FirstnameLastname (or SLD.CompanyName ) — your sovereign direct link for the decentralized environment (Web3 browsers and blockchain-native systems).
- SLD.FirstnameLastname.limo (or SLD.CompanyName.limo ) — your adaptive bridge link for the traditional internet infrastructure (legacy Web2 browsers).

Access to the deposited data of the Personal Oracle via these addresses is executed under the following conditions (settings) configured entirely by you:

4.1 Inbound interaction protocols (External world access to the Oracle).

The routing of your link from both the traditional web environment (Web2) and the decentralized environment (Web3) is deployed automatically, without relying on intermediary hosting servers:

Web3 resolving: Browsers with native support for decentralized networks (e.g., Brave, Opera) or specialized extensions read the root CID hash from the NFT domain metadata directly from the blockchain. The request is routed to the distributed IPFS network, which instantly assembles and renders the Oracle interface.
Web2 gateways: For users operating standard internet browsers, access via your link is deployed through decentralized DNS gateways (e.g., the .limo gateway). The gateway acts as a technical translator: it converts the Web2 request into a blockchain query, fetches the current content from IPFS, and displays it within a standard HTTP field.

4.2 Outbound interaction protocols (Oracle integration with external systems).

The Personal Oracle functions not merely as a website frontend, but as a verified Data Node capable of proving your identity to external environments:

Cryptographic authentication (Web3 Auth): Instead of legacy "username-password" pairs, Oracle utilizes a decentralized authentication protocol. External services (financial platforms, blockchain registries, private enterprise networks) prompt you to connect your non-custodial wallet. The system cross-references the wallet address with the NFT domain owner and the Verification Act. Authentication is executed in a single click by signing a cryptographic token.
Smart contract integration (Data feed): Certified data securely stored within the Oracle framework (such as verified IPFS acts, digital testaments, or corporate manifestos) can be read directly by external smart contracts via API gateways of decentralized oracle networks (e.g., Chainlink).

This enables the automated execution of external agreements (e.g., digital asset inheritance transfers upon specific triggers) based on the immutable data in your Oracle.

4.3 Privacy modes and access management (Token/Address gating).

The entire privacy configuration process is fully automated and managed manually by you. No programming skills are required: managing access to your Personal Oracle is executed through an intuitive graphical user interface based on a straightforward "toggle switch" principle. You can instantly deploy two ready-made access restriction modes utilizing simple trusted address lists (whitelists):

Option 1: Total perimeter gating (Total Oracle gating). You completely hide the entire infrastructure of your Oracle from public view. Upon navigating to your address, the external environment displays only a minimalist authentication prompt that requires a wallet connection. Access to the Oracle interface and data files is granted automatically and exclusively to those users whose wallet addresses you have personally added to your trusted list.
Option 2: Segmented access (Granular/Partial gating). The core infrastructure of your Oracle (your public brand, reputation assets, general manifestos) remains open to the global network. However, you lock specific critical sections (personal archives, records, confidential instructions). Access to these restricted segments is provisioned conditionally by you: either to specific wallet addresses from your list, or automatically to any user holding a specific marker NFT pass issued by you.

Instructional Note: The step-by-step algorithm for activating secured zones, the client-side encryption methodology for confidential files, and visual examples of managing access lists are thoroughly detailed in our reference: “Guide to Managing Privacy and Secured Zones of the Personal Oracle”. You will easily configure these parameters on your own by following the clear visual prompts.

Section 5. Legal framework and liability disclaimer.

The Personal Oracle functions exclusively as a decentralized infrastructural framework, provisioning the user with technical instruments for sovereign management and long-term data deposition.

Autonomy and mutual liability: The developers of the Oracle architecture and the domain name registrars have no technical access, moderation capabilities, or ability to alter or control user-deployed content. Comprehensive liability regarding the legal integrity of the content, copyright compliance, and adherence to the local legislation of your specific jurisdiction rests entirely with you as the sole custodian of the management wallet's private keys.
Verification status: The eKYC and notarization protocols (Verification Acts) anchored within the domain metadata serve strictly to validate identity within the Web3 ecosystem cryptographically. These cryptographic records are committed to the metadata upon successful completion of the verification procedure. They are dynamically updated throughout the Personal Oracle's lifecycle as legal certificates are renewed or upgraded.

These procedures do not substitute for official sovereign state identification documents in the physical world (Web2/offline environments) and operate strictly within the project's digital ecosystem.

Global infrastructure force majeure: The architects of this conception hold no liability for hardware malfunctions, protocol upgrades, or the operational cessation of third-party public blockchain networks (Polygon, Ethereum) and distributed data storage networks (IPFS, Filecoin) that form the baseline global infrastructure.

Section 6. Conclusion: Digital legacy as an act of sovereignty.

Deploying a Personal Oracle is far more than a mere technical procedure of launching a website or anchoring a domain within a blockchain. It represents a foundational leap toward achieving true digital sovereignty in an era when centralized platforms remain ephemeral and personal data is constantly exposed to censorship and erasure.

Claiming comprehensive ownership of your Semantic Identity (SITLD) restores an individual's sovereign right to their own history. Bringing structural order to your digital footprint, protecting your reputation, and capturing an immutable code of values constitutes a profound act of a digitally mature and responsible individual.

The Personal Oracle provides you with an architecture built for longevity: an instrument engineered to guarantee that your voice, your expertise, and your legacy endure pristine across decades, transferring seamlessly from generation to generation, unyielding to external regulatory shifts or technological disruptions.

A final word to the owner: The decentralized Web3 ecosystem offers you a clean slate. The very fact that you are engaging with this document and mastering the infrastructure of tomorrow already sets you apart from millions. Do not relegate this vital dimension of your life to tomorrow. Establish your digital vault, anchor the authenticity of your identity, and forge a Manifesto that will stand as an eternal beacon for your beneficiaries, partners, and successors. The future belongs exclusively to those who architect it today.

Welcome to the era of sovereign digital immortality!

Notice of original publication:

This White Paper was first officially published and cryptographically anchored on Paragraph.com . The author reserves all exclusive rights to the concept and methodology of the Personal Oracle.

Every like-minded individual can record their agreement with our concept by minting it as a sovereign NFT artifact directly from the Personal Oracle's page on Zora

Minting seals your status as an OG Pioneer and unlocks upcoming community rewards (Priority SLD allocation under TLDs from web3chance.com ). Don’t forget to mint.

--------------------------------------

Explore the foundational philosophical framework and core principles that preceded this technical architecture:

📜 The Personal Oracle Manifesto (Original Publication)