Point-to-point terminal and contract trading system

Abstract

A contract trading system is provided that has no single point of failure and is capable of determining a single contract outcome to be used from among multiple different contract outcomes. A peer-to-peer terminal comprises a bid data acquisition unit, a bid data transmission unit, a contract outcome calculation unit, a contract outcome transmission unit, a contract outcome receiving unit, and a contract outcome selection unit. The bid data acquisition unit acquires bid data. The bid data transmission unit transmits the bid data to other peer-to-peer terminals. The contract outcome calculation unit calculates a contract outcome based on the bid data set acquired by the bid data acquisition unit. The contract outcome transmission unit transmits the contract outcome to other peer-to-peer terminals. The contract outcome receiving unit receives other contract outcomes calculated by other peer-to-peer terminals from other peer-to-peer terminals. The contract outcome selection unit selects a contract outcome from the contract outcome and other contract outcomes.

Description

Technical Field

[0001] The present disclosure relates to a peer-to-peer terminal and a contract transaction system. Background Art

[0002] A contract transaction system has been proposed in which a person who wants to sell content and a person who wants to purchase content are matched via a network to conclude a contract transaction.

[0003] For example, in the financial asset trading system described in Patent Document 1, a user who wishes to trade financial assets operates a client terminal device (paragraph 0012). Furthermore, the exchange server receives transaction information transmitted from each client terminal device via the network and aggregates the transactions based on the received transaction information (paragraph 0013).

[0004] Prior art literature

[0005] Patent Literature

[0006] Patent Document 1: Japanese Utility Model Registration No. 3219516 Summary of the Invention

[0007] Technical issues to be solved by the invention

[0008] Conventional contract trading systems, such as the financial asset trading system described in Patent Document 1, employ a client-server model. Consequently, the server processes contract transactions. This makes the server a single point of failure. Consequently, a server failure renders the contract trading system unusable. Furthermore, to prevent unauthorized access to the server and malware infection, server security must be enhanced. Consequently, this incurs significant costs.

[0009] On the other hand, in peer-to-peer (P2P) networks like blockchains, peer terminals communicate with each other. Therefore, P2P networks lack a single point of failure, unlike the aforementioned servers. However, P2P networks lack a single terminal that manages the entire network, as described above. Therefore, when each terminal in a P2P network processes a contract transaction, the contract results calculated by each terminal may differ. Consequently, it is impossible to determine the single contract result to be relied upon.

[0010] The present disclosure is made in view of these problems and aims to provide a contract trading system that has no single point of failure and can determine a contract result to be relied upon from multiple different contract results.

[0011] Technical solutions to solve technical problems

[0012] The present disclosure relates to point-to-point terminals.

[0013] The peer-to-peer terminal includes a bid data acquisition unit, a bid data transmission unit, a contract result calculation unit, a contract result transmission unit, a contract result reception unit, and a contract result selection unit.

[0014] The bid data acquisition unit acquires bid data.

[0015] The bid data transmitting unit transmits the bid data to other peer-to-peer terminals.

[0016] The contract result calculation unit calculates the contract result based on the bid data set acquired by the bid data acquisition unit.

[0017] The contract result sending unit sends the contract result to other point-to-point terminals.

[0018] The contract result receiving unit receives, from the other peer-to-peer terminals, other contract results calculated by the other peer-to-peer terminals.

[0019] The contract result selection unit selects a contract result from the contract result and other contract results.

[0020] The present disclosure is also suitable for a contract trading system equipped with the point-to-point terminal.

[0021] Effects of the Invention

[0022] According to the present disclosure, contract transactions can be concluded in a peer-to-peer network comprising multiple peer-to-peer terminals. This provides a contract transaction system with no single point of failure. Furthermore, a contract transaction system can be provided that determines a single contract outcome to be relied upon from among multiple different contract outcomes.

[0023] The objects, features, aspects and advantages of the present disclosure will become more apparent from the following detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 It is a block diagram schematically illustrating a contract transaction system according to the first embodiment.

[0025] Figure 2 1 is a network diagram schematically illustrating a peer-to-peer (P2P) network including a plurality of terminals included in the contract transaction system according to the first embodiment.

[0026] Figure 3This is a block diagram schematically illustrating the hardware configuration of each terminal included in the contract transaction system according to the first embodiment.

[0027] Figure 4 This is a flowchart illustrating the flow of processing performed by each terminal included in the contract transaction system according to the first embodiment.

[0028] Figure 5 This is a diagram illustrating an example of bid data acquired by each terminal included in the contract transaction system according to the first embodiment.

[0029] Figure 6 This is a diagram illustrating an example of a contract result calculated by a terminal included in the contract transaction system according to the first embodiment.

[0030] Figure 7 This is a diagram illustrating an example of a selection criterion referred to by each terminal included in the contract trading system according to the first embodiment.

[0031] Figure 8 This is a diagram illustrating an example of blocks stored in each terminal included in the contract transaction system according to the first embodiment.

[0032] Figure 9 It is a block diagram schematically illustrating a contract transaction system according to the second embodiment.

[0033] Figure 10 This is a flowchart illustrating the flow of processing performed by each terminal included in the contract transaction system according to the second embodiment.

