JP6676102B2 - System, method and program for token exchange - Google Patents

Description

  The present invention relates to exchanging tokens. More specifically, the present invention relates to exchanging tokens between users utilizing a smart contract based on blockchain technology.

  There is known a payment method within a specific group using a mobile device such as a mobile phone or a personal computer for a local currency which is an evaluation value obtained by quantifying the degree of appreciation (for example, see Patent Document 1).

  Also, a token realized using a smart contract based on a blockchain technology such as Ethereum is known (for example, see Non-Patent Document 1).

JP 2003-303279 A

ERC: Token Standard # 20, https://github.com/ethereum/eips/issues/20

The applicant has noticed that various phenomena can be visualized according to the evaluation value obtained by quantifying the degree of appreciation.
For example, by issuing and distributing a token in which a degree of appreciation or the like is quantified in a certain company, it becomes possible to visualize the connection and evaluation between employees. According to this visualization, it is possible to easily find an activity at an organization level such as a department or a section, or an employee who is inconspicuous but has high contribution, that is, a human resource.

  Also, for example, by issuing and distributing tokens that express the degree of appreciation numerically globally, regardless of the framework of organizations such as companies, it is possible to connect people to each other and to develop human resources with specific skills. The existence can be visualized.

  However, Patent Literature 1 merely discloses how to pay and settle a local currency, which is a valuation value obtained by quantifying the degree of appreciation. Not even suggesting.

In addition, the applicant has noticed that it is preferable to provide an incentive for token exchange in order to activate token exchange in which the degree of appreciation or the like is quantified.
In addition, the applicant has realized that if a smart contract based on blockchain technology can be used to provide incentives for the above-described visualization and token exchange, a more robust system can be easily constructed.

The present invention has been made in view of the above.
One example of an embodiment of the present invention is a step in which a first computer performs a transaction based on a transaction for a first user to use a first token for a second user, the transaction being stored in a blockchain. Reducing the amount of stored first tokens associated with the first user without increasing the amount of stored first tokens associated with the second user; Increasing the amount of the second token associated with the second user and increasing the stored amount of the second token associated with the first user.

  In this method, the step of reducing the stored amount of the first token associated with the first user without increasing the stored amount of the first token associated with the second user is stored. Decreasing the amount of the first token associated with the first user being stored by a first predetermined amount, increasing the stored amount of the second token associated with the second user, and Increasing the stored amount of the second token associated with the first user comprises changing the stored amount of the second token associated with the first user to a first predetermined amount. Increasing by an amount multiplied by the ratio of The method also includes the step of the first computer performing the first user based on a transaction for the first user to use the first token with the second user, the method comprising a counter associated with the stored first user. Determining a first predetermined ratio based on the value of the first user, wherein the first predetermined ratio is determined not to increase when the value of the counter increases, and the stored first user And incrementing the value of a counter associated with.

  The method includes the step of the first computer performing a transaction based on a transaction for a first user to remit a second token to a second user, the transaction being stored in a blockchain. The method may further include reducing the amount of the second token associated with the first user and increasing the stored amount of the second token associated with the second user.

  The method includes the step of the second computer sending a transaction for performing a periodic process to the first computer as stored in a blockchain one or more times, and the first computer comprising: Updating a stored date and time associated with the first user based on a transaction for the user to use the first token for the second user; and a transaction for the first computer to perform a periodic process. Is a step performed for each user, based on the date and time associated with the transaction for performing the periodic processing, wherein the stored date and time associated with the user is earlier than the predetermined time length. Determining whether the first condition is satisfied; and storing the result if the first condition is satisfied. Decreasing the amount of the first token associated with the user that has been associated with the user, and otherwise increasing the amount of the first token associated with the user that has been stored. Can be.

  The method includes the steps of a first computer storing a date and time of expiration of a first token based on a transaction stored in a blockchain, and a step performed by the first computer based on a transaction for performing a periodic process. Determining the second condition that the date and time related to the transaction for performing the periodic processing is later than the stored date and time of the expiration date of the first token; and when the second condition is satisfied. Zeroing the amount of the first token associated with each user that is stored.

  In the method, a first computer stores information corresponding to the transaction as an event based on the transaction, and a second computer stores an event log as information stored as an event in the first computer. Obtaining the information.

  In this method, the step of obtaining the event log may include the step of the second computer obtaining an event log that satisfies a third condition among the event logs.

  In this method, the third condition is that the date and time relating to the event log is within a predetermined period, the event log includes a predetermined tag, and the event log includes a predetermined remittance source user. And that the event log includes a predetermined remittance destination user.

  In this way, the transaction can include a tag and a message ID. The method further includes the step of the second computer displaying at least a part of the information corresponding to the transaction based on the acquired event log, wherein at least a part of the information corresponding to the transaction is displayed. , A tag included in the transaction, and a message specified by a message ID included in the transaction.

  The method may include the step of the second computer generating an output for displaying the first graph based on the obtained event log. Here, the first graph includes two or more nodes and one or more directed edges, each node corresponding to a user, and the expression of each node representing the remittance of the second token to the corresponding user. Each directed edge extends from the node corresponding to the remittance source user of the second token to the node corresponding to the remittance destination user, and each directed edge is represented by the directed edge. The amount of remittance of the second token to the user includes the increase in the amount of the second token held by the user due to the use of the first token. The remittance source user of the second token may include a user who uses the first token, and the remittance destination user of the second token may include a user who uses the first token.

In this method, the node may be a pie chart representing a ratio of tokens for a corresponding user, and the representation of the node may be the size of the pie graph.
In this method, each user belongs to any one of a plurality of groups in each of the one or more layers, and each group includes one or more users, and based on the acquired event log, Generating an output for displaying a first graph includes, for one of the one or more layers, for each of a plurality of groups in the one or more layers, one or more belonging to the group. The entirety of one or more nodes respectively corresponding to the users is set as one node corresponding to the group, and the distance between the nodes corresponding to the plurality of groups in the one layer corresponds to the one layer. The method may include the step of adjusting the position of the node corresponding to each user so as to be responsive to the parameter.

The method may include the step of the second computer generating an output for displaying a second graph based on the obtained event log. Here, the second graph has a first axis and a second axis, includes a plurality of figures, each figure corresponds to a user, and the representation of each figure is In accordance with the total remittance amount of the two tokens, the position of each figure on the first axis and the second axis is the number of times the corresponding user has remitted the second token and the corresponding user, respectively. , The number of times the second token has been remitted,
The remittance amount of the second token to the user includes the increase amount of the second token held by the user due to the use of the first token, and the number of times the user has retransmitted the second token indicates that the user has used the first token. The number of times the second token has been remitted to the user may include the number of times the first token has been used by the user.

  In this method, a first computer is a transaction stored in a blockchain, wherein a first user sends a second user a plurality of types of tokens different in at least one of an issuer, a source, and a use. Storing, as an event, information related to the transaction based on the transaction for remittancing at least one of the transactions; and causing the second computer to display a third graph based on the acquired event log. Generating an output. Here, the third graph includes two or more nodes and one or more directed edges. Each node corresponds to a user, and each node includes a plurality of types of tokens remitted to the corresponding user. FIG. 4 is a pie chart representing a ratio of amounts, wherein each directed edge can extend from a node corresponding to at least one remittance source user of the plurality of tokens to a node corresponding to a remittance destination user.

Another example of the embodiment of the present invention is a system including one or both of the first computer and the second computer.
Yet another example of an embodiment of the present invention is one or more programs that cause one or both of the first computer and the second computer to execute the above steps. The one or more programs include one or more smart contracts that cause the first computer to perform the above steps, and one or more non-smart contract programs that cause the second computer to perform the above steps. be able to.

1 shows a schematic configuration of an exemplary system according to an embodiment of the present invention. It shows an example token use / remittance screen. 9 illustrates an example token history screen. 9 illustrates an exemplary second token remittance relationship visualization screen. 5 illustrates an example of a plurality of groups including one or more layers. 9 illustrates an exemplary graph in which nodes corresponding to users having similar affiliation code values are arranged closer to each other. Represents a component for adjusting the display of a graph. 5 shows a graph for explaining adjustment of an edge distance. 5 shows a graph for explaining adjustment of an edge distance. 13 illustrates an exemplary second token remittance count visualization screen. 9 illustrates an example token ranking screen. 13 illustrates an exemplary first token distribution process. 13 illustrates an exemplary first token expiration setting process. 7 illustrates an exemplary first token use process. 13 illustrates an exemplary second token remittance process. 9 illustrates an exemplary periodic process. 9 illustrates an exemplary first token expiration process. 9 illustrates an exemplary first token increase / decrease process. 9 illustrates an exemplary token history output generation process. 14 illustrates an exemplary generation process of a graph included in a second token remittance relation visualization screen. 9 illustrates an exemplary process for adjusting an edge distance. 14 illustrates an exemplary generation process of a graph included in the second token remittance count visualization screen. It shows an example token holding ratio visualization screen. FIG. 14 illustrates an example of a token amount visualization screen by token type. 15 illustrates an example process included in a token type holding amount visualization screen generation process. 1 illustrates an example of a hardware configuration of a computer.

1. One Embodiment of the Present Invention An example of an embodiment of the present invention is a system for exchanging tokens between users.
1-1 Schematic Configuration of System According to One Embodiment of the Present Invention FIG. 1 shows a schematic configuration of an exemplary system 100 according to one embodiment of the present invention.

 110A to 110C indicate terminals used by the user of the system 100. Although only three terminals are shown in FIG. 1, the number of terminals used by a user of the system 100 may be one or more. The user of the system 100 includes an administrator of the system 100. The terminals 110A to 110C are any type of computer such as a desktop computer, a laptop computer, a tablet, and a smartphone. Hereinafter, terminals 110A to 110C are collectively referred to as “terminal 110”.

  Reference numeral 120 denotes a terminal 110 and a gateway that communicates with a database 130 and a blockchain node group 140 (at least one of the blockchain nodes included in the blockchain node group 140) described below. ing. Although only one gateway 120 is shown in this figure, the number of gateways 120 may be any number greater than one. Gateway 120 is any type of computer.

  Reference numeral 130 denotes a database that communicates with the gateway 120. Although only one database 130 is shown in this figure, the number of databases 130 may be any number greater than one. Database 130 is any type of computer that has at least a database function. The database 130 can store any information required in the system 100.

  Reference numeral 140 denotes a blockchain node group that communicates with the gateway 120, and 140A to 140D denote respective blockchain nodes included in the blockchain node group 140. Although only four blockchain nodes included in the blockchain node group 140 are shown in FIG. 1, the number of blockchain nodes included in the blockchain node group 140 is an arbitrary number of one or more. Any number, preferably four or more. Blockchain nodes 140A-140D are any type of computer that has at least the ability to implement blockchain technology and smart contracts based on the technology.

  At least one of the terminal 110, the gateway 120, the database 130, and each of the blockchain nodes included in the blockchain node group 140 operates on one physical computer instead of one physical computer. Note that it can be one of one or more virtual computers. In addition, the function as one or both of the gateway 120 and the database 130 may be provided by one physical or virtual computer as one blockchain node included in the blockchain node group 140. Good.

  Also, between the terminal 110 and the gateway 120, between the gateway 120 and the database 130, between the gateway 120 and the blockchain node group 140, and between each blockchain node included in the blockchain node group 140. Note that there may be one or more networks (not shown), including the Internet.

1-2 Screen Displayed in System 100 The screen displayed in system 100 is assumed to be displayed on terminal 110, but may be displayed on another computer.

