WO2018080206A1 - Procédé d'émission de monnaie et d'exécution de paiement au moyen d'une structure arborescente de merkle de protocole orienté utxo et serveur l'utilisant - Google Patents

Procédé d'émission de monnaie et d'exécution de paiement au moyen d'une structure arborescente de merkle de protocole orienté utxo et serveur l'utilisant Download PDF

Info

Publication number
WO2018080206A1
WO2018080206A1 PCT/KR2017/011938 KR2017011938W WO2018080206A1 WO 2018080206 A1 WO2018080206 A1 WO 2018080206A1 KR 2017011938 W KR2017011938 W KR 2017011938W WO 2018080206 A1 WO2018080206 A1 WO 2018080206A1
Authority
WO
WIPO (PCT)
Prior art keywords
currency
hash value
transaction
specific
call
Prior art date
Application number
PCT/KR2017/011938
Other languages
English (en)
Korean (ko)
Inventor
송주한
홍재우
어준선
Original Assignee
주식회사 코인플러그
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 코인플러그 filed Critical 주식회사 코인플러그
Publication of WO2018080206A1 publication Critical patent/WO2018080206A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0655—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed centrally
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3825—Use of electronic signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3827—Use of message hashing

Definitions

  • a method for issuing and paying a currency using a Merkle tree structure in a UTXO based protocol, and a server using the same more specifically, (a) call recipient information for issuing the call from a currency issuer, (ii) the issue value of the currency issuer, (iii) the currency issuer's public key, and (iv) the currency issuer's public key and (iii) the currency issuer's private key. If a call issuing transaction is obtained, the call issuing transaction and the validity of the call issuing agent are checked to be valid, and if it is valid, the call issuing transaction is registered or registered in a private blockchain database, and the call issuing transaction is supported.
  • the call issuing private transaction ID indicating the location information on the private blockchain database Provide or provide at least some of the issuer and the call recipient, and (b) if a predetermined condition is met, a specific hash value generated by applying a hash function to the call issuing transaction and at least a match with the particular hash value. And register or register a representative hash value generated by calculating one neighbor hash value or a processed value of the representative hash value in a public blockchain database, and wherein the representative hash value or the processed value of the representative hash value is processed.
  • the present invention relates to a method for obtaining or obtaining a currency issuing public transaction ID indicating location information on a public blockchain database, and a server using the same. Furthermore, the present invention relates to a method for payment of a user's payment and a server using the same.
  • currency is a means of exchange that functions as a means of distribution or means of payment, and means the money officially designated and used by the state, ie payment and commercial distribution units.
  • a specific exchange means used only within a specific organization may be one currency.
  • central banks issue or manage currencies
  • commercial banks use currencies issued by central banks.
  • the interbank payments at commercial banks are made through the central bank's payment system, and do not involve actual cash movement. That is, the payment is made by depositing or withdrawing the payment amount for each bank from the account of each bank opened in the central bank.
  • the present invention aims to solve all the above-mentioned problems.
  • Another object of the present invention is to provide a method and a server for securing security and forgery / falsification by using a hash function and encryption technology for information such as currency issuance or payment of a currency.
  • Another object of the present invention is to provide a method and a server which can prevent problems such as duplicate payment of a currency in advance by registering information on issuing or paying a currency in a blockchain of a virtual currency. .
  • Another object of the present invention is to provide a method and a server for always checking the latest settlement information even without proceeding with the settlement process between the central bank and the commercial bank.
  • a method for issuing a currency comprising: (a) (i) call recipient information for issuing the call from a call issuer, (ii) issuing amount of the call, and (iii) the call issuer. If a currency issuing transaction is obtained that includes a public key of and (iv) a signature value of the currency issuer that signed (i), (ii), and (iii) with the currency issuer's private key, (I) the call recipient information, (ii) the issue amount of the call, (iii) the public key of the call issuer, and (iv) the signature of the call issuer, if valid by verifying the validity of the currency issuing transaction and the currency issuer.
  • the method comprising supporting the chain block group private calls issued private transaction ID that indicates the position information on the issuer database and the call, or to provide service to at least some of the call recipient; And (b) a predetermined condition, wherein the predetermined condition is a triggering condition for registering a predetermined hash value in a public blockchain database.
  • register or register a representative hash value generated by calculating at least one neighboring hash value matching the specific hash value or a processed value of the representative hash value in the public blockchain database, and the public blockchain database.
  • a location on the public blockchain database of the representative hash value or the processed value of the representative hash value registered at Assisting in obtaining or obtaining a call issuing public transaction ID representing information; There is provided a method comprising a.
  • a method of making a payment of a currency in a method of making a payment of a currency, (a) using at least one unused first currency of at least some previously unused for payment of the currency from a specific user.
  • the private transaction ID (ii) call recipient information, (iii) payment amount paid, (iv) the public key of the particular user and (v) the private key of the particular user, the (i), (ii), (iii) ), If a second currency use transaction is obtained that includes the signature value of the particular user who signed (iv), the server uses the second currency by referring to the balance of the particular user of the second currency use transaction.
  • the server determines whether the signature value of the specific user is valid, and if it is valid, in the state of storing the second currency use transaction in a storage unit, the server is paid by at least one other user and pays the specific user.
  • Second Call Use Fry Providing or providing a comb transaction ID and a third currency usage private transaction ID to at least some of the specific user, the specific recipient, and the other user; And (c) a predetermined condition, wherein the predetermined condition is a triggering condition for registering a predetermined hash value in the public blockchain database.
  • a method comprising a.
  • a server for issuing a call comprising: (i) call recipient information for issuing the call from the call issuer, (ii) the issue amount of the call, and (iii) the call issuer.
  • a communication unit for obtaining a call issuing transaction comprising a public key and (iv) a signature value of the call issuer who signed the (i), (ii) and (iii) with the call issuer's private key; And (i) the call recipient information, (ii) the issue amount of the call, (iii) the public issuer's public key, and (iv) if the obtained currency issuing transaction and the currency issuer are valid and valid.
  • Support for registering or registering the currency issuance transaction including the signature value of the currency issuer in a private blockchain database, the currency issuance indicating a location on the private blockchain database of the currency issuance transaction registered in the private blockchain database;
  • Support for registering or registering, and obtaining or obtaining a currency issuing public transaction ID representing location information on the public blockchain database of the representative hash value or the processed value of the representative hash value registered in the public blockchain database.
  • a processor to perform a process for performing the process; A server comprising a is provided.
  • the server for payment of a currency at least one unused first currency use private transaction ID which has been previously used (i) for payment of the currency from a specific user. , (ii) call recipient information, (iii) payment amount paid, (iv) the public key of the particular user, and (v) the private key of the particular user, wherein (i), (ii), (iii), and a communication unit for obtaining a second call use transaction including a signature value of the specific user who signed (iv): and the second call use transaction with reference to the balance of the specific user of the obtained second call use transaction; By confirming the payment settlement method of the payment, the balance of the specific user is greater than the payment payment amount, so that the payment settlement method of the second currency use transaction is "immediate payment payment”.
  • At least Offsetting the second currency use transaction and the third currency use transactions when at least one third currency use transaction paid by one or more other users and paying the specific user satisfies a predetermined offsetting condition.
  • register or register the offset-based second currency use transaction and the third currency use transaction in a private blockchain database and register the second currency use transaction and the third currency registered in the private blockchain database.
  • a predetermined condition wherein the predetermined condition is a triggering condition for registering a predetermined hash value in the public blockchain database.
  • the specific hash value is (1) the first hash value.
  • 2 is a hash value generated by applying a hash function to a currency use transaction, or (2) a hash value generated by applying a hash function to the second currency use transaction and the third currency use transaction, respectively, and matches with the specific hash value.
  • register or register a representative hash value generated by calculating at least one neighboring hash value or a processed value of the representative hash value in the public blockchain database, and the representative hash value registered in the public blockchain database. Or positioning the representative hash value on the public blockchain database.
  • a server comprising a is provided.
  • a computer readable recording medium for recording a computer program for executing the method of the present invention is further provided.
  • the present invention can improve the reliability and security of the issuing and payment settlement information of the currency by registering the issuing and payment settlement information of the currency in the blockchain of the virtual currency so that copying or forgery is impossible.
  • the present invention can improve the reliability and security of the issued and paid payment information of the currency by ensuring that the security of the issued and paid payment information of the currency by using a hash function and encryption technology, and forgery / modulation is impossible. .
  • the present invention by registering the information on the issuance and payment settlement of the currency in the blockchain of the virtual currency it is possible to prevent problems such as duplicate payment of the currency in advance.
  • the present invention can improve the convenience of users by always checking the latest settlement information settled even without proceeding the settlement process between the central bank and the commercial bank.
  • FIG. 1 schematically illustrates a server for issuing a call according to an embodiment of the present invention
  • 3 and 4 schematically illustrate a process of registering a currency issuing transaction in the public blockchain database according to an embodiment of the present invention
  • FIG. 5 schematically illustrates a method of registering a currency issuer for issuing a currency in a method for issuing a currency according to an embodiment of the present invention
  • FIG. 6A schematically illustrates a method of making an instant payment payment in accordance with an embodiment of the present invention
  • 6B schematically illustrates a method for making a delayed payment settlement of a currency in accordance with one embodiment of the present invention.
  • the word limited to the word “specific” herein is a concept associated with the main subject of the action
  • the word limited to the word “related” is a concept associated with other subjects than the main subject, in the following description Since the concept can be distinguished by the context, “specific” and “related” may be omitted. However, in the claims, “specific” and “related” are described to clearly understand the meaning.
  • the server 100 may include a communication unit 110 and a processor 120.
  • the same reference numerals are used for the convenience of description and are not intended to mean that these individual devices are the same.
  • the server may be configured differently to perform the method, or the method may be performed through the same server 100.
  • server 100 is typically a computing device (eg, a device that may include components of a computer processor, memory, storage, input and output devices, other conventional computing devices; electronic communications such as routers, switches, etc.). Desired system performance using a combination of a device; an electronic information storage system such as network attached storage (NAS) and a storage area network (SAN) and computer software (ie, instructions that cause a computing device to function in a particular manner). It may be to achieve.
  • NAS network attached storage
  • SAN storage area network
  • the communication unit 110 of such a computing device may transmit and receive a request and a response with another computing device to be interlocked.
  • the request and response may be made by the same TCP session, but are not limited thereto.
  • it may be transmitted and received as a UDP datagram.
  • the processor 120 of the computing device may include a hardware configuration such as a micro processing unit (MPU) or a central processing unit (CPU), a cache memory, a data bus, and the like.
  • the operating system may further include a software configuration of an application performing a specific purpose.
  • a currency issuer A including a central bank of a specific country or a currency management entity of a specific group generates and transmits a currency issuance transaction TrxA through a terminal to issue a currency (S100)
  • the server 100 The call issuing transaction TrxA is obtained through the communication unit 110.
  • the currency issuance transaction is composed of (i) the recipient's information of the call, (ii) the issue amount of the call, (iii) the public key of the call issuer, and (iv) the private key of the call issuer. (i) the recipient's information of the call, (ii) the issue amount of the call, and (iii) the signature of the call issuer who signed the call issuer's public key.
  • the receiver information of the call may be a public key of a specific user registered as a call user as information on the receiver of the issued call, and the public key of the call receiver and the public key of the call issuer are registered in advance in the server 100.
  • the registration information may be registered with the server 100 at a corresponding time, and the registration information may be a publisher or a user having a private key and a public key, and has registered his or her public key with the server 100. Will be described in other operations.
  • the call issuer A may have a public key of the call receiver B as information about the call receiver B in advance.
  • the currency issuance transaction has a data format of 1. payment payment method, 2. previous transaction ID, 3. recipient, 4. issue amount, 5. issuer public key, 6. issuer signature value.
  • the present invention is not limited thereto.
  • Payment methods may include“ immediate payments ”and“ delayed payments, ”“ immediate payments ”allow for immediate processing of currency-related transactions, and“ deferred payments ”for currency until certain conditions are met. It may be to delay the processing of the associated transaction.
  • “delayed payment” means that if the amount for the payment is insufficient, the payment of more than the balance can be offset against the amount received after the payment to solve the liquidity problem. .
  • “immediate payment” is set by default, or the payment issuance method for a currency issuing transaction. You can also include no data format.
  • Former Transaction ID contains information about the balance of the issuer or user. Private transaction ID representing location information on the private blockchain database or public blockchain database where transactions previously created or traded with respect to the currency are registered. Or as a public transaction ID, the issuance of a currency may result in the creation of a new currency and thus no previous transaction ID. Also, “3. Recipient ”can be the public key (PubB) of the call recipient who will receive the issued call,“ 4. Issuance amount ”may be the amount of currency to be issued,“ 5. Issuer public key ”may be a public key (PubA) registered by the issuer,“ 6. Issuer signature value ”may be a signature value (SignPrivA (1, 2, 3, 4, 5)) of 1, 2, 3, 4, 5 signed by the currency issuer with the private key.
  • the processor 120 of the server 100 may then (i) call recipient information obtained through the communication unit 110, (ii) the amount of calls issued, (iii) the public key of the call issuer, and (iv) the signature of the call issuer.
  • the validity of the currency issuance transaction (TrxA) and the currency issuer including the value is checked (S110).
  • the processor 120 of the server 100 checks whether the data format of the call issuance transaction TrxA is valid, whether the call receiver is valid, whether the call issuer's public key is valid, and whether the call issuer's signature value is valid. To confirm the validity of the currency issuance transaction (TrxA).
  • a call receiver obtained by using the call issuer's public key against the call issuer's signature value, and by verifying that the call issuer's public key matches the value contained in the call issue transaction (TrxA). And validity of the public key of the currency issuer.
  • the signature value of the currency issuer using the currency issuer's public key, not only the validity of the signature value of the currency issuer can be confirmed, but also the validity of the currency issuer can be verified through the currency issuer's public key.
  • the server 100 is valid (S110) (S210), (i) call recipient information, (ii) the amount of calls issued, (iii) the public key of the call issuer, and (iv) the signature of the call issuer.
  • a currency issuance transaction (TrxA) containing a value in a private blockchain database (S211), and a currency representing location information on a private blockchain database of a currency issuance transaction (TrxA) registered in a private blockchain database.
  • the issue private transaction ID (PrivTxid) may be provided to or provided to at least some of the call issuer A and the call receiver B (S212, S213).
  • the server 100 may provide or support the call issuer A to provide a response indicating a failure including an error message (S221).
  • the server 100 in response to the valid verification result, the server 100, if a predetermined condition, for example, a triggering condition for registering a predetermined hash value in the public blockchain database is satisfied (S230), (i) call recipient information, ( a specific hash value (hash (TrxA)) generated by applying a hash function to a currency issuance transaction (TrxA), which includes ii) the amount of currency issued, (iii) the currency issuer's public key, and (iv) the currency issuer's signature value; By calculating at least one neighboring hash value matching a specific hash value, a representative hash value or a value obtained by processing the representative hash value is generated as a Merkle root (S231), and the representative hash value or the representative hash value that is the generated Merkle root is processed.
  • a predetermined condition for example, a triggering condition for registering a predetermined hash value in the public blockchain database is satisfied (S230), (i) call recipient information, (
  • a public call issued transaction identifier represents the position information on the blocks of the root public database chain or obtained (S233).
  • the server 100 may obtain an OP message corresponding to the call issuance public transaction ID (PubTxid) from the public blockchain database 200.
  • the operation of a specific hash value and at least one neighboring hash value may be performed by various hash functions, and the hash function may be a MD4 function, an MD5 function, a SHA-0 function, a SHA-1 function, a SHA-224 function, It will be appreciated by those skilled in the art that the present invention may include, but is not limited to, an SHA-256 function, an SHA-384 function, an SHA-512 function, and an HAS-160 function. For example, Triple SHA256 would be possible.
  • the server 100 may store and manage a specific hash value and at least one neighbor hash value in a predetermined data structure.
  • the data structure may vary, for example, may be a merkle tree structure.
  • the calculation of a specific hash value and at least one neighboring hash value may be performed through a merkle tree.
  • the server 100 may support to generate or generate a merkle tree in which a specific hash value is assigned to a specific leaf node, and if a predetermined condition is satisfied, at least one other leaf matching the specific hash value.
  • a representative hash value or a processed value of the representative hash value, which is a Merkle root generated by calculating a hash value assigned to a node, may be registered or registered in the public blockchain database 200.
  • (x1) server 100 supports (i) calculating or calculating hash values of sibling nodes of nodes to which specific hash values and (ii) specific hash values are assigned. It can support assigning or assigning a hash value to the parent node of nodes. (x2) If the parent node is the root node of the Merkle tree, the hash value assigned to the parent node becomes the representative hash value. (x3) On the other hand, if the parent node is not the root node of the Merkle tree, the server 100 repeatedly performs (x1) to (x3) by using a hash value assigned to the parent node as a specific hash value.
  • the server 100 supports registering or registering the hash value finally assigned to the root node of the Merkle tree as the representative hash value in the public blockchain database 200.
  • a value obtained by processing the representative hash value may be registered.
  • a result value of performing a hex operation may be registered in the representative hash value.
  • the server 100 stores a specific hash value and at least one neighbor hash value in a predetermined first data structure, and then stores and manages a second data structure having the same form as the first data structure,
  • the data structure and the second data structure may be connected in a chain form.
  • first data structure and the second data structure are Merkle trees as in the above-described example
  • a root value of the first data structure or a hash value of the root value may be assigned to the first leaf node of the second data structure.
  • the integrity of the data may be more guaranteed by verifying the first data structure.
  • the verification of the second data structure will be described later.
  • the first leaf node of the first Merkle tree may be assigned a hash value or a processed value of predetermined message data consisting of text, numbers, or symbols. have.
  • a hash value of an input message initially given by the server 100 may be assigned when generating the merkle tree.
  • 3 and 4 illustrate an example of a merkle tree generated according to an embodiment of the present invention.
  • sha256 coinplug_unique_message
  • the server 100 may support to calculate or calculate (i) a specific hash value assigned to the h2 node and (ii) a hash value assigned to the h3 node that is a sibling node of the h2 node.
  • the hash value for the operation value is assigned to the parent node (h23 node) of the h2 node and the h3 node.
  • the server 100 may repeat the above process by using the hash value assigned to the h23 node as a specific hash value. That is, the hash value assigned to the h23 node can be used as a specific hash value, and the hash value assigned to the h23 node and the hash value assigned to the h01 node can be calculated and assigned to the parent node (h0123 node) of the h23 node and the h01 node. have.
  • the server 100 registers or registers a value (hex (h ⁇ node_index ⁇ )) of the hash value assigned to the h0123 node in the public blockchain database 200.
  • the above-mentioned predetermined conditions are (i) a condition in which transactions related to a currency are generated by a predetermined number, (ii) a condition in which a predetermined time elapses, (iii) a condition in which a block is generated in a private blockchain, (iv) ) May include at least one of conditions for service characteristics.
  • the transaction related to the currency may include issuer registration, payment settlement of a currency, user registration, and the like, which will be described later in addition to issuing a currency.
  • the Merkle tree may be generated, and the root value of the Merkle tree may be registered or supported in the public blockchain database 200.
  • the server 100 may generate the root value of the aforementioned Merkle tree on a predetermined time unit (condition (ii) above). In this case, when a predetermined time elapses, the server 100 may generate a Merkle tree by using input values up to that time and register or register the root value of the Merkle tree in the public blockchain database 200.
  • a value may not be assigned to a sibling node of a node to which a specific hash value of the Merkle tree is assigned. If the hash value is not assigned to the sibling node of the node to which the specific hash value is assigned even though the predetermined condition is satisfied as described above, the server 100 supports to assign or allocate the predetermined hash value to the sibling node. This allows the root value of the Merkle tree to be calculated. For example, server 100 may support assigning or assigning a particular hash value to a sibling node.
  • the service characteristic may include at least one of cost information provided by a call issuer requesting a call issuance, time zone information at which a call issuing transaction is registered, area information at which a call issuing transaction registration service is performed, and company type information requesting a call issuing transaction registration. It can be part of it.
  • the present invention is not limited to the above description and includes various condition information in which a generally accepted differential service can be provided.
  • the server 120 if a new Merkle tree generation starts and a predetermined condition is satisfied in the absence of a call issuing transaction, the server 120 generates a Merkle tree in which predetermined message data is assigned to the first leaf node and the second leaf node. Or to create or register the root value of the Merkle tree or a processed value thereof in the public blockchain database 120. In this case, a two leaf node Merkle tree may be created.
  • the server 100 stores a specific hash value and at least one neighboring hash value in a predetermined first data structure, and then stores and manages a second data structure having the same form as the first data structure.
  • the first data structure and the second data structure may be connected in a chain form.
  • a root value of the first data structure or a hash value of the root value may be assigned to the first leaf node of the second data structure.
  • FIG. 4 illustrates a Merkle tree generated as a second data structure according to an embodiment of the present invention.
  • the present invention has an advantage of improving data integrity by easily tracking even when data is tampered with by connecting a plurality of data structures generated when a transaction occurs.
  • the server 100 checks whether the call issuer A is valid and when the call issuer A is valid ( In operation S310, a random nonce RN may be delivered to or supported by the call issuer A in operation S311.
  • a random nonce RN may be delivered to or supported by the call issuer A in operation S311.
  • the server 100 may provide or provide a response indicating the issuer verification failure to the call issuer A. It may support (S321).
  • the method for determining whether the issuer A is valid is not limited thereto, and the validity of the issuer A may be determined using, for example, a time stamp. For reference, the following description will be given as an example of determining validity using a random nonce.
  • the server 100 100 checks whether the currency issuer A of the obtained public key is valid.
  • the validity of the call issuer (A) may use a public key infrastructure (PKI) certificate or use the identification information of the call issuer (A), but is not limited thereto.
  • PKI public key infrastructure
  • identification information that can verify a specific issuer through a public key-based certificate such as a public certificate or an OPSign certificate, or to prove the identity of an individual, a bank, or an organization such as a social security number, a passport, a corporate registration number, and a business registration number. You can check the currency issuer through.
  • RN a random nonce signature value
  • S312 a random nonce signature value
  • the server 100 determines whether the random nonce signature value is normally signed. Validate using the public key of the currency issuer (A). That is, the server 100 checks the random nonce RN from the random nonce signature value using the call issuer's public key, and checks whether the confirmed random nonce RN matches the random nonce RN delivered to the call issuer. If it matches, it verifies that it is a valid signature.
  • the server 100 issues a publisher registration transaction (RN, SignPrivA (RN) including a random nonce, a random nonce signature value, and the call issuer's public key.
  • PubA publisher registration transaction
  • PubA to register or register in the private blockchain database (S331), and includes a publisher registration private transaction ID (PrivTxid) indicating location information on the private blockchain database of the publisher registration transaction registered in the private blockchain database.
  • the server 100 may support or provide the call issuer A with a response including a message indicating that the signature value verification failed. There is (S341).
  • the server 100 satisfies a predetermined condition, for example, a triggering condition for registering a predetermined hash value in the public blockchain database (S350), random nonce, and random nonce signature.
  • a predetermined condition for example, a triggering condition for registering a predetermined hash value in the public blockchain database (S350), random nonce, and random nonce signature.
  • a specific hash value (hash (RN, SignPrivA (RN), PubA)) generated by applying a hash function to the issuer registration transaction that includes the value and the currency issuer's public key, and at least one neighboring hash value that matches the particular hash value.
  • a representative hash value or a processed value of the representative hash value generated by calculating as a Merkle root (S351), and register the processed hash value or the representative hash value, which is the generated Merkle root, in the public blockchain database or It supports to register (S352), the public of the value processed the representative hash value or representative hash value that is the Merkle root registered in the public blockchain database 200 Published register that indicates the position information on the registered chain database 200 can be supported to obtain or acquire a public transaction ID (PubTxid) (S352).
  • the representative hash value or the processed value of the representative hash value may be generated by the Merkle tree as described in FIG. 2.
  • the server 100 may obtain an OP message corresponding to the issuer registration public transaction ID (PubTxid) from the public blockchain database 200.
  • the server 100 transmits the communication unit 110. It receives through (S400).
  • the second currency use transaction may include (i) at least one or more unused first currency use transaction IDs, (ii) call recipient information, (iii) payment amount, and (iv) a specific user. And (v) at least one or more unused first currency usage transaction IDs that have previously been at least partially unused by the particular user's private key, (ii) call recipient information, (iii) payment amount paid, and (iv) It can contain the signature value of the specific user who signed the user's public key.
  • at least one or more unused first currency use transaction IDs, which are previously used are currency related transactions in which a usage amount is left with respect to payment payments received by a specific user from a currency issuer or other users.
  • the sum of the unused amounts of all owned first currency usage transactions may be the current balance of a particular user.
  • the call receiver information may be a public key of a call receiver that receives a call-paid currency among users registered as call users as information about a callee of a call-paid currency, and the public key of the call receiver and a specific user (C ) Is registered in the server 100 in advance, or may be registered in the server 100 at that time, if necessary, the registration information is issued by a publisher or user with a private key and a public key The key is registered in the server 100, and the description thereof will be described in another operation.
  • the specific user C may previously have a public key of the call receiver as information on the call receiver.
  • the second currency use transaction is 1. payment settlement method, 2. first currency use transaction ID, 3. recipient, 4. use amount, 5. balance, 6. balance owner information, 7. It may have a data format that contains the public key of a particular user, 8. The signature value of a particular user.
  • Payment methods may include“ immediate payments ”and“ delayed payments, ”“ immediate payments ”allow for immediate processing of currency-related transactions, and“ deferred payments ”for currency until certain conditions are met. It may be to delay the processing of the associated transaction. For example, “delayed payment” means that if the amount for the payment is insufficient, the payment of more than the balance can be offset against the amount received after the payment to solve the liquidity problem. .
  • First currency usage transaction ID includes information about the balance of a specific user C and indicates location information on a private blockchain database or a public blockchain database in which a currency usage transaction previously received with respect to the currency is registered.
  • Private transaction ID or public transaction ID which may be about information in a currency usage transaction, including currency usage transactions and some unused amounts paid by the issuer or other users of the currency, and owned by a particular user (C)
  • the sum of the balances of all the first currency use transactions may be a balance currently owned by a particular user (C).
  • “3. Recipient ” may be the public key (PubB) of the recipient of the currency to receive the currency in which payment is made, and“ 4.
  • Usage amount may be the amount to be paid and paid,“ 5.
  • Balance is the amount remaining after payment in the balance of a specific user (C). There is no balance due to payment or it may have a negative value.
  • the public key of a specific user may be the public key of a specific user (C) who wishes to pay now,“ 8.
  • Signature value of a specific user is a signature value of 1, 2, 3, 4, 5, 6, and 7 (SignPrivC (1, 2, 3, 4, 5, 6, 7) signed by a specific user C with a private key. May be).
  • the server 100 checks the payment settlement method of the second currency use transaction with reference to the balance of the specific user (C). In this case, if the balance owned by the specific user C is greater than the payment amount, the payment is immediately checked. If the balance owned by the specific user C is less than the payment amount, the balance may be confirmed as “delayed payment”. . In addition, depending on the payment settlement method included in the second currency transaction, it can be identified as “immediate payment settlement” and “delayed payment settlement.” In particular, the payment settlement method included in the second currency usage transaction is referred to as “immediate payment settlement.” If it is entered but the balance owned by the user C is less than the payment settlement, it may be determined as "delayed payment settlement”.
  • the server 100 determines whether the signature value of a specific user (C) of the second currency use transaction (TrxC) is valid If it is valid (S430), the second currency use transaction (TrxC) is registered in the private blockchain database (S431), the location information on the private blockchain database of the second currency use transaction (TrxC) registered in the private blockchain database
  • the second call usage private transaction ID (PrivTxid) may be provided to or provided to at least some of the specific user C and the call receiver (S432).
  • the server 100 may provide or support a specific user C to provide or provide a response indicating a failure including an error message (S441).
  • the server 100 when a predetermined condition, for example, a triggering condition is satisfied (S450), in response to a valid confirmation result, the server 100 generates a specific hash value (hash) generated by applying a hash function to the second currency use transaction TrxC. (TrxC)) and a neighbor hash value matched with a specific hash value to generate a representative hash value or a processed value of the representative hash value as a Merkle root (S451), and generates a representative hash value or a representative hash value which is the generated Merkle root.
  • a specific hash value hash
  • TrxC second currency use transaction TrxC.
  • a second currency use public transaction ID Txid representing location information on the chain database may be obtained or acquired.
  • the representative hash value or the processed value of the representative hash value may be generated by the Merkle tree as described in FIG. 2.
  • the server 100 may obtain an OP message corresponding to the second call use public transaction ID (PubTxid) from the public blockchain database 200.
  • the server 100 determines whether the signature value of a specific user (C) of the second currency use transaction (TrxC) is valid. If it is valid (S470), the second currency use transaction (TrxC) is stored in a recording device such as a netting database, a storage unit, a memory (S471). However, if the verification result is not a valid signature value (S480), the server 100 may provide or support a specific user C to provide or provide a response indicating a failure including an error message (S481).
  • At least one third currency use transaction which is paid by at least one other user D and has a specific user C as a payee, while the second currency use transaction TrxC is stored in the storage device.
  • TrxD When TrxD) is obtained (S472), the server 100 checks whether the acquired third currency use transaction TrxD and the second currency use transaction TrxC satisfy the offset conditions.
  • the third currency use transaction (TrxD) may be a currency use transaction stored in the storage device as a "delayed payment" to a specific user (C), in this case, the server 100 is "delayed payment"
  • the offset may be performed in response to the second currency use transaction TrxC, and the server 100 may set the third currency use transaction as an offset condition. If (TrxD) is obtained, the offsetting process is performed, and it is determined by the offsetting process whether the balance of the specific user C has a value of "0" or more.
  • the server 100 stores the acquired third currency use transaction (TrxD) on the recording medium, and another third currency. Wait for the usage transaction to be acquired (S501).
  • the server 100 offsets the second currency use transaction (TrxC) and at least one third currency use transaction (TrxD).
  • the plurality of third currency transactions are generated by a plurality of currency transactions generated by a specific other user, a plurality of currency transactions generated by a plurality of other users, or generated by a plurality of other users. It may be a plurality of currency transactions created by other users.
  • the server 100 may form a specific user (C). And a "delayed payment" between multiple other users, forming a circular loop that can offset all linked currency-using transactions.
  • the server 100 may offset all currency use transactions, which are "delayed payment settlement" forming a circular ring.
  • user A creates a currency-enabled transaction A with "deferred payment” to user B
  • user B creates a currency-enabled transaction B with “deferred payment” to user C
  • user C Deferred payment "creates a currency-enabled transaction C
  • User D creates a currency-enabled transaction D with" deferred payment "to User A, allowing users A, User B, User C, and User D to When a circular ring of payees is formed, the server 100 selects currency use transaction A, currency use transaction B, currency use transaction C, and currency use transaction D generated by user A, user B, user C, and user D. Offset can be processed.
  • each currency use transaction that is “deferred payment settlement” must be satisfied, and if the payment settlement amounts do not match, each currency use transaction that is "delay payment settlement” If another currency use transaction satisfies the offset processing condition and each of the " delayed payment settlement " currency use transactions in the form of a purifying ring satisfies the offset processing condition, the offset processing can be performed.
  • the server 100 supports to register or register the offsetted second currency use transaction (TrxC) and at least one third currency use transaction (TrxD) in the private blockchain database (S491), and the private blockchain database.
  • the ID PrivTid may be provided to or provided to at least some of a specific user C, a call receiver, and at least one other user D (S492 and S493).
  • the information stored in the recording medium that is, the second call use transaction TrxC and the obtained at least one third call use transaction TrxD may be deleted.
  • the server 100 corresponds to the offset processing of the second currency use transaction TrxC and the at least one third currency use transaction TrxD, and if a predetermined condition, for example, a triggering condition is satisfied (S510), the offset process.
  • a predetermined condition for example, a triggering condition is satisfied (S510)
  • Merkle root a representative hash value generated by calculating a specific hash value generated by applying a hash function to the second currency using transaction and at least one neighboring hash value matching the specific hash value, or a value obtained by processing the representative hash value
  • S511 supports to register or register in the public blockchain database
  • the server 100 may generate a representative hash generated by calculating a specific hash value generated by applying a hash function to each of the at least one third currency use transaction processed and at least one neighboring hash value matching the specific hash value.
  • a value or a processed value of the representative hash value may be generated as a Merkle root (S511), and may be registered or registered in the public blockchain database (S512). That is, the server 100 may support to register or register information on all the currency use transactions that have been offset in the public blockchain database 200.
  • the server 100 may include information indicating location information on the public blockchain database of the Merkle root corresponding to the second currency use transaction registered in the public blockchain database and the at least one third currency use transaction. It may support to acquire or obtain a 2 call usage public transaction ID (PubTxid) and at least one third call usage public transaction ID (PubTxid) (S513).
  • the representative hash value or the processed value of the representative hash value may be generated by the Merkle tree as described in FIG. 2.
  • the server 100 may obtain an OP message corresponding to each of the second call use public transaction ID PubTxid and the third call use public transaction ID PubTxid from the public blockchain database 200.
  • the process of registering a specific user who is a call user by the server 100 is as follows.
  • the registration of a specific user also performs the same method as the registration of the call issuer in FIG. 5, and similar parts are omitted since the description in FIG. 5 can be understood.
  • the server 100 checks whether the specific user C is valid, and if the specific user C is valid, randomly sets a random nonce to the specific user C. Can be delivered to or supported). In addition, when a specific user C is not valid, the server 100 may provide or support a response indicating a user confirmation failure to the specific user C.
  • the server 100 verifies whether the random nonce signature value is normally signed using the specific user's public key. .
  • the server 100 registers or registers a user registration transaction including a random nonce, a random nonce signature value, and a specific user's public key in the private blockchain database.
  • the user registration private transaction ID (PrivTxid) indicating location information on the private blockchain database of the user registration transaction registered in the private blockchain database may be provided or provided to a specific user (C).
  • the server 100 may provide or provide a response indicating the signature value verification failure to the specific user 111.
  • the server 100 may perform a user registration transaction including a random nonce, a random nonce signature value, and a specific user's public key if a predetermined condition, for example, a triggering condition is satisfied.
  • a predetermined condition for example, a triggering condition is satisfied.
  • a user registration public transaction ID indicating location information on the public blockchain database of the representative hash value or the processed value of the representative hash value registered in the public blockchain database 200. PubTxid) can be obtained or supported to acquire.
  • the representative hash value or the processed value of the representative hash value may be generated by the Merkle tree as described in FIG. 2.
  • the call receiver B, the call user C, and the call user D described above may be commercial banks or general individuals.
  • the embodiments according to the present invention described above may be implemented in the form of program instructions that may be executed by various computer components, and may be recorded in a computer-readable recording medium.
  • the computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination.
  • Program instructions recorded on the computer-readable recording medium may be those specially designed and configured for the present invention, or may be known and available to those skilled in the computer software arts.
  • Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs, DVDs, and magneto-optical media such as floptical disks. media), and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like.
  • Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.
  • the hardware device may be configured to operate as one or more software modules to perform the process according to the invention, and vice versa.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Development Economics (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

La présente invention concerne un procédé consistant à : obtenir une transaction d'émission de monnaie permettant une émission de monnaie à partir d'un émetteur de monnaie comprenant (i) des informations de destinataire de monnaie, (ii) un montant émis de la monnaie, (iii) une clé publique de l'émetteur de monnaie, et (iv) une valeur de signature signant les (i), (ii) et (iii) avec une clé privée de l'émetteur de monnaie, enregistrer la transaction d'émission de monnaie dans une base de données de chaînes de blocs privée, et fournir, à l'émetteur de monnaie ou au destinataire de monnaie, un ID de transaction privé d'émission de monnaie indiquant des informations de position de la transaction d'émission de monnaie dans la base de données de chaînes de blocs privée ; et (b) enregistrer une valeur de hachage spécifique et une valeur de hachage représentative générée à partir d'une valeur de hachage voisine correspondant à la valeur de hachage spécifique dans une base de données de chaînes de blocs publique, et obtenir un ID de transaction public d'émission de monnaie indiquant les informations de position de la valeur de hachage représentative dans la base de données de chaînes de blocs publique.
PCT/KR2017/011938 2016-10-26 2017-10-26 Procédé d'émission de monnaie et d'exécution de paiement au moyen d'une structure arborescente de merkle de protocole orienté utxo et serveur l'utilisant WO2018080206A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020160140164A KR101837167B1 (ko) 2016-10-26 2016-10-26 Utxo 기반 프로토콜에서 머클 트리 구조를 사용하여 통화를 발행 및 지급 결제하는 방법과 이를 이용한 서버
KR10-2016-0140164 2016-10-26

Publications (1)

Publication Number Publication Date
WO2018080206A1 true WO2018080206A1 (fr) 2018-05-03

Family

ID=61727734

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/011938 WO2018080206A1 (fr) 2016-10-26 2017-10-26 Procédé d'émission de monnaie et d'exécution de paiement au moyen d'une structure arborescente de merkle de protocole orienté utxo et serveur l'utilisant

Country Status (2)

Country Link
KR (1) KR101837167B1 (fr)
WO (1) WO2018080206A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109218303A (zh) * 2018-09-10 2019-01-15 浙江天脉领域科技有限公司 一种同源异构链网融合的新型区块链跨链方法
CN109274837A (zh) * 2018-08-22 2019-01-25 北京航空航天大学 基于区块链技术的电话来源可追溯方法及装置
CN109472578A (zh) * 2018-10-16 2019-03-15 东方银谷（北京）投资管理有限公司 数字资产的处理方法及装置
CN110688425A (zh) * 2018-07-06 2020-01-14 国际商业机器公司 针对区块链的条件性延期事务
CN111476555A (zh) * 2020-03-23 2020-07-31 深圳华数云计算技术有限公司 一种数字货币数据处理方法、系统和存储介质
CN111814175A (zh) * 2020-09-15 2020-10-23 北京东方通科技股份有限公司 一种区块链间跨链信息传输控制系统
CN115660679A (zh) * 2022-10-14 2023-01-31 重庆移通学院 一种基于哈希锁定的去中心化安全交易方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102077397B1 (ko) * 2018-07-23 2020-02-13 주식회사 더볼터 PoP 기반 블록체인에서의 동적 시간 지연 기반의 체인 연결 방법 및 시스템
CN110838064B (zh) * 2019-10-12 2022-05-20 华中科技大学 一种基于Fabric区块链平台实现资产溯源的方法及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101575030B1 (ko) * 2014-07-11 2015-12-07 조선대학교산학협력단 클라우드 상의 공유 데이터에 대한 다중 서명생성방법
KR101637854B1 (ko) * 2015-10-16 2016-07-08 주식회사 코인플러그 블록체인을 기반으로 하는 공인인증서 발급시스템과 이를 이용한 블록체인을 기반으로 하는 공인인증서 발급방법 및 블록체인을 기반으로 하는 공인인증서 인증시스템과 이를 이용한 블록체인을 기반으로 하는 공인인증서 인증방법

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101575030B1 (ko) * 2014-07-11 2015-12-07 조선대학교산학협력단 클라우드 상의 공유 데이터에 대한 다중 서명생성방법
KR101637854B1 (ko) * 2015-10-16 2016-07-08 주식회사 코인플러그 블록체인을 기반으로 하는 공인인증서 발급시스템과 이를 이용한 블록체인을 기반으로 하는 공인인증서 발급방법 및 블록체인을 기반으로 하는 공인인증서 인증시스템과 이를 이용한 블록체인을 기반으로 하는 공인인증서 인증방법

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Bulk Certificate Login Processing", 5 August 2016 (2016-08-05), Retrieved from the Internet <URL:https://github.com/Kangmo/blitz/wiki/fl> *
"Data Forgery Detection in Private Block Chain Using Public Block Chain", 5 August 2016 (2016-08-05), Retrieved from the Internet <URL:https://github.com/Kangmo/blitz/wiki> *
"Why Block Chain Could be Fatal to Your Business", CIO KOREA, 7 September 2016 (2016-09-07), Retrieved from the Internet <URL:http://www.ciokorea.com/news/31161> *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110688425A (zh) * 2018-07-06 2020-01-14 国际商业机器公司 针对区块链的条件性延期事务
CN110688425B (zh) * 2018-07-06 2023-12-22 国际商业机器公司 针对区块链的条件性延期事务的方法和系统
CN109274837A (zh) * 2018-08-22 2019-01-25 北京航空航天大学 基于区块链技术的电话来源可追溯方法及装置
CN109218303A (zh) * 2018-09-10 2019-01-15 浙江天脉领域科技有限公司 一种同源异构链网融合的新型区块链跨链方法
CN109218303B (zh) * 2018-09-10 2020-12-11 浙江天脉领域科技有限公司 一种同源异构链网融合的新型区块链跨链方法
CN109472578A (zh) * 2018-10-16 2019-03-15 东方银谷（北京）投资管理有限公司 数字资产的处理方法及装置
CN111476555A (zh) * 2020-03-23 2020-07-31 深圳华数云计算技术有限公司 一种数字货币数据处理方法、系统和存储介质
CN111814175A (zh) * 2020-09-15 2020-10-23 北京东方通科技股份有限公司 一种区块链间跨链信息传输控制系统
CN111814175B (zh) * 2020-09-15 2020-12-18 北京东方通科技股份有限公司 一种区块链间跨链信息传输控制系统
CN115660679A (zh) * 2022-10-14 2023-01-31 重庆移通学院 一种基于哈希锁定的去中心化安全交易方法

Also Published As

Publication number Publication date
KR101837167B1 (ko) 2018-03-09

Similar Documents

Publication Publication Date Title
WO2018080207A1 (fr) Procédé d&#39;émission de monnaie et d&#39;exécution de paiement par gestion d&#39;une base de données de solde pour chaque bloc d&#39;une chaîne de blocs et serveur l&#39;utilisant
WO2018080206A1 (fr) Procédé d&#39;émission de monnaie et d&#39;exécution de paiement au moyen d&#39;une structure arborescente de merkle de protocole orienté utxo et serveur l&#39;utilisant
US20200259666A1 (en) Methods and systems for using digital signatures to create trusted digital asset transfers
US11669811B2 (en) Blockchain-based digital token utilization
JP7108611B2 (ja) 電子手形管理方法及び装置並びに記憶媒体
CN109691008B (zh) 网络拓扑
WO2018070848A1 (fr) Procédé pour assurer un service de certificats basé sur des contrats intelligents, et serveur l&#39;employant
WO2017192007A2 (fr) Chaîne de blocs permettant de prendre en charge une pluralité de fonctions unidirectionnelles de vérification de blocs
WO2018070784A2 (fr) Procédé d&#39;émission, de remboursement, d&#39;acquittement, de règlement et de révocation d&#39;un coupon électronique par gestion d&#39;une base de données d&#39;équilibre par blocs dans une chaîne de blocs, et serveur l&#39;utilisant
US11108566B2 (en) Methods and systems for using digital signatures to create trusted digital asset transfers
WO2016204572A2 (fr) Système et procédé permettant de vérifier la falsification de pièces justificatives d&#39;institution financière sur la base d&#39;une chaîne de blocs
JP2021524088A (ja) リソース移行データの管理方法及び装置、並びにコンピュータプログラム
WO2018080205A1 (fr) Procédé d&#39;émission de monnaie et d&#39;exécution de paiement au moyen d&#39;un protocole orienté utxo et serveur l&#39;utilisant
WO2019078623A1 (fr) Procédé de paiement à base de chaînes de blocs et serveur de paiement le mettant en œuvre
WO2018070783A2 (fr) Procédé d&#39;émission, d&#39;échange, de remboursement, de règlement et de révocation d&#39;un bon électronique sur la base d&#39;utxo et à l&#39;aide d&#39;une structure arborescente de merkle, et serveur l&#39;utilisant
CN109447605A (zh) 一种基于区块链的链货币兑换方法、装置、设备和介质
US20210182793A1 (en) Distributed ledger system for automated claim adjudication
CN110503429B (zh) 一种去中心化的内容交互方法及系统
WO2019078622A1 (fr) Procédé de paiement basé sur une chaîne de blocs et serveur de paiement l&#39;utilisant
CN112788555B (zh) 跨运营商话费转移结算方法、装置及计算设备
WO2020103573A1 (fr) Procédé et dispositif de signature de transaction de réseau à base de chaîne de blocs, et équipement terminal
KR20200014121A (ko) 블록체인 서비스 제공 방법 및 시스템
KR102331971B1 (ko) 블록체인 기반의 바우처 제공방법 및 시스템
CN115953241A (zh) 基于区块链的资金管理方法和装置
CN113269646A (zh) 一种基于区块链实现票据资产流通的智能合约设计方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17864074

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 02/07/2019)

122 Ep: pct application non-entry in european phase

Ref document number: 17864074

Country of ref document: EP

Kind code of ref document: A1