Blockchain delegation: continuation

This patent continues the application that became US11245514B1. An owner grants authority, a delegate signs with a separate key, and the chain checks that transaction against stored authorization information. The official title remains Blockchain delegation; “continuation” distinguishes this record on the site.

Reading the two grants

The parent application is 16/653,773. This application, 17/650,030, claims priority to October 15, 2019. Its cross-reference explicitly identifies the continuation relationship.

Claim 1 describes stored grants and validation of delegated transactions. Claims 2 and 3 concern conditions and limits on transaction count or amount over a specified period. Claim 4 concerns revocation of some or all granted permissions. Restrictions and revocation also appear in the original grant: the later grant alone does not establish a new product capability.

Explanation and learning

The blockchain delegation record brings together the family explanation, SDK entry and related agent article. Start with limited delegated access for the underlying concept.

This page preserves a separate document identity for checking the application relationship and claims. The technical overview does not replace a legal reading of the original claims.

Read the mechanism in detail

How can software act while your main key stays offline? follows a hypothetical task through the two signatures, cumulative limits, and the ordering of revocation and execution.

Patent record

Read the grant and access its PDF. This records the grant event; it is not a current audit of maintenance fees, ownership changes or legal enforceability.

Back to Publications.