1-2-1 Token Use / Remittance Screen According to the system 100, the first token is distributed to each user, and by using the distributed first token to another user, the other user is provided with the first token. Will be distributed the second token. Furthermore, each user can also transfer the second token to another user. Hereinafter, in this section, “use” of the first token is also expressed as “remittance” of the first token for convenience.

FIG. 2 shows an example screen 200 for each user to transfer the first token or the second token.
Reference numeral 205 denotes a component for displaying a user who is currently using the terminal 110 (hereinafter, referred to as a “terminal user”). It is assumed that the terminal user has already logged in to the system 100 by a known method, and the system 100 can identify the terminal user. In this figure, "abcdefgh ...", which is the address of the terminal user, is displayed as a display for the terminal user. The address of the user specifies the user in the smart contract implemented in the blockchain node group 140. In addition, 205A of the components 205 indicates a component for displaying a QR code (registered trademark) encoding information for identifying the terminal user, and the QR code is displayed by tapping the component 205A or the like. It is supposed to be. The “information specifying the user” may be “user address”, but is not limited to this.

  Reference numeral 210 denotes a component for displaying the amount of token held by the terminal user. In this figure, "50,000" which is the amount of the first token, "0" which is the amount of the second token, and "50,000" which is the total thereof are displayed.

  215 is a component for designating a user to whom the token is to be remitted. 215A of the components 215 indicates a component for reading a QR code that encodes information for identifying a user. By tapping the component 215A, a screen (not shown) for reading the QR code is displayed. It is displayed. When the QR code is successfully read, the user specified by the information encoded in the QR code is specified as the remittance destination user. In this figure, the name of the designated user "Mr. B" and its address "stuvwxya ..." are displayed. It should be noted that the method of specifying the remittance destination user is arbitrary, and is not limited to the method using the QR code.

  Reference numeral 220 denotes a component for inputting arbitrary information associated with the transfer of the token. In the system 100, information associated with the transfer of the token is a tag and a message. The tag that can be input in the component 220 is one of a plurality of predetermined tags. 220A of the components 220 indicates a component for selecting a tag to be input, and a list of tags that can be input is displayed by tapping the component 220A, and the selected tag is input. . In addition, according to the input of the tag, a fixed phrase corresponding to the tag input as a message is automatically input to the component 220, but the component 220 outputs the automatically input message. It is configured so that the user can edit it. In this figure, the input tag “business support” and the input message “Thank you for your kindness.” Are displayed.

  225 is a component for designating the amount and type of the token to be remitted. 225A of the components 225 indicates a component for designating which of the first token and the second token is to be remitted. In this drawing, the token to be remitted is the first token, and "1,000" is displayed as the remittance amount.

  Reference numeral 230 denotes a component for remitting a specified amount of the specified token in association with the input information to the specified remittance destination user with the terminal user as the token remittance source user. By tapping the component 230 or the like, the remittance instruction is issued to the gateway 120.

1-2-2 Token History Screen According to the system 100, the use of the first token by another user to another user causes the second token to be distributed to the user who used the first token, and to each user. The distributed first token automatically increases or decreases according to whether or not a predetermined condition is satisfied.

  FIG. 3 shows an example screen 300 for checking the history of token use, remittance and distribution for a certain user. In screen 300, the history is represented in the form of a table, the first row of the table showing the label of each column, and the second to last rows are used for token use, remittance and distribution, respectively. Correspondingly, token use, remittance and distribution are chronologically arranged in descending order. Further, “[1st]” in the column of “amount” in the table indicates the first token, and “[2nd]” indicates the second token. Further, in this figure, ".." tilted by 90 degrees means omission. The screen 300 can be configured such that only a part of the table is displayed at a time, and another part of the table is displayed by scrolling or the like. Hereinafter, some rows will be described with reference to the numbers in the column of “#” in the table.

The row where the column of “#” is “100” corresponds to the fact that the first token has been distributed to each user as initialization processing in the system 100. According to this line, the amount of distribution to at least the terminal user (in this figure, "me" is displayed) is 50,000. According to this row, the distribution of the first token is determined according to the condition that the row of “#”, which is displayed as remittance of the first token from the administrator to the terminal user, is “101” in a predetermined condition. Does not satisfy, the amount of the first token held by the terminal user decreases. The predetermined condition for this row is that the terminal user used the first token the day before. According to this line, the decrease in the amount of the first token of the terminal user is displayed as remittance of the first token from the terminal user to the administrator.

  The row in which the column of “#” is “102” corresponds to the terminal use user using the first token for another user, Mr. B. The usage amount of the first token for this row is 1,000, the tag is “business support”, and the message is “Thank you for your kindness.” According to this line, the use of the first token of the terminal user is displayed as remittance of the first token from the terminal user to another user.

  The row where the column of “#” is “103” corresponds to the fact that the second token has been distributed to the terminal user by the use of the first token by the terminal user. The distribution amount of the second token for this row is 500, which is 50% of the usage amount of the first token. According to this line, distribution of the second token by use of the first token is displayed as remittance of the second token from the manager to the terminal user.

  The row in which the column of “#” is “104” indicates the amount of the first token held by the terminal user because the predetermined condition, that is, the condition that the terminal user used the first token the day before, is satisfied. Corresponds to the increase. According to this line, the increase in the amount of the first token of the terminal user is displayed as remittance of the first token from the administrator to the terminal user.

  The row where the column of “#” is “105” corresponds to another user using the first token or remitting the second token to the terminal user. According to this line, the use of the first token and the remittance of the second token are displayed as remittance of the second token from another user to the terminal user without distinguishing the two, but the former and the latter are used. The system 100 may be configured to be able to distinguish and display.

  The row in which the column of “#” is “321” corresponds to a decrease in the amount of the first token held by the terminal user because the predetermined condition is satisfied. The condition for this row is that the first token has expired. Due to this decrease, the amount of the first token held by the terminal use user may be zero, but may be a predetermined non-zero amount or an amount according to the amount of the first token held immediately before the decrease. You may.

1-2-3 Second Token Remittance Relationship Visualization Screen FIG. 4A shows an example screen 400 for confirming how the second token remittance is performed between users of the system 100. Note that the remittance of the second token is based on the use of the first token, for example, the remittance corresponding to “103” in the “#” column on the screen 300 and the use of the first token. For example, the column “#” on the screen 300 may be only one or both of the remittances corresponding to “105”, may include one or both, or may not include one or both. . The screen 400 includes a graph composed of nodes and directed edges.

  In the graph included in the screen 400, the nodes to which "A" to "Z" are respectively assigned correspond to the users A to Z, and the expression of the nodes is the remittance of the second token to the corresponding user. Is based on the total amount of In this figure, “node” is a circle, and “node expression” is the size of the circle (that is, the larger the total amount of remittance of the second token, the larger the circle), but is not limited thereto. Not necessarily. As the “expression of a node”, the shape, color, display density, and the like of the node can be considered. It is preferable that the node corresponding to the administrator is excluded from the graph included in the screen 400. Further, the screen 400 may be configured so that the screen 200 in which the node is the remittee user can be displayed by tapping the node or the like.

  Also, the node may be a pie chart, which may represent the ratio of tokens for the corresponding user. This ratio is the ratio between the amount of the first token held and the amount of the second token held, the amount of the remittance of the second token by using the first token, and the second by the use of the first token. Including, but not limited to, the amount of tokens remitted. Note that the “node representation” that is a pie graph is represented by color coding in the pie graph (for example, a portion corresponding to the amount of possession of the first token is the first color, and a portion corresponding to the amount of possession of the second token is the second color). Color).

  In the graph included in screen 400, the directed edge extends from the node corresponding to the remittance source user of the second token to the node corresponding to the remittance destination user. The number attached to the directed edge indicates the total amount of remittance corresponding thereto, and the expression of the directed edge is in accordance with the total amount. Note that the expression of a directed edge in this figure is the thickness of the directed edge (that is, the larger the total amount of the corresponding remittance, the thicker the directed edge), but is not limited to this. . As the “expression of a directed edge”, the shape of the tip of the directed edge, the display density, and the like can be considered.

  Incidentally, each user of the system 100 may belong to any one of a plurality of groups in each of one or more layers. FIG. 4B is a diagram illustrating an example of one or more such layers. In this example, the top hierarchy is “department” and the bottom hierarchy is “team”. In such a case, each user can be assigned an affiliation code in which the value corresponding to the group in each hierarchy is the value of each digit. For example, in this figure, "group A" which is the group in the highest hierarchy has a value of 1 as the third digit which is the highest digit, "A2 section" has a value of 2 as the second digit, Since “2” is assigned to the team “A2b”, which is the group in the lowest hierarchy, as the value of the first digit which is the lowest digit, “122” is assigned to the user belonging to team “A2b” as the belonging code. Will be assigned. In FIG. 4B, “123” is intended to be, for example, a section manager of section A2, and “131” is intended to belong to, for example, a section code assigned to a section manager.

  Here, in the graph included in the screen 400, it is preferable that nodes corresponding to users whose assigned code values are close in this way are arranged closer to each other. FIG. 4C shows a graph in which the nodes are arranged in such a manner, in which a solid circle indicates a node and a dotted circle indicates a group in each hierarchy. It should be noted that the dotted circle is drawn for explanation, and does not need to be actually displayed on the screen 400. In this figure, edges are omitted.

  Each user of the system may be assigned an attribute, for example, a position or role. In the graph included in the screen 400, the expression of the node may be determined according to the attribute of each user. Note that the expression of the node according to the total amount of remittance of the second token to the corresponding user is different from the expression of the node determined according to the attribute of the corresponding user (for example, the former is the size of the node, The latter may be in the form of a node.).

  According to the screen 400, it is possible to visually grasp from the nodes and edges the connection between users (relationship and existence of a central person) and the presence or absence of connection of a certain user to outside the group.

  Also, the use of the first token in the system 100 can be associated with a tag and a message, thus having communication implications. Therefore, according to the screen 400, the activity of communication between users can be visually grasped from the nodes and the edges.

  According to the screen 400, a user who belongs to a certain group and exchanges little with the outside of the group can be visually grasped from the nodes and the edges even if the user is outside the certain group.

