https://eureka.patsnap.com/resources/blog/rd-blog/verifiable-delay-function-construction-for-sequential-computation-proof-patent-landscape/ · Patsnap · data cut-off 2026-10-20 · downloaded from the live page
Patent Landscape · Cybersecurity & Digital Trust

Verifiable Delay Function Construction Patents for Sequential Computation Proof

A dataset of 9 patent families and 15 records on verifiable delay function construction for sequential computation proof, with filer and filing data.

15
Published Records
9
Simple Patent Families
47%
In Force at Cut-off
US
Leading Jurisdiction

15 published records collapse into 9 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 7 of 15 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.

  • 9 simple patent families and 15 published records make up this dataset, with no date limit applied to the search.
  • UNCHARTED IND LTD is named on 2 of the 9 families (22.2%), the largest single-row share in the listed filers.
  • 7 of 15 records were granted and still in force at retrieval, 47% of the total.
Check your own idea
Published byPatsnap Research··6 min readSourced from Patsnap Eureka
Overview

What this dataset covers

This page collects patent records matching a search string built around verifiable delay functions combined with sequential or puzzle-based computation. The search carries no date limit, so the 9 simple patent families and 15 published records here represent every matching document the search string found, regardless of when it was filed. A family groups filings for the same invention across countries; a record is counted once per publication, so the same invention can appear more than once if it was filed in several jurisdictions.

With only 9 families in scope, this is a small pool. The figures below describe what the search returned, not a map of the field: absence of a name or a classification here is as likely to mean the search terms missed it as that nobody filed there. Treat this page as a starting point for a closer search, not a finished picture.

Records vs. families in scope
  1. UNCHARTED IND LTD2
  2. THE BOARD OF TRUSTEES OF THE UNIV OF ILLINOIS1
  3. ADOBE INC1
  4. GRAPHEN INC1
  5. VELLORE INSITUTE OF TECH1

Ordered by volume only, not by importance or claim strength. Counted in simple (DOCDB) patent families, so one invention filed in several countries counts once. Names come from Patsnap's standardised assignee field as recorded on each document; subsidiaries and group companies are not merged. The icon before each name is read from the name itself (words such as University, Institute or Ltd); the data carries no organisation-type field, so treat it as a reading aid rather than a classification. Filings held by named individuals rather than organisations are removed where they can be identified (3 here); that identification is not exhaustive, so an individually held filing can still appear below. Either way those filings stay inside the totals above. This table shows the top 5 of the 5 filers returned for this search; the data endpoint returns at most 100 entities, so even that 5 is not the complete set of filers. A single family can name more than one filer, so these counts overlap and do not add up to the total.

Source: Patsnap Eureka. Assignee ranking and totals. Derived from one Patsnap search for Verifiable Delay Function Construction for Sequential Computation Proof Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Data

Filings, classification and legal status

The figures below are drawn directly from the search results: a filing-trend chart counted in published records, and a technology breakdown counted in simple patent families.

Filing trend by earliest filing year

Published records by earliest filing year run from 2 in 2018 to a peak of 4, reached in both 2023 and 2026. Years from 2022 onward are still filling in as later filings publish, so the recent uptick cannot be read as a trend; this chart also counts documents, not inventions, so one invention filed in several countries adds more than one mark to the line.

Filing trend by earliest filing year012342201820192020202120224202320242025420262022 onwards are shaded as still filling in: a filing is only visible once it publishes, up to 30 months after filing.

Counted in published records by earliest filing year, not de-duplicated into families. A filing is counted in the year it was filed, but it only becomes visible after it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. 2022 onwards are therefore still filling in and are shaded; no growth figure on this page uses them. Because this series counts documents rather than inventions, a rise can mean more inventions or the same inventions filed in more countries; this dataset cannot separate the two.

Technology composition by IPC subclass

H04L (digital information transmission) appears on 6 of the 9 families (66.7%), and G06Q (business, commerce & admin data processing) on 4 of the 9 (44.4%). A family can carry more than one classification, so these shares add up to more than 100%; the remaining subclasses in the chart sit at low counts and are not discussed in the text.

