IP Library › Granted Patent US 12,499,443
Granted Patent B2
US 12,499,443 · App. 18/371,945 · Granted Dec 16, 2025

Secure control of transactions using blockchain

Inventors: David John Kamalsky (Campbell, CA); Vidit Aggarwal (Sunnyvale, CA); Seyed-Mahdi Pedramrazi (San Jose, CA); Ethan Benjamin Rubinson (Santa Clara, CA); Sachin Tilloo (Fremont, CA); Sergio Pinzon Gonzales, Jr. (San Jose, CA)
Assignee: eBay Inc.
G06Q20/389G06F21/10G06F21/30G06F21/602G06F21/62G06F21/6218G06F21/6245G06Q20/0855G06Q20/3825G06Q20/3829G06Q20/401G06Q20/42G06Q30/018G06Q40/08H04L9/0637H04L9/0643H04L9/30H04L9/3236H04L9/3239H04L9/3247H04L9/3297H04L63/102H04L63/12H04L65/612H04L67/53H04L67/63G06F16/1805G06F16/27G06F21/645G06F2221/2107H04L9/50H04L67/52H04L2209/56
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,499,443
App. No.
18/371,945
Granted
Dec 16, 2025
Kind
B2
Abstract

Technologies are shown for controlling a transaction on a blockchain. A first block is created on a blockchain for a transaction involving a seller entity associated with a first key, a buyer entity associated with a second key, and an intermediary entity associated with a third key. Funds for the transaction are associated with the first block. A second block storing refund code is created and linked to the first block. The refund code is executable to refund the funds when a seller digital signature using the first key and/or an intermediary digital signature using the third key are received. A third block storing payment code is created and linked to the first block. The payment code is executable to transfer the funds when a buyer digital signature using the second key and/or an intermediary digital signature using the third key are received.

Claims (58)

1 . A computer-implemented method executed by at least one of a plurality of nodes of a distributed ledger network, the method comprising:

creating a first block on a blockchain of the distributed ledger network, the first block committing a transaction amount for a transaction involving a seller entity associated with a first key, a buyer entity associated with a second key, and an intermediary entity associated with a third key;

creating, on the blockchain and cryptographically linked to the first block, a second block storing a refund code, the refund code executable by the plurality of nodes to transfer the committed transaction amount to an address controlled by the buyer entity only when a digital signature produced using the first key and/or the third key is present and no digital signature using the second key is present;

creating, on the blockchain and cryptographically linked to the first block, a third block storing a payment code, the payment code executable by the plurality of nodes to transfer the committed transaction amount to an a address controlled by the seller entity only when a digital signature produced using the second key and/or the third key is present and no digital signature using the first key is present; and

broadcasting the first block, the second block, and the third block to other nodes of the distributed ledger network, wherein each node validates a transaction that transfers the committed transaction amount by determining that the transaction satisfies either the refund code of the second block or the payment code of the third block.

2 . The computer-implemented method of claim 1 , wherein the refund code is further executable to verify the digital signature is produced using the first key and/or the third keypad least partially based on data within the second block before transfer of the committed transaction amount.

3 . The computer-implemented method of claim 1 , wherein the payment code is further executable to verify the digital signature is produced using the second key and/or the third keypad least partially based on data within the third block before transfer of the committed transaction amount.

4 . The computer-implemented method of claim 1 , wherein the method further comprises:

creating a multisignature address using the first key for the seller entity, the second key for the buyer entity, and the third key for the intermediary entity; and

wherein creating the first block on the blockchain comprises creating the first block on the blockchain with the multisignature address.

5 . The computer-implemented method of claim 1 , wherein the method further comprises:

creating a fourth block on the blockchain, the fourth block committing a second transaction amount for a second transaction involving the seller entity, a second buyer entity associated with a fourth key, and the intermediary entity;

creating, on the blockchain and cryptographically linked to the fourth block, a fifth block storing a second refund code, the second refund code executable by the plurality of nodes to transfer the committed second transaction amount to the second buyer entity when a digital signature produced using the first key and/or the third key is present and no digital signature using the fourth key is present;