Further, according to the screen 400, the organizational structure and communication can be linked by changing the shape and color of the node according to the attribute of the user.
Screen 400 may include a portion 410 as depicted in FIG. 4D. The part 410 is for adjusting the display of the graph included in the screen 400. Note that the portion 410 can be displayed on a screen different from the screen 400.

  Reference numeral 412 denotes a component for visualizing, on the screen 400, only the remittance of the second token among the users of the system 100 within the selected period. Component 412 can be configured such that by selecting one date and then another, a period is selected with the former as the start date and the latter as the end date. In this figure, the period from October 2 to 8, 2017 is selected.

  Reference numeral 414 denotes a component for visualizing only the remittance associated with the selected tag among the remittances of the second token between the users of the system 100 on the screen 400. The component 414 can be configured to select one tag from a plurality of predetermined tags. In this figure, "work out" is selected as the tag.

  Note that the period and the tag are merely examples of conditions for extracting the remittance of the second token visualized on the screen 400. That is, portion 410 can include any component for selecting, specifying, or entering any conditions for extracting remittance of the second token to be visualized on screen 400. Portion 410 may also be configured such that terminal 110 transmits at least to gateway 120 the conditions selected, specified, or entered via components 412 and 414 and equivalents.

  Reference numeral 416 is a component for adjusting a display distance (edge distance) between nodes in a graph included in the screen 400. Component 416 can be configured to increase (or decrease) the edge distance by moving knob 416A to the right (or to the left). Portion 410 may also be configured such that terminal 110 transmits a value corresponding to the position of knob 416A of component 416 to at least gateway 120.

  One or more components 416 may be provided, each of which may be for adjusting an edge distance for each of the one or more layers described in connection with FIGS. 4B and 4C. Note that the component 416 may be provided only for a part of one or more layers.

  More specifically, when the graph shown in FIG. 4E (the edges are omitted) is set to an initial state, for example, only the component 416 corresponding to the “team” hierarchy is adjusted to increase the edge distance. Then, the graph can be as shown in FIG. 4F. According to FIGS. 4E and 4F, although the display distance between nodes that do not belong to the same “team” (including independent) is large, the display distance between nodes belonging to the same “team” is It can be seen that it has not changed.

  That is, each component of the one or more components 416 can change the distance between nodes corresponding to users belonging to different groups in the corresponding hierarchy. Here, the edge distance is preferably adjusted so that the distance between nodes corresponding to users belonging to the same group in the corresponding hierarchy does not change or the change is minimized by the operation of each component. .

  According to the part 410, even when there are a large number of nodes, it is possible to display only some of the nodes and to increase the display interval between the nodes, so that the users of the system 100 can be displayed. It is possible to more easily visualize how the second token is being remitted.

Further, according to the portion 110, only the remittance that satisfies the predetermined condition can be visualized, so that it is easy to grasp a user having a specific relationship.
1-2-4 Second Token Remittance Count Visualization Screen FIG. 5 shows the number of times the second token has been remitted (hereinafter referred to as “number of remittances”) and the number of times the second token has been remitted for the user of system 100. (Hereinafter, referred to as the “number of remittances”) and an example screen 500 for confirming the total amount of the retransmitted second tokens. In addition, the remittance of the second token may be one or both of the use of the first token and the use of the first token, or may include the one or both, or One or both may not be included. The screen 500 includes a graph in which the number of remittances is the first axis and the number of remittances is the second axis.

  In the graph included in the screen 500, the figures to which "A" to "Z" are respectively assigned correspond to the users A to Z, respectively, and the representation of the figures is the remittance of the second token to the corresponding user. It is based on the total amount. In this figure, the "graphic" is a circle, and the "expression of the graphic" is the size of the circle (that is, the larger the total amount of remittance of the second token, the larger the circle), but is not limited thereto. Not necessarily. As the “expression of figure”, the color and shape of the figure, display density, and the like can be considered. Further, it is preferable that the graphic corresponding to the manager is excluded from the graph included in the screen 500. Further, the screen 500 may be configured so that the screen 200 in which the figure is set as the remittee user by tapping the figure can be displayed. Furthermore, in the graph included in the screen 500, the representation of the graphic can be made according to the attribute of each user. Note that the representation of the graphic according to the total amount of remittance of the second token to the corresponding user is different from the representation of the node determined according to the attribute of the corresponding user (for example, the former is the size of the graphic, The latter may be in the form of a figure.). In the graph included in the screen 500, the position of the graphic corresponding to each user, more specifically, the position of a specific part (for example, the center or the center of gravity) of the graphic on the first axis and the second axis is determined by the user Is determined by the number of remittances and the number of remittances.

  As described above, in the system 100, when a certain user uses the first token for another user, the second token is distributed not only to another user but also to the certain user. Therefore, the amount of the second token held by a certain user is not limited to the use of the first token and the remittance of the second token to the certain user.

  According to screen 500, the number of remittances, that is, one or both of the number of times a certain user used the first token and the number of times the second token was remitted to another user, and the number of remittances, The ratio of the number of times the user has used the first token and the number of times the second token has been remitted to the user is visualized. Therefore, when one or both of the use of the first token and the transmission of the second token for a certain user are considered to be a result of a positive evaluation for the certain user, according to the screen 500, the relative evaluation is made. The user with a high score can be easily specified. For example, the user A who is above the dotted line 510 showing a plot of a point where the number of remittances matches the number of remittances and corresponds to the graphic represented by the largest circle, the number of remittances is larger than the number of remittances, In addition, since the total amount of the retransmitted second tokens is also large, it means that among the users A to Z, the user is highly evaluated by others.

1-2-5 Token Ranking Screen FIG. 6 shows an example screen 600 for displaying the ranking of the second token for the user of the system 100. The screen 600 includes a ranking of the total amount of the remitted second token for each period and for each affiliation of the user. Note that the token ranking screen may include the ranking of the number of times the second token has been remitted or the number of times the second token has been remitted, instead of the total amount of the second token remitted. Also, the remittance of the second token may be solely due to the use of the first token, or may or may not include.

1-3 Processing Executed in System 100 The processing executed in the system 100 includes a general program including a terminal 110, a gateway 120, a database 130, and a blockchain node included in the blockchain node group 140. At least one of the processes includes a process to be executed by at least one of them, and a process to be executed by each blockchain node included in the blockchain node group 140 by a smart contract which is a kind of a program.

1-3-1 Basic mechanism related to smart contract The basic mechanism related to smart contract based on blockchain technology will be described below. In the following description, a technology based on Ethereum is assumed as a blockchain technology executed by the blockchain node, and matters not described may be the same as those in Ethereum. However, it should be noted that the blockchain technology implemented by the blockchain node is not limited to this.

  Blockchain nodes store so-called blockchains. The block chain is composed of a plurality of blocks, and each block has only one parent block except for the first block (for example, the Genesis block).

  Each block can include a smart contract. The smart contract can define at least a process to be executed by the blockchain node and information (for example, a state or an event) to be stored by the blockchain node. Also, a smart contract can include one or more portions (eg, functions) that each define an operation to be performed. The process to be executed can include a process of updating the content of the information to be stored and a process of returning the content of the information to be stored in response to the request.

  Each block is based on information (for example, a hash value of the parent block) that is uniquely determined according to what the parent block includes, and the content of the information to be stored by the blockchain node when the block is generated. (For example, a state route or a receipt route), which is included in any block from a certain block to the first block, and the time when any of the blocks is generated Falsification of the information to be stored causes inconsistency.

  Upon receiving a transaction, the blockchain node verifies the validity of the transaction. The transaction may include a transaction for generating a smart contract (including the smart contract itself) and a transaction for executing a process defined in a part of the smart contract (parameters related to the process). ). Upon successful validation of the transaction, the blockchain node forwards the transaction, ie, the valid transaction, to at least one other blockchain node. Note that the blockchain node may generate a valid transaction by itself and transfer the transaction to at least one other blockchain node. Also, the processing defined in the smart contract part may be executed without a transaction (for example, via a call method).

  The blockchain node attempts to generate a block containing a valid transaction. In this trial, if the transaction is for generating a smart contract, an address of the smart contract (for example, an address of a Contract Acccount (CA)) is generated and associated with the smart contract. Also, in this trial, if the transaction is for executing a process defined in the smart contract part, the blockchain node executes the process. Upon successful creation of the block, the blockchain node adds the block to its stored blockchain and forwards it to at least one other blockchain node. In addition, when the block generation succeeds, the blockchain node stores the updated content of the information when executing the process of updating the content of the information to be stored in the attempt to generate the block. The block is generated using a method that succeeds when solving a problem that is computationally difficult (for example, a proof of work or a proof of stake).

  Upon receiving the block, the blockchain node verifies the validity of the block. In this verification, if the block includes a transaction for performing a process defined in the smart contract part, the blockchain node executes the process. Upon successful validation of the block, the blockchain node adds the block to its stored blockchain and forwards it to at least one other blockchain node. In addition, if the validation of the block is successful, the blockchain node stores the updated information when executing the process of updating the content of the information to be stored in the validation of the block. .

  With the above-described mechanism, in each block chain node included in the block chain node group 140, the process defined in the smart contract is executed, and the content of the information is stored.

1-3-2 Initialization Processing The initialization processing is the first processing in the system 100.
The initialization process may include a first token distribution process for distributing the first token to each user. FIG. 7A illustrates an exemplary first token distribution process 700.

Reference numeral 705 denotes a step in which the gateway 120 generates one or more transactions for executing the part of the smart contract corresponding to the first token distribution process. Each of the one or more transactions is:
An address of a specific user (for example, an administrator) as a source address;
The address of the smart contract as the destination address,
Information identifying the portion (eg, the first four bytes of the hash value of the function);
Information identifying each user (hereinafter referred to as “distributed user”) (for example, the address of the distributed user);
The predetermined distribution amount of the token,
Predetermined tags (eg, "distribution"),
The information may include, but is not limited to, information that specifies a predetermined message (hereinafter, referred to as “message ID”). This step can also include the gateway 120 obtaining at least a portion of the information to be included in the transaction from the database 130.

  As for the message ID, as described above, the transaction is stored in the block chain and cannot be deleted. Therefore, when the message itself is included in the transaction, the message is also stored and deleted. Can not do. As described above, the message is editable by the user and may include information that should not be stored. Therefore, it is preferable that the transaction includes the message ID instead of the message itself. Note that the message itself can be stored in the database 130.

  710 shows a step in which the gateway 120 transmits the generated one or more transactions to at least one blockchain node included in the blockchain node group 140.

  Step 715 is a step executed by each blockchain node executing the part of the smart contract corresponding to the first token distribution process by the above-described mechanism based on the transaction transmitted in Step 710. Is shown. This step is performed for each of one or more transactions.

720 shows the step of storing the distribution of the first token. In the system 100, this distribution will be stored as a remittance of the first token of the distribution amount from the specific user to the distributed user, and this step involves the blockchain node
Information indicating the remittance of the first token (for example, a predetermined character string);
Information identifying a specific user as a remittance source user,
Information identifying the recipient user as the remittee user;
Remittance amount specified distribution amount,
Predetermined tags,
This may be a step of storing the predetermined message ID as an event. What the blockchain node stores as events is not limited to these. What is stored as an event is hereinafter referred to as an “event log”.

725 indicates a step of realizing the distribution of the first token.
Step 725 includes the blockchain node increasing the stored first token amount associated with the distributed user by the distribution amount.

  Step 725 may also include the blockchain node reducing the stored amount of the first token associated with the particular user by the amount of distribution.

  Note that the stored amounts of the first token and the second token associated with each user may be zero immediately before the execution of the process. Further, the amount of the first token and the amount of the second token associated with each user may not be stored immediately before the execution of the process, in which case, the amount increased from zero is associated with the user. May be stored. Further, in the system 100, the stored token amount associated with each user is treated as the token amount held by each user. Furthermore, the amount of the first token and the amount of the second token can be associated with each user's address.

Steps 720 and 725 may be performed in any order.
The initialization processing may include a first token expiration setting processing for setting an expiration of the first token. FIG. 7B illustrates an exemplary first token expiration setting process 750.

Reference numeral 755 denotes a step in which the gateway 120 generates a transaction for causing the part of the smart contract corresponding to the first token expiration setting process to be executed. This transaction is
The address of the specific user as the source address,
The address of the smart contract as the destination address,
Information identifying the part,
It may include, but is not limited to, a set first token expiration date. This step can also include the gateway 120 obtaining at least a portion of the information to be included in the transaction from the database 130.

  760 indicates a step in which the gateway 120 transmits the generated transaction to at least one blockchain node included in the blockchain node group 140.

  765 is performed by each blockchain node executing the part of the smart contract corresponding to the first token expiration process according to the mechanism described above, based on the transaction transmitted in step 760. Steps are shown.

