IP Library Granted Patent US 12,732,382
Granted Patent B2
US 12,732,382 · App. 19/069,792 · Granted Sep 8, 2026

Techniques for correcting anomalous activity caused by smart contracts

Inventor: Lyle Walter Paczkowski (Mission Hills, KS)
Assignee: T-Mobile USA, Inc.
H04L9/3247H04L9/50H04L2209/80
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,732,382
App. No.
19/069,792
Granted
Sep 8, 2026
Kind
B2
Abstract

A system can correct or avoid an unexpected result caused by executing a smart contract. The system can detect a potential/actual result generated based on a primary smart contract, which is stored in association with a block of a blockchain and is configured to execute when a predetermined condition is satisfied. The system can determine that the potential/actual result deviates from an expected result and, in response, retrieve a secondary smart contract from a repository. The secondary smart contract is selected to prevent the unexpected result in the future. The system can store the secondary smart contract retrieved from the repository in association with a subsequent block of the blockchain. The primary smart contract and the secondary smart contract are then configured to execute in concert when the predetermined condition is satisfied such that the expected result is produced instead of the unexpected result.

Claims (64)

1 . A system comprising:

at least one hardware processor; and

at least one non-transitory memory storing instructions, which, when executed by the at least one hardware processor, cause the system to:

perform a test to determine whether an output is anomalous,

wherein the output is based at least in part on a primary smart contract configured to execute when a predetermined condition is satisfied;

detect that the output is anomalous based at least in part on the execution of the primary smart contract;

in response to detecting that the output is anomalous, select a secondary smart contract stored at a repository,

wherein the secondary smart contract is selected from among multiple secondary smart contracts based at least in part on execution of the primary smart contract, and

wherein the secondary smart contract is configured to execute when the predetermined condition is satisfied and stop the output from being anomalous; and

jointly execute the primary smart contract and the secondary smart contract in response to the predetermined condition being satisfied.

2 . The system of claim 1 further caused to:

store the primary smart contract in a first block of a blockchain; and

store the secondary smart contract in a second block of the blockchain,

wherein the second block is subsequent in time to the first block of the blockchain.

3 . The system of claim 1 , wherein the primary smart contract and the secondary smart contract are co-located on a common node of a telecommunications network.

4 . The system of claim 1 , wherein retrieving the secondary smart contract from the repository comprises:

searching an index of the multiple secondary smart contracts based on a criterion of the primary smart contract,

wherein the index includes pointers from the multiple secondary smart contracts to locations of the repository storing the multiple secondary smart contracts; and

retrieving the secondary smart contract from a location of the repository based on a pointer of the index.

5 . The system of claim 1 further caused to:

host the primary smart contract on the non-transitory memory; and

link, over a telecommunications network, to the repository on a memory of a server located remote from the non-transitory memory.

6 . A computer-implemented method comprising:

detecting that an output of a primary smart contract is anomalous based at least in part on an execution of the primary smart contract,

wherein the primary smart contract is configured to execute when one or more predetermined conditions are satisfied; and

in response to detecting that the output is anomalous, select a secondary smart contract stored at a repository,

wherein the secondary smart contract is selected from among multiple secondary smart contracts based at least in part on execution of the primary smart contract,

wherein the secondary smart contract is configured to execute when the one or more predetermined conditions are satisfied and stop the output from being anomalous; and

causing orchestrated execution the primary smart contract and the secondary smart contract in response to the one or more predetermined conditions being satisfied.

7 . The method of claim 6 , further comprising:

linking the primary smart contract and the secondary smart contract stored at the repository such that the primary smart contract and the secondary smart contract are capable of orchestrated execution.

8 . The method of claim 6 , wherein detecting that an output of a primary smart contract is anomalous based at least in part on the execution of the primary smart contract comprises:

performing a test to determine a test output of the primary smart contract; and

detecting that the test output deviates from an expected output.

9 . The method of claim 6 , further comprising:

storing the primary smart contract in a first block of a blockchain; and

storing the secondary smart contract in a second block of the blockchain,

wherein the second block is subsequent in time to the first block of the blockchain.

10 . The method of claim 6 , wherein the primary smart contract and the secondary smart contract are co-located on a common node of a telecommunications network.

11 . The method of claim 6 , further comprising:

hosting the primary smart contract on a memory of a wireless device; and

hosting the repository on the memory of the wireless device.

12 . The method of claim 6 , further comprising:

hosting the primary smart contract on a memory of a wireless device; and

linking, over a telecommunications network, to the repository on a memory of a server located remote from the wireless device.

13 . At least one non-transitory computer-readable storage medium storing instructions, which, when executed by at least one data processor, cause the at least one data processor to:

detect an error in response to the execution of a primary smart contract,

wherein the primary smart contract is configured to execute when a predetermined condition is satisfied to produce an expected result;

in response to the error being detected, select a secondary smart contract stored at a repository,

wherein the repository stores multiple secondary smart contracts configured to correct errors caused by execution of smart contracts,

wherein the secondary smart contract is selected to correct the error caused by execution of the primary smart contract; and

cause orchestrated execution of the primary smart contract and the secondary smart contract when the predetermined condition is satisfied to prevent the error.

14 . The at least one computer-readable storage medium of claim 13 further causing the at least one data processor to:

link the primary smart contract and the secondary smart contract such that the primary smart contract and the secondary smart contract are capable of orchestrated execution.

15 . The at least one computer-readable storage medium of claim 13 further causing the at least one data processor to:

retrieve the secondary smart contract from the repository; and

cause storage of the secondary smart contract in association with a block of a blockchain.

16 . The at least one computer-readable storage medium of claim 13 :

wherein the primary smart contract is configured to execute when the predetermined condition is satisfied by a software program to produce the expected result;

wherein the expected result occurs when the predetermined condition is satisfied by a first version of the software program, and

wherein the error occurs when the predetermined condition is satisfied by a second version of the software program different from the first version of the software program.

17 . The at least one computer-readable storage medium of claim 13 further causing the at least one data processor to:

host the primary smart contract on the at least one computer-readable storage medium; and

link, over a telecommunications network, to the repository on a memory of a server located remote from the at least one data processor.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2025
From: PACZKOWSKI, LYLE WALTER
To: T-MOBILE USA, INC.
Reel/Frame 070468/0157 →
Continuity (2)
Continuation 17990289 · Nov 18, 2022
Related Publication 20250202714A1 · Jun 19, 2025
References Cited (72)
US 10594477B2 · Shao · 2020 [cited by examiner]
US 10616324B1 · Kaddoura · 2020 [cited by examiner]
US 10812255B2 · Li · 2020 [cited by applicant]
US 11018851B2 · Sarin · 2021 [cited by applicant]
US 11057221B2 · Peng · 2021 [cited by applicant]
US 11068887B2 · Xia et al. · 2021 [cited by applicant]
US 11113271B2 · Zhuo et al. · 2021 [cited by applicant]
US 11139979B2 · Van De Ruit et al. · 2021 [cited by applicant]
US 11171782B2 · Tang et al. · 2021 [cited by applicant]
US 11176257B2 · Braghin et al. · 2021 [cited by applicant]
US 11315120B2 · Levacher et al. · 2022 [cited by applicant]
US 11354656B2 · Xia et al. · 2022 [cited by applicant]
US 11356270B2 · Fang · 2022 [cited by applicant]
US 11611445B2 · Baykaner · 2023 [cited by examiner]
US 20170308431A1 · Otterstedt · 2017 [cited by examiner]
US 20190236559A1 · Padmanabhan · 2019 [cited by applicant]
US 20190303623A1 · Reddy et al. · 2019 [cited by applicant]
US 20200235947A1 · Baykaner · 2020 [cited by examiner]
US 20200285633A1 · Zhuo · 2020 [cited by examiner]
US 20210004216A1 · Chang · 2021 [cited by examiner]
US 20210149880A1 · Ivkushkin et al. · 2021 [cited by applicant]
US 20210374731A1 · Kim · 2021 [cited by applicant]
US 20220029810A1 · Tang et al. · 2022 [cited by applicant]
US 20220318399A1 · Rodler · 2022 [cited by examiner]
CN 111028077A · 2020 [cited by applicant]
CN 111066047A · 2020 [cited by applicant]
CN 111417946A · 2020 [cited by applicant]
CN 107317730B · 2020 [cited by applicant]
CN 111738480A · 2020 [cited by applicant]
CN 111767555A · 2020 [cited by applicant]
CN 111831740A · 2020 [cited by applicant]
CN 111861465A · 2020 [cited by applicant]
CN 112085600A · 2020 [cited by applicant]
CN 112602083A · 2021 [cited by applicant]
CN 110692228B · 2022 [cited by applicant]
DE 102016109209A1 · 2017 [cited by applicant]
DE 102017005623A1 · 2018 [cited by applicant]
DE 102017212904A1 · 2019 [cited by applicant]
DE 102017223522A1 · 2019 [cited by applicant]
DE 102018002466A1 · 2019 [cited by applicant]
DE 102020100787A1 · 2020 [cited by applicant]
DE 102019000985A1 · 2020 [cited by applicant]
DE 102019202381A1 · 2020 [cited by applicant]
DE 102019006333A1 · 2021 [cited by applicant]
DE 112018007724T5 · 2021 [cited by applicant]
DE 102020113057A1 · 2021 [cited by applicant]
DE 102020113557A1 · 2021 [cited by applicant]
DE 102021109517A1 · 2021 [cited by applicant]
EP 3396575B1 · 2019 [cited by applicant]
EP 3654197A1 · 2020 [cited by applicant]
EP 3688717A1 · 2020 [cited by applicant]
EP 3769243A1 · 2021 [cited by applicant]
EP 3499789B1 · 2021 [cited by applicant]
EP 3841496A1 · 2021 [cited by applicant]
EP 3860043A2 · 2021 [cited by applicant]
EP 3673432B1 · 2021 [cited by applicant]
EP 3905165A1 · 2021 [cited by applicant]
EP 3821578B1 · 2022 [cited by applicant]
EP 3896894B1 · 2022 [cited by applicant]
JP 6638024B2 · 2019 [cited by applicant]
JP 2020501402A · 2020 [cited by applicant]
JP 2020510906A · 2020 [cited by applicant]
JP 7012730B2 · 2022 [cited by applicant]
KR 102030171B1 · 2019 [cited by applicant]
KR 102139551B1 · 2020 [cited by applicant]
WO 2018111295A1 · 2018 [cited by applicant]
WO 2019058340A1 · 2019 [cited by applicant]
WO 2019191515A1 · 2019 [cited by applicant]
WO 2020095226A1 · 2020 [cited by applicant]
WO 2020145591A1 · 2020 [cited by applicant]
WO 2021032192A1 · 2021 [cited by applicant]
WO 2022200035A1 · 2022 [cited by applicant]