creating, on the blockchain and cryptographically linked to the fourth block, a sixth block storing a second payment code, the second payment code executable by the plurality of nodes to transfer the committed second transaction amount to the seller entity when a digital signature produced using the fourth key and/or the third key is present and no digital signature using the first key is present; and

broadcasting the fourth block, the fifth block, and the sixth block to other nodes of the distributed ledger network, wherein each node validates a second transaction that transfers the committed second transaction amount by determining that the second transaction satisfies either the second refund code of the fifth block or the second payment code of the sixth block.

6 . The computer-implemented method of claim 1 , wherein the method further comprises:

executing the refund code to transfer the committed transaction amount in response to receiving the digital signature produced using the first key and/or the third key.

7 . The computer-implemented method of claim 1 , wherein the method further comprises:

executing the payment code to transfer the committed transaction amount in response to receiving the digital signature produced using the second key and/or the third key.

8 . One or more computer storage media storing computer-useable instructions that, when used by a computing device, cause the computing device to perform operations, the operations comprising:

creating a first block on a blockchain of the distributed ledger network, the first block committing a transaction amount for a transaction involving a seller entity associated with a first key, a buyer entity associated with a second key, and an intermediary entity associated with a third key;

creating, on the blockchain and cryptographically linked to the first block, a second block storing a refund code, the refund code executable by the plurality of nodes to transfer the committed transaction amount to an account of address controlled by the buyer entity only when a digital signature produced using the first key and/or the third key is present and no digital signature using the second key is present;

creating, on the blockchain and cryptographically linked to the first block, a third block storing a payment code, the payment code executable by the plurality of nodes to transfer the committed transaction amount to an a address controlled by the seller entity only when a digital signature produced using the second key and/or the third key seller is present and no digital signature using the first key is present; and

broadcasting the first block, the second block, and the third block to other nodes of the distributed ledger network, wherein each node validates a transaction that transfers the committed transaction amount by determining that the transaction satisfies either the refund code of the second block or the payment code of the third block.

9 . The one or more computer storage media of claim 8 , wherein the refund code is further executable to verify the digital signature is produced using the first key and/or the third keypad least partially based on data within the second block before transfer of the committed transaction amount.

10 . The one or more computer storage media of claim 8 , wherein the payment code is further executable to verify the digital signature is produced using the second key and/or the third keypad least partially based on data within the third block before transfer of the committed transaction amount.

11 . The one or more computer storage media of claim 8 , wherein the operations further comprise:

creating a multisignature address using the first key for the seller entity, the second key for the buyer entity, and the third key for the intermediary entity; and

wherein creating the first block on the blockchain comprises creating the first block on the blockchain with the multisignature address.

12 . The one or more computer storage media of claim 8 , wherein the operations further comprise:

creating a fourth block on the blockchain, the fourth block committing a second transaction amount for a second transaction involving the seller entity, a second buyer entity associated with a fourth key, and the intermediary entity;

creating, on the blockchain and cryptographically linked to the fourth block, a fifth block storing a second refund code, the second refund code executable by the plurality of nodes to transfer the committed second transaction amount to the second buyer entity when a digital signature produced using the first key and/or the third key is present and no digital signature using the fourth key is present;

creating, on the blockchain and cryptographically linked to the fourth block, a sixth block storing a second payment code, the second payment code executable by the plurality of nodes to transfer the committed second transaction amount to the seller entity when a digital signature produced using the fourth key and/or the third key is present and no digital signature using the first key is present; and

broadcasting the fourth block, the fifth block, and the sixth block to other nodes of the distributed ledger network, wherein each node validates a second transaction that transfers the committed second transaction amount by determining that the second transaction satisfies either the second refund code of the fifth block or the second payment code of the sixth block.

13 . The one or more computer storage media of claim 8 , wherein the operations further comprise:

executing the refund code to transfer the committed transaction amount in response to receiving the digital signature produced using the first key and/or the third key.

14 . The one or more computer storage media of claim 8 , wherein the operations further comprise:

executing the payment code to transfer the committed transaction amount in response to receiving the digital signature produced using the second key and/or the third key.