[0034] Figure 11 This is a diagram illustrating an example of an incentive ratio referenced by each terminal included in the contract transaction system according to the second embodiment.

[0035] Figure 12 A diagram illustrating an example of incentives calculated by each terminal included in the contract trading system according to the second embodiment.

[0036] Figure 13 A diagram schematically illustrating an example of a topological structure of a P2P network.

[0037] Figure 14 It is a block diagram schematically illustrating a contract transaction system according to a third embodiment.

[0038] Figure 15 This is a flowchart illustrating the flow of processing performed by each terminal included in the contract transaction system according to the third embodiment.

[0039] Figure 16 This is a diagram illustrating an example of evaluation indicators referenced by each terminal included in the contract trading system according to the third embodiment.

[0040] Reference numerals

[0041] 1, 2, 3: Contract trading system; 11: Multiple terminals; 12: Certification authority; 21: P2P network; 41: Authentication information acquisition unit; 42: Bid data acquisition unit; 43: Bid data sending unit; 44: Contract result calculation unit; 45: Contract result sending unit; 46: Contract result receiving unit; 47: Contract result verification unit; 48: Contract result selection unit; 49: Block receiving unit; 50: Block selection unit; 51: Contract result storage unit; 52: Incentive calculation unit; 53: Terminal evaluation unit. DETAILED DESCRIPTION

[0042] 1 Implementation Method 1

[0043] 1.1 Overview of the Contract Trading System

[0044] Figure 1 It is a block diagram schematically illustrating a contract transaction system according to the first embodiment.

[0045] Figure 1 The contract trading system 1 of the illustrated embodiment 1 acquires bid data 101 created by a user. The acquired bid data 101 indicates the content of a bid indicating an intention to trade a commodity. Bid data 101 is either buy bid data or sell bid data. Buy bid data indicates the content of a buy bid indicating an intention to purchase a commodity. Sell bid data indicates the content of a sell bid indicating an intention to sell a commodity. Commodities include securities, electricity, natural gas, wheat, gold, and the like.

[0046] Furthermore, the contract trading system 1 concludes a contract transaction between the buy bid and the sell bid, and calculates a contract result 102 indicating the result of the concluded contract transaction. The contract trading system 1 concludes the contract transaction so that a buyer user who has created buy bid data can purchase the product at a price below the bid price indicated by the buy bid data, and a seller user who has created sell bid data can sell the product at a price above the bid price indicated by the sell bid data.

[0047] A bid deadline is set in the contract trading system 1. The contract trading system 1 concludes a contract transaction between a buy bid represented by buy bid data acquired before the set bid deadline and a sell bid represented by sell bid data acquired before the set bid deadline. The contract trading system 1 concludes the contract transaction at the set bid deadline. The bid deadline is set, for example, at a fixed time interval. For example, the fixed time interval is 5 minutes. If the fixed time interval is 5 minutes, for example, at any given hour (TT), the bid deadlines are set at TT:00:00, TT:05, TT:10, TT:15, TT:20, TT:25, TT:30, TT:35, TT:40, TT:45, TT:50, and TT:55.

[0048] 1.2 Elements in the contract trading system

[0049] like Figure 1 As shown in the figure, the contract trading system 1 includes multiple terminals 11 and a certification agency 12. Figure 1 Only terminals 11a and 11b are shown in the figure among the plurality of terminals 11.

[0050] exist Figure 1 In the description, for convenience, the terminal 11 a is handled as each terminal 11 x included in the plurality of terminals 11 , and the terminal 11 b is handled as another terminal 11 y included in the plurality of terminals 11 .

[0051] Each terminal 11x is a peer-to-peer (P2P) terminal constituting a P2P network.

[0052] Each terminal 11x acquires bid data 101. The acquired bid data 101 includes bid data 101x received by each terminal 11x from a terminal not included in the plurality of terminals 11, bid data 101y received by each terminal 11x from another terminal 11y included in the plurality of terminals 11, or bid data (not shown) created by each terminal 11x. Based on this, each terminal 11x acquires a bid data set 103.

[0053] In addition, each terminal 11x transmits the acquired bid data 101 to the other terminal 11y.

[0054] Furthermore, each terminal 11x concludes a contract transaction between a buy bid and a sell bid, and calculates a contract result 102x indicating the result of the concluded contract transaction.

[0055] If the bid data sets 103 obtained by the terminals 11 are identical, the contract results 102x calculated by the terminals 11 are also identical. However, if the bid data sets 103 differ due to factors such as communication delays or the topology of the P2P network including the terminals 11, the contract results 102x may differ. If the contract results 102x differ, each terminal 11x selects one contract result from the multiple contract results 102x to be used as the basis.

[0056] The certification authority 12 issues a digital certificate 104 to each terminal 11x.

[0057] 1.3P2P Network

[0058] Figure 2 1 is a network diagram schematically illustrating a P2P network including a plurality of terminals included in the contract transaction system according to the first embodiment.

[0059] Figure 2 The P2P network 21 shown includes a plurality of terminals 11 . Figure 2 Only terminals 11a, 11b, 11c, 11d, 11e, and 11f are shown in the figure among the plurality of terminals 11.

