WO2021125399A1 - 블록체인에서의 스마트 컨트랙트를 이용한 에스크로 거래 방법 및 시스템 - Google Patents
블록체인에서의 스마트 컨트랙트를 이용한 에스크로 거래 방법 및 시스템 Download PDFInfo
- Publication number
- WO2021125399A1 WO2021125399A1 PCT/KR2019/018156 KR2019018156W WO2021125399A1 WO 2021125399 A1 WO2021125399 A1 WO 2021125399A1 KR 2019018156 W KR2019018156 W KR 2019018156W WO 2021125399 A1 WO2021125399 A1 WO 2021125399A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- escrow
- contract
- remittance
- token
- sender
- Prior art date
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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- 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/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- 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/08—Payment architectures
- G06Q20/14—Payment architectures specially adapted for billing systems
-
- 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
-
- 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
-
- 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/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/405—Establishing or using transaction specific rules
-
- 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/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/407—Cancellation of a transaction
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
Definitions
- the description below relates to an escrow transaction method and system using a smart contract in a blockchain.
- Blockchain is a distributed data storage technology that stores data in blocks, connects them in a chain, and replicates and stores them on numerous computers at the same time. It is also called a public transaction ledger. Transaction history is sent to all users participating in a transaction without keeping transaction records on a centralized server, and it can be implemented to prevent data forgery or falsification by sharing and collating information among all transaction participants in each transaction. have.
- 10-2019-0133573 relates to a blockchain transaction system and a method through a smart contract, and an interface to use transactions and services by a smart contract by utilizing the unique characteristics of a blockchain by providing help request information in the network ecosystem, the service provider posts a transaction or contract, and the person who wants to provide help provides help for the related information or the service user agrees to the transaction (signature), etc. button (action)
- a system and method in which cryptocurrency, an incentive, is paid as a reward by classifying the reward system for each activity by grade so that 'participation and sharing' activities can be continuously activated with a single mobile app in the network ecosystem by selecting . is starting
- an escrow transaction method and system are provided that can process the remittance to the recipient when certain conditions are satisfied after depositing the money without immediate remittance.
- a method for escrow transaction in a block chain system comprising: depositing a currency corresponding to the remittance of the sender in an escrow contract included in the block chain system for an escrow transaction from a sender to a receiver; remittance of the currency deposited in the escrow contract to the receiver when a predefined condition for the remittance of the sender is satisfied; and returning the currency deposited in the escrow contract to the sender when a predefined condition for the remittance is not satisfied.
- the depositing of the currency may include: requesting remittance of the currency to a token contract of the blockchain system for which approval is requested from the sender; and receiving a token that is subordinate to the token contract from the token contract and approved according to the request of the sender, and deposits it in the escrow contract as a currency corresponding to the sender's remittance.
- the depositing of the currency may include: receiving an escrow token remittance request from a token contract of the blockchain system that has received a request for escrow remittance from the sender; requesting remittance to the token contract in response to the request for remittance of the escrow token; and depositing a token remitted according to a request to the token contract as a currency corresponding to the remittance of the sender in the escrow contract.
- the escrow transaction method includes the steps of installing the escrow contract according to a request from an owner of the escrow contract; setting the escrow contract in the token contract according to a request from the escrow contract owner; and setting the token contract in the escrow contract according to the control of the token contract.
- the depositing of the currency may include: receiving a token fallback request including meta information related to an escrow transaction from a token contract of the blockchain system that has received a request for remittance from the sender; and receiving a token dependent on the token contract as a currency corresponding to the sender's remittance from the sender through the information on the escrow transaction obtained by parsing the meta information and depositing it in the escrow contract. can do.
- the escrow transaction method includes the steps of installing the escrow contract according to a request from the owner of the escrow contract; and associating the escrow contract with the token contract according to the address of the token contract included in the request from the escrow contract owner.
- the step of remittance of the deposited currency to the recipient may include, when a predefined condition for remittance of the sender is satisfied, according to an escrow reception request requested from a caller specified in the escrow contract, the It may be characterized by requesting a remittance from the escrow contract to the receiver with the token contract of the blockchain system.
- the step of returning the deposited currency to the sender may include, when a predefined condition for the sender's remittance is not satisfied, according to the escrow cancellation request requested from the caller specified in the escrow contract, It may be characterized by requesting a remittance from the escrow contract to the sender with the token contract of the blockchain system.
- the caller may be the owner or the sender of the escrow contract.
- the currency corresponding to the sender's remittance may include a reference currency of the block chain system.
- the currency may include a token subordinate to a token contract that the blockchain system further includes.
- a computer program stored in a computer-readable recording medium in combination with a computer device to execute the method on the computer device.
- At least one processor embodied to execute computer-readable instructions, wherein the at least one processor controls the remittance of the sender to an escrow contract comprised by the blockchain system for an escrow transaction from a sender to a receiver.
- Deposit a corresponding currency and when a predefined condition for the sender's remittance is satisfied, the currency deposited in the escrow contract is remitted to the receiver, and when the predefined condition for the remittance is not satisfied, It provides a computer device, characterized in that for returning the currency deposited in the escrow contract to the sender.
- immediate remittance does not occur, but after depositing money, remittance can be processed to the recipient when certain conditions are satisfied.
- the sender may cancel the remittance.
- FIG. 1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention.
- FIG. 2 is a block diagram illustrating an example of a computer device according to an embodiment of the present invention.
- 3 to 5 are diagrams illustrating an example of an escrow transaction of a reference currency according to an embodiment of the present invention.
- 6 to 8 are diagrams illustrating a first example of an escrow transaction for a token according to an embodiment of the present invention.
- 9 to 12 are diagrams illustrating a second example of an escrow transaction for a token according to an embodiment of the present invention.
- 13 to 16 are diagrams illustrating a third example of an escrow transaction for a token according to an embodiment of the present invention.
- 17 is a flowchart illustrating an example of an escrow transaction method according to an embodiment of the present invention.
- the escrow transaction system may be a blockchain system implemented by at least one computer device, and the escrow transaction method according to the embodiments of the present invention includes at least one computer included in the escrow transaction system. This can be done through the device.
- the computer program according to an embodiment of the present invention may be installed and driven in the computer device, and the computer device may perform the escrow transaction method according to the embodiments of the present invention under the control of the driven computer program.
- the above-described computer program may be stored in a computer-readable recording medium in combination with a computer device to execute the escrow transaction method in the computer.
- FIG. 1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention.
- the network environment of FIG. 1 shows an example including a plurality of electronic devices 110 , 120 , 130 , 140 , a plurality of servers 150 , 160 , and a network 170 .
- FIG. 1 is an example for explaining the invention, and the number of electronic devices or the number of servers is not limited as in FIG. 1 .
- the network environment of FIG. 1 only describes one example of environments applicable to the present embodiments, and the environment applicable to the present embodiments is not limited to the network environment of FIG. 1 .
- the plurality of electronic devices 110 , 120 , 130 , and 140 may be a fixed terminal implemented as a computer device or a mobile terminal.
- Examples of the plurality of electronic devices 110 , 120 , 130 , 140 include a smart phone, a mobile phone, a navigation device, a computer, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), and a portable multimedia player (PMP). ), and tablet PCs.
- PDA personal digital assistant
- PMP portable multimedia player
- FIG. 1 the shape of a smartphone is shown as an example of the electronic device 110 , but in embodiments of the present invention, the electronic device 110 is substantially different from another through the network 170 using a wireless or wired communication method. It may refer to one of various physical computer devices capable of communicating with the electronic devices 120 , 130 , 140 and/or the servers 150 and 160 .
- the communication method is not limited, and not only a communication method using a communication network (eg, a mobile communication network, a wired Internet, a wireless Internet, a broadcasting network) that the network 170 may include, but also short-range wireless communication between devices may be included.
- the network 170 may include a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), and a broadband network (BBN). , the Internet, and the like.
- PAN personal area network
- LAN local area network
- CAN campus area network
- MAN metropolitan area network
- WAN wide area network
- BBN broadband network
- the network 170 may include any one or more of a network topology including a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree, or a hierarchical network, etc. not limited
- Each of the servers 150 and 160 communicates with the plurality of electronic devices 110 , 120 , 130 , 140 and the network 170 through a computer device or a plurality of computers that provide commands, codes, files, contents, services, etc. It can be implemented in devices.
- the server 150 provides a service (eg, a content providing service, a group call service (or a voice conference service) to the plurality of electronic devices 110 , 120 , 130 , and 140 connected through the network 170 ).
- a service eg, a content providing service, a group call service (or a voice conference service)
- a messaging service e.g, a mail service, a social network service, a map service, a translation service, a financial service, a payment service, a search service, a location-based service, etc.
- FIG. 2 is a block diagram illustrating an example of a computer device according to an embodiment of the present invention.
- Each of the plurality of electronic devices 110 , 120 , 130 , 140 or the servers 150 and 160 described above may be implemented by the computer device 200 illustrated in FIG. 2 .
- the computer device 200 may include a memory 210 , a processor 220 , a communication interface 230 , and an input/output interface 240 .
- the memory 210 is a computer-readable recording medium and may include a random access memory (RAM), a read only memory (ROM), and a permanent mass storage device such as a disk drive.
- RAM random access memory
- ROM read only memory
- a permanent mass storage device such as a disk drive.
- a non-volatile mass storage device such as a ROM and a disk drive may be included in the computer device 200 as a separate permanent storage device distinct from the memory 210 .
- the memory 210 may store an operating system and at least one program code. These software components may be loaded into the memory 210 from a computer-readable recording medium separate from the memory 210 .
- the separate computer-readable recording medium may include a computer-readable recording medium such as a floppy drive, a disk, a tape, a DVD/CD-ROM drive, and a memory card.
- the software components may be loaded into the memory 210 through the communication interface 230 instead of a computer-readable recording medium.
- the software components may be loaded into the memory 210 of the computer device 200 based on a computer program installed by files received through the network 170 .
- the processor 220 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input/output operations.
- the instructions may be provided to the processor 220 by the memory 210 or the communication interface 230 .
- the processor 220 may be configured to execute a received instruction according to a program code stored in a recording device such as the memory 210 .
- the communication interface 230 may provide a function for the computer device 200 to communicate with other devices (eg, the storage devices described above) through the network 170 .
- a request, command, data, file, etc. generated by the processor 220 of the computer device 200 according to a program code stored in a recording device such as the memory 210 is transmitted to the network ( 170) to other devices.
- signals, commands, data, files, etc. from other devices may be received by the computer device 200 through the communication interface 230 of the computer device 200 via the network 170 .
- a signal, command, or data received through the communication interface 230 may be transferred to the processor 220 or the memory 210 , and the file may be a storage medium (described above) that the computer device 200 may further include. persistent storage).
- the input/output interface 240 may be a means for an interface with the input/output device 250 .
- the input device may include a device such as a microphone, keyboard, or mouse
- the output device may include a device such as a display or a speaker.
- the input/output interface 240 may be a means for an interface with a device in which functions for input and output are integrated into one, such as a touch screen.
- the input/output device 250 may be configured as one device with the computer device 200 .
- the computer device 200 may include fewer or more components than those of FIG. 2 . However, there is no need to clearly show most of the prior art components.
- the computer device 200 may be implemented to include at least a portion of the above-described input/output device 250 or may further include other components such as a transceiver and a database.
- a base coin defined in a protocol and a token defined through a smart contract may be utilized for transactions.
- escrow transactions are made possible by defining three functions of deposit, reception and cancellation in the smart contract for escrow (hereinafter, 'escrow contract').
- the terms "sender”, “receiver” and “third party” described below may refer to an electronic device used by a sender, a receiver, or a third party to process remittance.
- FIGS. 3 to 5 are diagrams illustrating an example of an escrow transaction of a reference currency according to an embodiment of the present invention.
- a smart contract 310 for escrow is installed in the blockchain system 300 to process an escrow transaction according to the invocation of three functions: deposit, reception, and cancellation for money as a reference currency.
- the sender A 320 deposits money as a reference currency in the escrow contract 310 by calling the escrow transfer function ("escrowTransfer()") defined in the escrow contract 310 .
- the first parameter “B” of the escrow remittance function may be an identifier of the recipient B 330 , the recipient of the remittance, and the second parameter “value” may indicate the amount of the remittance.
- "Coin Transfer” may represent a process in which the remittance of the base currency is made from the sender A 320 to the escrow contract 310 .
- the escrow receiving function may include a parameter for identifying a corresponding remittance.
- a caller who can call the escrow reception function may be specified in the escrow contract 310 . This caller may be the called party or a trusted third party.
- an escrow contract owner (escrow contract owner, 410) who is the owner or developer of the escrow contract 310 as a trusted third party is specified as a caller.
- the escrow contract owner 410 may call the escrow reception function to the escrow contract 310 when a predefined condition for the remittance is satisfied, and accordingly, the money deposited in the escrow contract 310 is transferred to the escrow contract ( 310) may be remitted to the recipient B (330).
- the function “baseCoinTransfer(B, value)” shown in FIG. 4 is a function for transferring the base currency, and the escrow contract 310 sends the second parameter “value” to the recipient B 330 identified by the first parameter “B”. It may mean a function of transferring money as a reference currency corresponding to ".
- the sender A 320 returns the amount deposited in the escrow contract 310 as the escrow cancellation function ("escrowCancel()") is called.
- the escrow cancellation function may include a parameter for identifying the remittance.
- a caller capable of calling the escrow cancellation function may be specified in the escrow contract 310 . This caller can be the sender himself or it can be a trusted third party. 5 shows an example in which the escrow contract owner 410 is specified as a caller as a trusted third party.
- the escrow contract owner 410 may call the escrow cancellation function to the escrow contract 310 when a predefined condition for the remittance is not satisfied, and accordingly, the money deposited in the escrow contract 310 is transferred to the sender A 320 may be remitted.
- the function “baseCoinTransfer(A, value)” shown in FIG. 5 is a function for transferring the base currency, and the escrow contract 310 sends the second parameter “value” to the sender A 320 identified by the first parameter “A”. It may mean a function of transferring money as a reference currency corresponding to ".
- the escrow transaction for the token has a flow similar to the escrow transaction for the reference currency described above with reference to FIGS. 3 to 5 .
- the function of the token contract must be called in addition to the functions of the escrow contract for token remittance.
- three methods for performing escrow transactions for tokens will be described.
- a DApp (Decentralized Application, DApp, 600) installed and driven in the block chain system 300 may be an application that distributes, stores, and drives information on a network without a central server by utilizing block chain technology.
- the DApp 600 may include an escrow contract 610 and a specific smart contract to which the token is dependent (hereinafter, 'token contract 620').
- FIG. 6 shows an example of a process in which the sender A 320 deposits money in the escrow contract 610 first in order to remit money as a token to the receiver B 320 .
- the sender A 320 requests approval of the remittance by using the approval function ("approve()") to the token contract 620 to which the token is dependent, and the escrow remittance function ("escrowTransfer() )") to request a deposit.
- the first parameter of the approval function may mean a remittance target. At this time, the money must be deposited in the escrow contract (610).
- the first parameter "escrowContractAddress" of the authorization function of the token contract 620 that the sender A 320 calls is the token contract 620 so that money can be transferred from the token contract 620 to the escrow contract 610.
- the second parameter “value” of the approval function may indicate the amount of remittance
- the third parameter “currentAllowance” may indicate the amount of money approved for remittance so far.
- the first parameter "B" of the escrow remittance function may indicate the recipient B 320, which is the actual recipient of the remittance
- the second parameter "value” may indicate the amount of the remittance.
- the escrow contract 610 may request remittance to the token contract 620 in response to the call of the escrow remittance function.
- the first parameter "A” is the sender A (320)
- the second parameter "escrowContractAddress” is the escrow contract 610
- the third parameter "value” is the amount of remittance. have.
- the escrow contract 610 may request the token contract 620 to transfer the money of the sender A 320 to the escrow contract 610 to the token contract 620 .
- the token contract 620 transfers the amount requested by the function "transferFrom()" within the amount approved by the sender A 320 through the approval function (the amount requested by the escrow contract 610) to the escrow contract ( 610) by remittance (actually changing the owner of the corresponding token from the sender A 320 to the escrow contract 610), the sender A 320's money can be deposited in the escrow contract 610.
- “Token Transfer” may represent a process in which the token contract 620 transfers a token to the escrow contract 610 .
- the escrow contract owner 620 as a trusted third party calls the escrow receiving function ("escrowReceive()") defined in the escrow contract 610 as a predefined condition for the remittance is satisfied.
- the escrow reception function may include a parameter for identifying the remittance.
- the escrow contract 610 may call the remittance function (“transfer( )”) to the token contract 620 so that the deposited money is transferred to the receiver B 330 .
- the first parameter “B” of the remittance function may be an identifier of the recipient B 330 , the target of the remittance, and the second parameter “value” may mean the amount of remittance.
- the token contract 620 may transfer the money deposited in the escrow contract 610 to the receiver B 330 by changing the owner of the token deposited by the escrow contract 610 to the receiver B 330. have.
- “Token Transfer” may represent a process in which the escrow contract 610 transfers money deposited by the sender A 320 to the receiver B 330 .
- the sender A 320 returns the amount deposited in the escrow contract 610 as the escrow cancellation function ("escrowCancel()") is called.
- the escrow cancellation function may include a parameter for identifying the remittance.
- a caller capable of calling the escrow cancellation function may be specified in the escrow contract 610 . This caller can be the sender himself or it can be a trusted third party. 8 shows an example in which the escrow contract owner 620 is specified as a caller as a trusted third party.
- the escrow contract 610 may call the remittance function (“transfer( )”) defined in the token contract 620 .
- the first parameter "A" of the remittance function may be the identifier of the recipient A 320, the target of the remittance, and the second parameter "value” may mean the amount of remittance.
- the token contract 620 may process the remittance from the escrow contract 610 to the sender A 320 by changing the token deposited in the escrow contract 610 to be owned by the sender A 320 .
- “Token Transfer” may represent a process in which the escrow contract 610 returns the money deposited by the sender A 320 to the sender A 320 .
- the escrow contract 610 and the token contract 620 are separate interfaces because the escrow contract 610 operates as an individual subject to receive and remit the token of the token contract 620. can be maintained
- FIGS. 9 to 12 are diagrams illustrating a second example of an escrow transaction for a token according to an embodiment of the present invention.
- the DApp 900 may be installed and driven in the blockchain system 300 , and may include a token contract 910 and an escrow contract 920 .
- the escrow contract owner 930 installs the token contract 910 and the escrow contract 920 in the DApp 900 .
- the escrow contract owner 930 can directly install the escrow contract 920 in the dapp 900, and a function defined to be executed when installing the contract in the token contract 910 already installed in the dapp 900.
- the token contract 910 can be controlled to set the escrow contract (920).
- the token contract 910 may set the escrow contract 920 , and set the address of the token contract 910 in the escrow contract 920 .
- 'contractAddress1' may mean the address of the escrow contract 920
- 'contractAddress2' may mean the address of the token contract 910, respectively.
- FIG. 10 shows an example of a process in which the token is deposited in the escrow contract 920 as the sender A 320 requests an escrow transaction.
- the token contract 910 first approves the remittance through the approval function ("approve()"), and then uses the escrow token remittance function ("escrowTokenTransfer()") to the escrow contract 920 to sender A 320, receiver B 330
- the approval function may use the address of the escrow contract 920 and the remittance amount as parameters, respectively.
- the escrow contract 920 may request a remittance from the token contract 910 to the escrow contract 920 using the function “transferFrom( )”.
- the first parameter "ES” of the function "transferFrom()” may indicate the address of the escrow contract 920, and the second parameter “value” may indicate the amount of remittance.
- "Token Transfer” means that the token that the sender A 320 wants to transfer to the receiver B 330 is transferred to the escrow contract 920 (actually, the owner of the corresponding token in the token contract 910 is the sender A ( 320) to the escrow contract 920) may mean that it is deposited in the escrow contract 920.
- the escrow contract owner 930 as a trusted third party calls the escrow receiving function ("escrowReceive()") defined in the escrow contract 920 as a predefined condition for the remittance is satisfied.
- the escrow reception function may include a parameter for identifying the remittance.
- the escrow contract 920 may call a remittance function (“transfer( )”) defined in the token contract 910 .
- the first parameter "B" of the remittance function may be an identifier of the recipient B 330, the target of the remittance, and the second parameter "value" may mean the amount of remittance.
- the token contract 910 changes the owner of the token of the escrow contract 920 to the recipient B 330, so that money deposited in the escrow contract 920 to the recipient B 330 can be transferred.
- “Token Transfer” may represent a process in which the escrow contract 920 transfers money deposited by the sender A 320 to the receiver B 330 .
- the sender A 320 returns the amount deposited in the escrow contract 920 as the escrow cancellation function ("escrowCancel()") is called.
- the escrow cancellation function may include a parameter for identifying the remittance.
- a caller capable of calling the escrow cancellation function may be specified in the escrow contract 920 . This caller can be the sender himself or it can be a trusted third party. 12 shows an example in which the escrow contract owner 930 is specified as a caller as a trusted third party.
- the escrow contract 920 may call the remittance function (“transfer( )”) defined in the token contract 910 .
- the first parameter "A" of the remittance function may be the identifier of the recipient A 320, the target of the remittance, and the second parameter "value" may mean the amount of remittance.
- the token contract 910 may change the owner of the token of the escrow contract 920 to the sender A 320, so that the deposited amount is returned.
- “Token Transfer” may represent a process in which the escrow contract 920 returns the money deposited by the sender A 320 to the sender A 320 .
- the sender A 320 can process the process for depositing money to be remitted through one transaction. do.
- FIGS. 13 to 16 are diagrams illustrating a third example of an escrow transaction for a token according to an embodiment of the present invention.
- the DApp 1300 may be installed and driven in the blockchain system 300 , and may include a token contract 1310 and an escrow contract 1320 .
- the escrow contract owner 930 may link the escrow contract 1320 with the token contract 1310 using a function defined to be executed when the contract is installed in the escrow contract 1320 .
- the sender A 320 may request a remittance to the escrow contract 1320 through the token contract 1310 using a remittance function (“transfer( )”) defined in the token contract 1310 .
- the second parameter of the remittance function may be an amount to be remitted, such as "value”.
- the third parameter of the remittance function may indicate escrow-related meta information (recipient, memo) such as "0x+'transferid:toAddress:memo".
- the token contract 1310 is a token fallback function (") defined in the contract corresponding to the CA (escrow contract 1320 in this embodiment) when the recipient is a CA (Contract Address) rather than an Externally Owned Wallet (EOA).
- tokenFallback() can be called, and the meta information described above can be entered in the data field of the token fallback function in the form of bytes.
- the escrow contract 1320 may deposit money remitted from the sender A 320 by parsing the meta information and performing the escrow logic.
- Token Transfer may mean that the token that the sender A 320 wants to send to the receiver B 330 is transferred to the escrow contract 920 and deposited.
- the function "escrow_token_transfer()" may be a function for post-processing such as being called within the token fallback function to record the recipient of the remittance in the escrow contract 920 and processing data validation.
- the escrow contract owner 1330 as a trusted third party calls the escrow receiving function ("escrowReceive()") defined in the escrow contract 1320 as a predefined condition for the remittance is satisfied.
- the escrow reception function may include a parameter for identifying the remittance.
- the escrow contract 1320 may call a remittance function (“transfer()”) defined in the token contract 1310 .
- the first parameter "B" of the remittance function may be an identifier of the recipient B 330, the target of the remittance, and the second parameter "value" may mean the amount of remittance.
- the token contract 1310 may process the money deposited in the escrow contract 920 to be remitted to the recipient B 330 by changing the owner of the token of the escrow contract 920 to the recipient B 330 .
- “Token Transfer” may represent a process in which the escrow contract 1320 transfers money deposited by the sender A 320 to the receiver B 330 .
- 16 shows that when a predefined condition for the remittance is not satisfied, the sender A 320 returns the amount deposited in the escrow contract 920 as the escrow cancellation function ("escrowCancel()") is called. example is shown.
- the escrow cancellation function may include a parameter for identifying the remittance.
- a caller capable of calling the escrow cancellation function may be specified in the escrow contract 1320 . This caller can be the sender himself or it can be a trusted third party. 16 shows an example in which the escrow contract owner 1330 is specified as a caller as a trusted third party.
- the escrow contract 1320 may call the remittance function (“transfer( )”) defined in the token contract 1310 .
- the first parameter "A" of the remittance function may be the identifier of the recipient A 320, the target of the remittance, and the second parameter "value” may mean the amount of remittance.
- the token contract 1310 may return the money deposited in the escrow contract 1320 to the sender A 320 by changing the owner of the token of the escrow contract 1320 to the sender A 320 .
- “Token Transfer” may represent a process in which the escrow contract 1320 returns the money deposited by the sender A 320 to the sender A 320 .
- the sender A 320 can process a process for depositing money to be remitted through one transaction.
- Conditions for remittance may be defined in various ways depending on the person who sets the conditions and in some cases. For example, it may be considered that a condition is satisfied when the sender requests the transfer of money, or it may be considered that the condition is not satisfied when the sender requests cancellation of the remittance. In addition, conditions such as allowing remittance to proceed after a certain period of time or allowing remittance to proceed on a specific date may be variously defined.
- the escrow transaction method according to this embodiment may be performed by the escrow contract included in the block chain system 300, and actually by the processor 200 of the computer device 200 executing the code of the escrow contract can be performed.
- the processor 220 of the computer device 200 executes a control instruction according to the code of the operating system included in the memory 210 or the code of at least one computer program (eg, the code of the escrow contract).
- the processor 220 causes the computer device 200 to perform the steps 1710 to 1740 included in the method of FIG. 17 according to a control command provided by the code stored in the computer device 200 . can control
- the computer device 200 may deposit a currency corresponding to the sender's remittance in the escrow contract included in the block chain system for the escrow transaction from the sender to the receiver.
- the currency corresponding to the sender's remittance in the blockchain system may include the reference currency of the blockchain system or a token subordinate to the token contract further included in the blockchain system.
- the computer device 200 may directly deposit the reference currency corresponding to the sender's remittance in the escrow contract.
- the currency corresponding to the sender's remittance is a token dependent on a specific token contract
- the token corresponding to the sender's remittance can be deposited in the escrow contract through the token contract as in the following embodiments.
- the computer device 200 requests a transfer of currency to the token contract of the blockchain system for which approval is requested from the sender in step 1710, is subordinated to the token contract from the token contract, and is approved according to the request of the sender You can receive the remitted token and deposit it in the escrow contract as a currency corresponding to the sender's remittance.
- the deposit method according to this embodiment has been described in detail above with reference to FIG. 6 .
- the computer device 200 receives the escrow token remittance request from the token contract of the blockchain system that has received the escrow remittance request from the sender in step 1710, and sends the remittance to the token contract in response to the escrow token remittance request and deposit the remitted token in the escrow contract as a currency corresponding to the sender's remittance according to the request to the token contract.
- the deposit method according to this embodiment has been described in detail above with reference to FIG. 10 .
- the computer device 200 installs the escrow contract according to a request from the owner of the escrow contract, and according to the request from the escrow contract owner, the token contract You can set up an escrow contract, and you can set up a token contract in the escrow contract under the control of the token contract.
- the escrow contract and the token contract are linked to each other so that the token contract can recognize the escrow contract.
- the computer device 200 receives a token fallback request including meta information related to the escrow transaction from the token contract of the block chain system that has received the request for remittance from the sender in step 1710, and transmits the meta information.
- a token dependent on the token contract can be remitted from the sender as a currency corresponding to the sender's remittance and deposited in the escrow contract.
- the deposit method according to this embodiment has been described in detail above with reference to FIG. 14 .
- the computer device 200 installs the escrow contract according to a request from the owner of the escrow contract, and the address of the token contract included in the request from the escrow contract owner Accordingly, the escrow contract can be linked with the token contract. In this case, there is no change in the specification of the token contract and there is no need to go through the process of separately recognizing the escrow contract.
- the computer device 200 may determine whether a predefined condition for the sender's remittance is satisfied. At this time, if the predefined condition is satisfied, the computer device 200 may perform step 1730 , and if the predefined condition is not satisfied, the computer device 200 may perform step 1740 .
- the predefined condition can be made by the caller specified in the escrow contract, and the caller uses the escrow reception function when the predefined condition is satisfied, and the escrow cancel function when the predefined condition is not satisfied. can be called individually.
- the computer device 200 may determine that a predefined condition is satisfied when the escrow reception function is called, and may determine that the predefined condition is not satisfied when the escrow cancel function is called.
- the computer device 200 may remit the currency deposited in the escrow contract to the receiver.
- the computer device 200 performs an escrow reception request from a caller specified in the escrow contract when a predefined condition for the sender's remittance is satisfied.
- the token contract of the blockchain system From the escrow contract to the receiver, the token contract of the blockchain system. You can request a remittance. Previously, the remittance to such a recipient has been described in detail with reference to FIGS. 7, 11 and 15 .
- the computer device 200 may return the currency deposited in the escrow contract to the sender.
- the computer device 200 in response to the escrow cancellation request requested from the caller specified in the escrow contract, when a predefined condition for the sender's remittance is not satisfied, from the escrow contract to the sender in the token contract of the blockchain system may request a remittance of The return of the deposited call to the sender has been described in detail above with reference to FIGS. 8, 12 and 16 .
- the caller may be the owner or sender of the escrow contract.
- immediate remittance is not performed, and the remittance can be processed to the recipient when a specific condition is satisfied after depositing money.
- the sender may cancel the remittance depending on whether certain conditions are satisfied.
- the source code of the smart contract is transparently disclosed on the blockchain network, users can transparently know what kind of logic the escrow function operates.
- the system or apparatus described above may be implemented as a hardware component or a combination of a hardware component and a software component.
- devices and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA). , a programmable logic unit (PLU), microprocessor, or any other device capable of executing and responding to instructions, may be implemented using one or more general purpose or special purpose computers.
- the processing device may execute an operating system (OS) and one or more software applications running on the operating system.
- the processing device may also access, store, manipulate, process, and generate data in response to execution of the software.
- OS operating system
- the processing device may also access, store, manipulate, process, and generate data in response to execution of the software.
- the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that can include For example, the processing device may include a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as parallel processors.
- the software may comprise a computer program, code, instructions, or a combination of one or more thereof, which configures a processing device to operate as desired or is independently or collectively processed You can command the device.
- the software and/or data may be any kind of machine, component, physical device, virtual equipment, computer storage medium or device, to be interpreted by or to provide instructions or data to the processing device. may be embodied in The software may be distributed over networked computer systems, and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.
- the method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium.
- the computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination.
- the medium may be to continuously store a computer executable program, or to temporarily store it for execution or download.
- the medium may be various recording means or storage means in the form of a single or several hardware combined, it is not limited to a medium directly connected to any computer system, and may exist distributed on a network.
- Examples of the medium include a hard disk, a magnetic medium such as a floppy disk and a magnetic tape, an optical recording medium such as CD-ROM and DVD, a magneto-optical medium such as a floppy disk, and those configured to store program instructions, including ROM, RAM, flash memory, and the like.
- examples of other media may include recording media or storage media managed by an app store that distributes applications, sites that supply or distribute various other software, and servers.
- Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like.
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Finance (AREA)
- General Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Description
Claims (19)
- 블록체인 시스템의 에스크로 거래 방법에 있어서,송신자로부터 수신자로의 에스크로 거래에 대해 상기 블록체인 시스템이 포함하는 에스크로 컨트랙트에 상기 송신자의 송금에 대응하는 통화를 예치하는 단계;상기 송신자의 송금에 대해 기 정의된 조건이 만족되는 경우, 상기 에스크로 컨트랙트에 예치된 통화를 상기 수신자에게 송금하는 단계; 및상기 송금에 대해 기 정의된 조건이 만족되지 않는 경우, 상기 에스크로 컨트랙트에 예치된 통화를 상기 송신자에게 반환하는 단계를 포함하는 에스크로 거래 방법.
- 제1항에 있어서,상기 통화를 예치하는 단계는,상기 송신자로부터 승인을 요청받은 상기 블록체인 시스템의 토큰 컨트랙트로 상기 통화의 송금을 요청하는 단계; 및상기 토큰 컨트랙트로부터 상기 토큰 컨트랙트에 종속되고 상기 송신자의 요청에 따라 승인된 토큰을 송금받아 상기 송신자의 송금에 대응하는 통화로서 상기 에스크로 컨트랙트에 예치하는 단계를 포함하는 것을 특징으로 하는 에스크로 거래 방법.
- 제1항에 있어서,상기 통화를 예치하는 단계는,상기 송신자로부터 에스크로 송금을 요청받은 상기 블록체인 시스템의 토큰 컨트랙트로부터 에스크로 토큰 송금 요청을 수신하는 단계;상기 에스크로 토큰 송금 요청에 응답하여 상기 토큰 컨트랙트로 송금을 요청하는 단계; 및상기 토큰 컨트랙트로의 요청에 따라 송금된 토큰을 상기 송신자의 송금에 대응하는 통화로서 상기 에스크로 컨트랙트에 예치하는 단계를 포함하는 것을 특징으로 하는 에스크로 거래 방법.
- 제3항에 있어서,상기 에스크로 컨트랙트의 오너(owner)로부터의 요청에 따라 상기 에스크로 컨트랙트를 설치하는 단계;상기 에스크로 컨트랙트 오너로부터의 요청에 따라 상기 토큰 컨트랙트에 상기 에스크로 컨트랙트를 설정하는 단계; 및상기 토큰 컨트랙트의 제어에 따라 상기 에스크로 컨트랙트에 상기 토큰 컨트랙트를 설정하는 단계를 더 포함하는 에스크로 거래 방법.
- 제1항에 있어서,상기 통화를 예치하는 단계는,상기 송신자로부터 송금을 요청받은 상기 블록체인 시스템의 토큰 컨트랙트로부터 에스크로 거래와 관련된 메타 정보가 포함된 토큰 폴백 요청을 수신하는 단계; 및상기 메타 정보를 파싱하여 얻어지는 에스크로 거래에 대한 정보를 통해 상기 송신자로부터 상기 송신자의 송금에 대응하는 통화로서 상기 토큰 컨트랙트에 종속된 토큰을 송금받아 상기 에스크로 컨트랙트에 예치하는 단계를 포함하는 것을 특징으로 하는 에스크로 거래 방법.
- 제5항에 있어서,상기 에스크로 컨트랙트의 오너로부터의 요청에 따라 상기 에스크로 컨트랙트를 설치하는 단계; 및상기 에스크로 컨트랙트 오너로부터의 요청이 포함하는 상기 토큰 컨트랙트의 주소에 따라 상기 에스크로 컨트랙트를 상기 토큰 컨트랙트와 연계시키는 단계를 더 포함하는 에스크로 거래 방법.
- 제1항에 있어서,상기 예치된 통화를 상기 수신자에게 송금하는 단계는,상기 송신자의 송금에 대해 기 정의된 조건이 만족되는 경우에 상기 에스크로 컨트랙트에 명시된 호출자로부터 요청되는 에스크로 수신 요청에 따라, 상기 블록체인 시스템의 토큰 컨트랙트로 상기 에스크로 컨트랙트로부터 상기 수신자로의 송금을 요청하는 것을 특징으로 하는 에스크로 거래 방법.
- 제1항에 있어서,상기 예치된 통화를 상기 송신자에게 반환하는 단계는,상기 송신자의 송금에 대해 기 정의된 조건이 만족되지 않은 경우에 상기 에스크로 컨트랙트에 명시된 호출자로부터 요청되는 에스크로 취소 요청에 따라, 상기 블록체인 시스템의 토큰 컨트랙트로 상기 에스크로 컨트랙트로부터 상기 송신자로의 송금을 요청하는 것을 특징으로 하는 에스크로 거래 방법.
- 제7항 또는 제8항에 있어서,상기 호출자는 상기 에스크로 컨트랙트의 오너 또는 상기 송신자인 것을 특징으로 하는 에스크로 거래 방법.
- 제1항에 있어서,상기 송신자의 송금에 대응하는 통화는 상기 블록체인 시스템의 기준 통화를 포함하는 것을 특징으로 하는 에스크로 거래 방법.
- 제1항에 있어서,상기 통화는 상기 블록체인 시스템이 더 포함하는 토큰 컨트랙트에 종속된 토큰을 포함하는 것을 특징으로 하는 에스크로 거래 방법.
- 컴퓨터 장치와 결합되어 제1항 내지 제8항, 제10항 또는 제11항 중 어느 한 항의 방법을 컴퓨터 장치에 실행시키기 위해 컴퓨터 판독 가능한 기록매체에 저장된 컴퓨터 프로그램.
- 제1항 내지 제8항, 제10항 또는 제11항 중 어느 한 항의 방법을 컴퓨터 장치에 실행시키기 위한 컴퓨터 프로그램이 기록되어 있는 컴퓨터 판독 가능한 기록매체.
- 컴퓨터에서 판독 가능한 명령을 실행하도록 구현되는 적어도 하나의 프로세서를 포함하고,상기 적어도 하나의 프로세서에 의해,송신자로부터 수신자로의 에스크로 거래에 대해 상기 블록체인 시스템이 포함하는 에스크로 컨트랙트에 상기 송신자의 송금에 대응하는 통화를 예치하고,상기 송신자의 송금에 대해 기 정의된 조건이 만족되는 경우, 상기 에스크로 컨트랙트에 예치된 통화를 상기 수신자에게 송금하고,상기 송금에 대해 기 정의된 조건이 만족되지 않는 경우, 상기 에스크로 컨트랙트에 예치된 통화를 상기 송신자에게 반환하는 것을 특징으로 하는 컴퓨터 장치.
- 제14항에 있어서,상기 적어도 하나의 프로세서에 의해,상기 송신자로부터 승인을 요청받은 상기 블록체인 시스템의 토큰 컨트랙트로 상기 통화의 송금을 요청하고,상기 토큰 컨트랙트로부터 상기 토큰 컨트랙트에 종속되고 상기 송신자의 요청에 따라 승인된 토큰을 송금받아 상기 송신자의 송금에 대응하는 통화로서 상기 에스크로 컨트랙트에 예치하는 것을 특징으로 하는 컴퓨터 장치.
- 제14항에 있어서,상기 적어도 하나의 프로세서에 의해,상기 송신자로부터 에스크로 송금을 요청받은 상기 블록체인 시스템의 토큰 컨트랙트로부터 에스크로 토큰 송금 요청을 수신하고,상기 에스크로 토큰 송금 요청에 응답하여 상기 토큰 컨트랙트로 송금을 요청하고,상기 토큰 컨트랙트로의 요청에 따라 송금된 토큰을 상기 송신자의 송금에 대응하는 통화로서 상기 에스크로 컨트랙트에 예치하는 것을 특징으로 하는 컴퓨터 장치.
- 제14항에 있어서,상기 적어도 하나의 프로세서에 의해,상기 송신자로부터 송금을 요청받은 상기 블록체인 시스템의 토큰 컨트랙트로부터 에스크로 거래와 관련된 메타 정보가 포함된 토큰 폴백 요청을 수신하고,상기 메타 정보를 파싱하여 얻어지는 에스크로 거래에 대한 정보를 통해 상기 송신자로부터 상기 송신자의 송금에 대응하는 통화로서 상기 토큰 컨트랙트에 종속된 토큰을 송금받아 상기 에스크로 컨트랙트에 예치하는 것을 특징으로 하는 컴퓨터 장치.
- 제14항에 있어서,상기 적어도 하나의 프로세서에 의해,상기 송신자의 송금에 대해 기 정의된 조건이 만족되는 경우에 상기 에스크로 컨트랙트에 명시된 호출자로부터 요청되는 에스크로 수신 요청에 따라, 상기 블록체인 시스템의 토큰 컨트랙트로 상기 에스크로 컨트랙트로부터 상기 수신자로의 송금을 요청하는 것을 특징으로 하는 컴퓨터 장치.
- 제14항에 있어서,상기 적어도 하나의 프로세서에 의해,상기 송신자의 송금에 대해 기 정의된 조건이 만족되지 않은 경우에 상기 에스크로 컨트랙트에 명시된 호출자로부터 요청되는 에스크로 취소 요청에 따라, 상기 블록체인 시스템의 토큰 컨트랙트로 상기 에스크로 컨트랙트로부터 상기 송신자로의 송금을 요청하는 것을 특징으로 하는 컴퓨터 장치.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/KR2019/018156 WO2021125399A1 (ko) | 2019-12-20 | 2019-12-20 | 블록체인에서의 스마트 컨트랙트를 이용한 에스크로 거래 방법 및 시스템 |
KR1020227017460A KR20220084401A (ko) | 2019-12-20 | 2019-12-20 | 블록체인에서의 스마트 컨트랙트를 이용한 에스크로 거래 방법 및 시스템 |
JP2022537151A JP7478240B2 (ja) | 2019-12-20 | 2019-12-20 | ブロックチェーンでスマートコントラクトを利用したエスクロー取引方法およびシステム |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/KR2019/018156 WO2021125399A1 (ko) | 2019-12-20 | 2019-12-20 | 블록체인에서의 스마트 컨트랙트를 이용한 에스크로 거래 방법 및 시스템 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021125399A1 true WO2021125399A1 (ko) | 2021-06-24 |
Family
ID=76478791
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2019/018156 WO2021125399A1 (ko) | 2019-12-20 | 2019-12-20 | 블록체인에서의 스마트 컨트랙트를 이용한 에스크로 거래 방법 및 시스템 |
Country Status (3)
Country | Link |
---|---|
JP (1) | JP7478240B2 (ko) |
KR (1) | KR20220084401A (ko) |
WO (1) | WO2021125399A1 (ko) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR102640622B1 (ko) * | 2022-07-21 | 2024-02-28 | 주식회사 인피닛블록 | 디지털 자산 수탁 및 출금 대납 시스템 및 이를 위한 방법 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190251629A1 (en) * | 2018-02-14 | 2019-08-15 | Causam Enterprises, Inc. | Blockchain instrument for transferable equity |
KR20190096220A (ko) * | 2018-02-08 | 2019-08-19 | 주식회사 케이티 | 블록체인 기반 안전거래 플랫폼 및 방법 |
KR20190132159A (ko) * | 2018-05-18 | 2019-11-27 | 주식회사 비즈모델라인 | 스마트 컨트랙트를 이용한 블록체인 기반 암호화폐 거래 플랫폼 제공 방법 |
KR20190136610A (ko) * | 2018-05-31 | 2019-12-10 | 박덕용 | 블록체인 기반의 스마트 컨트랙트를 이용한 거래 처리 장치 및 방법 |
KR20190137064A (ko) * | 2018-05-29 | 2019-12-10 | 알리바바 그룹 홀딩 리미티드 | 자산 이전 방법 및 장치, 및 전자 디바이스 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6971019B2 (ja) | 2016-09-26 | 2021-11-24 | Gmoインターネット株式会社 | データ管理システム、情報処理装置、プログラム、及び、データ管理方法 |
CA3102606A1 (en) | 2018-06-08 | 2019-12-12 | Rocket Lawyer Incorporated | Cryptographic contract payment and dispute resolution system |
-
2019
- 2019-12-20 KR KR1020227017460A patent/KR20220084401A/ko not_active Application Discontinuation
- 2019-12-20 JP JP2022537151A patent/JP7478240B2/ja active Active
- 2019-12-20 WO PCT/KR2019/018156 patent/WO2021125399A1/ko active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20190096220A (ko) * | 2018-02-08 | 2019-08-19 | 주식회사 케이티 | 블록체인 기반 안전거래 플랫폼 및 방법 |
US20190251629A1 (en) * | 2018-02-14 | 2019-08-15 | Causam Enterprises, Inc. | Blockchain instrument for transferable equity |
KR20190132159A (ko) * | 2018-05-18 | 2019-11-27 | 주식회사 비즈모델라인 | 스마트 컨트랙트를 이용한 블록체인 기반 암호화폐 거래 플랫폼 제공 방법 |
KR20190137064A (ko) * | 2018-05-29 | 2019-12-10 | 알리바바 그룹 홀딩 리미티드 | 자산 이전 방법 및 장치, 및 전자 디바이스 |
KR20190136610A (ko) * | 2018-05-31 | 2019-12-10 | 박덕용 | 블록체인 기반의 스마트 컨트랙트를 이용한 거래 처리 장치 및 방법 |
Also Published As
Publication number | Publication date |
---|---|
KR20220084401A (ko) | 2022-06-21 |
JP7478240B2 (ja) | 2024-05-02 |
JP2023514007A (ja) | 2023-04-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230360036A1 (en) | Blockchain-implemented method and system for access control on remote internet-enabled resources | |
CN110401715B (zh) | 资源收集任务管理方法、装置、存储介质及系统 | |
KR101994296B1 (ko) | 메신저를 이용한 결재 방법 및 시스템 | |
CN106030528B (zh) | 数据代理服务 | |
JP6882924B2 (ja) | 互いに異なるユーザ識別体系を利用して登録されたユーザを識別するサーバ間のサービス連動方法、システムおよびコンピュータプログラム | |
KR20190115652A (ko) | 송금 기능이 탑재된 메신저에서 메시지 내용을 인식하여 송금 기능을 제공하는 방법 및 시스템 | |
KR102118178B1 (ko) | 블록체인을 위한 다중 트랜잭션 병렬 처리 방법 및 시스템 | |
WO2018080206A1 (ko) | Utxo 기반 프로토콜에서 머클 트리 구조를 사용하여 통화를 발행 및 지급 결제하는 방법과 이를 이용한 서버 | |
JP2021072108A (ja) | 共有口座の取引に対する事前承認のためのコンピュータプログラム、方法、および装置 | |
WO2020213763A1 (ko) | 블록체인과는 다른 형식의 저장소에 저장되는 블록체인 데이터를 검증하는 방법 및 시스템 | |
WO2018128261A1 (ko) | 사용자 활동 정보를 공유하는 방법 및 시스템 | |
CN110766394A (zh) | 基于信用度的乘车支付方法、装置、电子设备及存储介质 | |
CN110163691A (zh) | 基于区块链的发票创建方法和装置、电子设备 | |
JP2021119544A (ja) | トランザクション委任方法、及びトランザクション委任システム | |
CN107274164A (zh) | 一种多渠道第三方移动支付融合转账系统及其方法 | |
WO2020096072A1 (ko) | 디앱에서 요구하는 높은 트랜잭션 처리량을 효율적으로 블록체인에서 처리하기 위한 방법 및 시스템 | |
KR20200044167A (ko) | 메신저 봇을 이용하여 IoT 기기를 제어하기 위한 방법, 시스템, 및 비-일시적인 컴퓨터 판독가능한 기록 매체 | |
WO2021125399A1 (ko) | 블록체인에서의 스마트 컨트랙트를 이용한 에스크로 거래 방법 및 시스템 | |
JP7101292B2 (ja) | 支払い方法およびシステム | |
WO2018080205A1 (ko) | Utxo 기반 프로토콜을 사용하여 통화를 발행 및 지급 결제하는 방법과 이를 이용한 서버 | |
CN115858182B (zh) | 一种应用于元宇宙的边缘计算节点的智能适配方法与系统 | |
JP2020109617A (ja) | ブロックチェーンの拡張を可能にするトランザクション処理システムおよび方法 | |
KR20150096190A (ko) | 애플리케이션 펀딩서비스를 제공하는 서버, 방법 및 시스템 | |
WO2019240305A1 (ko) | 사용 정도에 기초하여 대화방을 처리하는 방법과 시스템 및 비-일시적인 컴퓨터 판독가능한 기록 매체 | |
JP2003044602A (ja) | アプリケーション提供装置及びアプリケーション提供方法 |
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: 19956263 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20227017460 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2022537151 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19956263 Country of ref document: EP Kind code of ref document: A1 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19956263 Country of ref document: EP Kind code of ref document: A1 |