Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: EP2628142A4 Filed: 2010-10-12 Issued: 2014-04-09 Patent Holder: (Original Assignee) Thomson Reuters Markets LLC (Current Assignee) Thomson Reuters Markets LLC Inventor(s): Adam E Dix, Robert Warshaw, Joseph Franchi Title: Method and system for routing ioi's and trade orders |
1 |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US20130332343A1 Filed: 2005-10-06 Issued: 2013-12-12 Patent Holder: (Original Assignee) C SAM Inc (Current Assignee) Mastercard Mobile Transaction Solutions Inc Inventor(s): Mehul Desai, Satyan G. Pitroda, Nehal Maniar Title: Multi-tiered, secure mobile transactions ecosystem enabling platform comprising a personalization tier, a service tier, and an enabling tier |
[FEATURE ID: 1] computing device, transaction, transfer mechanism, decentralized digital currency, memory, second data source, computer processor, input, ledger, complete data record, computer network, copy, external state, device | network, wallet, component, system, gateway, browser, module | [FEATURE ID: 1] platform, multi-domain ecosystem, personalization tier, service, mobile device, tier, service tier, portion, server, tier application, wallet container application, mobile devices, client device, client, client runtime component, client independent application, client independent API layer, client runtime component abstracts client specific runtime environment, wallet capability, software development kit, specific wallet |
[TRANSITIVE ID: 2] processing, receiving | managing, executing, providing, establishing, implementing, facilitating, initiating | [TRANSITIVE ID: 2] enabling, effecting |
[FEATURE ID: 3] second client device | user, transaction, network | [FEATURE ID: 3] service provider |
[TRANSITIVE ID: 4] comprising, storing | having, including, providing, includes, incorporating, managing, implementing | [TRANSITIVE ID: 4] comprising |
[FEATURE ID: 5] network interface | receipt, storage, server | [FEATURE ID: 5] effect secure delivery |
[FEATURE ID: 6] terms | communications, content, transactions | [FEATURE ID: 6] execution |
[FEATURE ID: 7] reference | linkage, connection, coupling, linking, interaction, engagement, secure | [FEATURE ID: 7] user access, interoperation |
[FEATURE ID: 8] expiration timestamp, inchoate data record | event, account, enclave, order, index, application, operation | [FEATURE ID: 8] electronic wallet capability |
[TRANSITIVE ID: 9] coupled | accessible, configured, associated | [TRANSITIVE ID: 9] personalized |
[TRANSITIVE ID: 10] configured | disposed, implemented, operable, arranged, operative, executable, coupled | [TRANSITIVE ID: 10] configured, executing |
[TRANSITIVE ID: 11] read, compute, create | receive, provide, derive, determine, obtain, establish, compose | [TRANSITIVE ID: 11] facilitate |
[FEATURE ID: 12] data | transaction, operation, receipt | [FEATURE ID: 12] secure delivery |
[FEATURE ID: 13] digital currency | wallet, meter, platform | [FEATURE ID: 13] side workflow |
[FEATURE ID: 14] central authority | service, transaction, system | [FEATURE ID: 14] provider |
[FEATURE ID: 15] network participants | components, functions, users, systems, devices, infrastructure, software | [FEATURE ID: 15] ecosystem service elements, resources, different types, specific runtime environment features, client specific resources |
[FEATURE ID: 16] claim | preceding claim, embodiment, item, aspect, clair, paragraph, clause | [FEATURE ID: 16] claim |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction [FEATURE ID: 1] between a first client device , and a second client device [FEATURE ID: 3] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 4] a decentralized digital currency [FEATURE ID: 1] , the computing device comprising : a memory [FEATURE ID: 1] for storing [TRANSITIVE ID: 4] a first asymmetric key pair , the first asymmetric key pair comprising a first private key and a first public key ; a network interface [FEATURE ID: 5] for receiving [TRANSITIVE ID: 2] terms [FEATURE ID: 6] , the terms comprising : at least one of a first principal data or a second principal data ; a reference [FEATURE ID: 7] to at least one of a first data source or a second data source [FEATURE ID: 1] ; and an expiration timestamp [FEATURE ID: 8] ; a computer processor [FEATURE ID: 1] coupled [TRANSITIVE ID: 9] to the memory and the network interface , the computer processor configured [TRANSITIVE ID: 10] to : read [TRANSITIVE ID: 11] the first private key from the memory ; compute [TRANSITIVE ID: 11] a first cryptographic signature from the first private key ; create [TRANSITIVE ID: 11] an inchoate data record [FEATURE ID: 8] comprising : a commit input [FEATURE ID: 1] for receiving a commit data [FEATURE ID: 12] from a commit transaction ; one or more output data obtained from at least one of the first principal data or the second principal data , and a value data from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 13] comprises a distributed ledger [FEATURE ID: 1] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 14] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 1] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants [FEATURE ID: 15] in the computer network [FEATURE ID: 1] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy [FEATURE ID: 1] of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 1] . 2 . The device [FEATURE ID: 1] of claim [FEATURE ID: 16] |
1 - 181 . ( canceled ) 182 . A platform [FEATURE ID: 1] for secure personalized transactions in a multi-domain ecosystem [FEATURE ID: 1] comprising [TRANSITIVE ID: 4] : a personalization tier [FEATURE ID: 1] configured [TRANSITIVE ID: 10] to enable service provider personalization of one or more ecosystem service elements [FEATURE ID: 15] each configured to facilitate [TRANSITIVE ID: 11] user access [FEATURE ID: 7] to at least one service [FEATURE ID: 1] of the service provider [FEATURE ID: 3] via execution [FEATURE ID: 6] on a mobile device [FEATURE ID: 1] ; an enabling [TRANSITIVE ID: 2] tier [FEATURE ID: 1] executing [TRANSITIVE ID: 10] on the mobile device configured to facilitate interoperation [FEATURE ID: 7] of the personalization tier and a service tier [FEATURE ID: 1] with resources [FEATURE ID: 15] of the mobile device ; and the service tier further effecting [TRANSITIVE ID: 2] secure delivery [FEATURE ID: 12] of the at least one service independently of the enabling tier via at least one of the one or more service provider personalized [TRANSITIVE ID: 9] ecosystem service elements . 183 . The platform of claim [FEATURE ID: 16] 182 , further comprising a portion [FEATURE ID: 1] of the enabling tier executing on a server [FEATURE ID: 1] configured to effect secure delivery [FEATURE ID: 5] of the at least one service . 184 . The platform of claim 182 , wherein an enabling tier application [FEATURE ID: 1] operates in cooperation with a wallet container application [FEATURE ID: 1] adapted for execution on a plurality of different types [FEATURE ID: 15] of mobile devices [FEATURE ID: 1] . 185 . The platform of claim 184 , wherein the wallet container application enables an electronic wallet capability [FEATURE ID: 8] on the client device [FEATURE ID: 1] by abstracting client [FEATURE ID: 1] - specific runtime environment features [FEATURE ID: 15] . 186 . The platform of claim 182 , wherein an enabling tier application comprises a client runtime component [FEATURE ID: 1] adapted for execution on a mobile device . 187 . The platform of claim 186 , wherein the client runtime component is a client independent application [FEATURE ID: 1] that interoperates with client specific resources [FEATURE ID: 15] via a client independent API layer [FEATURE ID: 1] . 188 . The platform of claim 186 , wherein the client runtime component abstracts client specific runtime environment [FEATURE ID: 1] features to enable a wallet capability [FEATURE ID: 1] . 189 . The platform of claim 182 , wherein the personalization tier comprises a software development kit [FEATURE ID: 1] for developing a provider [FEATURE ID: 14] - specific wallet [FEATURE ID: 1] . 190 . The platform of claim 182 , wherein the service tier comprises a client - side workflow [FEATURE ID: 13] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US8583534B1 Filed: 2005-09-30 Issued: 2013-11-12 Patent Holder: (Original Assignee) Trading Technologies International Inc (Current Assignee) Trading Technologies International Inc Inventor(s): Robert J. Slezak Title: System and method for multi-market risk control in a distributed electronic trading environment |
[FEATURE ID: 1] computing device, first client device, transfer mechanism, decentralized digital currency, memory, first private key, network interface, second data source, computer processor, digital currency, ledger, central authority, second client device signs | network, processor, device, database, computer, server, system | [FEATURE ID: 1] method, first intermediary device, first client device, first electronic exchange, central module, second intermediary device, second client device, second matching process, second electronic exchange, local module |
[TRANSITIVE ID: 2] processing, storing, receiving, compute, create | creating, managing, providing, establish, accepting, generating, obtaining | [TRANSITIVE ID: 2] establishing |
[FEATURE ID: 3] transaction, first principal data, first cryptographic signature, complete data record | message, first, contract, communication, price, query, second | [FEATURE ID: 3] first tradeable object, balance, request |
[FEATURE ID: 4] second client device, reference, commit, value data | first, second, transaction, third, request, balance, trade | [FEATURE ID: 4] first local account balance, first matching process, trading account, second local account balance, second tradeable object, second portion, remaining, first trade order, second trade order, second trading account, second account balance |
[TRANSITIVE ID: 5] comprising | facilitating, implementing, managing, includes, using, comprises, having | [TRANSITIVE ID: 5] risk management, comprising |
[FEATURE ID: 6] first public key, second cryptographic signature | token, value, password, cryptogram, counter, message, hash | [FEATURE ID: 6] non-monetary balance |
[FEATURE ID: 7] terms | requests, claims, transactions, items, commands, messages | [FEATURE ID: 7] orders |
[FEATURE ID: 8] second principal data | transaction, currency, value, total, fund, sum, price | [FEATURE ID: 8] central account balance, monetary balance |
[FEATURE ID: 9] expiration timestamp, external state | application, event, identifier, action, electronic, algorithm, index | [FEATURE ID: 9] electronic trading environment |
[TRANSITIVE ID: 10] coupled, configured | arranged, set, assigned, disposed, operable, associated, secured | [TRANSITIVE ID: 10] established |
[FEATURE ID: 11] inchoate data record | account, item, addendum | [FEATURE ID: 11] additional account balance |
[FEATURE ID: 12] input, data, copy, recording | value, status, state, request, key, receipt, signature | [FEATURE ID: 12] portion |
[FEATURE ID: 13] network participants | devices, clients, servers, computers | [FEATURE ID: 13] different intermediary devices |
[FEATURE ID: 14] computer network | order, transaction, exchange | [FEATURE ID: 14] trade |
[FEATURE ID: 15] claim | clause, preceding claim, patent, clair, of claim, figure, embodiment | [FEATURE ID: 15] claim |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction [FEATURE ID: 3] between a first client device [FEATURE ID: 1] , and a second client device [FEATURE ID: 4] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 5] a decentralized digital currency [FEATURE ID: 1] , the computing device comprising : a memory [FEATURE ID: 1] for storing [TRANSITIVE ID: 2] a first asymmetric key pair , the first asymmetric key pair comprising a first private key [FEATURE ID: 1] and a first public key [FEATURE ID: 6] ; a network interface [FEATURE ID: 1] for receiving [TRANSITIVE ID: 2] terms [FEATURE ID: 7] , the terms comprising : at least one of a first principal data [FEATURE ID: 3] or a second principal data [FEATURE ID: 8] ; a reference [FEATURE ID: 4] to at least one of a first data source or a second data source [FEATURE ID: 1] ; and an expiration timestamp [FEATURE ID: 9] ; a computer processor [FEATURE ID: 1] coupled [TRANSITIVE ID: 10] to the memory and the network interface , the computer processor configured [TRANSITIVE ID: 10] to : read the first private key from the memory ; compute [TRANSITIVE ID: 2] a first cryptographic signature [FEATURE ID: 3] from the first private key ; create [TRANSITIVE ID: 2] an inchoate data record [FEATURE ID: 11] comprising : a commit [TRANSITIVE ID: 4] input [FEATURE ID: 12] for receiving a commit data [FEATURE ID: 12] from a commit transaction ; one or more output data obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 4] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger [FEATURE ID: 1] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 1] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 3] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants [FEATURE ID: 13] in the computer network [FEATURE ID: 14] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs [FEATURE ID: 1] the inchoate data record and saves a copy [FEATURE ID: 12] of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording [FEATURE ID: 12] of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 9] . 2 . The device of claim [FEATURE ID: 15] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further configured to : compute a second cryptographic signature [FEATURE ID: 6] |
1 . A method [FEATURE ID: 1] for risk management [FEATURE ID: 5] in an electronic trading environment [FEATURE ID: 9] , comprising [TRANSITIVE ID: 5] : establishing [TRANSITIVE ID: 2] a first local account balance [FEATURE ID: 4] at a first intermediary device [FEATURE ID: 1] that forwards trade [TRANSITIVE ID: 14] orders [FEATURE ID: 7] to buy or sell a first tradeable object [FEATURE ID: 3] from a first client device [FEATURE ID: 1] to a first matching process [FEATURE ID: 4] at a first electronic exchange [FEATURE ID: 1] , the first local account balance comprising a first portion of a central account balance [FEATURE ID: 8] established [TRANSITIVE ID: 10] for a trading account [FEATURE ID: 4] at a central module [FEATURE ID: 1] , wherein the first portion is of a first type of balance [FEATURE ID: 3] ; establishing a second local account balance [FEATURE ID: 4] at a second intermediary device [FEATURE ID: 1] that forwards trade orders to buy or sell a second tradeable object [FEATURE ID: 4] from a second client device [FEATURE ID: 1] to a second matching process [FEATURE ID: 1] at a second electronic exchange [FEATURE ID: 1] , the second local account balance comprising a second portion [FEATURE ID: 4] of the first type of balance at the central account balance established for the trading account , the second portion allocated based on a remaining [TRANSITIVE ID: 4] portion [FEATURE ID: 12] of the first type of balance of the central account balance after the first local account balance was allocated from the central account balance , wherein the first intermediary device and the second intermediary device are different intermediary devices [FEATURE ID: 13] ; upon receiving at the first intermediary device a first trade order [FEATURE ID: 4] associated with the trading account to be sent to the first matching process , determining whether to send the first trade order to the first matching process based on the first local account balance , without communicating with the central module associated with the central account balance , wherein the first intermediary device sends the first trade order to the first matching process when the first local account balance is sufficient , and wherein the first intermediary device refrains from sending the first trade order to the first matching process when the first local account balance is not sufficient ; and upon receiving at the second intermediary device a second trade order [FEATURE ID: 4] associated with the second trading account [FEATURE ID: 4] to be sent to the second matching process , determining whether to send the second trade order to the second matching process based on the second local account balance , without communicating with the central module associated with the central account balance , wherein the second intermediary device sends the second trade order to the second matching process when the second local account balance is sufficient , and wherein the second intermediary device refrains from sending the second trade order to the second matching process when the second local account balance is not sufficient ; and upon determining that the first local account balance is not sufficient when the first trade order is received , sending a request [FEATURE ID: 3] to the central module associated with the central account balance to allocate an additional account balance [FEATURE ID: 11] to the first local account balance ; and upon determining that the second local account balance is not sufficient when the second trade order is received , sending a request to the central module associated with the central account balance to allocate an additional account balance to the second local account balance . 2 . The method of claim [FEATURE ID: 15] 1 , further comprising : when the first local account balance is sufficient upon allocation of the additional account balance to send the first trade order , sending the first trade order to the first matching process ; and when the second local account balance is sufficient upon allocation of the additional account balance to send the second trade order , sending the second trade order to the second matching process . 3 . The method of claim 1 , further comprising : updating the first local account balance upon sending the first trade order to the first matching process ; and updating the second local account balance upon sending the second trade order to the second matching process . 4 . The method of claim 1 , wherein when the first local account balance is not sufficient , the method further comprising : sending a request to a local module [FEATURE ID: 1] associated with the second local account balance to allocate an additional account balance to the first local account balance . 5 . The method of claim 4 , further comprising : allocating the additional account balance from the second local account balance to the first local account balance ; and when the first account balance is sufficient upon allocation of the additional account balance from the second local account balance , sending the first trade order to the first matching process . 6 . The method of claim 1 , wherein when the second local account balance is not sufficient , the method further comprising : sending a request to a local module associated with the first local account balance to allocate an additional account balance to the second local account balance . 7 . The method of claim 6 , further comprising : allocating the additional account balance from the first local account balance to the second local account balance ; and when the second account balance [FEATURE ID: 4] is sufficient upon allocation of the additional account balance from the first local account balance , sending the second trade order to the second matching process . 8 . The method of claim 1 , wherein the first account balance comprises a monetary balance [FEATURE ID: 8] for the trading account . 9 . The method of claim 1 , wherein the second account balance comprises a monetary balance for the trading account . 10 . The method of claim 1 , wherein the first account balance comprises a non-monetary balance [FEATURE ID: 6] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US20130212388A1 Filed: 2012-02-13 Issued: 2013-08-15 Patent Holder: (Original Assignee) AlephCloud Systems Inc (Current Assignee) AlephCloud Systems Inc Inventor(s): Roy Peter D'Souza, Jieming Zhu Title: Providing trustworthy workflow across trust boundaries |
[FEATURE ID: 1] computing device, network interface, digital currency | device, mechanism, network, system, platform, server, process | [FEATURE ID: 1] method |
[TRANSITIVE ID: 2] processing, storing, receiving, compute | transmitting, managing, exchanging, transferring, creating, establishing, obtaining | [TRANSITIVE ID: 2] providing, generating, maintaining, publishing, encrypting, re-encrypting |
[FEATURE ID: 3] second client device, second principal data, second data source, central authority | second, third, first, user, key, third party, party | [FEATURE ID: 3] first party A, second party B, second public key, second secret key |
[TRANSITIVE ID: 4] comprising | including, containing, using, involving, comprises, by, employing | [TRANSITIVE ID: 4] comprising, having |
[FEATURE ID: 5] first asymmetric key pair, first private key, reference, first cryptographic signature, data, complete data record, copy, second cryptographic signature | key, secret key, secret, value, first, cryptographic key, certificate | [FEATURE ID: 5] first public key, first secret key, second proxy re-encryption key, key k, first proxy re-enctyption key, public key, secret key SK B, proxy re-encryption key, cryptographic |
[FEATURE ID: 6] first public key | hash, key, value, signature, seed, password, salt | [FEATURE ID: 6] cryptographic function |
[FEATURE ID: 7] terms, expiration timestamp, value data | content, information, communications, material, messages, authentication, identity | [FEATURE ID: 7] trustworthy workflow, trust boundaries, data |
[FEATURE ID: 8] need, recording | use, assistance, availability, receipt, involvement, provision, ownership | [FEATURE ID: 8] knowledge |
[FEATURE ID: 9] network participants | parties, members, users, providers, managers, publishers, entities | [FEATURE ID: 9] curators, custodians |
[FEATURE ID: 10] claim | clause, preceding claim, of claim, clair, the claim, claims, figure | [FEATURE ID: 10] claim |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction between a first client device , and a second client device [FEATURE ID: 3] via a transfer mechanism , the transfer mechanism comprising [TRANSITIVE ID: 4] a decentralized digital currency , the computing device comprising : a memory for storing [TRANSITIVE ID: 2] a first asymmetric key pair [FEATURE ID: 5] , the first asymmetric key pair comprising a first private key [FEATURE ID: 5] and a first public key [FEATURE ID: 6] ; a network interface [FEATURE ID: 1] for receiving [TRANSITIVE ID: 2] terms [FEATURE ID: 7] , the terms comprising : at least one of a first principal data or a second principal data [FEATURE ID: 3] ; a reference [FEATURE ID: 5] to at least one of a first data source or a second data source [FEATURE ID: 3] ; and an expiration timestamp [FEATURE ID: 7] ; a computer processor coupled to the memory and the network interface , the computer processor configured to : read the first private key from the memory ; compute [TRANSITIVE ID: 2] a first cryptographic signature [FEATURE ID: 5] from the first private key ; create an inchoate data record comprising : a commit input for receiving a commit data [FEATURE ID: 5] from a commit transaction ; one or more output data obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 7] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger that enables processing the transaction between the first client device and the second client device without the need [FEATURE ID: 8] for a trusted central authority [FEATURE ID: 3] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 5] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants [FEATURE ID: 9] in the computer network for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy [FEATURE ID: 5] of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording [FEATURE ID: 8] of the complete data record in the distributed ledger by observing an external state . 2 . The device of claim [FEATURE ID: 10] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further configured to : compute a second cryptographic signature [FEATURE ID: 5] |
1 . A method [FEATURE ID: 1] of providing [TRANSITIVE ID: 2] trustworthy workflow [FEATURE ID: 7] across trust boundaries [FEATURE ID: 7] between a first party A [FEATURE ID: 3] and a second party B [FEATURE ID: 3] , comprising [TRANSITIVE ID: 4] : one or more curators [FEATURE ID: 9] generating [TRANSITIVE ID: 2] a first public key [FEATURE ID: 5] ( PK C1 ) and a second public key [FEATURE ID: 3] ( PK C ) , and the one or more curators generating and maintaining [TRANSITIVE ID: 2] a first secret key [FEATURE ID: 5] ( SK C1 ) and a second secret key [FEATURE ID: 3] ( SK C ) ; the one or more curators publishing [TRANSITIVE ID: 2] the first public key ( PK C1 ) and the second public key ( PK C2 ) ; the one or more curators generating a first proxy re-encryption key RK C1 - C2 ) and a second proxy re-encryption key [FEATURE ID: 5] ( RK C2 - B ) ; the first party A encrypting [TRANSITIVE ID: 2] data [FEATURE ID: 7] having [TRANSITIVE ID: 4] a key k [FEATURE ID: 5] , wherein k is encrypted according to the first public key ( PK C1 ) ; one or more custodians proxy re-encrypting [TRANSITIVE ID: 2] k from the first public key ( PK C ) to the second public key ( PK C2 ) using the first proxy re-enctyption key [FEATURE ID: 5] ( RK C1 - C2 ) herein the proxy re-encryption is one - way ; the one or more custodians proxy re-encrypting k from the second public key ( PK C2 ) to a public key [FEATURE ID: 5] ( PK B ) of the second party B using the second proxy re-encryption key ( RK C2 ) , wherein the proxy re-encryption is one - way ; and the second party B receiving the data and decrypting the data with the key k , decrypted from a secret key SK B [FEATURE ID: 5] , 2 . The method of claim [FEATURE ID: 10] 1 , wherein the proxy re-encryption being one - way comprises : the one or more curators generating the proxy re-encryption key [FEATURE ID: 5] utilizing a cryptographic [FEATURE ID: 5] one - way function. , wherein the cryptographic one - way function comprises a cryptographic pairing , and wherein the proxy re-encryption is restricted to be one - way . 3 . The method of claim 1 , wherein the one or more curators generate the second proxy re-encryption key ( RK C2 - B ) without knowledge [FEATURE ID: 8] of the secret key SK B comprising : obtaining a public key of the second party B ; generating the second proxy re-encryption key ( RK C2 - B ) by applying a cryptographic function [FEATURE ID: 6] to the public key of the second party B. 4 . The method of claim 1 , further comprising preventing collusion between the one or more custodians [FEATURE ID: 9] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US20130211990A1 Filed: 2012-02-09 Issued: 2013-08-15 Patent Holder: (Original Assignee) Cinnober Financial Technology AB (Current Assignee) Cinnober Financial Technology AB Inventor(s): Jicun ZHONG Title: Risk Assessment |
[FEATURE ID: 1] computing device, transfer mechanism, decentralized digital currency, memory, network interface, second data source, computer processor, commit, digital currency, ledger, central authority, computer network | network, server, database, device, mechanism, platform, system | [FEATURE ID: 1] risk assessment system, memory device, portfolio, control device, risk calculator |
[FEATURE ID: 2] transaction | trading, price, transfer, contract, purchase, payment, request | [FEATURE ID: 2] new order |
[FEATURE ID: 3] second client device | transaction, client, user | [FEATURE ID: 3] financial entity |
[TRANSITIVE ID: 4] comprising, storing | providing, including, having, involving, managing, incorporating, containing | [TRANSITIVE ID: 4] comprising |
[FEATURE ID: 5] terms, output data, network participants | values, transactions, data, parameters, options, items, metrics | [FEATURE ID: 5] information, positions, financial instruments, orders, been, collateral, SPAN risk arrays, criteria |
[FEATURE ID: 6] expiration timestamp, inchoate data record, external state | index, algorithm, event, order, attribute, output, object | [FEATURE ID: 6] risk assessment, estimate |
[TRANSITIVE ID: 7] coupled, configured | adapted, assigned, operable, connected, associated, linked, structured | [TRANSITIVE ID: 7] configured, belonging, matched |
[TRANSITIVE ID: 8] read, compute, create, data | determine, provide, retrieve, acquire, request, generate, access | [TRANSITIVE ID: 8] store, receive |
[FEATURE ID: 9] first cryptographic signature, value data, copy | value, result, portion, key, signature, certificate, digest | [FEATURE ID: 9] combination |
[FEATURE ID: 10] input | value, time, transaction, region, point | [FEATURE ID: 10] Standard Portfolio Analysis, lead time |
[FEATURE ID: 11] complete data record | value, process, rule, trade, term | [FEATURE ID: 11] assessment, SPAN price |
[FEATURE ID: 12] claim | any, figure, claims claim, the claim, preceding claim, item, paragraph | [FEATURE ID: 12] claim |
[FEATURE ID: 13] further | particularly, farther, preferably further, at least, also, additionally, specifically | [FEATURE ID: 13] further |
1 . A computing device [FEATURE ID: 1] for processing a transaction [FEATURE ID: 2] between a first client device , and a second client device [FEATURE ID: 3] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 4] a decentralized digital currency [FEATURE ID: 1] , the computing device comprising : a memory [FEATURE ID: 1] for storing [TRANSITIVE ID: 4] a first asymmetric key pair , the first asymmetric key pair comprising a first private key and a first public key ; a network interface [FEATURE ID: 1] for receiving terms [FEATURE ID: 5] , the terms comprising : at least one of a first principal data or a second principal data ; a reference to at least one of a first data source or a second data source [FEATURE ID: 1] ; and an expiration timestamp [FEATURE ID: 6] ; a computer processor [FEATURE ID: 1] coupled [TRANSITIVE ID: 7] to the memory and the network interface , the computer processor configured [TRANSITIVE ID: 7] to : read [TRANSITIVE ID: 8] the first private key from the memory ; compute [TRANSITIVE ID: 8] a first cryptographic signature [FEATURE ID: 9] from the first private key ; create [TRANSITIVE ID: 8] an inchoate data record [FEATURE ID: 6] comprising : a commit [TRANSITIVE ID: 1] input [FEATURE ID: 10] for receiving a commit data [FEATURE ID: 8] from a commit transaction ; one or more output data [FEATURE ID: 5] obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 9] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger [FEATURE ID: 1] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 1] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 11] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants [FEATURE ID: 5] in the computer network [FEATURE ID: 1] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy [FEATURE ID: 9] of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 6] . 2 . The device of claim [FEATURE ID: 12] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further [FEATURE ID: 13] |
1 . A risk assessment system [FEATURE ID: 1] comprising [TRANSITIVE ID: 4] : a memory device [FEATURE ID: 1] configured [TRANSITIVE ID: 7] to store [TRANSITIVE ID: 8] information [FEATURE ID: 5] about positions [FEATURE ID: 5] belonging [TRANSITIVE ID: 7] to a portfolio [FEATURE ID: 1] of financial instruments [FEATURE ID: 5] , the portfolio comprising at least one or more orders [FEATURE ID: 5] that have been [TRANSITIVE ID: 5] accepted but not matched [TRANSITIVE ID: 7] with other orders ; and a control device [FEATURE ID: 1] configured to receive [TRANSITIVE ID: 8] information about a new order [FEATURE ID: 2] associated with the portfolio , calculate a risk assessment order based on a combination [FEATURE ID: 9] of a risk associated the new order and a risk associated with the one or more accepted orders , and determine whether to accept the new order based on the risk assessment [FEATURE ID: 6] . 2 . A risk assessment system according to claim [FEATURE ID: 12] 1 , wherein the portfolio further comprises one or more trades and the control device is configured to carry out said risk assessment based on a combination of the risk associated with the new order , the risk associated with the one or more accepted orders , and a risk associated with the one or more trades . 3 . A risk assessment system according to claim 1 , wherein the control device is configured to calculate a margin requirement for the portfolio ; and the control device is further [FEATURE ID: 13] configured to compare the margin requirement with collateral [FEATURE ID: 5] provided by a financial entity [FEATURE ID: 3] associated with the portfolio to determine whether to accept the new order . 4 . A risk assessment system according to claim 1 , wherein the control device is configured to calculate a margin requirement for the portfolio based on a Standard Portfolio Analysis [FEATURE ID: 10] of Risk ( SPAN ) assessment [FEATURE ID: 11] . 5 . A risk assessment system according to claim 4 , wherein the portfolio comprises a plurality of combined commodity portfolios , each combined commodity portfolio comprising a subset of the positions of said portfolio , and wherein the control device comprises a risk calculator [FEATURE ID: 1] configured to calculate the risk assessment by considering a plurality of SPAN price [FEATURE ID: 11] and volatility scenarios for each combined commodity portfolio and calculating a scan risk for each scenario for each combined commodity portfolio using a plurality of SPAN risk arrays [FEATURE ID: 5] , wherein the scan risk for a combined commodity portfolio is an estimate [FEATURE ID: 6] of a profit or loss the positions of the combined commodity portfolio can make in lead time [FEATURE ID: 10] . 6 . A risk assessment system according to claim 5 , wherein the risk calculator is configured to calculate the scan risk for a combined commodity portfolio and a scenario of said plurality of SPAN price and volatility scenarios by determining , according to predetermined criteria [FEATURE ID: 5] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US20130179337A1 Filed: 2012-01-09 Issued: 2013-07-11 Patent Holder: (Original Assignee) Walter Ochynski Inventor(s): Walter Ochynski Title: Account free possession and transfer of electronic money |
[FEATURE ID: 1] computing device, transfer mechanism, memory, first asymmetric key pair, network interface, second data source, computer processor, ledger | network, database, mechanism, device, client, computer, means | [FEATURE ID: 1] system capable, system, secure server, secure internet connection, trustworthy issuer, Wallet, several mediums, server, internet |
[TRANSITIVE ID: 2] processing, storing, receiving | managing, recording, transmitting, generating, securing, exchanging, creating | [TRANSITIVE ID: 2] representing |
[FEATURE ID: 3] transaction | purchase, payment, transfer, transactions, redemption, data | [FEATURE ID: 3] electronic bills, receipt |
[FEATURE ID: 4] second client device | computer, terminal, server, device, ipad, pc, pd | [FEATURE ID: 4] user ', tablet, smart phone |
[TRANSITIVE ID: 5] comprising | via, having, and, containing, including, utilizing, employing | [TRANSITIVE ID: 5] using |
[FEATURE ID: 6] decentralized digital currency | connection, contract, communication, gateway, firewall, transfer, trust | [FEATURE ID: 6] https protocol, accordance, stock |
[FEATURE ID: 7] first private key, second principal data, first cryptographic signature, input, data, value data, complete data record, copy, second cryptographic signature | value, key, signature, token, secret, date, message | [FEATURE ID: 7] name, password |
[FEATURE ID: 8] first public key | value, key, signature, password, hash | [FEATURE ID: 8] URL |
[FEATURE ID: 9] terms, network participants | information, values, transactions, systems, metadata, elements, entities | [FEATURE ID: 9] electronic money, parameters |
[FEATURE ID: 10] reference, coupled, read | connection, call, download, couple, request, link, access | [FEATURE ID: 10] connect |
[FEATURE ID: 11] expiration timestamp | exchange, authentication, identity | [FEATURE ID: 11] ownership |
[FEATURE ID: 12] inchoate data record, external state | electronic, object, account, index, event, algorithm, artifact | [FEATURE ID: 12] application |
[FEATURE ID: 13] digital currency | wallet, virtual currency, currency | [FEATURE ID: 13] E-Bills |
[FEATURE ID: 14] central authority | principal, party, person, participant, entity | [FEATURE ID: 14] E-Bill ' |
[FEATURE ID: 15] computer network | order, sequence, future, exchange | [FEATURE ID: 15] various denominations |
[FEATURE ID: 16] recording | presence, uniqueness, ownership, value, validity, existence, inclusion | [FEATURE ID: 16] knowledge, redemption |
[FEATURE ID: 17] claim | paragraph, patent, claims, figure, clause, of claim, item | [FEATURE ID: 17] claim |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction [FEATURE ID: 3] between a first client device , and a second client device [FEATURE ID: 4] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 5] a decentralized digital currency [FEATURE ID: 6] , the computing device comprising : a memory [FEATURE ID: 1] for storing [TRANSITIVE ID: 2] a first asymmetric key pair [FEATURE ID: 1] , the first asymmetric key pair comprising a first private key [FEATURE ID: 7] and a first public key [FEATURE ID: 8] ; a network interface [FEATURE ID: 1] for receiving [TRANSITIVE ID: 2] terms [FEATURE ID: 9] , the terms comprising : at least one of a first principal data or a second principal data [FEATURE ID: 7] ; a reference [FEATURE ID: 10] to at least one of a first data source or a second data source [FEATURE ID: 1] ; and an expiration timestamp [FEATURE ID: 11] ; a computer processor [FEATURE ID: 1] coupled [TRANSITIVE ID: 10] to the memory and the network interface , the computer processor configured to : read [TRANSITIVE ID: 10] the first private key from the memory ; compute a first cryptographic signature [FEATURE ID: 7] from the first private key ; create an inchoate data record [FEATURE ID: 12] comprising : a commit input [FEATURE ID: 7] for receiving a commit data [FEATURE ID: 7] from a commit transaction ; one or more output data obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 7] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 13] comprises a distributed ledger [FEATURE ID: 1] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 14] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 7] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants [FEATURE ID: 9] in the computer network [FEATURE ID: 15] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy [FEATURE ID: 7] of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording [FEATURE ID: 16] of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 12] . 2 . The device of claim [FEATURE ID: 17] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further configured to : compute a second cryptographic signature [FEATURE ID: 7] |
1 . A system capable [FEATURE ID: 1] of representing [TRANSITIVE ID: 2] electronic money [FEATURE ID: 9] using [TRANSITIVE ID: 5] unique , identifiable , and potentially variable parameters , where knowledge [FEATURE ID: 16] of said parameters [FEATURE ID: 9] indicates ownership [FEATURE ID: 11] of the electronic money . 2 . The system [FEATURE ID: 1] described in claim [FEATURE ID: 17] 1 wherein said parameters are comprised of a name [FEATURE ID: 7] , which can also be expressed as a URL [FEATURE ID: 8] , and a password [FEATURE ID: 7] . 3 . The system described in claim 1 wherein said electronic money is stored on a secure server [FEATURE ID: 1] that the owner of said electronic money can connect [TRANSITIVE ID: 10] to through a secure internet connection [FEATURE ID: 1] . 4 . The system described in claim 1 and claim 2 wherein a means for changing said password enables the ownership of the electronic money to change . 5 . The system described in claim 1 wherein a trustworthy issuer [FEATURE ID: 1] guarantees the redemption [FEATURE ID: 16] of said electronic money . 6 . An application [FEATURE ID: 12] ( Wallet [FEATURE ID: 1] ) which provides means for keeping records of electronic bills [FEATURE ID: 3] and means for facilitating receipt [FEATURE ID: 3] and transfer of said electronic bills . 7 . The application described in claim 6 , whereby said application may be located on several mediums [FEATURE ID: 1] including but not limited to said server [FEATURE ID: 1] or decentrally on a user ' [FEATURE ID: 4] s PC , tablet [FEATURE ID: 4] or smart phone [FEATURE ID: 4] . 8 . The system described in claim 1 and claim 6 where said electronic money is made up of said electronic bills ( E-Bills [FEATURE ID: 13] ) which will be issued in various denominations [FEATURE ID: 15] and will be stored on said secure server connected to the internet [FEATURE ID: 1] through https protocol [FEATURE ID: 6] . 9 . The system described in claim 1 and claim 6 where ownership of said E-Bills is determined by knowledge of the E-Bill ' [FEATURE ID: 14] s name and password . 10 . A system in accordance [FEATURE ID: 6] with claim 1 and claim 6 where said electronic money is substituted by other financial asset , for example , stock [FEATURE ID: 6] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US20130166455A1 Filed: 2011-12-23 Issued: 2013-06-27 Patent Holder: (Original Assignee) BITBILLS Inc (Current Assignee) BITBILLS Inc Inventor(s): Douglas Feigelson Title: Creating and using digital currency |
[FEATURE ID: 1] computing device, transaction, transfer mechanism, network interface, expiration timestamp, inchoate data record, input, digital currency, ledger, central authority, external state | system, device, network, mechanism, platform, entity, identifier | [FEATURE ID: 1] apparatus, physical device, transaction, manner, party, digital currency network, key pair |
[TRANSITIVE ID: 2] processing, comprising, storing | providing, managing, defining, including, implementing, having, generating | [TRANSITIVE ID: 2] comprising |
[FEATURE ID: 3] second client device, memory, second principal data, second data source, commit, computer network | second, transaction, first, network, database, user, value | [FEATURE ID: 3] digital domain |
[FEATURE ID: 4] decentralized digital currency, computer processor | currency, token, key, certificate, card, memory, banknote | [FEATURE ID: 4] portable device, machine readable form, secret, Bitcoin |
[FEATURE ID: 5] first asymmetric key pair | certificate, secret, public key, public, signature, data, value | [FEATURE ID: 5] private key, private key pair |
[FEATURE ID: 6] first private key | public, key, secret, user, pair, signature, private | [FEATURE ID: 6] public key, private key part |
[FEATURE ID: 7] first public key, second cryptographic signature | value, hash, signature, key, password, secret, cryptogram | [FEATURE ID: 7] security feature, QR code, basis |
[FEATURE ID: 8] terms, output data | values, documents, information, data, messages, transactions, the | [FEATURE ID: 8] characters, units |
[TRANSITIVE ID: 9] coupled, configured | operable, adapted, arranged, operative, effective | [TRANSITIVE ID: 9] usable |
[TRANSITIVE ID: 10] read, compute | retrieve, provide, extract, get, derive, determine, acquire | [TRANSITIVE ID: 10] transfer |
[FEATURE ID: 11] first cryptographic signature, data, copy, recording | value, signature, status, version, code, key, result | [FEATURE ID: 11] representation |
[FEATURE ID: 12] value data | content, data, material | [FEATURE ID: 12] value |
[FEATURE ID: 13] complete data record | value, message, condition, document, form, database | [FEATURE ID: 13] state, human readable form |
[FEATURE ID: 14] claim | any, figure, of claim, the claim, preceding claim, item, paragraph | [FEATURE ID: 14] claim |
[FEATURE ID: 15] further | also, optionally, is | [FEATURE ID: 15] being |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction [FEATURE ID: 1] between a first client device , and a second client device [FEATURE ID: 3] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 2] a decentralized digital currency [FEATURE ID: 4] , the computing device comprising : a memory [FEATURE ID: 3] for storing [TRANSITIVE ID: 2] a first asymmetric key pair [FEATURE ID: 5] , the first asymmetric key pair comprising a first private key [FEATURE ID: 6] and a first public key [FEATURE ID: 7] ; a network interface [FEATURE ID: 1] for receiving terms [FEATURE ID: 8] , the terms comprising : at least one of a first principal data or a second principal data [FEATURE ID: 3] ; a reference to at least one of a first data source or a second data source [FEATURE ID: 3] ; and an expiration timestamp [FEATURE ID: 1] ; a computer processor [FEATURE ID: 4] coupled [TRANSITIVE ID: 9] to the memory and the network interface , the computer processor configured [TRANSITIVE ID: 9] to : read [TRANSITIVE ID: 10] the first private key from the memory ; compute [TRANSITIVE ID: 10] a first cryptographic signature [FEATURE ID: 11] from the first private key ; create an inchoate data record [FEATURE ID: 1] comprising : a commit [TRANSITIVE ID: 3] input [FEATURE ID: 1] for receiving a commit data [FEATURE ID: 11] from a commit transaction ; one or more output data [FEATURE ID: 8] obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 12] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger [FEATURE ID: 1] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 1] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 13] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants in the computer network [FEATURE ID: 3] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy [FEATURE ID: 11] of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording [FEATURE ID: 11] of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 1] . 2 . The device of claim [FEATURE ID: 14] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further [FEATURE ID: 15] configured to : compute a second cryptographic signature [FEATURE ID: 7] |
1 . An apparatus [FEATURE ID: 1] comprising [TRANSITIVE ID: 2] a physical device [FEATURE ID: 1] that carries value [FEATURE ID: 12] and can be physically delivered in a transaction [FEATURE ID: 1] , the physical device comprising a representation [FEATURE ID: 11] of the value carried by the physical device , the representation being [TRANSITIVE ID: 15] usable [FEATURE ID: 9] to transfer [TRANSITIVE ID: 10] the value from the physical device to a digital domain [FEATURE ID: 3] , and a security feature [FEATURE ID: 7] that can change from a state [FEATURE ID: 13] indicating that the value carried by the physical device has not been compromised to a state indicating that the value carried by the physical device may have been compromised , the change in state being detectable , the representation of the value carried by the physical device being inaccessible except in a manner [FEATURE ID: 1] that causes the security feature to change state . 2 . The apparatus of claim [FEATURE ID: 14] 1 in which the physical device comprises a portable device [FEATURE ID: 4] . 3 . The apparatus of claim 1 in which the representation of the value is expressed in a human readable form [FEATURE ID: 13] . 4 . The apparatus of claim 3 in which the human readable form comprises printed characters [FEATURE ID: 8] . 5 . The apparatus of claim 1 in which the representation of value is expressed in a machine readable form [FEATURE ID: 4] . 6 . The apparatus of claim 4 in which the machine readable form comprises a one - dimensional or two - dimensional bar or mark code . 7 . The apparatus of claim 6 in which the code comprises a QR code [FEATURE ID: 7] . 8 . The apparatus of claim 1 in which the representation of value comprises a secret [FEATURE ID: 4] . 9 . The apparatus of claim 1 in which the representation of value comprises a private key [FEATURE ID: 5] of a public key [FEATURE ID: 6] and private key pair [FEATURE ID: 5] . 10 . The apparatus of claim 9 in which the public key ( a ) can be provided by a paid party [FEATURE ID: 1] to a paying party in connection with a transaction and ( b ) can form the basis [FEATURE ID: 7] of an address a digital currency network [FEATURE ID: 1] to which the paying party can assign units [FEATURE ID: 8] of value for use by the paid party . 11 . The apparatus of claim 1 in which the representation of value comprises fifty - one ASCII encoded characters representing a base 58 encoding of a private key part [FEATURE ID: 6] of a key pair [FEATURE ID: 1] associated with a Bitcoin [FEATURE ID: 4] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US8473401B2 Filed: 2006-12-20 Issued: 2013-06-25 Patent Holder: (Original Assignee) CLS Services Ltd (Current Assignee) CLS Services Ltd Inventor(s): Philip Paul Trickey, Joseph Halberstadt, Sean Christopher Daly, Dirk Cavens, Naeem Ahmad, William Patrick Fraser-Campbell Title: System and method for processing and settling payment instructions relating to various financial instruments |
[FEATURE ID: 1] computing device, transfer mechanism, memory, computer processor, digital currency, ledger, central authority | network, mechanism, platform, device, transaction, controller, processor | [FEATURE ID: 1] system, first processor |
[FEATURE ID: 2] transaction, decentralized digital currency, first asymmetric key pair, first private key, first public key, reference, second data source, first cryptographic signature, commit, input, data, value data, complete data record, copy, second cryptographic signature | value, message, key, payment, request, token, certificate | [FEATURE ID: 2] financial instruments, derivative instruction, derivative transaction, first instruction, financial instrument, second instruction, non-derivative instrument, specified currency, transaction, non-deliverable forward transaction, foreign exchange option transaction |
[FEATURE ID: 3] second client device | second, first, third, instruction, computer, database, transaction | [FEATURE ID: 3] first form, second instructions, second processor, first additional instruction, second additional instruction, second additional instructions, third processor |
[TRANSITIVE ID: 4] comprising, storing | including, having, containing, using, representing, by, with | [TRANSITIVE ID: 4] involving, comprising |
[FEATURE ID: 5] network interface, configured | designed, operable, storage, capable, effective, disposed, configuration | [FEATURE ID: 5] configured, participants |
[FEATURE ID: 6] terms | values, conditions, claims, instructions, parameters, contracts, rights | [FEATURE ID: 6] payments, pre-settlement rules |
[FEATURE ID: 7] second principal data | value, token, principal | [FEATURE ID: 7] fictitious currency |
[FEATURE ID: 8] expiration timestamp, inchoate data record, external state | identifier, indicator, index, entity, exchange, instrument, output | [FEATURE ID: 8] interface, association, amount |
[TRANSITIVE ID: 9] coupled | corresponding, related, linked, responsive | [TRANSITIVE ID: 9] relating, associated |
[TRANSITIVE ID: 10] read, compute, create | determine, provide, obtain, generate, derive, retrieve, identify | [TRANSITIVE ID: 10] receive, establish |
[FEATURE ID: 11] network participants | members, exchanges, components, elements, options, points, participants | [FEATURE ID: 11] multiple participants, units, group |
[FEATURE ID: 12] computer network | sequence, hierarchy, system, chain | [FEATURE ID: 12] set |
[FEATURE ID: 13] claim | item, paragraph, preceding claim, patent, aspect, clair, requirement | [FEATURE ID: 13] claim |
[FEATURE ID: 14] further | particularly, farther, at least, optionally further, yet further, also, additionally | [FEATURE ID: 14] further |
1 . A computing device [FEATURE ID: 1] for processing a transaction [FEATURE ID: 2] between a first client device , and a second client device [FEATURE ID: 3] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 4] a decentralized digital currency [FEATURE ID: 2] , the computing device comprising : a memory [FEATURE ID: 1] for storing [TRANSITIVE ID: 4] a first asymmetric key pair [FEATURE ID: 2] , the first asymmetric key pair comprising a first private key [FEATURE ID: 2] and a first public key [FEATURE ID: 2] ; a network interface [FEATURE ID: 5] for receiving terms [FEATURE ID: 6] , the terms comprising : at least one of a first principal data or a second principal data [FEATURE ID: 7] ; a reference [FEATURE ID: 2] to at least one of a first data source or a second data source [FEATURE ID: 2] ; and an expiration timestamp [FEATURE ID: 8] ; a computer processor [FEATURE ID: 1] coupled [TRANSITIVE ID: 9] to the memory and the network interface , the computer processor configured [TRANSITIVE ID: 5] to : read [TRANSITIVE ID: 10] the first private key from the memory ; compute [TRANSITIVE ID: 10] a first cryptographic signature [FEATURE ID: 2] from the first private key ; create [TRANSITIVE ID: 10] an inchoate data record [FEATURE ID: 8] comprising : a commit [TRANSITIVE ID: 2] input [FEATURE ID: 2] for receiving a commit data [FEATURE ID: 2] from a commit transaction ; one or more output data obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 2] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger [FEATURE ID: 1] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 1] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 2] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants [FEATURE ID: 11] in the computer network [FEATURE ID: 12] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy [FEATURE ID: 2] of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 8] . 2 . The device of claim [FEATURE ID: 13] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further [FEATURE ID: 14] configured to : compute a second cryptographic signature [FEATURE ID: 2] |
1 . A system [FEATURE ID: 1] to facilitate settlement of payments [FEATURE ID: 6] relating [TRANSITIVE ID: 9] to transactions involving [TRANSITIVE ID: 4] financial instruments [FEATURE ID: 2] among multiple participants [FEATURE ID: 11] , comprising [TRANSITIVE ID: 4] : an interface [FEATURE ID: 8] configured [TRANSITIVE ID: 5] to : receive [TRANSITIVE ID: 10] at least one derivative instruction [FEATURE ID: 2] associated [TRANSITIVE ID: 9] with a derivative transaction [FEATURE ID: 2] ; and receive from participants [FEATURE ID: 5] a first instruction [FEATURE ID: 2] associated with a financial instrument [FEATURE ID: 2] of a first form [FEATURE ID: 3] and a second instruction [FEATURE ID: 2] associated with the financial instrument of the first form , the financial instrument of the first form comprising a non-derivative instrument [FEATURE ID: 2] ; a first processor [FEATURE ID: 1] configured to : establish [TRANSITIVE ID: 10] an association [FEATURE ID: 8] between the first and second instructions [FEATURE ID: 3] associated with the financial instrument of the first form ; and apply a set [FEATURE ID: 12] of pre-settlement rules [FEATURE ID: 6] to the first and second instructions associated with the financial instrument of the first form ; and a second processor [FEATURE ID: 3] , different from the first processor , the second processor configured to : receive the at least one derivative instruction associated with a derivative transaction from the interface ; accept the at least one derivative instruction ; and submit the at least one accepted derivative instruction to the first processor ; wherein the first processor is further [FEATURE ID: 14] configured to : validate the at least one derivative instruction received from the second processor ; for each validated derivative instruction : generate a first additional instruction [FEATURE ID: 3] based on the validated derivative instruction , the first additional instruction specifying ( i ) an amount [FEATURE ID: 8] of a specified currency [FEATURE ID: 2] to be settled , and ( ii ) zero units [FEATURE ID: 11] of a fictitious currency [FEATURE ID: 7] to be settled ; generate a second additional instruction [FEATURE ID: 3] based on the validated derivative instruction , the second additional instruction specifying ( i ) an amount of a specified currency to be settled , and ( ii ) zero units of a fictitious currency to be settled ; establish an association between the first and second additional instructions [FEATURE ID: 3] ; designate the associated first and second additional instructions as settlement eligible ; and submit the associated first and second additional instructions for settlement . 2 . The system of claim [FEATURE ID: 13] 1 , further comprising : a third processor [FEATURE ID: 3] , different from the first processor and the second processor , the third processor configured to : direct the first and second instructions associated with the financial instrument of the first form to the first processor ; and direct the at least one derivative instruction to the second processor . 3 . The system of claim 1 , wherein the financial instrument of the first form relates to at least one transaction [FEATURE ID: 2] chosen from among the group [FEATURE ID: 11] consisting of : a foreign exchange transaction , a non-deliverable forward transaction [FEATURE ID: 2] , and a foreign exchange option transaction [FEATURE ID: 2] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US20130054471A1 Filed: 2007-04-19 Issued: 2013-02-28 Patent Holder: (Original Assignee) Gideon Samid Inventor(s): Gideon Samid Title: Bit Currency: Transactional Trust Tools |
[FEATURE ID: 1] computing device, transfer mechanism, decentralized digital currency, memory, network interface, second principal data, second data source, computer processor, data, digital currency, central authority, complete data record, device, second cryptographic signature | network, server, database, processor, mechanism, transaction, token | [FEATURE ID: 1] digital coin, method |
[TRANSITIVE ID: 2] processing, storing, receiving | providing, generating, transmitting, issuing, managing, handling, using | [TRANSITIVE ID: 2] transacting, receiving, splitting |
[FEATURE ID: 3] transaction | data, price, balance | [FEATURE ID: 3] coin value |
[FEATURE ID: 4] second client device | second, first, third, first second, binary, two, corresponding second | [FEATURE ID: 4] second digital coin, second bit string |
[TRANSITIVE ID: 5] comprising, second client device signs | having, including, stores, uses, involving, occupies, involves | [TRANSITIVE ID: 5] comprising, comprises, includes |
[FEATURE ID: 6] first public key | payload, message, header, value, number, portion, token | [FEATURE ID: 6] first bit string, third digital coin |
[FEATURE ID: 7] terms, output data | values, results, signals, parameters, keys, data, inputs | [FEATURE ID: 7] bits |
[FEATURE ID: 8] expiration timestamp, external state | attribute, action, identifier, amount, integrity, outcome, order | [FEATURE ID: 8] identity |
[TRANSITIVE ID: 9] configured | arranged, set, designed | [TRANSITIVE ID: 9] used |
[TRANSITIVE ID: 10] read, compute, create | provide, form, identify, derive, define, receive, produce | [TRANSITIVE ID: 10] represent, determine |
[FEATURE ID: 11] first cryptographic signature, commit | second, message, digital, token, commitment, first | [FEATURE ID: 11] first digital coin |
[FEATURE ID: 12] input, recording | state, value, bit, remainder, correctness, integrity, accuracy | [FEATURE ID: 12] third bit string, bit order |
[FEATURE ID: 13] value data, copy | content, value, portion, numbers, result, key, plurality | [FEATURE ID: 13] number, bit values |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction [FEATURE ID: 3] between a first client device , and a second client device [FEATURE ID: 4] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 5] a decentralized digital currency [FEATURE ID: 1] , the computing device comprising : a memory [FEATURE ID: 1] for storing [TRANSITIVE ID: 2] a first asymmetric key pair , the first asymmetric key pair comprising a first private key and a first public key [FEATURE ID: 6] ; a network interface [FEATURE ID: 1] for receiving [TRANSITIVE ID: 2] terms [FEATURE ID: 7] , the terms comprising : at least one of a first principal data or a second principal data [FEATURE ID: 1] ; a reference to at least one of a first data source or a second data source [FEATURE ID: 1] ; and an expiration timestamp [FEATURE ID: 8] ; a computer processor [FEATURE ID: 1] coupled to the memory and the network interface , the computer processor configured [TRANSITIVE ID: 9] to : read [TRANSITIVE ID: 10] the first private key from the memory ; compute [TRANSITIVE ID: 10] a first cryptographic signature [FEATURE ID: 11] from the first private key ; create [TRANSITIVE ID: 10] an inchoate data record comprising : a commit [TRANSITIVE ID: 11] input [FEATURE ID: 12] for receiving a commit data [FEATURE ID: 1] from a commit transaction ; one or more output data [FEATURE ID: 7] obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 13] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 1] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 1] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants in the computer network for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs [FEATURE ID: 5] the inchoate data record and saves a copy [FEATURE ID: 13] of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording [FEATURE ID: 12] of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 8] . 2 . The device [FEATURE ID: 1] of claim 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further configured to : compute a second cryptographic signature [FEATURE ID: 1] |
1 . A digital coin [FEATURE ID: 1] , comprising [TRANSITIVE ID: 5] : a bit string , wherein a number [FEATURE ID: 13] of bits [FEATURE ID: 7] in the bit string is used [TRANSITIVE ID: 9] to represent [TRANSITIVE ID: 10] coin value [FEATURE ID: 3] of the digital coin and bit values [FEATURE ID: 13] of bits of the bit string are used to determine [TRANSITIVE ID: 10] an identity [FEATURE ID: 8] of the digital coin . 2 . A method [FEATURE ID: 1] for transacting [TRANSITIVE ID: 2] a digital coin , comprising : receiving [TRANSITIVE ID: 2] a bit string , wherein a number of bits in the bit string is used to represent coin value of the digital coin and bit values of bits of the bit string are used to determine an identity of the digital coin . 3 . A method for splitting [TRANSITIVE ID: 2] a digital coin , comprising : receiving a first digital coin [FEATURE ID: 11] , wherein the first digital coin comprises [TRANSITIVE ID: 5] a first bit string [FEATURE ID: 6] that includes [TRANSITIVE ID: 5] two or more bits , wherein a number of bits in the first bit string is used to represent a coin value of the first digital coin , and wherein bit values of bits of the first bit string are used to determine an identity of the first digital coin ; and splitting the first digital coin into at least a second digital coin [FEATURE ID: 4] and a third digital coin [FEATURE ID: 6] , wherein the first digital coin is split by dividing the first bit string into a second bit string [FEATURE ID: 4] and a third bit string [FEATURE ID: 12] without disturbing the bit order [FEATURE ID: 12] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US8341067B2 Filed: 2008-06-30 Issued: 2012-12-25 Patent Holder: (Original Assignee) ITG Software Solutions Inc (Current Assignee) Virtu Itg Software Solutions LLC Inventor(s): Ronald D. Lee, Mervin C. Newell, Scott H. Kurland, Ian P. L. Hoenisch, James B. Weiner, Gerald B. Drayer, Robert L. Sher Title: Apparatus and method for trade aggregation of trade allocations and settlements |
[FEATURE ID: 1] computing device, transfer mechanism, memory, network interface, second data source, computer processor, input, digital currency, ledger, central authority, computer network | network, database, platform, system, mechanism, transaction, client | [FEATURE ID: 1] financial trading system, data interface system, broker, post-trade aggregation system, settlement system, module, research module |
[TRANSITIVE ID: 2] processing, comprising, storing, receiving | providing, establishing, defining, transmitting, enabling, generating, supporting | [TRANSITIVE ID: 2] including, managing, communicating |
[FEATURE ID: 3] transaction, data | request, price, message, payment, transfer, communication, process | [FEATURE ID: 3] trade order, allocation information |
[FEATURE ID: 4] second client device | recipient, client, user | [FEATURE ID: 4] customer |
[FEATURE ID: 5] decentralized digital currency, second principal data, second cryptographic signature | key, currency, date, token, value, protocol, counter | [FEATURE ID: 5] clearing agent |
[FEATURE ID: 6] terms, output data | parameters, transactions, orders, contracts, inputs, securities, categories | [FEATURE ID: 6] behalf, trade orders, individual trade order executions, programmable settings, compression interval, execution services, firms, class configuration |
[FEATURE ID: 7] expiration timestamp, inchoate data record, external state | exchange, application, order, index, event, algorithm, entity | [FEATURE ID: 7] executing, order staging system, aggregated basis, execution management system |
[TRANSITIVE ID: 8] coupled, configured | adapted, operable, operative, arranged, configure, structured, enabled | [TRANSITIVE ID: 8] configured |
[TRANSITIVE ID: 9] read, compute, create | determine, retrieve, obtain, acquire, extract, provide, derive | [TRANSITIVE ID: 9] receive |
[FEATURE ID: 10] complete data record | process, record, trade | [FEATURE ID: 10] clear |
[FEATURE ID: 11] network participants | clients, participants, agents, investors, processors, subscribers, packers | [FEATURE ID: 11] order destinations, custodial accounts |
[FEATURE ID: 12] claim | any, figure, any claim, preceding claim, paragraph, clause, embodiment | [FEATURE ID: 12] claim |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction [FEATURE ID: 3] between a first client device , and a second client device [FEATURE ID: 4] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 2] a decentralized digital currency [FEATURE ID: 5] , the computing device comprising : a memory [FEATURE ID: 1] for storing [TRANSITIVE ID: 2] a first asymmetric key pair , the first asymmetric key pair comprising a first private key and a first public key ; a network interface [FEATURE ID: 1] for receiving [TRANSITIVE ID: 2] terms [FEATURE ID: 6] , the terms comprising : at least one of a first principal data or a second principal data [FEATURE ID: 5] ; a reference to at least one of a first data source or a second data source [FEATURE ID: 1] ; and an expiration timestamp [FEATURE ID: 7] ; a computer processor [FEATURE ID: 1] coupled [TRANSITIVE ID: 8] to the memory and the network interface , the computer processor configured [TRANSITIVE ID: 8] to : read [TRANSITIVE ID: 9] the first private key from the memory ; compute [TRANSITIVE ID: 9] a first cryptographic signature from the first private key ; create [TRANSITIVE ID: 9] an inchoate data record [FEATURE ID: 7] comprising : a commit input [FEATURE ID: 1] for receiving a commit data [FEATURE ID: 3] from a commit transaction ; one or more output data [FEATURE ID: 6] obtained from at least one of the first principal data or the second principal data , and a value data from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger [FEATURE ID: 1] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 1] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 10] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants [FEATURE ID: 11] in the computer network [FEATURE ID: 1] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 7] . 2 . The device of claim [FEATURE ID: 12] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further configured to : compute a second cryptographic signature [FEATURE ID: 5] |
1 . A post-trade aggregation and clearing system for a financial trading system [FEATURE ID: 1] , said financial trading system including [TRANSITIVE ID: 2] a data interface system [FEATURE ID: 1] for managing [TRANSITIVE ID: 2] a trade order [FEATURE ID: 3] to be executed by an executing [TRANSITIVE ID: 7] broker [FEATURE ID: 1] on behalf [FEATURE ID: 6] of a customer [FEATURE ID: 4] and an order staging system [FEATURE ID: 7] for apportioning the trade order into a plurality of smaller trade orders [FEATURE ID: 6] and communicating [TRANSITIVE ID: 2] the plurality of smaller trade orders to a plurality of order destinations [FEATURE ID: 11] , said post-trade aggregation and clearing system including : a post-trade aggregation system [FEATURE ID: 1] configured [TRANSITIVE ID: 8] to receive [TRANSITIVE ID: 9] individual trade order executions [FEATURE ID: 6] for the plurality of smaller trade orders from the data interface system or from the order staging system , and to compress the individual trade order executions into a single average - priced block and clear [FEATURE ID: 10] the individual trade order executions on an aggregated basis [FEATURE ID: 7] ; wherein said post-trade aggregation system includes : allocation middleware configured to compress by computer the individual trade order executions from said plurality of order destinations into a single average - priced block ; said individual order executions clearing broker - to - broker with a designated clearing agent [FEATURE ID: 5] ; and said allocation middleware configured to allocate by computer the average - priced block among a plurality of custodial accounts [FEATURE ID: 11] based on the received allocation information [FEATURE ID: 3] . 2 . The post-trade aggregation and clearing system of claim [FEATURE ID: 12] 1 , wherein said data interface system is selected from an order management system , an execution management system [FEATURE ID: 7] , and a settlement system [FEATURE ID: 1] . 3 . The post-trade aggregation and clearing system of claim 1 , further comprising : one or more programmable settings [FEATURE ID: 6] , each setting selected from among compression interval [FEATURE ID: 6] , brokers , execution services [FEATURE ID: 6] , clearing firms [FEATURE ID: 6] , allocation rules , class configuration [FEATURE ID: 6] , and combinations thereof . 4 . The post-trade aggregation and clearing system of claim 1 , further comprising one or both of : a reporting module [FEATURE ID: 1] ; and a research module [FEATURE ID: 1] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US8321327B1 Filed: 2009-05-06 Issued: 2012-11-27 Patent Holder: (Original Assignee) ICAP North America Inc (Current Assignee) CME Group Inc Inventor(s): Jesse Robert Drennan, Jerome Bayer Title: Mapping an over the counter trade into a clearing house |
[FEATURE ID: 1] computing device, digital currency, computer network | system, process, mechanism, network, device, platform, transfer mechanism | [FEATURE ID: 1] method |
[TRANSITIVE ID: 2] processing, storing, receiving, compute | providing, creating, establishing, including, managing, obtaining, transmitting | [TRANSITIVE ID: 2] having, defining |
[FEATURE ID: 3] transaction, second cryptographic signature | date, time, price, value, maturity, market, trading | [FEATURE ID: 3] processor, calendar day, business prices, maturity date equal |
[FEATURE ID: 4] second client device, transfer mechanism | server, computer, computer network, network, processor, payee, transaction | [FEATURE ID: 4] clearing house |
[TRANSITIVE ID: 5] comprising | including, providing, comprises, containing, having, involving, includes | [TRANSITIVE ID: 5] comprising |
[FEATURE ID: 6] terms | transactions, contracts, parties, values, positions, executions, spreads | [FEATURE ID: 6] OTC positions, business days |
[FEATURE ID: 7] second principal data, reference, data | value, price, name, date, currency, key, request | [FEATURE ID: 7] maturity date, tenor |
[FEATURE ID: 8] expiration timestamp, inchoate data record, external state | index, order, event, output, input, action, instruction | [FEATURE ID: 8] opening position |
[TRANSITIVE ID: 9] coupled | assigned, relating, associated, linked, responsive | [TRANSITIVE ID: 9] corresponding |
[FEATURE ID: 10] input | value, time, state | [FEATURE ID: 10] move |
[FEATURE ID: 11] value data | value, response, reference, quote | [FEATURE ID: 11] new position equal |
[FEATURE ID: 12] ledger | account, market, transaction | [FEATURE ID: 12] contract |
[FEATURE ID: 13] central authority | transaction, system, processor | [FEATURE ID: 13] next business day |
[FEATURE ID: 14] complete data record | value, trade, transaction, contract | [FEATURE ID: 14] OTC position, margin requirement |
[FEATURE ID: 15] claim | clause, preceding claim, clair, claims, figure, embodiment, paragraph | [FEATURE ID: 15] claim |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction [FEATURE ID: 3] between a first client device , and a second client device [FEATURE ID: 4] via a transfer mechanism [FEATURE ID: 4] , the transfer mechanism comprising [TRANSITIVE ID: 5] a decentralized digital currency , the computing device comprising : a memory for storing [TRANSITIVE ID: 2] a first asymmetric key pair , the first asymmetric key pair comprising a first private key and a first public key ; a network interface for receiving [TRANSITIVE ID: 2] terms [FEATURE ID: 6] , the terms comprising : at least one of a first principal data or a second principal data [FEATURE ID: 7] ; a reference [FEATURE ID: 7] to at least one of a first data source or a second data source ; and an expiration timestamp [FEATURE ID: 8] ; a computer processor coupled [TRANSITIVE ID: 9] to the memory and the network interface , the computer processor configured to : read the first private key from the memory ; compute [TRANSITIVE ID: 2] a first cryptographic signature from the first private key ; create an inchoate data record [FEATURE ID: 8] comprising : a commit input [FEATURE ID: 10] for receiving a commit data [FEATURE ID: 7] from a commit transaction ; one or more output data obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 11] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger [FEATURE ID: 12] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 13] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 14] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants in the computer network [FEATURE ID: 1] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 8] . 2 . The device of claim [FEATURE ID: 15] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further configured to : compute a second cryptographic signature [FEATURE ID: 3] |
1 . A method [FEATURE ID: 1] for conversion of OTC positions [FEATURE ID: 6] into contracts , each OTC position [FEATURE ID: 14] having [TRANSITIVE ID: 2] a maturity date [FEATURE ID: 7] , each contract [FEATURE ID: 12] being clearable at a clearing house [FEATURE ID: 4] , the method comprising [TRANSITIVE ID: 5] : a ) defining [TRANSITIVE ID: 2] a plurality of tenors , the plurality of tenors being fewer than the OTC maturity dates of the OTC positions ; b ) defining a contract , clearable at the clearing house , corresponding [TRANSITIVE ID: 9] to each tenor [FEATURE ID: 7] defined in step a ) ; c ) mapping each OTC position with a processor [FEATURE ID: 3] , as it is executed , into one or more of the contracts , based on the maturity date of the OTC position ; and d ) between business days [FEATURE ID: 6] , re-mapping each contract mapped at step c ) to account for the move [FEATURE ID: 10] of calendar day [FEATURE ID: 3] . 2 . The method of claim [FEATURE ID: 15] 1 , wherein step d ) for each contract , comprises generating a position cancelling the contract position mapped at step c ) and generating a new position equal [FEATURE ID: 11] to the contract position mapped at step c ) but based on the maturity date of OTC position being one business day closer . 3 . The method of claim 2 , further comprising adding the contract positions mapped at step c ) to the generated contract positions to produce an opening position [FEATURE ID: 8] for the next business day [FEATURE ID: 13] . 4 . The method of claim 1 , further comprising , between business days , for each market participant , comparing the value of the contracts position mapped at step c ) with the notional value of the contracts position mapped at step c ) at close - of - business prices [FEATURE ID: 3] , and allocating the difference to the market participant as a margin requirement [FEATURE ID: 14] at the clearing house . 5 . The method of claim 1 , wherein the OTC positions comprise OTC spot positions and , for the OTC spot positions , step a ) comprises defining three tenors and step b ) comprises defining three corresponding contracts . 6 . The method of claim 5 wherein step c ) comprises : mapping OTC positions having a maturity date equal [FEATURE ID: 3] |
Targeted Patent: Patent: US11196566B2 Filed: 2014-05-09 Issued: 2021-12-07 Patent Holder: (Original Assignee) Veritaseum Inc Inventor(s): Reginald Middleton, Matthew Bogosian Title: Devices, systems, and methods for facilitating low trust and zero trust value transfers | Cross Reference / Shared Meaning between the Lines |
Charted Against: Patent: US8315940B2 Filed: 2010-04-27 Issued: 2012-11-20 Patent Holder: (Original Assignee) OMX Technology AB (Current Assignee) Nasdaq Technology AB Inventor(s): HÃ¥kan Winbom, Ulf Ahlenius Title: System and method for rapidly calculating risk in an electronic trading exchange |
[FEATURE ID: 1] computing device, transfer mechanism, decentralized digital currency, second data source, computer processor, digital currency, ledger, central authority, computer network, device | system, network, server, memory, platform, database, computer | [FEATURE ID: 1] trade order processing method, electronic trading exchange trade orders, non-transitory computer, electronic trading exchange apparatus, data processor, processor |
[TRANSITIVE ID: 2] processing, comprising, receiving, compute | providing, implementing, establishing, executing, managing, obtaining, performing | [TRANSITIVE ID: 2] reducing, comprising, receiving |
[FEATURE ID: 3] transaction, first private key, first cryptographic signature, value data | data, second, request, first, key, result, message | [FEATURE ID: 3] trade, first trade order, risk |
[FEATURE ID: 4] second client device, commit, input, complete data record | transaction, database, second, first, ledger, buffer, trader | [FEATURE ID: 4] trade order book, memory, second trade order, second trade orders, trade risk standpoint |
[FEATURE ID: 5] memory | processor, store, device, system, database, cache, medium | [FEATURE ID: 5] readable storage medium, order book |
[TRANSITIVE ID: 6] storing | store, receiving, accepting, including, keeping, preserving, maintaining | [TRANSITIVE ID: 6] storing |
[FEATURE ID: 7] first public key | value, share, message, pair | [FEATURE ID: 7] trade order |
[FEATURE ID: 8] network interface | mechanism, means, memory, controller | [FEATURE ID: 8] electronic circuitry |
[FEATURE ID: 9] terms | information, entries, instructions, conditions, messages, data, contracts | [FEATURE ID: 9] trade orders, computer readable code |
[FEATURE ID: 10] second principal data | second, first, token | [FEATURE ID: 10] first validation status marker |
[FEATURE ID: 11] expiration timestamp, inchoate data record | order, event, index, instrument, entity, object, output | [FEATURE ID: 11] electronic trading exchange, account, invalidated order |
[TRANSITIVE ID: 12] coupled | associated, bound, related | [TRANSITIVE ID: 12] valid trade orders |
[TRANSITIVE ID: 13] read, create | receive, provide, determine, obtain, derive, delete, load | [TRANSITIVE ID: 13] store |
[FEATURE ID: 14] data | operation, order, response | [FEATURE ID: 14] parallel operations |
[FEATURE ID: 15] network participants | users, processes, systems, machines, components, elements | [FEATURE ID: 15] processors |
[FEATURE ID: 16] recording | availability, consistency, correctness, validity, existence, accuracy, security | [FEATURE ID: 16] trading risk, properties |
[FEATURE ID: 17] external state | operation, action, activity | [FEATURE ID: 17] step |
[FEATURE ID: 18] claim | paragraph, embodiment, the claim, preceding claim, item, clause, figure | [FEATURE ID: 18] claim |
[FEATURE ID: 19] further | particularly, farther, the, also, additionally, specifically, furthermore | [FEATURE ID: 19] further |
1 . A computing device [FEATURE ID: 1] for processing [TRANSITIVE ID: 2] a transaction [FEATURE ID: 3] between a first client device , and a second client device [FEATURE ID: 4] via a transfer mechanism [FEATURE ID: 1] , the transfer mechanism comprising [TRANSITIVE ID: 2] a decentralized digital currency [FEATURE ID: 1] , the computing device comprising : a memory [FEATURE ID: 5] for storing [TRANSITIVE ID: 6] a first asymmetric key pair , the first asymmetric key pair comprising a first private key [FEATURE ID: 3] and a first public key [FEATURE ID: 7] ; a network interface [FEATURE ID: 8] for receiving [TRANSITIVE ID: 2] terms [FEATURE ID: 9] , the terms comprising : at least one of a first principal data or a second principal data [FEATURE ID: 10] ; a reference to at least one of a first data source or a second data source [FEATURE ID: 1] ; and an expiration timestamp [FEATURE ID: 11] ; a computer processor [FEATURE ID: 1] coupled [TRANSITIVE ID: 12] to the memory and the network interface , the computer processor configured to : read [TRANSITIVE ID: 13] the first private key from the memory ; compute [TRANSITIVE ID: 2] a first cryptographic signature [FEATURE ID: 3] from the first private key ; create [TRANSITIVE ID: 13] an inchoate data record [FEATURE ID: 11] comprising : a commit [TRANSITIVE ID: 4] input [FEATURE ID: 4] for receiving a commit data [FEATURE ID: 14] from a commit transaction ; one or more output data obtained from at least one of the first principal data or the second principal data , and a value data [FEATURE ID: 3] from at least one of the first data source or the second data source ; and the first cryptographic signature ; and publish the inchoate data record to at least one of the first client device or the second client device , wherein the decentralized digital currency [FEATURE ID: 1] comprises a distributed ledger [FEATURE ID: 1] that enables processing the transaction between the first client device and the second client device without the need for a trusted central authority [FEATURE ID: 1] , wherein the inchoate data record is used by at least one of the first client device or the second client device to create a complete data record [FEATURE ID: 4] and to create the transaction by broadcasting the complete data record for transmitting and receiving among network participants [FEATURE ID: 15] in the computer network [FEATURE ID: 1] for recording in the distributed ledger , wherein at least one of the first client device or the second client device signs the inchoate data record and saves a copy of the inchoate data record on at least one of the first client device or the second client device ; and wherein the at least one of the computing device , the first client device , or the second client device verifies the recording [FEATURE ID: 16] of the complete data record in the distributed ledger by observing an external state [FEATURE ID: 17] . 2 . The device [FEATURE ID: 1] of claim [FEATURE ID: 18] 1 , where : the computer processor is configured to obtain the one or more output data based on : the first principal data ; and the value data from the first data source . 3 . The device of claim 1 , where the computer processor is further [FEATURE ID: 19] |
1 . A trade order processing method [FEATURE ID: 1] for reducing [TRANSITIVE ID: 2] trade order processing latency in an electronic trading exchange [FEATURE ID: 11] , comprising [TRANSITIVE ID: 2] the steps of : receiving [TRANSITIVE ID: 2] at the electronic trading exchange trade orders [FEATURE ID: 1] to be matched against trade orders [FEATURE ID: 9] stored in a trade order book [FEATURE ID: 4] in a memory [FEATURE ID: 4] ; storing [TRANSITIVE ID: 6] at least some of the received trade orders in the trade order book before validating those received trade orders for trading risk [FEATURE ID: 16] ; determining , by one or more processors [FEATURE ID: 15] , whether a first one of the received trade orders matches a second trade order [FEATURE ID: 4] stored in the trade order book ; and verifying that the matched first and second trade orders are trade risk validated before executing a trade [FEATURE ID: 3] of the matched first and second trade orders . 2 . The trade order processing method of claim [FEATURE ID: 18] 1 , wherein the first trade order [FEATURE ID: 3] is stored in the trade order book if it does not match the second trade order , and the first trade order and the second trade order are validated after it is determined that the first one of the received trade orders matches the second trade order . 3 . The trade order processing method of claim 1 , wherein the step [FEATURE ID: 17] of determining whether the first trade order matches the second trade order is executed in parallel with validating one or both of the first and second trade orders [FEATURE ID: 4] . 4 . The trade order processing method of claim 1 , further comprising removing a trade order [FEATURE ID: 7] stored in the trade order book if the trade order is found invalid . 5 . The trade order processing method of claim 1 , wherein validating the trade orders includes calculating a risk [FEATURE ID: 3] associated with the trade orders and / or confirming properties [FEATURE ID: 16] of an account [FEATURE ID: 11] associated with the trade orders . 6 . A non-transitory computer [FEATURE ID: 1] - readable storage medium [FEATURE ID: 5] having computer readable code [FEATURE ID: 9] embodied therein for executing a trade order processing method for reducing trade order processing latency in an electronic trading exchange , comprising : receiving at the electronic trading exchange trade orders to be matched against trade orders stored in a trade order book in a memory ; storing at least some of the received trade orders in the trade order book before validating those received trade orders for trading risk ; determining whether a first one of the received trade orders matches a second trade order stored in the trade order book ; and verifying that the matched first and second trade orders are trade risk validated before executing a trade of the matched first and second trade orders . 7 . An electronic trading exchange apparatus [FEATURE ID: 1] , comprising : a memory configured to store a trade order book for storing trade orders ; and electronic circuitry [FEATURE ID: 8] , coupled to the memory , for reducing trade order processing latency in an electronic trading exchange and configured to : receive trade orders to be matched against trade orders stored in the trade order book ; store [FEATURE ID: 13] at least some of the received trade orders in the trade order book before validating those received trade orders for trading risk ; determine that a first one of the received trade orders matches a second trade order stored in the trade order book , and verify that the matched first and second trade orders are validated for trade risk before executing a trade of the matched first and second trade orders . 8 . The electronic trading exchange apparatus according to claim 7 , wherein the electronic circuitry is configured to remove a trade order stored in the trade order book if the trade order is not validated . 9 . The electronic trading exchange apparatus according to claim 7 , wherein the electronic circuitry is configured to validate trade orders by calculating a risk associated with each of the trade orders and confirming an account associated with each of the trade orders . 10 . An electronic trading exchange apparatus , comprising : a memory configured to store a trade order book for storing trade orders ; and a data processor [FEATURE ID: 1] , coupled to the memory , for reducing trade order processing latency when matching trade orders in an electronic trading exchange and programmed to : receive a first trade order for executing a trade with a second trade order stored in the trade order book , determine if the first trade order matches the second trade order stored in the trade order book before validating the first and second trade orders for trade risk , store the first trade order in the trade order book without trade risk validating the first trade order if the first trade order does not match the second trade order , validate the first trade order ; and the second trade order for trade risk after the first trade order matches the second trade order , and execute a trade of the matched first and second trade orders if the first and second trade orders are successfully trade risk validated . 11 . The electronic trading exchange apparatus in claim 10 , wherein the data processor is programmed to remove an invalidated order [FEATURE ID: 11] from the order book [FEATURE ID: 5] . 12 . An electronic trading exchange apparatus , comprising : a memory configured to store a trade order book for storing trade orders ; and a processor [FEATURE ID: 1] , coupled to the memory , for reducing trade order processing latency when matching trade orders in an electronic trading exchange and configured to : receive trade orders to be matched against trade orders stored in the trade order book , store at least some of the received trade orders in the trade order book before validating those received trade orders for trade risk , and determine in parallel operations [FEATURE ID: 14] whether a first one of the received trade orders matches a second trade order stored in the order book and whether the first and second trade orders are valid trade orders [FEATURE ID: 12] from a trade risk standpoint [FEATURE ID: 4] , wherein the processor is further [FEATURE ID: 19] configured to complete the parallel operations before executing a trade of the matched first and second trade orders . 13 . The electronic trading exchange apparatus according to claim 12 , wherein the processor is further configured to : assign a first validation status marker [FEATURE ID: 10] |