[0060] like Figure 2 As shown, the P2P network 21 includes a plurality of communication lines 22. Each communication line 22x included in the plurality of communication lines 22 connects two terminals included in the plurality of terminals 11 to each other so as to be communicable.

[0061] Each terminal 11 x knows the address of a terminal communicably connected to the terminal 11 x and can transmit and receive data to and from the terminal.

[0062] Each terminal 11x is operated by a user who exclusively owns the terminal 11x. Therefore, terminals 11a, 11b, 11c, 11d, 11e, 11f, ... are respectively operated by users A, B, C, D, E, F, ... Each terminal 11x may be operated by two or more users who share the terminal 11x.

[0063] 1.4 Hardware structure of each terminal

[0064] Figure 3 This is a block diagram schematically illustrating the hardware configuration of each terminal included in the contract transaction system according to the first embodiment.

[0065] Each terminal 11x includes Figure 3 The personal computer (PC) 31 is shown. Each terminal 11x may include an information processing device other than the PC 31. For example, each terminal 11x may include a smartphone, a tablet, or the like.

[0066] like Figure 3 As shown, the PC 31 includes a processor 32 , a memory 33 , and a storage 34 .

[0067] The contract transaction program 35 is installed in the storage 34 . The contract transaction program 35 can be installed by writing the contract transaction program 35 read from the external recording medium 36 into the storage 34 or by writing the contract transaction program 35 received via the network 37 into the storage 34 .

[0068] Processor 32 may be a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing unit (DSP), or the like. Memory 33 may be a random access memory (RAM), or the like. Storage 34 may be a hard disk drive, a solid-state drive, a RAM disk, or the like. External recording medium 36 may be a compact disc (CD), a digital versatile disc (DVD), a Blu-ray disc (BD), a universal serial bus (USB) memory, or the like.

[0069] The memory 33 , the storage 34 , and the external recording medium 36 are non-transitory computer-readable recording media on which the contract transaction program 35 is recorded.

[0070] In the PC 31, the contract transaction program 35 installed in the storage 34 is loaded into the memory 33, and the loaded contract transaction program 35 is executed by the processor 32. In this way, the PC 31 functions as each terminal 11x.

[0071] 1.5 Elements in each terminal

[0072] like Figure 1 As shown, each terminal 11x includes an authentication information acquisition unit 41, a bid data acquisition unit 42, a bid data transmission unit 43, a contract result calculation unit 44, a contract result transmission unit 45, a contract result reception unit 46, a contract result verification unit 47, a contract result selection unit 48, a block reception unit 49, a block selection unit 50, and a contract result storage unit 51. The bid data acquisition unit 42 includes a bid data reception unit 54 and a bid data creation unit 55.

[0073] These elements are configured by loading the contract transaction program 35 installed in the storage 34 into the memory 33 and executing the loaded contract transaction program 35 by the processor 32. Some of these elements may be configured by hardware that does not execute the program.

[0074] 1.6 Processing Flow of Each Terminal

[0075] Figure 4 This is a flowchart illustrating the flow of processing performed by each terminal included in the contract transaction system according to the first embodiment.

[0076] Each terminal 11x executes Figure 4 Steps S101 to S111 are shown.

[0077] In step S101, the authentication information acquisition unit 41 performs authentication information acquisition processing. At this point, the authentication information acquisition unit 41 acquires the digital certificate 104 of each terminal 11x from the certification authority 12 and stores the acquired digital certificate 104 of each terminal 11x. The acquired digital certificate 104 is, for example, a digital certificate that complies with the public key infrastructure standard X.509 established by the International Telecommunication Union Telecommunication Standardization Sector (ITU-T).

[0078] In the next step S102, the bid data acquisition unit 42 performs bid data acquisition processing. At this point, the bid data acquisition unit 42 acquires bid data 101 and stores the acquired bid data 101. Based on this, the bid data acquisition unit 42 acquires a bid data set 103 and stores the acquired bid data set 103. The acquired bid data 101 includes bid data 101x received by the bid data receiving unit 54 from terminals not included in the plurality of terminals 11, bid data 101y received by the bid data receiving unit 54 from other terminals 11y included in the plurality of terminals 11, and bid data (not shown) created at each terminal 11x by the bid data creation unit 55. Each terminal 11x creates bid data by operating the terminal 11x through the user of each terminal 11x. Terminals not included in the plurality of terminals 11 include terminals owned by the user, for example. Terminals owned by the user include smartphones, for example.

[0079] Figure 5 This is a diagram illustrating an example of bid data acquired by each terminal included in the contract transaction system according to the first embodiment.

[0080] like Figure 5 As shown, the acquired bid data 101 includes a bid data identifier (ID) 111 , a timestamp 112 , a terminal ID 113 , a user ID 114 , a product 115 , a bid quantity 116 , a bid unit price 117 , a buying and selling category 118 and a digital certificate 119 .

[0081] The bid data ID 111, time stamp 112, terminal ID 113, user ID 114, product 115, bid quantity 116, bid unit price 117, transaction category 118, and digital certificate 119 are recorded in the first to ninth columns of the table, respectively.

