# US 2026/0312813 A1 · Systems and Methods for Creating a Verified Web Using Blockchain Domains, AI Agents and Verified Resolutions Using Metadata and Proofs

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0312813 A1
- Document ID: US20260312813A1
- Status: Published application
- Kind: A1
- Application number: 19/561,465
- Filed: 2026-03-09
- Published: 2026-10-08
- Earliest claimed: 2025-01-09
- Inventors: Prem Makeig
- Web page: https://patentgrep.com/patent/US20260312813A1

## CPC

- H04L 9/3218: {using proof of knowledge, e.g. Fiat-Shamir, GQ, Schnorr, ornon-interactive zero-knowledge proofs}
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3247: {involving digital signatures}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A unified framework is disclosed for creating a Verified Web that integrates blockchain domain resolution, cryptographic proofs, and Verified AI Agents. The system merges trust-scored resolution APIs (“Unruggable Resolve”) with a cross-chain data gateway (“Unruggable Gateways”) to retrieve data from multiple blockchains and off-chain sources. Cryptographic proofs anchor domain records, user credentials, and AI Agent workflows, ensuring tamper-resistant authenticity while preventing malicious resolver switching. The framework accommodates local or cloud-based Large Language Models (LLMs), enabling clients to dynamically assemble Verified AI Agents from verifiably sourced metadata. By mitigating AI-generated misinformation and supporting unstoppable name resolution, the solution fosters a robust ecosystem of decentralized, multi-chain applications, strengthening trust, security, and interoperability across evolving blockchain and AI landscapes.

## Claims

### Claim 1

A method of resolving a blockchain-based domain name via an API service that returns metadata and cryptographic proofs, the method comprising:
(a) receiving, at the API service, a resolution request identifying a blockchain-based domain name;
(b) determining that at least a portion of one or more domain records is stored on a different blockchain or off-chain source;
(c) retrieving the one or more domain records and media files via one or more gateway servers that generate one or more cryptographic proofs;
(d) assigning metadata, comprising one or more of a trust score, resolver modification date, whether the name uses off-chain resolution, and audited resolver status, to the one or more domain records and media files;
(e) returning, to a requesting client, both the one or more domain records and media files and the metadata;
(f) the client determining whether to resolve the one or more domain records and media files of the domain name based on the metadata; and
(g) the client resolving the one or more domain records and media files or terminating the resolution process.

### Claim 2 (depends on 1)

The method of claim 1, further comprising the client verifying the proof to verify the one or more domain records and media files.

### Claim 3 (depends on 1)

The method of claim 1, further comprising maintaining a registry of audited resolvers to detect and flag any unauthorized substitution of a resolver address, wherein such substitution triggers one or more actions including reducing the trust score and rejecting the resolution of the one or more domain records and media files.

### Claim 4 (depends on 1)

The method of claim 1, wherein the proof includes one or more of zero-knowledge proofs, Merkle-based inclusion proofs, and signed attestations verified by specialized logic in the verifier.

### Claim 5 (depends on 1)

The method of claim 1, wherein the one or more domain records and media files comprise user data comprising one or more of user profile credentials, proof-of-personhood, and user profile image, and further comprising verifying the user data to detect AI-generated deepfakes or content alterations by comparing hashes.

### Claim 6 (depends on 1)

The method of claim 1, wherein the requesting client obtains a locally verifiable proof in addition to the one or more domain records and media files, allowing local-blockchain-client verification.

### Claim 7 (depends on 1)

The method of claim 1, wherein the gateway servers implement ERC-3668 for cross-chain data retrieval from Layer-2 rollups.

### Claim 8 (depends on 1)

The method of claim 1, further comprising calculating the trust score using one or more factors selected from the group consisting of: (i) the resolver's audit history, (ii) proof validation outcomes, and (iii) the date of the last change to the resolver; wherein the trust score is displayed on a website portal.

### Claim 9 (depends on 1)

The method of claim 1, wherein malicious attempts to change the resolver to spoof a domain record result in one or more of reducing the trust score and the client not resolving the record.

### Claim 10 (depends on 1)

The method of claim 1, further comprising verifying user data comprising one or more of age, nationality, and a credential using zero-knowledge proofs linked to the domain's on-chain records, thereby enabling selective access to offers or services based on proven credentials.

### Claim 11 (depends on 1)

The method of claim 1, wherein the domain's trust score is dynamically updated in real time based on changes to on-chain records, newly detected security vulnerabilities, or proof-of-personhood credentials stored on a secondary blockchain, and displayed on a website portal.

### Claim 12

An agentic system, the system comprising:
(a) a retrieval module configured to obtain AI agent workflow components from one or more on-chain or off-chain sources comprising at least one blockchain domain record, along with corresponding cryptographic proofs;
(b) a proof validation component that uses a verifier to validate the cryptographic proofs; and
(c) an AI agent client software used to assemble a verified AI agent from validated components and one or more AI foundation models, wherein the verified AI agent can be used to complete a multi-step task.

### Claim 13 (depends on 12)

The agentic system of claim 12, wherein the assembled verified AI agent employs retrieval-augmented generation (RAG) by leveraging vector database entries or blockchain records to dynamically fetch and prove context for queries processed by a large language model.

### Claim 14 (depends on 12)

The agentic system of claim 12, further comprising a fallback mechanism that deactivates or restricts the AI Agent if any component's cryptographic proof validation fails.

### Claim 15 (depends on 12)

The agentic system of claim 12, wherein the AI Agent signs on-chain transactions using a private key of the client.

### Claim 16 (depends on 12)

The agentic system of claim 12, further comprising an Agents Communication Platform (ACP) that facilitates AI agent-to-AI agent collaboration, wherein each agent's persona and workflow data are shared and cryptographically validated, ensuring authenticity before any new context is integrated.

### Claim 17 (depends on 12)

The agentic system of claim 12, wherein the AI agent's chain-of-thought reasoning or step-by-step action logs are hashed and stored either on-chain or off-chain, enabling auditors to confirm the agent's decision-making process using cryptographic proofs.

### Claim 18 (depends on 12)

The agentic system of claim 12, further comprising a real-time trust score update mechanism that modifies the AI Agent's trust score based on on-chain records, known vulnerabilities, feedback from other AI Agents in the ACP, or user-supplied evaluations, wherein the trust score is displayed on a website portal.

### Claim 19 (depends on 12)

The agentic system of claim 12, wherein the AI Agent Client Software (AACS) integrates domain-specific knowledge graphs, external APIs, or specialized databases, each requiring verified references or proof-of-validity prior to use in the agent's context.

### Claim 20 (depends on 12)

The agentic system of claim 12, wherein the cryptographic proofs for workflow components include zero-knowledge attestations that reveal no sensitive user data but confirm that certain access or membership criteria have been met.
