Registration system

Abstract

Provided is a registration system (1) comprising a management server (100) and a plurality of digital registration nodes (100). The management server registers information in the plurality of independent digital registration nodes in parallel in a consolidated manner. Alternatively, provided is a registration system (1) comprising a plurality of servers (100). The plurality of servers each perform recording by using a different encryption scheme from the other servers and has a key for decrypting ciphers of the other servers. If the server has found, from among the records therein, a record that is different from the records in the other servers, the server stops the recording or corrects the record therein in conformity with the record data in the majority servers.

Description

Bookkeeping system

[0001] The present invention relates to internet technology.

[0002] Conventionally, in the Web3 environment (decentralized services utilizing blockchain technology), crypto assets (virtual currencies) and tokens have been operated. For example, according to U.S. Patent No. US11397962 (B2) (Patent Document 1), a decentralized loyalty ID is used to distribute points among a plurality of loyalty partners, and the allocation of points based on transaction events and non-transaction events is managed.

[0003] U.S. Patent No. US11397962 (B2)

[0004] An object of the present invention is to provide a system capable of safely distributing and storing data over the internet.

[0005] According to one aspect of the present invention, a bookkeeping system including a management server and a plurality of digital bookkeeping nodes is provided. The management server centrally performs bookkeeping in parallel on a plurality of independent digital bookkeeping nodes.

[0006] As described above, according to the present invention, it is possible to safely distribute and store data over the internet.

[0007] This is a schematic diagram showing the overall configuration of the network system according to the first embodiment. This is a block diagram showing the configuration of the server according to the first embodiment. This is a block diagram showing the configuration of the communication terminal according to the first embodiment. This is a schematic diagram showing the structure of the Web2 virtual blockchain according to the first embodiment. This is a schematic diagram of the parallel bookkeeping system according to the first embodiment. This is a schematic diagram showing the M-out-of-N verification algorithm according to the first embodiment. This is a schematic diagram showing the overall configuration of the network system according to the second embodiment. This is a schematic diagram showing the encryption key data according to the second embodiment. This is a flowchart showing information processing in each server according to the second embodiment. This is a flowchart showing information processing in each server according to the third embodiment.

[0008] The embodiments of the present invention will be described below with reference to the drawings. In the following description, the same parts are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed explanations of them will not be repeated, and the previous explanations will be used as a reference. <Explanation of Terms>

[0009] • Web2 environment: A technological environment in which conventional centralized internet services are provided. User data and transactions are managed on a central server. • Web3 environment: A decentralized technological environment based on blockchain technology. Transparency and tamper resistance of transactions are ensured by distributed ledger technology. <First Embodiment> <Overall Configuration of Network System 1>

[0010] First, the overall configuration of the network system 1 according to this embodiment will be described with reference to Figure 1. The network system 1 according to this embodiment mainly includes a plurality of servers 100, 100... for providing a pseudo-blockchain in a Web2 environment as described below, and communication terminals 300, 500... used by each of the plurality of users who use the service. The communication terminals 300, 500 used by companies and individuals are implemented as personal computers, smartphones, tablets, etc., and can communicate with the server 100 on the cloud via the internet or carrier network. <Configuration of Server 100>

[0011] One configuration of the server 100 that constitutes the network system 1 according to this embodiment will be described. Referring to Figure 2, the server 100 includes, as its main components, a CPU (Central Processing Unit) 110, a memory 120, an operation unit 140, and a communication interface 160.

[0012] The CPU 110 controls various parts of the server 100 by executing programs stored in the memory 120. For example, the CPU 110 executes programs stored in the memory 120 and performs various processes described later by referring to various data.

[0013] The memory 120 is implemented using various types of RAM (Random Access Memory), various types of ROM (Read Only Memory), etc., and may be embedded in the server 100, or it may be detachable from various interfaces of the server 100, or it may be a recording medium of another device accessible from the server 100. The memory 120 stores programs executed by the CPU 110, data generated by the execution of programs by the CPU 110, various input data, and databases used for services according to this embodiment.

[0014] The operation unit 140 receives commands from service administrators and others, and inputs those commands to the CPU 110.

[0015] The communication interface 160 transmits data from the CPU 110 to the communication terminal 300 and other devices via the internet, carrier network, router, etc. Conversely, the communication interface 160 receives data from these devices via the internet, carrier network, router, etc., and either passes it to the CPU 110 or stores it in the memory 120. <Configuration of the communication terminal 300>