[0082] Bid data ID 111 identifies bid data 101. Bid data ID 111 is determined so as not to overlap with bid data IDs included in other bid data. Bid data ID 111 is the hash value returned when a hash function is given information about the terminal that created bid data 101 and the time when bid data 101 was created as arguments.

[0083] The timestamp 112 indicates the time when the bid data 101 was created. The timestamp 112 has the format of "yyyy / MM / dd / hh:mm:ss". "yyyy" indicates year. "MM" indicates month. "dd" indicates day. "hh" indicates hour. "mm" indicates minute. "ss" indicates second.

[0084] The terminal ID 113 identifies the terminal that created the bid data 101 .

[0085] User ID 114 identifies the user who created bid data 101 .

[0086] Product 115, bid quantity 116, bid price 117, and trade category 118 respectively indicate the product, bid quantity, bid price, and trade category that constitute the bid represented by bid data 101. Trade category 118 indicates whether bid data 101 is buy bid data or sell bid data. If trade category 118 is "buy," bid data 101 is buy bid data. If trade category 118 is "sell," bid data 101 is sell bid data.

[0087] The digital certificate 119 is a digital certificate of the terminal that created the bid data 101 .

[0088] If user A creates buy bid data on terminal A at 00:00:30 on January 1, 2019, indicating a buy bid to purchase item "X" in quantity "2.0" at a bid price of "12," bid data ID 111 is, for example, "0002." Furthermore, timestamp 112 is "2019 / 01 / 01 / 00:00:30." Terminal ID 113 is terminal A's terminal ID. User ID 114 is user A's user ID. Item 115 is "X." Bid quantity 116 is "2.0." Bid price 117 is "12." Buy / sell category 118 is "Buy." Digital certificate 119 is "Certificate A," which is terminal A's digital certificate.

[0089] In the next step S103, the bid data transmitting unit 43 performs bid data transmission processing. At this time, the bid data transmitting unit 43 transmits the acquired bid data 101 to the other terminal 11y. The bid data transmitting unit 43 broadcasts the acquired bid data 101 to the other terminal 11y.

[0090] In the next step S104, the contract result calculation unit 44 performs contract result calculation processing. At this point, the contract result calculation unit 44 calculates the contract result 102x based on the acquired bid data set 103 and saves the calculated contract result 102x. If the bid deadline is set at 5-minute intervals, the contract result calculation unit 44 calculates the contract result 102x at 5-minute intervals. For example, if the current time is 00:05:00 on January 1, 2019, the contract result calculation unit 44 calculates the contract result 102x based on the bid data set 103 containing the bid data 101, which includes a timestamp 112 indicating a time before 00:05:00 on January 1, 2019. The contract result calculation unit 44 concludes a contract transaction between the buy bid and the sell bid for each type of product 115. The combination of bid and ask prices, the number of contracts, and the contract price for a contract transaction are determined using a method similar to the itayose method used before the stock market opens.

[0091] Figure 6 This is a diagram illustrating an example of a contract result calculated by a terminal included in the contract transaction system according to the first embodiment.

[0092] Figure 6 (a) Figure 6 (b) and Figure 6 (c) shows examples of a contract result 121a calculated by the terminal 11a, a contract result 121b calculated by the terminal 11b, and a contract result 121c calculated by the terminal 11c.

[0093] like Figure 6 As shown, each contract result 121x included in the contract results 121a, 121b and 121c includes a header 131 and a body 132.

[0094] like Figure 6 As shown, the block header 131 includes a contract result ID 141 , a timestamp 142 , a terminal ID 143 and a digital certificate 144 .

[0095] The contract result ID 141 , the timestamp 142 , the terminal ID 143 , and the digital certificate 144 are respectively recorded in the first to fourth columns of the table.

[0096] The contract result ID 141 identifies each contract result 121x. The contract result ID 141 is determined so that it does not overlap with the contract result IDs included in other contract results. The contract result ID 141 is the hash value returned when a hash function is applied with information about the terminal that calculated each contract result 121x and the time each contract result 121x was calculated as arguments.

[0097] The timestamp 142 indicates the time when each contract result 121x was calculated. The timestamp 142 has the format of "yyyy / MM / dd / hh:mm:ss". "yyyy" represents the year. "MM" represents the month. "dd" represents the day. "hh" represents the hour. "mm" represents the minute. "ss" represents the second.

[0098] The terminal ID 143 identifies the terminal that calculated each contract result 121x.

[0099] The digital certificate 144 is a digital certificate of the terminal that calculated each contract result 121x.

[0100] like Figure 6 As shown, block 132 includes a buy bid data ID 151 , a sell bid data ID 152 , a contract quantity 153 , and a contract unit price 154 .

[0101] The buy bid data ID 151 , sell bid data ID 152 , contract quantity 153 , and contract unit price 154 are respectively recorded in the first to fourth columns of the table.

[0102] The buy bid data ID 151 and the sell bid data ID 152 identify the buy bid data and the sell bid data respectively indicating the details of the buy bid and the sell bid of the completed contract transaction.