770 shows the step in which the blockchain node stores the expiration date of the first token.
1-3-3 First Token Use Process The first token use process is a process for a certain user to use a first token for another user. FIG. 8 illustrates an exemplary first token use process 800.

  Reference numeral 805 denotes a step in which the terminal 110 displays the token use / transmission screen 200. This step may include a step in which the terminal 110 obtains information necessary for display from the database 130 and at least one blockchain node included in the blockchain node group 140 via the gateway 120.

  Reference numeral 810 denotes a step in which the terminal 110 issues an instruction to the gateway 120 based on the content specified and input on the screen 200. Here, it is assumed that the use of the first token is specified. In this step, it is determined whether or not the designated amount of remittance tokens is equal to or less than a predetermined amount, and an instruction is issued to the gateway 120 only when the designated amount of remittance tokens is equal to or less than the predetermined amount. Steps may be included.

Reference numeral 815 denotes a step in which the gateway 120 generates a transaction for executing the part of the smart contract corresponding to the first token use process based on the received instruction. This transaction is
The user's address as the sender address,
The address of the smart contract as the destination address,
Information identifying the part,
Information identifying the user;
The specified usage,
The entered tag,
The message ID may include, but is not limited to, a message ID identifying the input message. This step may also include the step of the API gateway 120 or the database 130 generating a message ID and storing the generated message ID in the database 130 in association with the message.

  820 indicates a step in which the gateway 120 transmits the generated transaction to at least one blockchain node included in the blockchain node group 140.

  825 is a step performed by each blockchain node executing the portion of the smart contract corresponding to the first token use process by the mechanism described above based on the transaction transmitted in step 820. Is shown.

830 shows a first step of storing the use of the first token. In the system 100, this use will be stored at least as a remittance of a first token of usage from the using user to the used user, the first step being that the blockchain node
Information indicating the remittance of the first token,
Information identifying the user as the sender of the remittance,
Information identifying the user to be used as a remittance user,
The usage amount specified as the remittance amount,
The entered tag,
This may be a step of storing the generated message ID as an event. What the blockchain node stores as events is not limited to these.

835 shows a first step for realizing the use of the first token.
This first step involves the blockchain node reducing the stored amount of the first token associated with the using user by the amount used.

  The first step can also include the blockchain node increasing the stored amount of the first token associated with the particular user by the usage amount.

  Further, the first step may include the step of the blockchain node incrementing the stored value of the first counter associated with the user by a predetermined value, for example, one. Note that the stored value of the first counter associated with each user may be zero immediately before the execution of the initialization processing. Further, the value of the first counter associated with each user may not be stored immediately before the execution of the initialization process. In this case, the value of the first counter associated with the user is incremented from zero. The determined value may be stored in this first step. Further, the value of the first counter associated with each user may be stored for each remittance destination user. Furthermore, the stored value of the first counter associated with each user can be initialized in a periodic process described later.

  Furthermore, the first step may include the step of the blockchain node storing the date and time related to the transaction as the date and time when the user last used the first token in association with the user. The “date and time related to the transaction” is, for example, the date and time when the transaction is generated or the date and time when a block including the transaction is generated, but is not limited thereto. It is preferable that the “date and time relating to the transaction” is determined so that each block chain node included in the block chain node group 140 can uniquely identify the same one.

840 shows a second step of storing the use of the first token. In the system 100, this use will be stored at least as a remittance of a first predetermined amount of a second token from the using user to the used user, the second step being that the blockchain node
Information indicating the remittance of the second token,
Information identifying the user as the sender of the remittance,
Information identifying the user to be used as a remittance user,
A first predetermined amount as a remittance amount;
The entered tag,
This may be a step of storing the generated message ID as an event. What the blockchain node stores as events is not limited to these. Further, the “first predetermined amount” may be an amount obtained by multiplying the specified usage amount by a predetermined ratio (for example, 0.5).

845 shows a second step for realizing the use of the first token.
This second step involves the blockchain node increasing the stored amount of the second token associated with the used user by a first predetermined amount.

  The second step can also include the blockchain node reducing the stored amount of the second token associated with the particular user by a first predetermined amount.

850 shows a third step of storing the use of the first token. In the system 100, this use will be stored at least as a remittance of a second predetermined amount of the second token from the specific user to the use user, and the third step is that the blockchain node
Information indicating the remittance of the second token,
Information identifying a specific user as a remittance source user,
Information identifying the user as the remittance user,
A second predetermined amount as the remittance amount;
Predefined tags (eg, "cashback")
This may be a step of storing the predetermined message ID as an event. What the blockchain node stores as events is not limited to these.

  The second predetermined amount may be an amount obtained by multiplying the specified usage amount by a fixed predetermined ratio (for example, 0.5), but depending on the usage situation of the first token by the user. The amount may be determined by, for example, the amount determined by the following equation.

y = x * a (c ≦ c _thre )
x * a * (1-b) ＾ ( _ccthre ) (c> _cthre ) (1)
here,
y is a second predetermined amount,
x is the specified usage,
a is a predetermined real number satisfying 0 ≦ a ≦ 1 (for example, 0.5);
b is a predetermined real number satisfying 0 ≦ b ≦ 1 (for example, 0.1);
c is the value of the stored first counter associated with the user,
c _thre is a predetermined integer (for example, 5)
It is. If the value of the first counter is not stored, c may be zero. The above expression is an example of a function in which y does not increase when c increases, that is, an example of a broadly monotonic decreasing function. Further, the second predetermined amount may be zero when the user has used the first token a predetermined number of times within a predetermined period.

Reference numeral 855 denotes a third step for realizing the use of the first token.
This third step involves the blockchain node increasing the stored amount of the second token associated with the using user by a second predetermined amount.

  The second step may also include the blockchain node reducing the stored amount of the second token associated with the particular user by a second predetermined amount.

  Note that step 825 may include the step of the blockchain node calculating one or both of the first predetermined amount and the second predetermined amount. Steps 830 to 855 may be performed in any order.

  According to the first token use process 800, the use of the first token for a certain user is not the increase of the first token held by the certain user but the increase of the second token. Therefore, when the use of the first token for a certain user is considered to be the result of a positive evaluation for the certain user, the amount of the first token held by the certain user does not become an evaluation scale for the certain user. . That is, according to the first token use processing 800, it is possible to prevent a user who is conscious of the evaluation from others from choosing not to use the first token in order to maintain the amount of the first token held. Can be.

  Further, according to the first token use processing 800, the use of the first token by a certain user also increases the second token for the certain user. Therefore, when the increase of the second token to the user who uses the first token is considered to be due to the positive evaluation of the user in the sense that the communication through the system 100 has been performed, the first token use processing 800 This would give each user of the system 100 an incentive to use the first token.

  According to the first token use processing 800, the user can specify the amount of use of the first token by himself, and thus can quantitatively express the degree of evaluation of others.

  According to the first token use processing 800, by setting an upper limit on the amount of the first token that can be used at one time, use of the first token only for obtaining the second token can be suppressed.

  According to the first token use processing 800, the increase amount of the second token for the user can be made to correspond to the use situation of the first token by the user. In the case of use, particularly when the same user is used more than a predetermined number of times a day, the amount of the second token held by the used user is prevented from increasing, so that a certain user can be used. Of evaluations (contracts) can be suppressed.

  Further, according to the first token use processing 800, since the user can input a tag or a message, the user can communicate with others in the use.

  Further, according to the first token use processing 800, the input tag and the message ID for specifying the input message are stored as an event log, and the event log has a date and time as described later. For this reason, for example, by providing “attendance / departure” as a tag, the system 100 can be made to function as at least a part of the attendance system (described later in relation to the token history output generation processing).

1-3-4 Second Token Remittance Process The second token remittance process is a process for a certain user to remit the second token to another user. FIG. 9 illustrates an exemplary second token remittance process 900.

Reference numeral 905 denotes the same step as step 805.
910 indicates the same step as step 810. However, it is assumed that remittance of the second token has been designated.

  Reference numeral 915 denotes a step similar to the step 815. However, the transaction can include the address of the remittance source user, information specifying the remittance destination user, and the specified remittance amount as the source address.

920 indicates the same step as step 820.
Step 925 is a step performed by each blockchain node executing the portion of the smart contract corresponding to the first token use process by the mechanism described above based on the transaction transmitted in Step 920. Is shown.

930 shows the step of storing the remittance of the second token. In this step, the blockchain node
Information indicating the remittance of the second token,
Information identifying the sender of the remittance,
Information identifying the remittee user,
The remittance amount specified,
The entered tag,
This may be a step of storing the generated message ID as an event. What the blockchain node stores as events is not limited to these.

935 shows the blockchain node reducing the amount of the second token associated with the remittance source user by the remittance amount.
940 shows the blockchain node increasing the amount of the second token associated with the remittance destination user by the remittance amount.

Steps 930 to 940 may be performed in any order.
According to the second token remittance process 900, only the amount of the second token held by the user who remits the second token is reduced. Therefore, according to the second token remittance process 900, each user of the system 100 can express an evaluation of another person excluding the profit and loss account.

1-3-5 Periodic Processing Periodic processing is processing that is periodically executed, and is processing for increasing or decreasing the amount of the first token held by each user depending on whether a predetermined condition is satisfied. It is. FIG. 10 illustrates an exemplary periodic process 1000. Note that the periodic processing 1000 can be started after the initialization processing ends. For example, the periodic process 1000 may be started after a predetermined period (for example, 24 hours) has elapsed after the end of the initialization process, or may be started immediately after the end of the initialization process.

Reference numeral 1005 denotes a step in which the gateway 120 generates a transaction for executing a part of the smart contract corresponding to the periodic processing. This transaction is
The address of the specific user as the source address,
The address of the smart contract as the destination address,
The information may include, but is not limited to, information specifying the part.

  Reference numeral 1010 denotes a step in which the gateway 120 transmits the generated transaction to at least one block chain node included in the block chain node group 140.

  Reference numeral 1015 denotes a step in which the gateway 120 determines whether the first predetermined condition is satisfied. The first predetermined condition can be a condition that the current date and time has passed the expiration date of the first token. The first predetermined condition may be a condition that a predetermined period (for example, 24 hours) has elapsed after the expiration date of the first token with reference to the current date and time. If the condition is satisfied, the periodic processing 1000 ends, and if not, the process returns to step 1005. When returning to step 1005, the gateway 120 can execute step 1005 after a predetermined period (for example, 24 hours) has elapsed by using, for example, a timer function of an OS operating in the gateway 120.

Therefore, steps 1005 to 1015 are repeated one or more times.
1020 shows the steps performed by each blockchain node executing the part of the smart contract corresponding to the periodic processing by the above-described mechanism based on the transaction transmitted in step 1010. I have.

1025 indicates a step of determining whether the blockchain node satisfies a second predetermined condition. The second predetermined condition may be a condition that the date and time of the transaction has passed the expiration date of the first token, and this step includes obtaining the stored expiration date of the first token. be able to. If the condition is satisfied, the process proceeds to step 1030; otherwise, the process proceeds to step 1035. The block chain node 1010 performs a first token expiration process. This step will be described later.

  1035 indicates a step of determining whether the blockchain node satisfies a third predetermined condition. The third predetermined condition may be a condition that the date and time relating to the transaction has passed the date and time at which the first token should be increased or decreased, and this step includes the step of changing the date and time at which the stored first token should be increased or decreased. The step of obtaining The blockchain node can store the date and time when the first token should be increased or decreased in the above-described initialization processing. If the condition is satisfied, the process proceeds to step 1040; otherwise, the execution of the smart contract part ends.