[0016] Next, with reference to Figure 3, one configuration of a stationary communication terminal 300 used by companies, individuals, etc., will be described. For example, the communication terminal 300 according to this embodiment includes, as its main components, a CPU 310, a memory 320, a display 330, an operation unit 340, a communication interface 360, and a speaker 370.

[0017] The CPU 310 controls various parts of the communication terminal 300 by executing various programs stored in the memory 320.

[0018] The memory 320 is implemented using various types of RAM and ROM. The memory 320 stores application programs for various services, web pages downloaded from the internet, data generated by the execution of programs by the CPU 310, data received from the server 100, data entered via the operation unit 340, information about the communication terminal 300 itself, product information, customer information, and so on.

[0019] The display 330 displays images and text based on data from the CPU 310. The operation unit 340 consists of a pointing device and switches, and inputs various commands from the user to the CPU 310. The communication terminal 300 may also have a touch panel 350 that includes the display 330 and the operation unit 340.

[0020] The communication interface 360 ​​transmits and receives data with other devices such as the server 100 via the internet, a carrier network, or a router. For example, the CPU 310 exchanges various types of information with the server 100 via the communication interface 360, such as web page data, text data, image data, and audio data, according to the web browser program or other application programs. <Configuration of the communication terminal 500>

[0021] The configuration of another type of communication terminal 500 used by companies and users is the same as that of communication terminal 300, so we will not repeat the explanation here. <Layer 0 (DFS Web Chain) and Parallel Accounting System>

[0022] The network system 1 according to this embodiment constitutes a centralized pseudo-blockchain built on a Web2 environment, as shown in Figure 4, using the above-mentioned multiple servers 100, 100, ..., etc. While it provides a user interface and operation feel similar to a Web3 blockchain, it is technically a server-based centralized system. In particular, "DFS Web Chain" is optimized for inter-company collaboration and is designed as a technological foundation for small and medium-sized enterprises to gain collective strength.

[0023] Furthermore, the Web2 pseudo-blockchain according to this embodiment is also capable of inter-environment connectivity. While typically the focus is primarily on data sharing and transaction recording within the same environment, the network system 1 according to this embodiment can also bridge the gap between the Web2 and Web3 environments. As a result, the Web2 virtual blockchain achieves high throughput and low-cost operation in the Web2 environment while maintaining compatibility with the Web3 environment. The Web2 virtual blockchain will be described in detail after the example of bridging.

[0024] For example, in the pseudo-blockchain according to this embodiment, each transaction, or transaction record, is independently recorded by multiple "digital ledger nodes," and a verification system is constructed that uses an "M-in-N" method, where a transaction is deemed valid if M out of N records match. This achieves the reliability and traceability of a blockchain while being in a Web2 environment.

[0025] In this embodiment, five independent servers 100, 100... (recording nodes) each record transactions using a different encryption method, and a transaction is only considered valid if at least three of these records match. This provides robustness, ensuring that the reliability of the entire system is not compromised even if a single server 100 is attacked or accessed illegally.

[0026] Each transaction is assigned a unique transaction identifier (TxID) and recorded along with a timestamp. These records are stored with cryptographic signatures, making them technically difficult to tamper with. The transaction history is maintained in a chain structure, and each record includes a reference to the previous record, ensuring the continuity and integrity of the history. This makes it possible to achieve the same transparency and traceability as Web3 blockchains while maintaining the ease of use of Web2.

[0027] As shown in Figure 5, the specific configuration of the parallel accounting system is as follows: 1. System Architecture - Central Management Server (CMS): Controls the entire process - Multiple Independent Digital Accounting Nodes (DRN): A minimum of 5 independent nodes is the standard configuration. - Inter-Node Synchronization Module (NSM): Manages communication between accounting nodes. - Verification Engine (VE): Executes the "N-in-M verification" algorithm.

[0028] 2. Mathematical Definition of the "M Verification in N" Method As shown in Figure 6, a transaction is determined to be valid if at least three of the five nodes, representing a majority, match. A verification parameter adjustment mechanism may be provided to dynamically adjust the total number of nodes N and the required number of matches M according to the importance of the transaction. For example, the value of M in N could be determined according to the importance (e.g., the amount). A transaction worth 10,000 yen would be considered valid if two out of three nodes match, while a transaction worth 1,000,000 yen would be considered valid if six out of seven nodes match. Since the number of nodes is unknown to the attacker if the values ​​of N and M are not known, this method is more secure.