[0103] The contract quantity 153 and the contract unit price 154 respectively indicate the contract quantity and the contract unit price constituting the contents of the completed contract transaction.

[0104] In the block 132, a buy bid data ID 151 and a sell bid data ID 152, which respectively indicate the details of the buy bid and the sell bid of the completed contract transaction, are associated with each other.

[0105] To conclude a contract transaction on the P2P network 21, each terminal 11x, rather than the server, must calculate the contract outcome 102x. However, when each terminal 11x calculates the contract outcome 102x, the bid data sets 103 obtained by each of the multiple terminals 11x may differ due to factors such as communication delays and the topology of the P2P network 21. As a result, the multiple contract outcomes 102x calculated by each of the multiple terminals 11x may differ. For example, when the bid data set 103 acquired by the terminal 11a includes bid data 101 including bid data IDs 111 such as "0001", "0002", and "0003", the bid data set 103 acquired by the terminal 11b includes bid data 101 including bid data IDs 111 such as "0001" and "0002", and the bid data set 103 acquired by the terminal 11c includes bid data 101 including bid data IDs 111 such as "0002" and "0003", Figure 6 As shown, the contract result 121a calculated by the terminal 11a, the contract result 121b calculated by the terminal 11b, and the contract result 121c calculated by the terminal 11c are different. In step S108, the contract result selection process is performed to select one contract result as the final result from these contract results 121a, 121b, and 121c.

[0106] In the next step S105, the contract result transmission unit 45 performs contract result transmission processing. At this point, the contract result transmission unit 45 transmits the calculated contract result 102x to the other terminal 11y. Furthermore, if there are other contract results 102y received from the other terminal 11y by the contract result reception unit 46, the contract result transmission unit 45 transmits the received other contract results 102y to the other terminal 11y. The contract result transmission unit 45 broadcasts the calculated contract result 102x and the received other contract results 102y to the other terminal 11y.

[0107] In the next step S106, the contract result receiving unit 46 performs contract result receiving processing. At this time, the contract result receiving unit 46 receives the other contract result 102y calculated by the other terminal 11y from the other terminal 11y and stores the received other contract result 102y.

[0108] In the next step S107, the contract result verification unit 47 performs contract result verification processing. At this point, the contract result verification unit 47 verifies the received other contract result 102y and, based on the verification results, determines whether the other contract result 102y is a candidate for the one contract result selected in step S108. If the received other contract result 102y is not a candidate for the one contract result selected, the contract result verification unit 47 deletes the other contract result 102y.

[0109] When verifying the received other contract result 102y, the contract result verification unit 47 verifies whether the other contract result 102y is consistent. If the received other contract result 102y is consistent, the contract result verification unit 47 selects the other contract result 102y as a candidate for the selected contract result. If the received other contract result 102y is inconsistent, the contract result verification unit 47 does not select the other contract result 102y as a candidate for the selected contract result and deletes it.

[0110] Verification of whether there is consistency includes, for example, the following verification.

[0111] (1) Verify that the digital certificates 119 contained in the bid data 101 identified by the buy bid data ID 151 and the sell bid data ID 152 contained in the other contract result 102y are consistent with the digital certificates 104 obtained from the certification authority 12,

[0112] (2) Verify whether the digital certificate 144 contained in the other contract result 102y is consistent with the digital certificate 104 obtained from the certification authority 12,

[0113] (3) Verify whether the time indicated by the timestamp 112 included in the bid data 101 determined by using the buy bid data ID 151 and the sell bid data ID 152 included in the other contract result 102y is before the time indicated by the timestamp 142 included in the other contract result 102y,

[0114] (4) Verify whether the bid price 117 included in the buy bid data 101 determined by the buy bid data ID 151 included in the other contract result 102y is less than the bid price 117 included in the sell bid data 101 determined by the sell bid data ID 152 associated with the buy bid data ID 151,

[0115] (5) Verify whether the bid price 117 included in the selling bid data 101 identified by the selling bid data ID 152 included in the other contract result 102y is greater than the bid price 117 included in the buying bid data 101 identified by the buying bid data ID 151 associated with the selling bid data ID 152,

[0116] (6) Verify whether the total of the bid quantity 116 included in the buy bid data 101 identified by the buy bid data ID 151 included in the other contract result 102y is less than the total of the bid quantity 116 included in the sell bid data 101 identified by the sell bid data ID 152 associated with the buy bid data ID 151, and

[0117] (7) Verify whether the total of the bid quantity 116 included in the selling bid data 101 specified by the selling bid data ID 152 included in the other contract result 102y is less than the bid quantity 116 included in the buying bid data 101 specified by the buying bid data ID 151 associated with the selling bid data ID 152.

[0118] In the next step S108, the contract result selection unit 48 performs contract result selection processing. At this point, the contract result selection unit 48 selects a contract result from the calculated contract result 102x and the received other contract results 102y. If it is determined that the other contract result 102y is a candidate for selection, the contract result selection unit 48 selects a contract result from the contract result 102x and the other contract results 102y that were selected as candidates. If the bid deadline is set at 5-minute intervals, the contract result selection unit 48 selects a contract result at 5-minute intervals, selecting a contract result from the contract result 102x and the other contract results 102y calculated in the past 5 minutes. The contract result selection unit 48 selects a contract result based on the selection index 107.