Reference numeral 1040 denotes a step in which the blockchain node performs a first token increase / decrease process. This step will be described later.
1045 indicates a step of updating the third predetermined condition. This step may include updating the date and time at which the stored first token should be increased or decreased (eg, updating the date and time after 24 hours).

  Step 1045 may include the step of the blockchain node initializing the stored value of the first counter associated with each user to a predetermined value, for example, zero.

FIG. 11 illustrates an exemplary first token expiration process 1100.
1105 shows a step in which the blockchain node selects a certain user. Since step 1105 can be repeated as described later, this step may be more specifically a step of selecting a certain user among users who have not been selected yet.

1110 illustrates the blockchain node obtaining the stored amount of the first token associated with the selected user.
Reference numeral 1115 denotes a first step of storing execution of the first token expiration process for the selected user. In the system 100, this execution will be stored as a remittance of the acquired amount of the first token from the selected user to the particular user, and this step is performed by the blockchain node
Information indicating the remittance of the first token,
Information identifying the user selected as the remittance source user;
Information specifying a specific user as a remittance destination user;
The amount obtained as the remittance amount,
A given tag (eg, "expired")
This may be a step of storing the predetermined message ID as an event. What the blockchain node stores as events is not limited to these.

  1120 illustrates the blockchain node reducing the stored first token amount associated with the selected user by the acquired first token amount. That is, by this step, the amount of the first token held by the user becomes zero.

Step 1120 may include the step of the blockchain node increasing the stored first token amount associated with the specific user by the acquired first token amount. FIG. 7 illustrates a step in which the chain node determines whether there is a user who has not yet been selected. If there is a user who has not yet been selected, the process returns to step 1105; otherwise, the first token expiration process 1100 ends.

Steps 1115 and 1120 can be executed in any order.
According to the first token expiration process 1100, when the first token expires, the amount of the first token held by each user of the system 100 becomes zero, and the first token held by using the first token becomes zero. You will not be able to increase the amount of two tokens. Therefore, if the increase of the second token to the user who uses the first token is considered to be due to the positive evaluation of the user in the sense that the communication via the system 100 has been performed, the first token expiration processing 1100 is performed. This would give each user of the system 100 an incentive to use the first token.

FIG. 12 illustrates an example first token increase / decrease process 1200.
1205 shows a step in which the blockchain node selects a certain user. Since step 1205 can be repeated as described later, this step may be a step of selecting a certain user among users who have not yet been selected.

  1210 illustrates a step in which the blockchain node determines whether a fourth predetermined condition is satisfied for the selected user. The fourth predetermined condition may be a condition that the selected user has used the first token within a predetermined period in the past (for example, 24 hours) based on the date and time of the transaction. The step may include obtaining a date and time when the stored selected user last used the first token. If the condition is satisfied, the process proceeds to step 1215; otherwise, the process proceeds to step 1230.

Numeral 1215 indicates a step of storing that the bonus is applied to the selected user. In the system 100, the application will be stored as a remittance of a predetermined amount of the first token from the particular user to the selected user, and this step involves the blockchain node
Information indicating the remittance of the first token,
Information identifying a specific user as a remittance source user,
Information identifying the user selected as the remittee user,
A third predetermined amount as a remittance amount;
Predefined tags (eg, "bonus")
This may be a step of storing the predetermined message ID as an event. What the blockchain node stores as events is not limited to these. In addition, the “third predetermined amount” may be a fixed predetermined amount, or may be an amount determined according to the use situation of the first token by the selected user. The amount can be determined by:

y = x + a * c (2)
here,
y is a third predetermined amount,
x is a fixed predetermined amount,
a is a predetermined value,
c is a stored second counter value associated with the selected user, which will be described later. If the value of the second counter is not stored, c may be zero.

  Reference numeral 1220 denotes a step of incrementing the stored value of the second counter associated with the selected user by a predetermined value, for example, one. The stored value of the second counter may be zero immediately before the execution of the initialization processing. In addition, the value of the second counter may not be stored immediately before the execution of the initialization processing. In that case, the value incremented from zero in step 1220 may be stored.

  Reference numeral 1225 denotes a step of realizing the application of the bonus to the selected user. Step 1225 includes the blockchain node increasing the stored amount of the first token associated with the selected user by a third predetermined amount. Also, step 1225 can include the blockchain node reducing the stored amount of the first token associated with the particular user by a third predetermined amount.

1230 shows the step of storing applying the natural depreciation to the selected user. In the system 100, the application will be stored as a remittance of a predetermined amount of the first token from the selected user to the specific user, and the step is that the blockchain node
Information indicating the remittance of the first token,
Information identifying the user selected as the remittance source user;
Information specifying a specific user as a remittance destination user;
A fourth predetermined amount as a remittance amount;
Predefined tags (eg, "natural depreciation")
This may be a step of storing the predetermined message ID as an event. What the blockchain node stores as events is not limited to these. Further, the fourth predetermined amount may be a fixed predetermined amount.

  Reference numeral 1235 denotes a step of initializing the stored value of the second counter associated with the selected user to a predetermined value, for example, zero. If the value of the second counter is not stored, a predetermined value may be stored as the value of the second counter.

  Reference numeral 1240 denotes a step of realizing the application of the natural depreciation to the selected user. Step 1240 includes the blockchain node reducing the stored amount of the first token associated with the selected user by a fourth predetermined amount. Also, step 1240 can include the blockchain node increasing the stored amount of the first token associated with the particular user by a fourth predetermined amount.

  1245 shows a step in which the blockchain node determines whether there is a user who has not yet selected. If there is a user who has not yet been selected, the process returns to step 1205; otherwise, the first token increase / decrease process 1200 ends.

  According to the first token increase / decrease process 1200, if the first token is used, the amount of the first token held increases, and if the first token is not used, the amount of the first token held decreases. Depending on usage, the amount of the first token that can be used to increase the second token increases or decreases. Therefore, when it is considered that the increase of the second token to the user who uses the first token is based on the positive evaluation of the user who has used the communication through the system 100, the first token increase / decrease processing 1200 is performed. For example, each user of the system 100 may be provided with an incentive to use the first token.

  Further, according to the first token increase / decrease process 1200, the amount of increase of the first token for each user can be made to correspond to the situation of use of the first token by each user. By increasing the increment of the first token for the user who has used it, an incentive to use the first token can be further given to the user of the system 100.

1-3-6 Token History Output Generation Process The token history output generation process is a process for generating an output or the like for displaying the token history screen 300 for the terminal user. Here, the output may be, for example, an HTML file, json format, or CSV format data, but is not limited thereto. FIG. 13 illustrates an exemplary token history output generation process 1300.

Reference numeral 1305 denotes a step in which the terminal 110 requests the gateway 120 for a predetermined output, for example, an output for displaying the screen 300 about the terminal user.
Reference numeral 1310 denotes a step in which the gateway 120 requests an event log from at least one blockchain node included in the blockchain node group 140. This request may or may not be due to a transaction.

  Reference numeral 1315 denotes a step in which at least one block chain node included in the block chain node group 140 returns at least a part of the event log to the gateway 120.

  Reference numeral 1320 denotes a step in which the gateway 120 extracts an event log satisfying a predetermined condition from the acquired event log. The predetermined condition may be a condition that the predetermined condition includes information for identifying the terminal user as the remittance source user or the remittance destination user. In addition, the predetermined condition may be a condition that includes a predetermined tag, for example, “work-in / out”.

  At least one blockchain node included in the blockchain node group 140 extracts an event log satisfying a predetermined condition from all event logs, and returns the event log extracted in step 1310 to the gateway 120. In that case, step 1315 is unnecessary.

  Reference numeral 1325 indicates a step in which the gateway 120 generates a predetermined output based on the extracted event log. Note that the generated output need not include all the information of the extracted event log. For example, the generated output can include only information corresponding to a particular column in a table included in screen 300.

Reference numeral 1330 denotes a step in which the gateway 120 returns the generated output to the terminal 110.
Reference numeral 1335 denotes a step in which the terminal 110 performs processing based on the returned output, for example, displaying the screen 300 based on the returned output.

  The terminal 110 requesting in step 1305 can be a terminal as part of the attendance system. Here, in step 1320, if the event log including the tag of “working in and out” is extracted, and in step 1325, for example, the output in the CSV format is generated, the terminal can perform the date and time (for example, (Corresponding to the date and time in the “execution date and time” column in the table included in the screen 300) can be used as the date and time relating to attendance. That is, according to the token history output generation processing, the system 100 can be used for attendance management and can be linked with the attendance management system.

1-3-7 Second Token Remittance Relationship Visualization Screen Generation Process The second token remittance relationship visualization screen generation process is a process for generating an output for displaying the second token remittance relation visualization screen 400. . Note that this output can include an output for displaying portion 410 described above with respect to FIG. 4D. This process may be similar to the token history output generation process.

However, the predetermined condition used in the step corresponding to step 1320 is:
A time period (to extract event logs having a date and time within the time period);
Tags (extract event logs that contain the specified tags)
A remittance source user (the remittance source user extracts an event log that is a user specified on the terminal 110);
At least one of a remittee user (an event log in which the remittee user is the user specified on the terminal 110). The “date and time” of the “event log” may be the date and time relating to the transaction that stores the event log. In this step, an attribute of each user may be acquired from the database 130, and a user having a certain attribute may be included in the predetermined condition. Further, the predetermined condition may be selected, specified or entered via one or more of the components as part 410 includes and received from terminal 110.

Further, a step corresponding to step 1325 includes a graph generation process. FIG. 14A illustrates an exemplary graph generation process 1400.
Reference numeral 1405 indicates a step of selecting a certain user. Since step 1405 can be repeated as described later, this step may be a step of selecting a certain user among users who have not yet been selected.

  Reference numeral 1410 denotes a step of further extracting, from the event logs extracted in the step corresponding to step 1320, the event log stored as the remittance destination user by the selected user.

Reference numeral 1415 denotes a step of specifying one or more remittance source users from the extracted event log.
Reference numeral 1420 denotes a step of calculating the total remittance amount for each specified remittance source user from the extracted event log.

  Reference numeral 1425 denotes a step of calculating the total amount of remittance of the second token to the selected user by summing the remittance amount to the selected user from the extracted event log or the further extracted event log.

  Reference numeral 1430 denotes a step of determining whether there is a user who has not yet been selected. If there is a user that has not been selected, the process returns to step 1405; otherwise, the process proceeds to step 1435.

  Reference numeral 1435 denotes a step of calculating the expression and position of the node corresponding to each user, the expression of each directed edge, and the positions of both ends based on the calculation results in steps 1420 and 1425. Step 1435 may include a step of determining the shape and color of the node based on the attribute of the user corresponding to the node.

  According to the second token remittance relation visualization screen generation process, by using the period as the predetermined condition used in the step corresponding to step 1320, only the remittance of the second token generated within a certain period, that is, communication is visualized. Can be.

  Further, according to the second token remittance relation visualization screen generation process, by using a tag as the predetermined condition used in the step corresponding to step 1320, it is possible to visualize only communication having a meaning corresponding to a certain tag. .

  Furthermore, according to the second token remittance relation visualization screen generation process, a node corresponding to the user is selectively displayed by using a user having an attribute as a predetermined condition used in the step corresponding to step 1320. For example, it is possible to visualize only communication about users having a certain post or role.

FIG. 14B illustrates an example process 1450 that step 1435 may include.
Reference numeral 1455 denotes a step of initializing a variable i used in the example process 1450 to 1 and further initializing the position of each node. Preferably, the position of each node is initialized such that nodes corresponding to users with similar affiliation codes are located closer together, as described above with respect to FIGS. 4B and 4C.

Reference numeral 1460 denotes a step of selecting one of a plurality of groups in the i-th hierarchy. The smaller the value of i, the lower the hierarchical level.
Reference numeral 1465 denotes a step of calculating a position of one node corresponding to the selected group from positions of one or more nodes respectively corresponding to one or more users belonging to the selected group. Here, the “node corresponding to the group” corresponds to one or more nodes corresponding to one or more users belonging to the group, and if a uniquely determined position can be calculated, its shape May be considered as anything (in the system 100, it is not necessary to display the “node corresponding to the group” itself), but for ease of understanding, it corresponds to the dotted line in FIGS. 4C, 4E and 4F. You may think that. The position of the “node corresponding to the group” to be calculated may be a position uniquely determined from the position of one or more nodes corresponding to each of one or more users belonging to the group. It may be the centroid of the location of one or more nodes corresponding to each of the users.

  Reference numeral 1470 denotes a step of determining whether or not there is a group that has not been selected among a plurality of groups in the i-th hierarchy. If there is a group that has not yet been selected, the process returns to step 1460; otherwise, the process proceeds to step 1475.

  Reference numeral 1475 denotes a step of acquiring a parameter corresponding to the i-th hierarchy. This parameter may be a value corresponding to knob 416A of component 416 described above with respect to FIG. 4D, corresponding to the ith hierarchy.

  Reference numeral 1480 denotes a step of adjusting the position of the node corresponding to each group such that the distance between the plurality of nodes respectively corresponding to the plurality of groups in the i-th hierarchy has a value corresponding to the acquired parameter. Here, “distance between a plurality of nodes respectively corresponding to a plurality of groups” may be based on “position of a node corresponding to each group”. If the acquired parameter is a specific value (for example, a value acquired when the position of the knob 416A of the component 416 is at the initial position (for example, the center of the component 416)), in step 1480, the parameter corresponding to each group is set. Note that adjustment of the position of the node may not be performed substantially.

  Reference numeral 1485 denotes a step of adjusting the position of the node corresponding to each user based on the adjusted position of the node corresponding to each group. In this step, when the position of the node corresponding to a certain group is moved by a certain distance in a certain direction due to the adjustment, the positions of all the nodes corresponding to one or more users belonging to the certain group are changed in the certain direction. The method may include the step of moving by a distance. If the position of the node corresponding to each group is not substantially adjusted in step 1480, the position of the node corresponding to each user is not substantially adjusted (that is, the position of each node is not adjusted). Note that no movement occurs.)

