# US 2026/0178771 A1 · Multilayer system and method for securing estate documents in a single repository

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

- Number: US 2026/0178771 A1
- Document ID: US20260178771A1
- Status: Published application
- Kind: A1
- Application number: 19/416,164
- Filed: 2025-12-11
- Published: 2026-06-25
- Earliest claimed: 2024-12-20
- Assignees: Gorman Squared LLC
- Applicants: Gorman Squared LLC
- Inventors: David GORMAN; Mark GORMAN
- Web page: https://patentgrep.com/patent/US20260178771A1

## CPC

- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- H04L 9/0631: {Substitution permutation network [SPN], i.e. cipher composed of a number of stages or rounds each involving linear and nonlinear transformations, e.g. AES algorithms}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3249: {using RSA or related signature schemes, e.g. Rabin scheme}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A multi-layer cybersecurity system and method for protecting documents in a digital vault. Specifically, the invention employs AES-256 CTR and RSA 2048 encryption to protect data stored in UTF-16 format in the digital vault. Furthermore, environmental based signature weighting is applied to the keys. As a result, cold signers can do anything hot signers can but hot signers cannot do what cold signers can such as taking control, recovering control, or reconstitute the data of the vault in real time, if necessary.

## Claims

### Claim 1

A multi-layer cybersecurity system for protecting one or more estate vault(s) holding estate documents and other critical information, the system comprising:
a software application, the application operating on a mobile computer device or on a computer device, in communication with a estate professional, a testator, an oversight guardian, and, optionally a token issuer or Account Holder the application is configured to receive:
an instruction to make a digital key, the instruction received from the testator, token issuer, or oversight guardian or Account Holder
at least one private key, the private key authorizing access to data in an Estate Vault;
an environmental designation, previously configured or uploaded by an employee or agent of the System, wherein the environmental designation identifies the private keys that reside in a hot environment and the private keys that reside in a cold environment;
a signature weight designation, previously configured or uploaded by an employee or agent of the token issuer or oversight guardian, wherein the signature weight designation includes:
a signature weight ascribed to private keys residing primarily in a hot environment, and
a signature weight ascribed to private keys residing primarily in a cold environment, wherein the signature weight ascribed to private keys residing primarily in the cold environment is greater than the signature weight ascribed to private keys primarily residing in the hot environment; and
a transaction weight designation previously configured or uploaded by an employee or agent of the token issuer or oversight guardian, establishing a minimum signature weight required to effectuate different changes to the keys;
a processor in communication through the wired and/or wireless communication network with the software application, the processer is configured to:
compare the instruction to the transaction weight designation and determine a minimum signature weight required to effectuate the change;
compare the environmental designation to the private keys and determine whether the private keys reside in a hot environment or a cold environment;
compare the signature weight designation to the determination of the environment in which the private keys reside and determine the aggregate signature weight of the private keys submitted; and
compare the aggregate signature weight to the minimum signature weight required to make the change and, if the aggregate signature weight is greater than or equal to the minimum signature weight required to make the change, the processor is configured to generate and transmit the change, including an updated timestamp memorializing the date and time of the change;
wherein, the processor is further configured to monitor the state of the data in an estate vault and when a change occurs from a first state to a second state without the aggregate signature weight being greater than or equal to the minimum weight required to make the change, the processor is configured to issue orders:
reversing the change, and
optionally, instructing the oversight guardian to prohibit any future changes to the data in the estate vault by a party other than the testator, token issuer, or oversight guardian.

### Claim 2 (depends on 1)

The system of claim 1, wherein the application further implements a multi-layer encryption scheme in which data in the Estate Vault is encrypted using AES-256 in CTR mode with a randomly generated AES key and initialization vector (IV), and the AES key and IV are each encrypted using an RSA-2048 public key prior to storage or transmission.

### Claim 3 (depends on 1)