[0119] Figure 7 This is a diagram illustrating an example of a selected index referenced by each terminal included in the contract trading system according to the first embodiment.

[0120] Figure 7The selected indicator 107 shown is the "largest total contract volume" selected indicator. When the selected indicator 107 is the "largest total contract volume" selected indicator, the contract result with the largest total contract quantity 153, included in the calculated contract result 102x and the received other contract results 102y, is selected as the contract result. For example, consider the following situation: the bid deadline is set at 5-minute intervals, and the current time is 00:10:00 on January 1, 2019. From the calculated bid deadline at 00:05:00 on January 1, 2019, Figure 6 The contract result shown in (a) 121a, Figure 6 The contract result shown in (b) 121b and Figure 6 A single contract result is selected from the contract results 121c shown in (c). In this case, the total number of contracts 153 included in contract result 121a is 3.0 + 1.0 = 4.0, the total number of contracts 153 included in contract result 121b is 3.0, and the total number of contracts 153 included in contract result 121c is 1.0. Therefore, contract result 121a, which has the largest total number of contracts 153 of 4.0, is the selected contract result. This allows the selection of a single contract result even when multiple contract results 102x calculated by multiple terminals 11 differ.

[0121] In the next step S109, the block receiving unit 49 performs block reception processing. At this point, the block receiving unit 49 receives, from the other terminal 11y, a past block 108 containing a contract result selected before the contract result was selected in step S108. If the past block 108 is not stored in each terminal 11x, the block receiving unit 49 receives the past block 108 from the other terminal 11y. For example, if the bid deadline is set at 5-minute intervals, and the previous block containing a contract result selected at 00:00:00 on January 1, 2019, 5 minutes prior, is not stored in terminal 11a due to a malfunction of terminal 11a, and terminal 11a recovers at 00:05:00 on January 1, 2019, the block receiving unit 49 of terminal 11a receives the previous block from the other terminal 11y.

[0122] In the next step S110, the block selection unit 50 performs block selection processing. At this time, the block selection unit 50 selects a past block 108 to follow the new block from the multiple past blocks received by the block reception unit 49 and stores the selected past block 108. The selected past block 108 is the past block with the largest number of blocks, as determined by majority voting, among the multiple past blocks received by the block reception unit 49.

[0123] In the next step S111, the contract result storage unit 51 performs contract result storage processing. At this point, the contract result storage unit 51 stores the selected contract result and updates the bid data 101. The updated bid data 101 is obtained by replacing the bid quantity contained in the pre-update bid data 101 with the new bid quantity obtained by subtracting the contract quantity from the bid quantity. When storing the selected contract result, the contract result storage unit 51 stores a new block containing the selected contract result. The new block is stored following the selected past block 108.

[0124] Figure 8 1 and 2 illustrate examples of blocks stored in each terminal included in the contract transaction system according to the first embodiment.

[0125] like Figure 8 As shown, the new block 161 follows the previous block 162.

[0126] New block 161 includes a selected contract result 171 and a hash value 172. Previous block 162 includes a selected contract result 173 from 5 minutes ago and a hash value 174. Hash value 174 is the hash value returned when the previous block (not shown) is given as an argument to hash function 175. Hash value 172 is the hash value returned when hash function 175 is given the previous block 162 as an argument.

[0127] 1.7 Effects of Implementation Method 1

[0128] According to the first embodiment, contract transactions do not need to be concluded on a server, as is the case with a client-server model. Instead, contract transactions can be concluded on a P2P network 21 comprising multiple terminals 11. This provides a contract transaction system 1 with no single point of failure. Furthermore, it is possible to determine a single contract outcome 171 to be relied upon from among multiple different contract outcomes.

[0129] 2 Implementation Method 2

[0130] 2.1 Differences between Implementation 1 and Implementation 2

[0131] Figure 9 It is a block diagram schematically illustrating a contract transaction system according to the second embodiment. Figure 10 This is a flowchart illustrating the flow of processing performed by each terminal included in the contract transaction system according to the second embodiment.

[0132] Figure 9 The contract transaction system 2 of the embodiment 2 shown is mainly different from the following aspects Figure 1The contract transaction system 1 of the embodiment 1 shown is different. In the contract transaction system 2, the same configuration as that adopted in the contract transaction system 1 is adopted also in the aspects not described below.

[0133] like Figure 9 As shown in FIG. 1 , each terminal 11x included in the contract transaction system 2 further includes an incentive calculation unit 52. Figure 10 As shown, each terminal 11x included in the contract trading system 2 further executes step S112.

[0134] In step S112, the incentive calculation unit 52 performs an incentive calculation process. The incentive calculation unit 52 calculates an incentive for the terminal that calculated the selected contract result. The user of the terminal receives the calculated incentive. The incentive calculation unit 52 calculates the incentive based on the incentive ratio 109.

[0135] Figure 11 This is a diagram illustrating an example of an incentive ratio referenced by each terminal included in the contract transaction system according to the second embodiment. Figure 12 A diagram illustrating an example of incentives calculated by each terminal included in the contract trading system according to the second embodiment.