Reference numeral 1490 denotes a step of incrementing the variable i.
Reference numeral 1495 indicates a step of determining whether or not the variable i is equal to or less than the number n of one or more layers. If the variable i is equal to or smaller than the number n of one or more layers, the process returns to step 1460; otherwise, the process ends. Note that n can be 1.

According to the example process 1450, even when a large number of nodes exist, it is possible to present an easy-to-view graph in which the display interval between the nodes is adjusted.
1-3-8 Second Token Remittance Count Visualization Screen Generation Process The second token remittance count visualization screen generation process is a process for generating an output for displaying the second token remittance count visualization screen 500. . This processing may be the same processing as the second token remittance relation visualization screen generation processing.

However, the graph generation processing can be the exemplary processing 1500 illustrated in FIG.
Reference numeral 1505 denotes a step of selecting a certain user. Since step 1505 can be repeated as described later, this step may be a step of selecting a certain user among users who have not yet been selected.

  Reference numeral 1510 denotes a step of counting the number of event logs stored as the remittance source user by the selected user in the event log extracted in the step corresponding to step 1320, and calculating the number of remittances.

  Reference numeral 1515 denotes a step of counting the number of event logs in which the selected user is stored as the remittance destination user in the extracted event log, and calculating the number of remittances.

Reference numeral 1520 denotes a step of calculating the total amount of remittance of the second token to the selected user by summing the remittance amount to the selected user from the extracted event log.
Reference numeral 1525 denotes a step of determining whether there is a user who has not been selected yet. If there is a user who has not yet selected, the process returns to step 1505; otherwise, the process proceeds to step 1530.

Reference numeral 1530 denotes a step of calculating the expression and position of the figure corresponding to each user based on the calculation results in steps 1510 to 1520.
1-3-9 Token Ranking Screen Generation Process The token ranking screen generation process is a process for generating an output for displaying the token ranking screen 600. This processing may be the same processing as the token remittance relation visualization screen generation processing, but steps corresponding to steps 1415, 1420, and 1435 are not required.

2. Another Embodiment of the Present Invention Another example of an embodiment of the present invention is another system for exchanging tokens between users.

  Although the schematic configuration of the present system may be similar to that shown in FIG. 1, the present system is a system for exchanging a plurality of types of tokens in addition to or instead of the first token described with respect to system 100. is there. The plurality of types of tokens may differ in one or more of the issuer, the source, and the use. Further, the plurality of types of tokens may include the second token described with respect to the system 100. Thus, for example, if the system is capable of exchanging the first token described with respect to the system 100 for a plurality of types of tokens, including the second token, at least the system will not allow remittances There will be a plurality of types of tokens having different uses such as a first token and a second token that can be remitted. Hereinafter, the present system exchanges α tokens, β tokens, and γ tokens as a plurality of types of tokens.

2-1 Exemplary Screen Displayed in the System The screen displayed in the system is assumed to be displayed on the terminal 110, but may be displayed on another computer.

2-1-1 Token Holding Ratio Visualization Screen FIG. 16A illustrates an example token holding ratio visualization screen 1600. Screen 1600 includes a graph composed of nodes and directed edges.

  In the graph included in the screen 1600, the nodes to which "A" to "E" are respectively assigned correspond to the users A to E, and the expression of the node is a plurality of tokens held by the corresponding user. It has become according to the amount of. Note that “node” in this figure is a pie chart representing the holding ratio of a plurality of tokens held by the corresponding user, but is not limited to these. Further, the “representation of a node” which is a pie graph includes color classification in the pie graph (portions of the plurality of tokens corresponding to the holding amounts of the respective tokens are different colors).

  In the graph included in the screen 1600, the one-way or two-way directed edge extending from one of the two nodes to the other is a user corresponding to one of the two nodes when the edge is a one-way directed edge. In the case of a bidirectional directed edge, it corresponds to bidirectional remittance of one or more tokens of a plurality of types of tokens. The expression of the directed edge is in accordance with the type of the remitted token. In this figure, "expression of a directed edge" is a figure showing the type of the remitted token (for example, in this figure, the bidirectional transfer of the γ token between Mr. C and Mr. D) Is represented.), But is not limited to this.

2-1-2 Token Type Retained Amount Visualization Screen FIG. 16B shows an example token type retained amount visualization screen 1625. The screen 1625 includes a table indicating the token holding amount for each token type and each user.

2-2 Exemplary processing in the present system 2-2-1 Various token remittance processing The various token remittance processing may be the same as the second token remittance processing in the system 100. Therefore, for example, according to the α token transmission process, at least the blockchain node
information indicating the remittance of the α token,
Information identifying the sender of the remittance,
Information identifying the remittee user,
The designated remittance amount may be stored as an event.

2-2-2 Token holding ratio visualization screen generation process The token holding ratio visualization screen generation process is a process for generating an output for displaying the token holding ratio visualization screen 1600. This processing may be the same processing as the token remittance relation visualization screen generation processing.

However, the graph generation process
Further identifying, from the extracted event log, one or more types of remitted tokens for each identified remittance source user;
Calculating the total amount of remittance to the selected user for each type of token from the extracted event log or further extracted event log;
Calculating the information needed to display a pie chart based on the total amount of remittance to the selected user for each calculated token type.

2-2-3 Token Type Retention Volume Visualization Screen Generation Process The token type retention volume visualization screen generation process is a process for generating an output for displaying the token type retention volume visualization screen 1625. . This process may be similar to the token history output generation process.

  However, the token amount holding amount visualization screen generation processing may not include the step corresponding to step 1320. Further, a step corresponding to step 1325 may include an example process 1650 shown in FIG. 16C.

  Reference numeral 1655 indicates a step of selecting a certain user. Since step 1655 can be repeated as described later, this step may be a step of selecting a certain user among the users who have not yet been selected.

Reference numeral 1660 denotes a step of calculating the total remittance amount to the selected user for each type of token from the returned event log.
Reference numeral 1665 denotes a step of determining whether there is a user who has not yet been selected. If there is a user who has not been selected yet, the process returns to step 1655; otherwise, the gateway 120 outputs an output for displaying the token type holding amount visualization screen based on the calculation result in step 1660. Will be generated.

2-3 Example of using this system 2-3-1 First example Full-time employee X of α Company, which undertakes system development for financial institutions, joined the company because he was engaged in system development as a leader in a client project. Since then, he has been resident at customers and has been little known within the company. On the other hand, the person in charge of β bank, a user company of α company, has received high praise, and as a thankful person, Mr. Y, the person in charge of β bank remitted the β token issued by β bank to Mr. X It was decided to do. As a result, Mr. X of α company has β token. That is, the amount of possession of a certain token is basically proportional to the reputation as a human resource for the entity corresponding to the token.

  In addition, Engineer Q of Company γ, a development partner company of Company α, participated in the project of Bank β along with Mr. X. Thanks to Mr. Q, we will remit β tokens and α tokens issued by α company. Therefore, Mr. Q of γ company has both α token and β token.

Later, Mrs. X and Mrs. Q were assigned to different banks, but each did not receive much credit.
At one point, I had a problem with a project for beta bank, and I was looking for a human resource / team that could solve it well. At that time, from the token holding ratio visualization screen 1600 of this system,
In the past, Mr. X has been sent β tokens,
In the past, it was easy to read that Mr. X had sent α and β tokens from Mr. X, so the relationship and combination between Mr. X, Mr. Q and β bank became clear, and the two companies again became X and Q were assigned to the project as a team, and as a result, the trouble was solved brilliantly by the activities of X and Q. At a later date, the β token was further transferred from Mr. Y, the person in charge of β bank to Mr. X, and Mr. X remitted the sent β token to Mr. Q.

  As described above, according to this system, it is easy to read from the record on the blockchain that the evaluation of the system development for β bank by Mr. X and Mr. Q, that is, the effective staffing of Mr. X and Mr. Q is effective. Will be able to

2-3-2 Second Case Each company / organization (hereinafter, referred to as “company etc.”) issues an activity / contribution that contributes to the company in some form to that company / company. Suppose the situation is to send a token. Specifically, if software (library) essential for products sold by a certain company etc. is open source and developed by a general engineer, the company etc. issues it regardless of the technician's affiliation Assume a situation in which a token is remitted.

Under such circumstances, the amount of tokens corresponding to a certain company or the like can be a technician's skill proof (non-falsification) for the company.
Also, assuming that tokens are exchanged instead of greetings at various seminars and study sessions, the remittance relationship and holding ratio of such various tokens from different sources will indicate a series of people connection Become.

  That is, according to the present system, it is possible to provide a platform for visualizing that an external technician of a certain company or the like has skills for the company and a series of connections between persons.