The system of claim 1, wherein the processor is further configured to form, for each Account Holder, a Total Concatenated String by combining: (i) an RSA private key; (ii) an encrypted AES key; and (iii) an encrypted AES IV, and to compute insertion indices for (ii) and (iii) within the RSA private key based on numeric values derived from UTF 16 code units of a Control String comprising ten consecutive characters of the RSA private key.

### Claim 4 (depends on 1)

The system of claim 1, wherein the application is further configured to generate an Account Holder key (AH Key) by removing at least four non-uniform 8-character chunks from the Total Concatenated String at interval-based positions and prepending the Control String to the removed chunks to produce a 50-character AH Key, while storing the remaining System Key on the system.

### Claim 5 (depends on 1)

The system of claim 1, wherein the environmental designation assigns higher signature weights to private keys residing in a cold environment than to private keys residing in a hot environment, the weights for cold signers being between two (2×) and ten (10×) the weights of hot signers.

### Claim 6 (depends on 1)

The system of claim 1, wherein the transaction weight designation differentiates among operation categories, such that “high” category operations comprising freezing access to an Estate Vault, re-keying documents in an Estate Vault, and reversing key transfers require an aggregate signature weight achievable only with at least a threshold number of cold signers.

### Claim 7 (depends on 1)

The system of claim 1, wherein the processor is further configured to generate, offload, and store Recovery Keys by: encrypting the AES key and AES IV with a newly generated RSA-2048 public key, combining the resulting encrypted strings, converting the combination to a QR code image, and transferring the QR code image to a non-Internet-connected device for storage, with optional additional storage on a BitLocker-protected USB device and paper printout in a locked safe.

### Claim 8 (depends on 1)

The system of claim 1, wherein the application implements a verification process that, upon uploading a staged QR code file, retrieves a corresponding RSA private key, validates readable content of the uploaded file, and upon successful verification deletes the staged file and removes any corresponding AES key and IV entries from a backup key table.

### Claim 9 (depends on 1)

The system of claim 1, wherein hot signers are enabled to perform low and medium category operations including: setting or storing data elements with a wallet address, establishing trust lines to token-issuer wallet(s), and sending title of documents held in the Estate Vault; and wherein cold signers are additionally enabled to perform high category operations including freezing access, re-keying, and reversing key transfers.

### Claim 10 (depends on 1)

The system of claim 1, wherein the processor continuously monitors for anomalies comprising state changes lacking a sufficient aggregate signature weight, and upon detecting such an anomaly automatically issues orders reversing the change and optionally instructs the oversight guardian to prohibit future changes by parties other than the testator, token issuer, or oversight guardian.

### Claim 11

A method for securing one or more estate vault(s) holding estate documents and other critical information, the method comprising:
receiving:
an instruction to make a change to a key, the instruction received from a testator, token issuer, or oversight guardian;
at least one private key signature, the private key signature authorizing the changing of the state of the key from a first state to a second state;
an environmental designation, previously configured or uploaded by an employee or agent of the token issuer or oversight guardian, wherein the environmental designation identifies the private key signatures that reside in a hot environment and the private key signatures that reside in a cold environment;
a signature weight designation, previously configured or uploaded by an employee or agent of the token issuer or oversight guardian, wherein the signature weight designation includes:
a signature weight ascribed to private key signatures residing primarily in a hot environment, and
a signature weight ascribed to private key signatures residing primarily in a cold environment, wherein the signature weight ascribed to private key signatures residing primarily in the cold environment is greater than the signature weight ascribed to private key signatures primarily residing in the hot environment; and
a transaction weight designation previously configured or uploaded by an employee or agent of the token issuer or oversight guardian,
establishing a minimum signature weight required to effectuate different state changes to the keys;
upon receiving the instruction and the transaction weight designation, comparing the instruction to the transaction weight designation and determining a minimum signature weight required to effectuate the state change;
upon receiving the environmental designation and the private key signatures comparing the environmental designation to the private keys and determining whether the private key signatures reside in a hot environment or a cold environment;
upon receiving the signature weight designation and the environment in which the private key signatures reside, comparing the signature weight designation to the determination of the environment in which the private key signatures reside and determining the aggregate signature weight of the private key signatures;
upon receiving the aggregate signature weight to the minimum signature weight required to make the state change and the minimum signature weight required to make the state change, comparing the signature weight designation to the determination of the environment in which the private key signatures reside and determining the aggregate signature weight of the private key signatures; and
monitoring the state of the keys and when a state change to the keys changes from the first state to the second state without the aggregate signature weight being greater than or equal to the minimum weight required to make the state change, issuing orders:
resetting the state of the keys to the first state, and optionally, instructing the oversight guardian to prohibit any changes to the estate vault by parties other than the testator, token issuer, or oversight guardian.