[0136] Figure 11 The incentive ratio 109 shown is an incentive ratio of "1%". When the incentive ratio 109 is an incentive ratio of "1%", the result of the selected contract is Figure 6 In the case of the contract result 121a shown in (a), the calculation is Figure 12 Excitation 181 shown.

[0137] Figure 12Incentive 181 shown includes bid / ask data ID 191, ask / ask data ID 192, and commission 193. Bid / ask data ID 191, ask / ask data ID 192, and commission 193 are listed in columns 1 through 3 of the table, respectively. Bid / ask data ID 191 and ask / ask data ID 192 identify bid / ask data and ask / ask data, respectively, representing the bid / ask and ask / ask details of the completed contract transaction. Commission 193 represents the commission paid to the user of the terminal that calculated the contract result representing the result of the completed contract transaction. Commission 193 is the product of the number of contracts 153 included in the contract result representing the result of the completed contract transaction, the contract unit price 154 included in the contract result, and the incentive ratio 109. Therefore, the commission 193 paid to user A of terminal 11a, who calculated the following contract result 121a, representing the result of a contract transaction concluded between a buy bid for the content indicated by buy bid data ID 191 "0001" and a sell bid for the content indicated by sell bid data ID 192 "0002," is 3.0 × 11.5 × 1% = 0.345. Buyer user B, who created the buy bid data indicated by buy bid data ID 191 "0001," pays commission 193 "0.345" to user A of terminal 11a, who holds digital certificate 144 "Certificate A." Furthermore, commission 193 paid to user A of terminal A, who calculated contract result 121a, representing the result of a contract transaction concluded between a buy bid represented by buy bid data ID 191 "0003" and a sell bid represented by sell bid data ID 192 "0002," is 1.0 × 11 × 1% = 0.11. Buyer user C, who created the buy bid data identified by buy bid data ID 191 "0003," pays commission 193 "0.11" to user A of terminal 11a, which holds digital certificate "Certificate A." Alternatively, the buyer and seller users may share commission 193 equally. Alternatively, the seller user may pay commission 193.

[0138] In step S111 , the contract result storage unit 51 performs contract result storage processing. At this time, the contract result storage unit 51 stores the incentive 181 calculated together with the selected contract result and updates the bid data 101 .

[0139] 2.2 Effects of Implementation Method 2

[0140] The second embodiment has the same effects as those of the first embodiment.

[0141] Furthermore, the second embodiment also has the following effects.

[0142] Figure 13 A diagram schematically illustrating an example of a topological structure of a P2P network.

[0143] In the P2P network 21 has Figure 13 In the topology shown, communication line 202, which connects terminal set 201a including terminal 11a and terminal set 201b including terminal 11b for mutual communication, consists solely of communication line 203, which connects terminal 11a and terminal 11b for mutual communication. Therefore, if communication via communication line 203 is disconnected, P2P network 21 is severed, and the contract results calculated at terminal set 201a and terminal set 201b differ from each other.

[0144] In the second embodiment, the user of the terminal that calculates the selected contract result, that is, the contract result with the largest total number of contracts 153, receives incentive 181. Therefore, to obtain incentive 181, there is an incentive to increase the bid data 101 received by each terminal 11x and to increase the bid data 101 reflected in the contract result 102x calculated by each terminal 11x. Furthermore, to increase the bid data 101 received by each terminal 11x, it is effective to increase the number of terminals communicably connected to each terminal 11x, thus increasing the number of communication lines 22 constituting the P2P network 21. As a result, the disconnection of the P2P network 21 can be prevented, and the contract results calculated by the terminal set 201a and the contract results calculated by the terminal set 201b can be prevented from differing from each other.

[0145] 3 Implementation Method 3

[0146] 3.1 Differences between Implementation 1 and Implementation 3

[0147] Figure 14 It is a block diagram schematically illustrating a contract transaction system according to a third embodiment. Figure 15 This is a flowchart illustrating the flow of processing performed by each terminal included in the contract transaction system according to the third embodiment.

[0148] Figure 14 The contract transaction system 3 of the embodiment 3 shown is mainly different from the following aspects: Figure 1 The contract transaction system 1 of the embodiment 1 shown is different. Regarding the points not described below, the contract transaction system 3 also adopts the same configuration as that adopted in the contract transaction system 1.

[0149] like Figure 14 As shown in FIG. 1 , each terminal 11x included in the contract transaction system 3 further includes a terminal evaluation unit 53. Figure 15As shown, each terminal 11x included in the contract trading system 3 further executes step S113.

[0150] In step S113, the terminal evaluation unit 53 performs terminal evaluation processing. At this point, the terminal evaluation unit 53 evaluates the other terminal 11y and selects the transmission source terminal of the past block 108 from the other terminal 11y based on the evaluation results. The terminal evaluation unit 53 evaluates the other terminal 11y based on the evaluation index 110.

[0151] Figure 16 This is a diagram illustrating an example of evaluation indicators referenced by each terminal included in the contract trading system according to the third embodiment.