Technology composition by IPC subclassH04L · Digital information transmissi…666.7%G06Q · Business, commerce & admin dat…444.4%G06F · Electric digital data processi…111.1%G06N · Computing based on AI models111.1%G07B · Ticket & fare-registering111.1%H04N · Pictorial communication (video…111.1%

Shares are the percentage of the 9 patent families in scope. One patent family can carry several IPC classes, so the shares add up to more than 100%.

Source: Patsnap Eureka. Filing trend and technology composition. Derived from one Patsnap search for Verifiable Delay Function Construction for Sequential Computation Proof Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.

Go deeper on Verifiable Delay Function Construction for Sequential Computation Proof Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about verifiable delay function construction for sequential computation proof patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Record in Focus

A record from the result set

First record returned
US20230299939A12023-09-21

Method of generating randomness by public participation

THE BOARD OF TRUSTEES OF THE UNIVERSITY OF ILLINOIS

US20230299939A1 describes a method where commodity devices execute a protocol with a setup phase, a contribution phase and a result-generation phase. The setup phase initializes parameters and a verifiable delay function; the contribution phase runs in stages where parameters are published, random values are received, and a Merkle tree root and audit paths are published; the result-generation phase runs a matching number of stages.This is the first record returned under the database's default ordering, not the most cited, newest or broadest filing in the set. What the granted claims actually require has to be read from the claim set itself, not inferred from this abstract.

US20230299939A1, patent drawing 1US20230299939A1, patent drawing 2
View record

Selected as the first record the search returns under the database default order, then shown in full. It is not ranked by citations, claim breadth or commercial importance, and it is not a judgement about which filing in this space matters most.

Source: Patsnap Eureka. The first record the search returned, shown in full. Derived from one Patsnap search for Verifiable Delay Function Construction for Sequential Computation Proof Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Run it yourself

Put your own technology through the same analysis


  
Where to run it
Fastest

Eureka on the web

When you want the answer in the next five minutes.

The agent works the prompt against patents and technical literature, citing every source.

Run your analysis now →
For builders

MCP server & REST API

When it has to run inside your own pipeline.

Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.

Browse MCP servers →
Insights

Reading the numbers

Three figures from this dataset, reported without ranking or interpretation beyond what the numbers themselves show.

Family vs. record count
9 families / 15 records
simple patent families / published records

Two different counts of the same search

The search returns 9 simple patent families, each one invention de-duplicated across countries, and 15 published records, counted per publication. The gap between the two numbers reflects filings of the same invention in more than one jurisdiction, not additional inventions.

No date limit applied to the search string.
Largest listed filer
22.2%
of 9 simple patent families

One row's share of the family count

UNCHARTED IND LTD is named on 2 of the 9 simple patent families in scope, a 22.2% share of that row alone. The remaining listed filers each hold 2 or fewer families; filer rows are not summed here because one family can name more than one filer.

5 of 5 listed filers hold 2 or fewer families each.
Legal status at retrieval
7 of 15
published records granted and in force

Status snapshot, not a success rate

7 of the 15 published records (47%) were granted and still in force at the data-retrieval date. The remaining records fall into pending, withdrawn, refused, lapsed or undetermined categories that are not broken out individually in this dataset.

Legal status changes continuously after retrieval.
Classification overlap
66.7% / 44.4%
of 9 simple patent families

H04L and G06Q shares, counted separately

H04L appears on 6 of the 9 families (66.7%) and G06Q on 4 of the 9 (44.4%). Because a family can carry both classifications, these two shares are not additive and the overlap between them cannot exceed the smaller of the two counts.

Shares are counted against the 9-family total, not against each other.
Eureka AI Agent
Looking for what nobody has claimed yet?

Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to verifiable delay function construction for sequential computation proof patent landscape, with the prior art for and against each one.

Find the white space →
Source: Patsnap Eureka. Derived observations on the same dataset. Derived from one Patsnap search for Verifiable Delay Function Construction for Sequential Computation Proof Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
What's Next

Go deeper on this dataset

The figures on this page are a starting point. These paths dig into specific records, filers or classifications.

Pull the granted claims

Family and record counts cannot establish claim scope. Reading the granted claims of any record named here is the only way to assess what it actually covers.

Explore in Patsnap Eureka

Check filer rows individually

The listed filers overlap and cannot be summed. Reviewing each row on its own, rather than as a group, avoids over-stating any single entity's position.

Explore in Patsnap Eureka

Expand the search string

With only 9 families in scope, adjacent terms and classifications may surface records this search string missed.

Explore in Patsnap Eureka
Source: Patsnap Eureka. Suggested next steps. No new data: every figure named here is one of those above. Derived from one Patsnap search for Verifiable Delay Function Construction for Sequential Computation Proof Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
FAQ

Frequently asked questions

Answers are grounded in the same dataset. Derived from one Patsnap search for Verifiable Delay Function Construction for Sequential Computation Proof Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP

Research Verifiable Delay Function Construction for Sequential Computation Proof Patent Landscape in depth with Eureka

Go past this page: query the whole verifiable delay function construction for sequential computation proof patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.

Try Eureka
How this page was built, and what the numbers do and do not mean

Search. Every figure on this page comes from one Patsnap search, run once and not edited afterwards. This is the exact search string:

TAC:(("verifiable delay function") AND (sequential OR puzzle) AND computation*)

Reading the field codes: TAC searches the title, abstract and claims of each record, not the full description. The search string sets no date limit, so the scope is every matching record in the database regardless of when it was filed. It is not restricted to recent years. How this string was built matters for how far the counts can be pushed. It was generated in batch from a topic list rather than hand-crafted for this page, and the result set is not manually screened. A keyword search over title, abstract and claims both over-captures (unrelated filings that happen to use the same words) and under-captures (the same invention written in different words). This page cannot measure either effect, so read every figure here as what this particular string returned, not as what exists in the field. One subclass (H04L) carries 66.7% of the patent families, so this search returned a classification-tight set.

What is being counted. Two different units appear on this page and they are not interchangeable. The filer list and the technology split are counted in simple (DOCDB) patent families: one invention counts once however many countries it was filed in. The total, the jurisdiction split and the filing-year chart are counted in published records: the same invention counts once per publication. For this search that is 15 records and 9 families. Record counts reward filing in many jurisdictions; family counts do not. Shares are only ever taken against a denominator in the same unit, and each one names it.

Who the filers are. Names come from Patsnap's standardised assignee field, as recorded on the documents themselves. They are not rolled up to corporate group: a parent and its subsidiaries appear as separate entries, and a portfolio acquired from another company stays under the name on the document unless the assignment is reflected there. This list is meant to carry organisations, not people. Filings held by a named individual are identified by matching the assignee against the inventors on the same search, and, for names written in Chinese, Japanese or Korean characters, by the name carrying no organisational suffix; those are removed from the list (3 of them here). Neither test is exhaustive: the inventor list it matches against is itself capped, and a personal name written in Latin script with no organisational wording in it cannot be told apart from a short company name by rule. So an individually held filing can still appear in the list. Those filings stay inside every total and share on this page either way, so the listed entries can add up to less than the total. A record shown in full further down still names its assignee exactly as the patent office records it, including where that is a person: that name is how the record is identified and checked. What is left out of the ranking is people as ranked entries, not people as cited sources. The table shows the top 5 of the 5 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 5 is not every filer. One patent family can name several filers and each is counted separately, so these rows are not slices of a divided whole: adding them together over-counts, and this page deliberately publishes no combined "top five" share for that reason. See every filer, individuals included

Dates. The year chart counts by earliest filing year, not publication year. A filing only becomes visible once it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. Measured across these pages, the year four back from today still holds only about 89% of its eventual count. 2022 onwards are therefore shaded on the chart as still filling in. The data behind this page was retrieved on 2026-10-20.

Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (7 of 15). Everything else is pending, withdrawn, refused, lapsed or not determinable, and those states are not broken out here because the underlying codes do not separate them cleanly. Legal status changes continuously and is reported per document, not per family. Get the status breakdown in Eureka

Classification. The technology split uses IPC subclasses (four characters, for example H01M). A single record usually carries several, so the shares add up to more than 100% and a record can appear in more than one bar. Subclass is a coarse grouping; it describes the field a record was classified into, not what the claims cover. Break the classes down to subgroup level

Who wrote the words. The tables, charts, counts, shares and patent numbers on this page are produced directly from the search result by a program; none of them are written or estimated by a language model. The surrounding prose, headings, FAQ answers and the answers in the question panel are drafted by a language model that is given those same figures and is not permitted to introduce others. Prose can still mis-describe a correct figure, so where the two disagree, the tables and charts are the record.

Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.

Patent data carries limitations that apply to every figure above. Recent filings are under-counted, because an application is not public until roughly 18 months after filing and database loading adds further delay. The search string defines and constrains everything shown: records that use different terminology, or that sit outside the fields searched, are absent and cannot be counted. Applicant names, classification codes, legal-status codes and citation records are taken as recorded and may contain errors, duplicates, omissions or stale entries. Ordering by volume is not a measure of quality, scope, enforceability or commercial value, and a larger portfolio is not a stronger one. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.

Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, validity or infringement search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. No attorney-client relationship is created by it. Any patent, commercial, or strategic decision should be verified independently against the primary records and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.

The question panel. The answers behind the suggested questions on this page were written when the page was generated, not in response to your click. The progress steps that play before an answer appears are an animation of how that analysis was done; nothing is being searched or computed at that moment. Typing your own question instead opens Patsnap Eureka, which does run it live.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.