3. Computer Hereinafter, an example of a hardware configuration of a computer that can be used as the terminal 110, the gateway 120, the database 130, and the blockchain node will be described.

  FIG. 17 illustrates an example of a hardware configuration of a computer. As shown in the figure, the computer 1700 mainly includes, as hardware resources, a processor 1710, a main storage device 1720, an auxiliary storage device 1730, a user interface 1740, and a communication interface 1750. Are connected to each other via a bus line 1760 including an address bus, a data bus, a control bus and the like. Note that an interface circuit (not shown) may be interposed between the bus line 1760 and each hardware resource as appropriate.

The processor 1710 controls the entire computer.
The main storage device 1720 provides a work area to the processor 1710, and is a volatile memory such as an SRAM or a DRAM.

  The auxiliary storage device 1730 is a non-volatile memory, such as a hard disk drive or a flash memory, for storing software programs and data. The program is loaded from the auxiliary storage device 1730 to the main storage device 1720 via the bus line 1760 at any time.

  The user interface 1740 performs one or both of presenting information to a user and receiving information input from the user, and includes a digital camera, a keyboard, a mouse, a display, a touch panel display, a microphone, a speaker, and the like. .

  The communication interface 1750 is connected to the network 1770, and sends and receives data via the network 1770. Communication interface 1750 and network 1770 may be connected by wire or wirelessly. The communication interface 1750 may also obtain information about a network, for example, information about a Wi-Fi access point, information about a base station of a communication carrier, and the like.

  It is understood by those skilled in the art that a computer can function as desired means, execute desired steps, and realize desired functions by cooperation of the hardware resources exemplified above and software, for example, a program. Will be obvious.

4. Conclusion While some examples of the embodiments of the present invention have been described above, it should be understood that these are merely examples, and do not limit the technical scope of the present invention. It should be understood that changes, additions, improvements, etc., of the embodiments can be made as appropriate without departing from the spirit and scope of the present disclosure. The technical scope of the present invention should not be limited by any of the above-described embodiments, but should be defined only by the claims and equivalents thereof.

Claims (42)