15 . A computer system comprising:

a processor; and

a computer storage medium storing computer-useable instructions that, when used by the processor, causes the computer system to perform operations comprising:

creating a first block on a blockchain of the distributed ledger network, the first block committing a transaction amount for a transaction involving a seller entity associated with a first key, a buyer entity associated with a second key, and an intermediary entity associated with a third key;

creating, on the blockchain and cryptographically linked to the first block, a second block storing a refund code, the refund code executable by the plurality of nodes to transfer the committed transaction amount to an address controlled by the buyer entity only when a digital signature produced using the first key and/or the third key is present and no digital signature using the second key is present;

creating, on the blockchain and cryptographically linked to the first block, a third block storing a payment code, the payment code executable by the plurality of nodes to transfer the committed transaction amount to an a address controlled by the seller entity only when a digital signature produced using the second key and/or the third key is present and no digital signature using the first key is present; and

broadcasting the first block, the second block, and the third block to other nodes of the distributed ledger network, wherein each node validates a transaction that transfers the committed transaction amount by determining that the transaction satisfies either the refund code of the second block or the payment code of the third block.

16 . The computer system of claim 15 , wherein the refund code is further executable to verify the digital signature is produced using the first key and/or the third key at least partially based on data within the second block before transfer of the committed transaction amount; and wherein the payment code is further executable to verify the digital signature is produced using the second key and/or the third keypad least partially based on data within the third block before transfer of the committed transaction amount.

17 . The computer system of claim 15 , wherein the operations further comprise:

creating a multisignature address using the first key for the seller entity, the second key for the buyer entity, and the third key for the intermediary entity; and

wherein creating the first block on the blockchain comprises creating the first block on the blockchain with the multisignature address.

18 . The computer system of claim 15 , wherein the operations further comprise:

creating a fourth block on the blockchain, the fourth block committing a second transaction amount for a second transaction involving the seller entity, a second buyer entity associated with a fourth key, and the intermediary entity;

creating, on the blockchain and cryptographically linked to the fourth block, a fifth block storing a second refund code, the second refund code executable by the plurality of nodes to transfer the committed second transaction amount to the second buyer entity when a digital signature produced using the first key and/or the third key is present and no digital signature using the fourth key is present;

creating, on the blockchain and cryptographically linked to the fourth block, a sixth block storing a second payment code, the second payment code executable by the plurality of nodes to transfer the committed second transaction amount to the seller entity when a digital signature produced using the fourth key and/or the third key is present and no digital signature using the first key is present; and

broadcasting the fourth block, the fifth block, and the sixth block to other nodes of the distributed ledger network, wherein each node validates a second transaction that transfers the committed second transaction amount by determining that the second transaction satisfies either the second refund code of the fifth block or the second payment code of the sixth block.

19 . The computer system of claim 15 , wherein the operations further comprise:

executing the refund code to transfer the committed transaction amount in response to receiving the digital signature produced using the first key and/or the third key.

20 . The computer system of claim 15 , wherein the operations further comprise:

executing the payment code to transfer the committed transaction amount in response to receiving the digital signature produced using the second key and/or the third key.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 22, 2023
From: KAMALSKY, DAVID JOHN; AGGARWAL, VIDIT; PEDRAMRAZI, SEYED-MAHDI; RUBINSON, ETHAN BENJAMIN; TILLOO, SACHIN; GONZALES, SERGIO PINZON, JR
To: EBAY INC.
Reel/Frame 065001/0048 →
Continuity (3)
Continuation 16041658 · Jul 20, 2018
Provisional Application 62612091 · Dec 29, 2017
Related Publication 20240013209A1 · Jan 11, 2024
References Cited (165)
US 5557088A · Shimizu et al. · 1996 [cited by applicant]
US 5607350A · Levasseur et al. · 1997 [cited by applicant]
US 7627531B2 · Breck et al. · 2009 [cited by applicant]
US 7656271B2 · Ehrman et al. · 2010 [cited by applicant]
US 9635000B1 · Muftic · 2017 [cited by applicant]
US 9641342B2 · Sriram et al. · 2017 [cited by applicant]
US 9680799B2 · Iyer et al. · 2017 [cited by applicant]
US 9722790B2 · Ebrahimi · 2017 [cited by applicant]
US 9749140B2 · Oberhauser et al. · 2017 [cited by applicant]
US 9749297B2 · Gvili · 2017 [cited by applicant]
US 9774578B1 · Ateniese et al. · 2017 [cited by applicant]
US 9794074B2 · Toll et al. · 2017 [cited by applicant]
US 9849364B2 · Tran et al. · 2017 [cited by applicant]
US 10022613B2 · Tran et al. · 2018 [cited by applicant]
US 10715323B2 · Chan et al. · 2020 [cited by applicant]
US 10764067B2 · Lewison et al. · 2020 [cited by applicant]
US 10839386B2 · Kamalsky et al. · 2020 [cited by applicant]
US 11115205B2 · Bitauld et al. · 2021 [cited by applicant]
US 11130042B2 · Tran et al. · 2021 [cited by applicant]
US 11803847B2 · Kamalsky et al. · 2023 [cited by applicant]
US 20040024688A1 · Bi et al. · 2004 [cited by applicant]
US 20040192437A1 · Amaitis · 2004 [cited by examiner]
US 20060100965A1 · Simelius · 2006 [cited by applicant]
US 20130174272A1 · Chevalier et al. · 2013 [cited by applicant]
US 20130219458A1 · Ramanathan · 2013 [cited by applicant]
US 20150269538A1 · Stanchfield · 2015 [cited by applicant]
US 20150302400A1 · Metral · 2015 [cited by applicant]
US 20150332283A1 · Witchey · 2015 [cited by applicant]
US 20160028552A1 · Spanos et al. · 2016 [cited by applicant]
US 20160191243A1 · Manning · 2016 [cited by applicant]
US 20160203572A1 · Mcconaghy et al. · 2016 [cited by applicant]
US 20160284033A1 · Winand · 2016 [cited by applicant]
US 20160300234A1 · Moss-pultz et al. · 2016 [cited by applicant]
US 20160321752A1 · Tabacco · 2016 [cited by applicant]
US 20160330034A1 · Back et al. · 2016 [cited by applicant]
US 20160335533A1 · Davis · 2016 [cited by applicant]
US 20160342976A1 · Davis · 2016 [cited by applicant]
US 20160342977A1 · Lam · 2016 [cited by applicant]
US 20160358184A1 · Radocchia et al. · 2016 [cited by applicant]
US 20160379212A1 · Bowman et al. · 2016 [cited by applicant]
US 20170005804A1 · Zinder · 2017 [cited by applicant]
US 20170011460A1 · Molinari et al. · 2017 [cited by applicant]
US 20170046526A1 · Chan et al. · 2017 [cited by applicant]
US 20170046651A1 · Lin et al. · 2017 [cited by applicant]
US 20170046664A1 · Haldenby et al. · 2017 [cited by applicant]
US 20170046693A1 · Haldenby et al. · 2017 [cited by applicant]
US 20170048209A1 · Lohe et al. · 2017 [cited by applicant]
US 20170078493A1 · Melika et al. · 2017 [cited by applicant]
US 20170103385A1 · Wilson et al. · 2017 [cited by applicant]
US 20170103390A1 · Wilson et al. · 2017 [cited by applicant]
US 20170109735A1 · Sheng et al. · 2017 [cited by applicant]
US 20170116693A1 · Rae et al. · 2017 [cited by applicant]
US 20170132620A1 · Miller · 2017 [cited by examiner]
US 20170132630A1 · Castinado et al. · 2017 [cited by applicant]
US 20170149560A1 · Shah · 2017 [cited by applicant]
US 20170177898A1 · Dillenberger · 2017 [cited by applicant]
US 20170232300A1 · Tran et al. · 2017 [cited by applicant]
US 20170236102A1 · Biton · 2017 [cited by applicant]
US 20170236103A1 · Biton · 2017 [cited by applicant]
US 20170236104A1 · Biton · 2017 [cited by applicant]
US 20170237570A1 · Vandervort · 2017 [cited by applicant]
US 20170243193A1 · Manian et al. · 2017 [cited by applicant]
US 20170250796A1 · Samid · 2017 [cited by applicant]
US 20170300627A1 · Giordano et al. · 2017 [cited by applicant]
US 20170300928A1 · Radocchia et al. · 2017 [cited by applicant]
US 20170302663A1 · Nainar et al. · 2017 [cited by applicant]
US 20170308872A1 · Uhr et al. · 2017 [cited by applicant]
US 20170317997A1 · Smith et al. · 2017 [cited by applicant]
US 20170329980A1 · Hu et al. · 2017 [cited by applicant]
US 20170331810A1 · Kurian · 2017 [cited by applicant]
US 20170337534A1 · Goeringer et al. · 2017 [cited by applicant]
US 20170338967A1 · Lewison et al. · 2017 [cited by applicant]
US 20170345011A1 · Salami et al. · 2017 [cited by applicant]
US 20170366353A1 · Struttmann · 2017 [cited by applicant]
US 20180018723A1 · Nagla et al. · 2018 [cited by applicant]
US 20180025442A1 · Isaacson et al. · 2018 [cited by applicant]
US 20180078843A1 · Tran et al. · 2018 [cited by applicant]
US 20180091524A1 · Setty et al. · 2018 [cited by applicant]
US 20180101844A1 · Song et al. · 2018 [cited by applicant]
US 20180117447A1 · Tran et al. · 2018 [cited by applicant]
US 20180143995A1 · Bailey et al. · 2018 [cited by applicant]
US 20180173719A1 · Bastide et al. · 2018 [cited by applicant]
US 20180257306A1 · Mattingly et al. · 2018 [cited by applicant]
US 20180294957A1 · O'Brien et al. · 2018 [cited by applicant]
US 20180309569A1 · Martin et al. · 2018 [cited by applicant]
US 20180330348A1 · Uhr et al. · 2018 [cited by applicant]
US 20180330349A1 · Uhr et al. · 2018 [cited by applicant]
US 20180349621A1 · Schvey et al. · 2018 [cited by applicant]
US 20180349893A1 · Tsai · 2018 [cited by applicant]
US 20190102409A1 · Shi et al. · 2019 [cited by applicant]
US 20190109713A1 · Clark et al. · 2019 [cited by applicant]
US 20190172057A1 · Vincent · 2019 [cited by applicant]
US 20190179801A1 · Jang et al. · 2019 [cited by applicant]
US 20190205558A1 · Gonzales, Jr. · 2019 [cited by applicant]
US 20190205563A1 · Gonzales, Jr. · 2019 [cited by applicant]
US 20190205870A1 · Kamalsky et al. · 2019 [cited by applicant]
US 20190205873A1 · Kamalsky et al. · 2019 [cited by applicant]
US 20190205894A1 · Gonzales et al. · 2019 [cited by applicant]
US 20190207995A1 · Gonzales, Jr. · 2019 [cited by applicant]
US 20200012763A1 · Arngren et al. · 2020 [cited by applicant]
US 20200036519A1 · Bitauld et al. · 2020 [cited by applicant]
US 20200119905A1 · Revankar et al. · 2020 [cited by applicant]
US 20200195436A1 · Khan · 2020 [cited by applicant]
US 20210035096A1 · Kamalsky et al. · 2021 [cited by applicant]
CN 106130738A · 2016 [cited by applicant]
CN 106777923A · 2017 [cited by applicant]
CN 106920169A · 2017 [cited by applicant]
CN 107070644A · 2017 [cited by applicant]
CN 107077682A · 2017 [cited by applicant]
CN 107086909A · 2017 [cited by applicant]
CN 107273759A · 2017 [cited by applicant]
EP 3413254A1 · 2018 [cited by applicant]
KR 101781583B1 · 2017 [cited by applicant]
WO 2016128567A1 · 2016 [cited by applicant]
WO 2017004527A1 · 2017 [cited by applicant]
WO 2017006136A1 · 2017 [cited by applicant]
WO 2017027900A1 · 2017 [cited by applicant]
WO 2017066002A1 · 2017 [cited by applicant]
WO 2017090041A1 · 2017 [cited by applicant]
WO 2017098519A1 · 2017 [cited by applicant]
WO 2017145003A1 · 2017 [cited by applicant]
WO 2017145017A1 · 2017 [cited by applicant]
WO 2017145047A1 · 2017 [cited by applicant]
WO 2017148245A1 · 2017 [cited by applicant]
WO 2017153495A1 · 2017 [cited by applicant]
WO 2017163069A1 · 2017 [cited by applicant]
WO 2017163220A1 · 2017 [cited by applicant]
WO 2017178956A1 · 2017 [cited by applicant]
WO 2017182601A1 · 2017 [cited by applicant]
WO 2017195160A1 · 2017 [cited by applicant]
WO 2017196701A1 · 2017 [cited by applicant]
WO 2019133307A1 · 2019 [cited by applicant]
WO 2019133308A1 · 2019 [cited by applicant]
WO 2019133309A1 · 2019 [cited by applicant]
WO 2019133310A1 · 2019 [cited by applicant]
Ethereum Wallets are Enabling Transaction Scheduling, Killer Feature, Ethereum News, Retrieved from the Internet URL: <https://www.ccn.com/ethereum-wallets-are-enabling-transaction-scheduling-killer-feature/>, Sep. 18, … [cited by applicant]
The Alarm Service Is Now Available on the Testnet, Retrieved from the Internet URL: <http://blog.ethereum-alarm-clock.com/blog/2016/1/16/the-alarm-service-is-now-available-on-the-testnet>, Jan. 16, 2016, 2 pages. [cited by applicant]
Bhargavan et al., “Short Paper: Formal Verification of Smart Contracts”, retrieved From Internet URL<http://research.microsoft.com/en-us/um/people/nswamy/papers/solidether.pdf>, Aug. 27, 2016, pp. 1-6. [cited by applicant]
Bidder Coin, “Bidder Coin, Bidder Coin White Paper, Dec. 28, 2017, pp. 36”, Dec. 28, 2017, 36 pages. [cited by applicant]
Chainfrog, “What are Smart Contracts?”, Retrieved from the Internet URL: <http://www.chainfrog.com/wp-content/uploads/2017/08/smart-contracts.pdf>, 2017, 13 pages. [cited by applicant]
Chan, “Motif Finding”, Retrieved from the Internet URL: <https://www.mathworks.com/matlabcentral/fileexchange/29362-motif-finding>, Nov. 15, 2010, 4 pages. [cited by applicant]
Chronologic, “Temporal Innovation on the Blockchain”, Retrieved from the Internet URL: <https://chronologic.network/uploads/Chronologic_Whitepaper.pdf>, Oct. 11, 2018, 25 pages. [cited by applicant]
Ethereum, “blockchain—How can a contract run itself at a later time?”, Retrieved from the Internet URL:<https://ethereum.stackexchange.com/questions/42/how-can-a-contract-run-itself-at-a-later-time>, Accesses date on Se… [cited by applicant]
Gollapudi, “White Paper—A Next-Generation Smart Contract and Decentralized Application Platform”, Retrieved from the Internet URL: < https://github.com/ethereum/wiki/wiki/White-Paper/f18902f4e7fb21dc92b37e8a0963eec4b3f4… [cited by applicant]
Huckle et al., “Internet ofThings, Blockchain and Shared Economy Applications”, Procedia Computer Science. Elsevier B.V. 98: 463., 2016, pp. 461-466. [cited by applicant]
Kehrli, “Blockchain Explained”, Retrieved from the Internet URL: <https://www.niceideas.ch/blockchain_explained.pdf>, Oct. 7, 2016, pp. 1-25. [cited by applicant]
Szabo, “Smart Contracts: Building Blocks for Digital Markets”, Retrieved online from the Internet URL: <http://www.alamut.com/subj/economics/nick_szabo/smartContracts.html>, 1996, pp. 1-17. [cited by applicant]
Triantafyllidis, “Developing an Ethereum Blockchain Application”, Retrieved from the Internet URL: <http://www.delaat.net/rp/2015-2016/p53/report.pdf >, Feb. 19, 2016, 59 pages. [cited by applicant]
Adams, “A Tech Startup Wants to Use Blockchain to Make Event Tickets Fraud-Proof”, Retrieved from the Internet URL: <https://www.forbes.com/sites/forbestreptalks/2017/06/15/a-tech-startup-upgraded-wants-to-use-blockchai… [cited by applicant]
Ateniese, et al., “Redactable Blockchain—or—Rewriting History in Bitcoin and Friends”, IEEE European Symposium on Security and Privacy, Mar. 11, 2017, pp. 1-38. [cited by applicant]
Aventus, “The Aventus Protocol: Blockchain for Ticketing”, Retrieved from the Internet URL: <https://aventus.io/>, Accessed on Sep. 11, 2018, 9 pages. [cited by applicant]
Blocktix, “Blocktix—an Ethereum Event Hosting Platform Designed for the Real World”, Retrieved from the Internet URL: <https://blog.blocktix.io/blocktix-an-ethereum-event-hosting-platform-designed-for-the-real-world-d52… [cited by applicant]
Chen et al., “Under-Optimized Smart Contracts Devour Your Money”, Retrieved from the Internet URL: <https://arxiv.org/pdf/1703.03994.pdf>, Mar. 11, 2016, 5 pages. [cited by applicant]
Cloudchain—Ticketing Platform Based on Blockchain—Reply, Retrieved from the Internet URL: <http://www.reply.com/en/content/blockchain-ticketing-solution-cloudchain>, Accessed on Sep. 11, 2018, 3 pages. [cited by applicant]
Event Chain, “Blockchain Secure Event Ticketing for Music, Festivals and Meetups”, Retrieved from the Internet URL: <https://eventchain.io/>, Accessed on Sep. 11, 2018, 9 pages. [cited by applicant]
Guts Tickets—Honest ticketing, Retrieved from the Internet URL: <https://guts.tickets/>, Accessed on Sep. 11, 2018, 9 pages. [cited by applicant]
Keane, “Blockchain Startups Take on Ticket Touting, but Will They Gain Traction?”, Retrieved from the Internet URL: <https://www.coindesk.com/blockchain-startups-take-ticket-touting-will-gain-traction/>, Jul. 30, 2017, … [cited by applicant]
Kishigami et al., “The Blockchain-Based Digital Content Distribution System”, 2015 IEEE Fifth International Conference on Big Data and Cloud Computing, Aug. 1, 2015, pp. 187-190. [cited by applicant]
Kosterova, “Crypto.tickets”, Retrieved from the Internet URL: <https://blog.crypto.tickets/>, Accessed on Sep. 11, 2018, 2 pages. [cited by applicant]
Ramachandran et al, “Using Blockchain and smart contracts for secure data provenance management”, Sep. 28, 2017, pp. 1-11. [cited by applicant]
Softjourn, “Blockchain Revolutionizes Ticketing”, Blockchain in Ticketing. Why do ticketing companies need it?, Retrieved from the Internet URL: <https://softjourn.com/blockchain-in-ticketing>, Accessed on Sep. 11, 2018… [cited by applicant]
Steichen, et al., “Blockchain-Based, Decentralized Access Control for IPFS”, Retrieved from the Internet URL: <https://www.researchgate.net/publication/327034734>, Jul. 2018, pp. 1499-1506. [cited by applicant]
Upgraded Tickets, “Digital “Smart” Tickets That Let You Trust Your Tickets and Maximize Your Event Experience”, Retrieved from the Internet URL: <https://www.upgraded-inc.com/>, Accessed on Sep. 11, 2018, 14 pages. [cited by applicant]
White Paper, “White Paper: PGP Key Management Server from Symantec”, An Introduction to PGP Key Management Server from Symantec, 2010, 17 pages. [cited by applicant]
Zhang, “Orthogonality Between Key Privacy and Data Privacy, Revisited”, ResearchGate, Conference Paper, Aug. 2007, pp. 1-16. [cited by applicant]