# US 2026/0095306 A1 · Secure recovery mechanism with interactive time delay interface

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

- Number: US 2026/0095306 A1
- Document ID: US20260095306A1
- Status: Published application
- Kind: A1
- Application number: 19/171,980
- Filed: 2025-04-07
- Published: 2026-04-02
- Earliest claimed: 2024-10-02
- Assignees: Block, Inc.
- Applicants: Block, Inc.
- Inventors: Jurvis Si Jun Tan; Wilmer Paulino; Jonathan Pollack; Jesse Posner; Jordan Mecom; Clayton Douglas Garrett
- Web page: https://patentgrep.com/patent/US20260095306A1

## CPC

- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3829: {involving key management}
- G06Q 20/401: {Transaction verification}
- H04L 9/008: {involving homomorphic encryption}
- H04L 9/0841: {involving Diffie-Hellman or related key agreement protocols}
- H04L 9/085: {Secret sharing or secret splitting, e.g. threshold schemes}
- H04L 9/0866: {involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3255: {using group based signatures, e.g. ring or threshold signatures}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/46: Secure multiparty computation, e.g. millionaire problem
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Systems and methods are disclosed for security through multi-party computation (MPC). In some examples, a system generates, at a first device and using a first private key share (of a plurality of private key shares). The plurality of private key shares each correspond to different devices. The system receives, from one or more additional devices, one or more additional partial signatures that are generated using one or more additional private key shares (of the plurality of private key shares). The system identifies that a total amount of partial signatures associated with the transaction is meets or exceeds a minimum threshold amount of partial signatures. The system aggregates the first partial signature and the one or more additional partial signatures to generate a signature, and facilitates processing of a transaction using the signature and a distributed ledger.

## Claims

### Claim 1

A computer-implemented method for time-delayed secure recovery, further comprising:
receiving, at a server and through a first communication channel, a request for initiation of a recovery procedure;
initiating a timer that is scheduled to count from a request time to an end time, wherein the request time is associated with the request;
providing, from the server and through a second communication channel, a communication indicative of the request and the end time, wherein the communication includes an interactive element that is configured to send a response to the communication to cancel the initiation of the recovery procedure; and
initiating the recovery procedure based on the response not being received as of the end time.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein initiating the recovery procedure includes permitting a mobile device to decrypt an encrypted variant of a server private key share from a secure enclave of the mobile device, the server private key share having been generated by the server.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein initiating the recovery procedure includes permitting communication of an application private key share between a mobile device and a cloud backup system.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein initiating the recovery procedure includes facilitating derivation of a social recovery key based on a personal identification number (PIN) using an oblivious pseudorandom function (OPRF) and authenticating a token, wherein the token is based on data from a trusted contact device.

### Claim 5

A computer-implemented method for time-delayed recovery, further comprising:
initiating a timer that is scheduled to count from a request time to an end time, wherein the request time is associated with communication of a request for initiation of a recovery procedure;
providing a notification indicative of the request and the end time, wherein the notification includes an interactive element that is configured to trigger sending of a response to cancel the initiation of the recovery procedure; and
initiating the recovery procedure based on the response not being communicated as of the end time.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5, wherein initiating the recovery procedure includes permitting a first device to decrypt an encrypted variant of a second device private key share from a secure enclave of the first device, the second device private key share having been generated by a second device.

### Claim 7 (depends on 5)

The computer-implemented method of claim 5, wherein initiating the recovery procedure includes decrypting an encrypted variant of a second device private key share from a secure enclave of a first device, the second device private key share having been generated by a second device.

### Claim 8 (depends on 5)

The computer-implemented method of claim 5, wherein initiating the recovery procedure includes permitting communication of a first device private key share between a first device and a second device, the first device private key share having been generated by the first device.

### Claim 9 (depends on 5)

The computer-implemented method of claim 5, wherein initiating the recovery procedure includes sending a first device private key share from a first device to a second device, the first device private key share having been generated by the first device.

### Claim 10 (depends on 5)

The computer-implemented method of claim 5, wherein initiating the recovery procedure includes receiving a first device private key share at a first device and from a second device, the first device private key share associated with the first device.

### Claim 11 (depends on 5)

The computer-implemented method of claim 5, wherein initiating the recovery procedure includes facilitating derivation of a social recovery key based on a personal identification number (PIN) using an oblivious pseudorandom function (OPRF) and authenticating a token, wherein the token is based on data from a trusted contact device.

### Claim 12 (depends on 5)

The computer-implemented method of claim 5, wherein initiating the recovery procedure includes facilitating derivation of a social recovery key using a personal identification number (PIN) and based on an oblivious pseudorandom function (OPRF), sending the social recovery key to a device, receiving a seed and nonce from the device in response to a verification of the social recovery key by the device, derives a token and an encryption key based on the seed and the nonce, provides the token for authentication to a second device to receive a ciphertext and an integrity tag, and decrypts the ciphertext in response to verifying an integrity of the ciphertext using the integrity tag.

### Claim 13 (depends on 5)

The computer-implemented method of claim 5, wherein the request for initiation of the recovery procedure is communicated through a first communication channel, and wherein the notification is communicated through a second communication channel that is different from the first communication channel.

### Claim 14 (depends on 13)

The computer-implemented method of claim 13, wherein an email communication channel is one of the first communication channel or the second communication channel.

### Claim 15 (depends on 13)

The computer-implemented method of claim 13, wherein a text message communication channel is one of the first communication channel or the second communication channel.

### Claim 16 (depends on 13)

The computer-implemented method of claim 13, wherein an application communication channel associated with an application is one of the first communication channel or the second communication channel.

### Claim 17 (depends on 5)

The computer-implemented method of claim 5, wherein the communication of the request includes receiving the request, and wherein providing the notification includes sending the notification.

### Claim 18 (depends on 5)

The computer-implemented method of claim 5, wherein the communication of the request includes sending the request, and wherein providing the notification is responsive to receiving the notification.

### Claim 19 (depends on 5)

The computer-implemented method of claim 5, wherein a duration of time between the request time and the end time is at least one day.

### Claim 20

A system comprising:
at least one memory storing instructions; and
at least one processor, wherein execution of the instructions by the at least one processor causes the at least one processor to:
initiate a timer that is scheduled to count from a request time to an end time, wherein the request time is associated with communication of a request for initiation of a recovery procedure;
provide a notification indicative of the request and the end time, wherein the notification includes an interactive element that is configured to trigger sending of a response to cancel the initiation of the recovery procedure; and
initiate the recovery procedure based on the response not being communicated as of the end time.