[0029] In the N-M verification method, the specific arbitration mechanism in case of a mismatch is implemented as follows: First, the management server 100 prioritizes referring to the record of the node with the most recent timestamp, and then calculates the degree of agreement with other nodes. The record of the node with the highest degree of agreement is provisionally made valid and notified to all nodes. Upon receiving this notification, each node compares it with its own record and, if there is an objection, initiates the objection process. If the number of objections exceeds a certain number (usually N / 3), a manual arbitration process by the administrator is triggered. This minimizes data inconsistencies due to system failures or security breaches.

[0030] The central management server and verification engine may consist of one server 100 or multiple servers 100. Similarly, a single node may consist of one server 100 or multiple servers 100. Furthermore, multiple nodes may consist of a single server 100.

[0031] 3. Implementation of Different Encryption Methods Each digital record node employs a different encryption method, for example, as follows: Node 1: AES-256-GCM Node 2: ChaCha20-Poly1305 Node 3: RSA-4096 Node 4: ECC (Elliptic Curve Cryptography) P-384 Node 5: Twofish-256

[0032] The main features of Layer 0 are as follows: 1. It operates in a browser. No special software installation is required. It can be accessed from a common web browser. 2. It provides a UI / UX similar to Web3 blockchains. It displays transaction history and has wallet and token management functions. 3. Transparency and traceability are ensured. Transaction history can be visualized using the DfcScan explorer function. Transparency levels can be set based on permissions (control of the scope of disclosure). Transaction chain verification is possible, and it has an audit function. 4. It has a token issuance function. Companies and servers 100 and communication terminals 300 operated by companies can easily issue their own tokens. Token attributes can be customized. Companies and servers 100 and communication terminals 300 operated by companies can freely set the conversion ratio. 5. Centralized management by the server. This speeds up transaction processing and reduces operating costs. 6. Reliability is improved by a parallel recording system. Each transaction is recorded by multiple independent nodes. Multiple recording is performed using different encryption methods. A verification process using the N-in-M verification method is performed.

[0033] In other words, the parallel accounting system according to this embodiment employs an "M-in-N verification" method in which multiple independent digital accounting nodes record transactions using different encryption methods, and a transaction is deemed valid if M or more records out of N nodes match. Traceability is ensured by assigning a unique identifier and timestamp to each transaction, and transparency is achieved by maintaining the transaction history in a chain structure. <Second Embodiment>

[0034] In the above embodiment, the management server checked whether the data on the five nodes matched and determined the correct data, which represented the majority. In this embodiment, multiple servers 100, 100... each store data using a different encryption method, and each checks whether there are any differences between the data stored on one of the other servers 100, 100...

[0035] In this embodiment, as shown in Figure 7, for example, multiple servers 100, 100... record data using different encryption methods. However, multiple servers 100, 100... may record data using the same encryption method, or all servers 100, 100... may employ different encryption methods. In this embodiment, the memory 120 of server 100 stores encrypted record data, an encryption key for decrypting its own encrypted data, and encryption key data for decrypting encrypted data of other servers.

[0036] More specifically, as shown in Figure 8, the encryption key data 121 stores, for each of the other servers 100, 100..., the address of server 100 and the encryption key used to decrypt the data encrypted using the encryption method employed by that server 100.

[0037] In this embodiment, each CPU 110 of servers 100, 100... performs the following processing. In this embodiment, periodically, for example, at a predetermined time each day, or when new data is recorded, the CPU 110 executes the processing shown in Figure 9 by running the program in memory 120.

[0038] In this embodiment, the CPU 110 repeats the following processing for each of the servers 100, 100... (step S102).

[0039] The CPU 110 refers to the encryption key data 121 and accesses the target server 100 for data matching via the communication interface 160, and reads the contents of the record data by using the encryption key of the server 100 (step S104).

[0040] The CPU 110 determines whether the content of the bookkeeping data of the server 100 matches the content of the bookkeeping data stored by itself (step S106).

[0041] If the bookkeeping data of the server matches the bookkeeping data stored by itself (YES in step S106), the CPU 110 accesses the next server 100 to be verified (step S102).