### Claim 12 (depends on 2)

The method of claim 2, further comprising encrypting data in the Estate Vault using AES-256 in CTR mode with a randomly generated AES key and IV, encrypting the AES key and IV with an RSA-2048 public key, and storing only the encrypted AES materials with the data to facilitate decryption upon authorized state changes.

### Claim 13 (depends on 2)

The method of claim 2, wherein generating indices for inserting an encrypted AES IV and an encrypted AES key into an RSA private key includes deriving numeric values from UTF 16 encodings of characters of a Control String comprising of ten consecutive characters of the RSA private key, computing an indentation value between 1 and 150 and a starting value between 1 and 199, and inserting the encrypted AES materials at positions based on those values to form a Total Concatenated String.

### Claim 14 (depends on 2)

The method of claim 2, further comprising forming an AH Key by dividing the Total Concatenated String into intervals based on its total length and a selected number n of chunks, removing at least four 8-character chunks at successive interval positions, embedding digits representing lengths of the encrypted AES IV and AES key into predetermined positions within the chunks using index adjustment values derived from the Control String, and prepending the Control String to produce a 50-character AH Key.

### Claim 15 (depends on 2)

The method of claim 2, wherein the environmental designation assigns a greater signature weight to private key signatures residing in a cold environment than to private key signatures residing in a hot environment, including a multiplier of at least three (3×) for cold signers relative to hot signers in certain configurations.

### Claim 16 (depends on 2)

The method of claim 2, wherein the transaction weight designation defines thresholds such that any two hot signers or a hot signer and a cold signer can authorize a token transfer, while at least two cold signers are required to authorize re-keying of data in the Estate Vault.

### Claim 17 (depends on 2)

The method of claim 2, further comprising generating Recovery Keys for use when the AH Key is unavailable by encrypting the AES key and IV with a newly generated RSA-2048 public key, combining the encrypted strings, converting the combination into a QR code image, staging and uploading the QR file to a non-Internet-connected device, verifying the file using a corresponding RSA private key, and upon verification deleting staged files and removing AES materials from backup tables, and then storing redundant copies on a BitLocker-protected USB drive and as a paper copy in a locked safe.

### Claim 18 (depends on 2)

The method of claim 2, wherein hot signers are permitted to perform low and medium category operations comprising setting or storing data elements with a wallet address, establishing trust lines to token-issuer wallet(s), and sending title of documents, and cold signers are additionally permitted to perform high category operations comprising freezing access, re-keying documents, and reversing key transfers.

### Claim 19 (depends on 2)

The method of claim 2, further comprising continuously monitoring the state of the keys and reversing any state change from the first state to the second state that lacks an aggregate signature weight greater than or equal to the required minimum, and optionally instructing the oversight guardian to prohibit further changes by parties other than the testator, token issuer, or oversight guardian.

### Claim 20 (depends on 2)

The method of claim 2, wherein the receiving of the instruction includes receiving a cryptographic signature signed by a separate private key held by the testator or a peer, comparing the signature to a stored public key, and, upon validation and satisfaction of the minimum signature weight, generating and transmitting a proposed transaction with an updated timestamp memorializing the change and authorizing keys or signatures.