[0152] Figure 16 The evaluation indicator 110 shown is the "number of contract result calculations." When this is the case, the terminal evaluation unit 53 references the received past block and extracts other terminals 11y that calculated contract results. Furthermore, the terminal evaluation unit 53 sorts the other terminals 11y in descending order of the number of times they calculated contract results and selects a set number of other terminals 11y that are ranked first as the source terminals for the past block 108.

[0153] In the next step S109, the block receiving unit 49 performs a block receiving process. At this time, the block receiving unit 49 receives the past block 108 from the transmission source terminal of the selected past block 108.

[0154] 3.2 Effects of Implementation 3

[0155] The third embodiment has the same effects as those of the first embodiment.

[0156] Furthermore, the third embodiment has the following effects.

[0157] In the first embodiment, if past blocks 108 are not stored in each terminal 11x, the block receiving unit 49 receives multiple past blocks from multiple other terminals 11y. Furthermore, the block selecting unit 50 selects a past block 108 from among the received past blocks to be followed by the new block. The selected past block 108 is determined by a majority vote among the received past blocks. However, to ensure the reliability of the majority vote, the block receiving unit 49 must receive a large number of past blocks, which increases the load on each terminal 11x during the block reception process.

[0158] In contrast, in the third embodiment, when past blocks are not stored in each terminal 11x, the past block 108 is received from the selected terminal that sent the past block 108. Therefore, the block receiving unit 49 does not need to receive a large number of past blocks, and the load imposed on each terminal 11x during the block reception process is reduced.

[0159] Furthermore, the various embodiments can be freely combined or the various embodiments can be appropriately modified or omitted.

[0160] While the embodiments have been described in detail, the above description is in all aspects illustrative and the embodiments are not limited thereto, and it is understood that numerous modifications not shown are conceivable.

Claims

1. A point-to-point terminal comprising: A bid data acquisition unit, which acquires bid data; a bid data sending unit, configured to send the bid data to other point-to-point terminals; a contract result calculation unit, configured to calculate a contract result based on the bid data set acquired by the bid data acquisition unit; A contract result sending unit, sending the contract result to the other point-to-point terminals; a contract result receiving unit, receiving, from the other peer-to-peer terminals, other contract results calculated by the other peer-to-peer terminals; as well as A contract result selection unit selects a contract result to be used as a final result from the contract result and the other contract results, wherein When the contract result is different from the other contract results due to a difference in the plurality of bid data sets acquired by the peer-to-peer terminal and the other peer-to-peer terminals, the contract result selection unit selects the one contract result based on a selection index. The peer-to-peer terminal further includes a contract result verification unit that verifies the other contract results and determines, based on the verification result, whether the other contract results are candidates for the one contract result to be selected by the contract result selection unit. The contract result verification unit verifies whether the other contract results are consistent. If the other contract results are consistent, the other contract results are used as candidates for the one contract result. If the other contract results are inconsistent, the other contract results are not used as candidates for the one contract result and are deleted. The contract result selection unit selects the one contract result from the contract result and other contract results that are candidates for the one contract result.

2. A point-to-point terminal according to claim 1, wherein The selected indicator is the maximum total number of contracts. The one contract result is the contract result with the largest total number of contracts included in the contract result and the other contract results.

3. The point-to-point terminal according to claim 1, wherein The system further includes an incentive calculation unit that calculates an incentive for a peer-to-peer terminal that calculates the one contract result.

4. A point-to-point terminal according to claim 2, wherein: The system further includes an incentive calculation unit that calculates an incentive for a peer-to-peer terminal that calculates the one contract result.

5. The point-to-point terminal according to any one of claims 1 to 4, further comprising: a block receiving unit that receives a past block from the other peer-to-peer terminal, the past block including a past contract result selected before the one contract result is selected; and The contract result storage unit stores a new block, which follows the past block and includes the one contract result.

6. A point-to-point terminal according to claim 5, wherein: The block receiving unit receives a plurality of past blocks, The method further includes a block selecting unit configured to select the past block from among the plurality of past blocks.

7. The point-to-point terminal according to claim 5, wherein: further comprising a terminal evaluation unit that evaluates the other peer-to-peer terminals and selects a peer-to-peer terminal that is a transmission source of the past block from among the other peer-to-peer terminals based on a result of the evaluation; The block receiving unit receives the past block from a peer-to-peer terminal that is a transmission source of the past block.

8. The point-to-point terminal according to claim 6, wherein: further comprising a terminal evaluation unit that evaluates the other peer-to-peer terminals and selects a peer-to-peer terminal that is a transmission source of the past block from among the other peer-to-peer terminals based on a result of the evaluation; The block receiving unit receives the past block from a peer-to-peer terminal that is a transmission source of the past block.

9. A point-to-point terminal according to any one of claims 1 to 4, wherein: The device further comprises an authentication information acquisition unit, which acquires the digital certificate of the point-to-point terminal from a certification authority. The bidding data includes a digital certificate of the peer-to-peer terminal that created the bidding data, The contract result includes a digital certificate of the peer-to-peer terminal that calculates the contract result.

10. A contract trading system, comprising multiple point-to-point terminals, wherein Each of the plurality of point-to-point terminals is the point-to-point terminal according to any one of claims 1 to 9.

Images