[0042] If the bookkeeping data of the server is different from the bookkeeping data stored by itself (YES in step S108), an error flag is set, and the CPU 110 accesses the next server 100 via the communication interface 160 (step S102).

[0043] When data verification is completed for all other servers 100 (YES in step S110), the CPU 110 determines whether the number of servers 100 having the same bookkeeping data as itself is equal to or greater than M (step S112). Here, M is set to a value that is 50% or more of the total number of all servers 100. That is, it is determined whether the number of servers having the same data as itself exceeds a majority of the entire system.

[0044] If the number of servers 100 having the same bookkeeping data as itself is equal to or greater than M (YES in step S112), the current process is terminated with the own bookkeeping data regarded as correct.

[0045] On the other hand, if the number of servers 100 having the same bookkeeping data as itself is less than M (YES in step S112), the CPU 110 determines that its own data is incorrect, and rewrites its own data with data obtained by encrypting the bookkeeping data of another server 100 using its own encryption method (step S114). <Third Embodiment>

[0046] In the above-described embodiment, when the number of servers 100 having the same bookkeeping data as the local server is less than M, the local server rewrites its own data to match the bookkeeping data of the other servers 100. However, regarding the present embodiment, as shown in FIG. 10, when the number of servers 100 having the same bookkeeping data as the local server is less than M (YES in step S110), the CPU 110 determines that its own data is incorrect, and stops updating the bookkeeping (step S122). The CPU 110 transmits error information to the administrator's communication terminal 300 via the communication interface 160 (step S124). <Fourth Embodiment>

[0047] In the above-described embodiment, the server 100 as a single device performs bookkeeping using one encryption method. However, each of the servers 100, 100... does not need to be implemented by a single device. For example, the servers 100, 100... that implement a plurality of services may be implemented by a single device, or a plurality of devices may assume the role of one server 100 for one encryption method. <Summary>

[0048] In the above-described embodiment, a bookkeeping system including a management server and a plurality of digital bookkeeping nodes is provided. The management server centrally performs bookkeeping in parallel on the plurality of independent digital bookkeeping nodes.

[0049] Preferably, the bookkeeping system uses different encryption methods for the plurality of digital bookkeeping nodes respectively to record transactions in parallel.

[0050] Preferably, the bookkeeping system determines that the transaction is valid when records of a predetermined proportion or more among the plurality of digital bookkeeping nodes are consistent, and retains the history of the transaction in a chain structure.

[0051] In the above embodiment, an accounting system comprising multiple servers is provided. Each of the multiple servers (1) records using a different encryption method than the other servers, (2) has a key to decrypt the encryption of the other servers, and (3) modifies its own records to match the record data of the majority of servers when it finds something in its own records that is different from that of the other servers.

[0052] In the above embodiment, an accounting system comprising multiple servers is provided. Each of the multiple servers (1) records using an encryption method different from that of the other servers, (2) has a key to decrypt the encryption of the other servers, and (3) stops recording when it finds something in its own records that is different from that of the other servers.

[0053] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims rather than by the foregoing description, and all modifications within the meaning and scope equivalent to the claims are intended to be included.

[0054] 1: Network system 100: Server 110: CPU 120: Memory 140: Control panel 160: Communication interface 300: Communication terminal 310: CPU 320: Memory 330: Display 340: Control panel 350: Touch panel 360: Communication interface 370: Speaker 500: Communication terminal

Claims

1. A record-keeping system comprising a management server and multiple digital record-keeping nodes, wherein the management server centrally records entries in parallel to the multiple independent digital record-keeping nodes.

2. The accounting system according to claim 1, wherein transactions are recorded in parallel for each of the multiple digital accounting nodes using a different encryption method.

3. The pseudo-blockchain system according to claim 1, wherein a transaction is deemed valid if a predetermined percentage or more of the records among the plurality of digital recording nodes match, and the history of the transaction is maintained in a chain structure.

4. A record-keeping system comprising multiple servers, wherein each of the multiple servers records using a different encryption method than the other servers, possesses a key to decrypt the encryption of the other servers, and corrects its own records to match the record data of the majority of servers when it finds something in its own records that differs from that of the other servers.

5. A record-keeping system comprising multiple servers, wherein each of the multiple servers records using a different encryption method than the other servers, possesses a key to decrypt the encryption of the other servers, and stops recording when it finds something in its own records that is different from that of the other servers.

Images