The first computer is
A transaction for a first user to use a first token for a second user, the transaction being performed based on a transaction stored in a blockchain,
Gets the amount stored in the first token associated with the first user, the obtained the amount reduces, stores the amount of reduced as the amount the new first token associated with the first user a first step you,
Gets the amount stored in the second token associated with the second user, acquired the amount increased, stores the amount was increased as the amount the new second token associated with the second user to Rutotomoni, obtains the amount stored in the second token associated with the first user, increasing the obtained the amount of new second token associated with the amount obtained by increasing the first user look including the step of including a second step you stored as an amount, by the first step performed by the computer on the basis of the transaction for the first user uses the first token to the second user, the second user The method of claim 1, wherein the stored amount of the first token associated with is not increased . The method of claim 1, wherein
The first step includes the step of reducing the obtained amount of the first token associated with the first user by a first predetermined amount,
The second step includes a step of increasing an amount obtained by multiplying the first predetermined percentage of the acquired amount of the second token associated with the first user to the first predetermined amount,
The method comprises:
A first computer performing a first user based on a transaction for using a first token with a second user, the first computer comprising:
Based on the value of associated with the first user stored counter, a step you calculate a first predetermined ratio, when the value of the counter is increased, increasing the first predetermined ratio and a step that be calculated so as not to,
Acquires the stored value of the counter associated with the first user, is incremented the obtained the values, and storing the incremented the value as a new value of the counter associated with the first user A method comprising steps. The method according to claim 1 or 2, wherein
The first computer performing a transaction for the first user to transfer the second token to the second user, the first computer performing a transaction based on the transaction stored in the blockchain;
Gets the amount stored in the second token associated with the first user, the obtained the amount reduces, stores the amount of reduced as the amount the new second token associated with the first user and step you,
Gets the amount stored in the second token associated with the second user, acquired the amount increased, stores the amount was increased as the amount the new second token associated with the second user further comprising the step of including the steps you. The method according to any one of claims 1 to 3, wherein
The second computer transmitting a transaction for performing a periodic process to the first computer so as to be stored in a block chain, one or more times;
First computer, the steps of first user based on the transaction for using the first token to the second user, to store the date and time according to the transaction, as time associated with the first user,
A step in which the first computer performs a periodic process for each user based on a transaction for performing the periodic process ,
A first condition that a stored date and time associated with the user is acquired, and the acquired date and time is earlier than a predetermined length of time based on a date and time relating to a transaction for performing a periodic process. Determining whether or not
If it meets the first condition, acquires the amount stored in the first token associated with the user, reducing the obtained the amount of the amount of reduced associated with the user was stored as a new amount of the first token, otherwise, to get the amount stored in the first token associated with the user, increasing the obtained the amount, the amount the of increased method comprising the steps of comprising the steps you stored as the amount the new first token associated with the user. 5. The method according to claim 4, wherein
A first computer storing a date and time of expiration of the first token based on the transaction stored in the blockchain;
A first computer performing a periodical process based on a transaction for performing the periodical process ,
It acquires date and time stored in the time limit of the first token, than the date and time acquired, determining the second condition that is after the date of the transaction for performing periodical treatment,
Method comprising the steps of and storing the zero if you meet the second condition, as the amount of the first token associated with each user. A method according to any one of claims 1 to 5, wherein
The first computer is information defined in a predetermined smart contract based on the transaction, wherein the predetermined smart contract defines at least a part of a process executed by the first computer by the transaction . Storing a certain information as an event;
A second computer obtaining an event log that is information stored as an event on the first computer. The method of claim 6, wherein
The step of acquiring an event log includes the step of the second computer acquiring an event log that satisfies a third condition among the event logs.
Method. The method according to claim 7, wherein
The third condition is
That the date and time related to the event log is within a predetermined period,
That the event log contains the given tags,
The event log contains the given sender user,
The event log includes one or more of the following:
Method. A method according to any one of claims 6 to 8, wherein
The transaction includes a tag and a message ID,
The method comprises:
A second computer displaying at least a part of the information corresponding to the transaction based on the acquired event log, wherein at least a part of the information corresponding to the transaction includes a tag included in the transaction; And including a message identified by a message ID that the transaction includes. The method according to any one of claims 6 to 9, wherein
A second computer generating an output for displaying a first graph based on the obtained event log;
The first graph includes two or more nodes and one or more directed edges,
Each node corresponds to a user, and the expression of each node is according to the sum of the remittance amount of the second token to the corresponding user;
Each directed edge extends from the node corresponding to the remittance source user of the second token to the node corresponding to the remittance destination user. Depending on the sum of the quantities,
The remittance amount of the second token to the user includes an increase in the second token held by the user due to the use of the first token,
The sending user of the second token includes the user of the first token,
The remittance user of the second token includes the used user of the first token,
Method. The method according to claim 10, wherein
The node is a pie chart representing a ratio of tokens for the corresponding user,
The representation of the node is the size of the pie graph,
Method. A method according to any one of claims 10 or 11, wherein
Each user belongs to any one of a plurality of groups in each of the one or more layers, and each group includes one or more users;
Generating an output for displaying a first graph based on the obtained event log includes: for one of the one or more layers,
For each of the plurality of groups in the one layer, one or more nodes respectively corresponding to one or more users belonging to the group are set as one node corresponding to the group, and the plurality of nodes in the one layer are set. And adjusting the position of the node corresponding to each user such that the distance between the plurality of nodes respectively corresponding to the group is dependent on the parameter corresponding to the one hierarchy. A method according to any one of claims 6 to 12, wherein
A second computer generating an output for displaying a second graph based on the obtained event log;
The second graph has a first axis and a second axis, includes a plurality of graphics,
Each figure corresponds to a user,
The representation of each figure is in accordance with the total amount of remittance of the second token to the corresponding user,
The position of each figure with respect to the first axis and the second axis depends on the number of times the corresponding user has remitted the second token and the number of times the corresponding user has received the second token. Yes,
The remittance amount of the second token to the user includes an increase in the second token held by the user due to the use of the first token,
The number of times the user has remitted the second token includes the number of times the user has used the first token,
The number of times the second token has been remitted to the user includes the number of times the first token has been used for the user.
Method. 14. The method according to any one of claims 6 to 13, wherein
A first computer is a transaction stored in a blockchain, wherein a first user provides a second user with at least one of a plurality of types of tokens that differ in at least one of an issuer, a source, and a use. Storing information related to the transaction as an event based on the transaction for remitting
A second computer generating an output for displaying a third graph based on the obtained event log;
The third graph includes two or more nodes and one or more directed edges,
Each node corresponds to a user, and each node is a pie chart representing a ratio of the amount of the plurality of types of tokens transferred to the corresponding user;
Each directed edge extends from a node corresponding to a remittance user of at least one of the plurality of tokens to a node corresponding to a remittance user;
Method. A system including one or more computers, wherein the first computer included by the system comprises:
A transaction for a first user to use a first token for a second user, the transaction being performed based on a transaction stored in a blockchain,
Gets the amount stored in the first token associated with the first user, the obtained the amount reduces, stores the amount of reduced as the amount the new first token associated with the first user a first step you,
Gets the amount stored in the second token associated with the second user, acquired the amount increased, stores the amount was increased as the amount the new second token associated with the second user to Rutotomoni, obtains the amount stored in the second token associated with the first user, increasing the obtained the amount of new second token associated with the amount obtained by increasing the first user executing step and a second step you stored as an amount, by the first step performed by the computer on the basis of the transaction for the first user uses the first token to the second user, the second user The stored amount of the first token associated with the system does not increase . The system according to claim 15, wherein
The first step includes the step of reducing the obtained amount of the first token associated with the first user by a first predetermined amount,
The second step includes a step of increasing an amount obtained by multiplying the first predetermined percentage of the acquired amount of the second token associated with the first user to the first predetermined amount,
A first computer included in the system includes:
Performing a first user transaction with a second user based on a transaction for using the first token,
Calculating a first predetermined rate based on a stored value of a counter associated with the first user, wherein the first predetermined rate does not increase when the value of the counter increases. and step you calculated as,
Acquires the stored value of the counter associated with the first user, is incremented the obtained the values, and storing the incremented the value as a new value of the counter associated with the first user A system that performs steps. The system according to claim 15 or 16, wherein
A first computer included in the system, wherein the first computer performs a transaction for remitting a second token to the second user based on a transaction stored in a blockchain,
Gets the amount stored in the second token associated with the first user, the obtained the amount reduces, stores the amount of reduced as the amount the new second token associated with the first user and step you,
Gets the amount stored in the second token associated with the second user, acquired the amount increased, stores the amount was increased as the amount the new second token associated with the second user further performing the steps comprising the steps you,
system. The system according to any one of claims 15 to 17, wherein
The second computer included in the system executes a step of transmitting a transaction for performing a periodic process to the first computer so as to be stored in a block chain one or more times,
A first computer included in the system includes:
Based on a transaction for the first user to use the first token for the second user, storing a date and time related to the transaction as a date and time associated with the first user;
Based on a transaction for performing a periodic process , a step to be performed for each user as a periodic process ,
A first condition that a stored date and time associated with the user is acquired, and the acquired date and time is earlier than a predetermined length of time based on a date and time relating to a transaction for performing a periodic process. Determining whether or not
If it meets the first condition, acquires the amount stored in the first token associated with the user, reducing the obtained the amount of the amount of reduced associated with the user was stored as a new amount of the first token, otherwise, to get the amount stored in the first token associated with the user, increasing the obtained the amount, the amount the of increased It executes the steps comprising the steps you stored as the amount the new first token associated with the user, the system. 19. The system according to claim 18, wherein the first computer included in the system comprises:
Storing the expiration date and time of the first token based on the transactions stored in the blockchain;
A step of performing a periodic process based on a transaction for performing the periodic process ,
It acquires date and time stored in the time limit of the first token, than the date and time acquired, determining the second condition that is after the date of the transaction for performing periodical treatment,
If it meets the second condition, and a step comprising the step of storing a zero as the amount of the first token associated with each user, the system. 20. The system according to any one of claims 15 to 19,
A first computer included in the system is information defined in a predetermined smart contract based on the transaction, and the predetermined smart contract includes at least a part of a process that the transaction causes the first computer to execute. Performing the step of storing the information as an event , which is defined ,
A second computer included in the system executes a step of acquiring an event log, which is information stored as an event in the first computer;
system. 21. The system according to claim 20, wherein
Obtaining the event log includes obtaining an event log that satisfies a third condition among the event logs;
system. 22. The system according to claim 21, wherein
The third condition is
That the date and time related to the event log is within a predetermined period,
That the event log contains the given tags,
The event log contains the given sender user,
The event log includes one or more of the following:
system. The system according to any one of claims 20 to 22, wherein
The transaction includes a tag and a message ID,
A second computer included in the system, wherein at least a part of the information corresponding to the transaction is displayed based on the acquired event log, wherein at least a part of the information corresponding to the transaction is Performing steps, including a message specified by a tag included in the transaction and a message ID included in the transaction;
system. The system according to any one of claims 20 to 23,
A second computer included in the system performs a step of generating an output for displaying a first graph based on the obtained event log;
The first graph includes two or more nodes and one or more directed edges,
Each node corresponds to a user, and the expression of each node is according to the sum of the remittance amount of the second token to the corresponding user;
Each directed edge extends from the node corresponding to the remittance source user of the second token to the node corresponding to the remittance destination user, and the expression of each directed edge is represented by a remittance from the remittance source user which is one end of the directed edge. Depending on the sum of the quantities,
The remittance amount of the second token to the user includes an increase in the second token held by the user due to the use of the first token,
The sending user of the second token includes the user of the first token,
The remittance user of the second token includes the used user of the first token,
system. The system according to claim 24, wherein
The node is a pie chart representing a ratio of tokens for the corresponding user,
The representation of the node is the size of the pie graph,
system. The system according to any one of claims 24 or 25,
Each user belongs to any one of a plurality of groups in each of the one or more layers, and each group includes one or more users;
Generating an output for displaying a first graph based on the obtained event log includes: for one of the one or more layers,
For each of the plurality of groups in the one layer, one or more nodes respectively corresponding to one or more users belonging to the group are set as one node corresponding to the group, and the plurality of nodes in the one layer are set. And adjusting the position of the node corresponding to each user such that the distance between the plurality of nodes respectively corresponding to the group is determined according to the parameter corresponding to the one hierarchy. The system according to any one of claims 20 to 26,
A second computer included in the system executes a step of generating an output for displaying a second graph based on the obtained event log;
The second graph has a first axis and a second axis, includes a plurality of graphics,
Each figure corresponds to a user,
The representation of each figure is in accordance with the total amount of remittance of the second token to the corresponding user,
The position of each figure with respect to the first axis and the second axis depends on the number of times the corresponding user has remitted the second token and the number of times the corresponding user has received the second token. Yes,
The remittance amount of the second token to the user includes an increase in the second token held by the user due to the use of the first token,
The number of times the user has remitted the second token includes the number of times the user has used the first token,
The number of times the second token has been remitted to the user includes the number of times the first token has been used for the user.
system. 28. The system according to any one of claims 20 to 27,
A first computer included in the system is a transaction stored in a blockchain, in which a first user provides a second user with a plurality of types of tokens different in at least one of an issuer, a source, and a use. Executing a step of storing information on the transaction as an event based on a transaction for remittancing at least one of the transactions;
A second computer included in the system performs a step of generating an output for displaying a third graph based on the obtained event log;
The third graph includes two or more nodes and one or more directed edges,
Each node corresponds to a user, and each node is a pie chart representing a ratio of the amount of the plurality of types of tokens transferred to the corresponding user;
Each directed edge extends from a node corresponding to a remittance user of at least one of the plurality of tokens to a node corresponding to a remittance user;
system. One or more programs, the first computer comprising:
A transaction for a first user to use a first token for a second user, the transaction being performed based on a transaction stored in a blockchain,
Gets the amount stored in the first token associated with the first user, the obtained the amount reduces, stores the amount of reduced as the amount the new first token associated with the first user a first step you,
Gets the amount stored in the second token associated with the second user, acquired the amount increased, stores the amount was increased as the amount the new second token associated with the second user to Rutotomoni, obtains the amount stored in the second token associated with the first user, increasing the obtained the amount of new second token associated with the amount obtained by increasing the first user such to execute the steps and a second step you stored as an amount, by the steps of first user has a first computer performs, based on the transaction for using the first token to the second user, the second user one or more programs amount stored in the first token associated you characterized in that it does not increase. 30. The one or more programs of claim 29, wherein:
The first step includes the step of reducing the obtained amount of the first token associated with the first user by a first predetermined amount,
The second step includes a step of increasing an amount obtained by multiplying the first predetermined percentage of the acquired amount of the second token associated with the first user to the first predetermined amount,
On the first computer,
Performing a first user transaction with a second user based on a transaction for using the first token,
Based on the value of associated with the first user stored counter, a step you calculate a first predetermined ratio, when the value of the counter is increased, increasing the first predetermined ratio and a step that be calculated so as not to,
Acquires the stored value of the counter associated with the first user, is incremented the obtained the values, and storing the incremented the value as a new value of the counter associated with the first user One or more programs that perform the steps. 31. The one or more programs according to claim 29 or 30,
A transaction for the first user to transfer the second token to the second user to the first computer, the transaction being performed based on the transaction stored in the blockchain;
Gets the amount stored in the second token associated with the first user, the obtained the amount reduces, stores the amount of reduced as the amount the new second token associated with the first user and step you,
Gets the amount stored in the second token associated with the second user, acquired the amount increased, stores the amount was increased as the amount the new second token associated with the second user one or more programs for executing the steps including a step you further. 32. One or more programs according to any one of claims 29 to 31, wherein
Causing the second computer to transmit the transaction for performing the periodic processing to the first computer so as to be stored in the block chain, performing the step of performing one or more times,
On the first computer,
Based on a transaction for the first user to use the first token for the second user, storing a date and time related to the transaction as a date and time associated with the first user;
Based on a transaction for performing a periodic process , a step to be performed for each user as a periodic process ,
A first condition that a stored date and time associated with the user is acquired, and the acquired date and time is earlier than a predetermined length of time based on a date and time relating to a transaction for performing a periodic process. Determining whether or not
If it meets the first condition, acquires the amount stored in the first token associated with the user, reducing the obtained the amount of the amount of reduced associated with the user was stored as a new amount of the first token, otherwise, to get the amount stored in the first token associated with the user, increasing the obtained the amount, the amount the of increased one or more programs to be executed and a step including the steps you stored as the amount the new first token associated with the user. 33. The one or more programs according to claim 32, wherein the first computer comprises:
Storing the expiration date and time of the first token based on the transactions stored in the blockchain;
A step of performing a periodic process based on a transaction for performing the periodic process ,
It acquires date and time stored in the time limit of the first token, than the date and time acquired, determining the second condition that is after the date of the transaction for performing periodical treatment,
If it meets the second condition, one or more programs to be executed and a step including the step of storing a zero as the amount of the first token associated with each user. 34. One or more programs according to any one of claims 29 to 33,
Information defined in a predetermined smart contract based on the transaction by the first computer, wherein the predetermined smart contract defines at least a part of a process executed by the first computer by the transaction . there, to execute the steps of storing the information as an event,
At least one program that causes a second computer to execute a step of acquiring an event log, which is information stored as an event in the first computer. 35. The one or more programs according to claim 34, wherein:
Obtaining the event log includes obtaining an event log that satisfies a third condition among the event logs;
One or more programs. 36. The one or more programs of claim 35, wherein:
The third condition is
That the date and time related to the event log is within a predetermined period,
That the event log contains the given tags,
The event log contains the given sender user,
The event log includes one or more of the following:
One or more programs. One or more programs according to any one of claims 34 to 36,
The transaction includes a tag and a message ID,
Displaying at least a part of the information corresponding to the transaction on the second computer based on the acquired event log, wherein at least a part of the information corresponding to the transaction includes a tag included in the transaction; And one or more programs for performing steps, including a message identified by a message ID included in the transaction. One or more programs according to any one of claims 34 to 37,
Causing the second computer to generate an output for displaying the first graph based on the acquired event log;
The first graph includes two or more nodes and one or more directed edges,
Each node corresponds to a user, and the expression of each node is according to the sum of the remittance amount of the second token to the corresponding user;
Each directed edge extends from the node corresponding to the remittance source user of the second token to the node corresponding to the remittance destination user. Depending on the sum of the quantities,
The remittance amount of the second token to the user includes an increase in the second token held by the user due to the use of the first token,
The sending user of the second token includes the user of the first token,
The remittance user of the second token includes the used user of the first token,
One or more programs. 39. The one or more programs of claim 38, wherein:
The node is a pie chart representing a ratio of tokens for the corresponding user,
The representation of the node is the size of the pie graph,
One or more programs. One or more programs according to any one of claims 38 or 39,
Each user belongs to any one of a plurality of groups in each of the one or more layers, and each group includes one or more users;
Generating an output for displaying a first graph based on the obtained event log includes: for one of the one or more layers,
For each of the plurality of groups in the one layer, one or more nodes respectively corresponding to one or more users belonging to the group are set as one node corresponding to the group, and the plurality of nodes in the one layer are set. Adjusting the position of the node corresponding to each user such that the distance between the plurality of nodes respectively corresponding to the group of the groups corresponds to the parameter corresponding to the one layer.
One or more programs. 41. One or more programs according to any one of claims 34 to 40,
Causing a second computer to generate an output for displaying a second graph based on the acquired event log;
The second graph has a first axis and a second axis, includes a plurality of graphics,
Each figure corresponds to a user,
The representation of each figure is in accordance with the total amount of remittance of the second token to the corresponding user,
The position of each figure with respect to the first axis and the second axis depends on the number of times the corresponding user has remitted the second token and the number of times the corresponding user has received the second token. Yes,
The remittance amount of the second token to the user includes an increase in the second token held by the user due to the use of the first token,
The number of times the user has remitted the second token includes the number of times the user has used the first token,
The number of times the second token has been remitted to the user includes the number of times the first token has been used for the user.
One or more programs. 42. One or more programs according to any one of claims 34 to 41,
A transaction stored in a blockchain on a first computer, wherein a first user sends to a second user at least one of a plurality of types of tokens that differ in at least one of an issuer, a source, and a use. Executing a step of storing information related to the transaction as an event, based on a transaction for remitting one transaction,
Causing a second computer included in the system to generate an output for displaying a third graph based on the obtained event log;
The third graph includes two or more nodes and one or more directed edges,
Each node corresponds to a user, and each node is a pie chart representing a ratio of the amount of the plurality of types of tokens transferred to the corresponding user;
Each directed edge extends from a node corresponding to a remittance user of at least one of the plurality of tokens to a node corresponding to a remittance user;
One or more programs.

Images