KR20230040734A - The method and appartus for encryption of block chain based transaction history proof and ownership transfer - Google Patents

Abstract

According to the embodiments of the present invention, provided is an encryption method for blockchain-based transaction history proof and transfer of ownership using distributed computing, which includes the steps of: generating a first asset block through a preset consensus node of a private blockchain based on the first asset information; generating at least one token corresponding to a digital security based on the first asset block; distributing at least one or more tokens to at least one or more initial investors; and registering at least one or more tokens distributed to at least one or more initial investors in an exchange node.

Description

Encryption method and device for proof of blockchain-based transaction details and transfer of ownership

Embodiments are directed to an encryption method and apparatus for proof of transaction history and transfer of ownership based on blockchain using distributed computing.

More specifically, digital securities are issued based on blockchain for real assets, and transaction details for the issued securities are verified to transfer ownership, thereby providing transactions for real assets using distributed computing. can

Previously, real assets such as real estate could be owned by one owner or owned by a small number of people based on shared shares. In addition, real assets such as real estate were recorded in a certified copy of the register through an intermediary office, and ownership was transferred, so transactions could be limited. In addition, only some wealthy people were able to trade high-value real estate, and investment was restricted to ordinary investors who could not afford the high amount. Here, it is possible to invest in high-priced real estate assets through recent real estate funds and REITs, but this is also a situation in which complex system design and high operating costs are generated due to the complex composition of tasks such as trustees, asset management companies, and sales companies. There is a problem in that the cost burden caused by this is passed on to investors. Therefore, in the following, a method for efficiently trading by issuing digital securities for real assets based on blockchain is described.

Korean Patent Application No. 10-2021-0102688

This specification relates to an encryption method for blockchain-based transaction details proof and ownership transfer using computing.

This specification is about a method of constructing a private blockchain based on real assets and issuing digital securities through the private blockchain to provide efficient transactions.

This specification relates to a method of registering digital securities for real assets and generating tokens based thereon to support transactions between users.

This specification relates to a method of recording real assets in a blockchain based on a plurality of private nodes.

This specification relates to a method for providing efficient transactions by generating non-fungible token (NFT) tokens for real assets and issuing digital securities based thereon.

This specification relates to a method of issuing digital securities for real assets based on a private chain and trading the issued securities based on a side chain.

The problem to be solved in the present specification is not limited to the above, and can be extended to various matters that can be derived by the embodiments of the invention described below.

According to an embodiment of the present specification, in the encryption method for blockchain-based transaction details proof and ownership transfer using distributed computing, a first through a preset consensus node of a private blockchain based on first asset information Creating an asset block, generating at least one or more tokens corresponding to digital securities based on the first asset block, distributing the at least one token to at least one or more initial investors, and at least one or more initial investors It may include registering at least one or more tokens distributed to the exchange node in the exchange node.

In addition, according to an embodiment of the present specification, it is possible to provide a computer program stored in a computer-readable medium to execute a blockchain-based encryption method for proof of transaction details and transfer of ownership by utilizing distributed computing.

In addition, according to one embodiment of the present specification, the first asset information includes at least one or more of asset location information, asset appraisal information, asset bank record information, asset collateral information, volatility information, asset insurance information, and asset management information do,

The first asset block may be generated based on the first asset information through the private blockchain.

In addition, according to an embodiment of the present specification, the step of distributing at least one or more tokens to at least one or more initial investors may include the platform providing at least one first asset block information generated based on the first asset information and the private block chain. Transmitting to the node of each of the initial investors, the platform based on the first asset information and the first asset block information from each node of the at least one or more initial investors, investment consent information and token information allocated to each of the initial investors Receiving fund deposit information based on; and

The platform may include distributing at least one or more tokens to each node of one or more initial investors based on the consent information and the fund deposit information.

In addition, according to an embodiment of the present specification, the preset consensus node of the private blockchain includes a first node, a second node, and a platform node, and a first asset block is generated based on the preset consensus node. Node 1 may be a node that processes trust information of a first asset, and node 2 may be a node that processes fund information verified based on at least one or more tokens.

In addition, according to an embodiment of the present specification, when the registration entity node is included in the preset consensus node of the private blockchain, the first asset block is based on the platform node, the first node, the second node, and the registration entity node At least one token generated and issued based on the first asset block is registered as a digital security without verification of the registration entity node, and when the registration entity node is not included in the preset consensus node of the private blockchain, the first asset A block is created based on a platform node, a first node and a second node, the platform issues at least one or more tokens based on the first asset block, and transmits at least one or more token information to a registration entity, and the registration entity It is possible to determine whether to register as digital securities based on at least one token information received.

In addition, according to an embodiment of the present specification, when at least one or more tokens distributed to at least one or more initial investors are registered in an exchange node, at least one or more initial investors trade for at least one or more tokens based on the exchange node However, when a transaction is performed, a transaction occurs, and the transaction may be recorded and updated in the first asset block based on the private blockchain.

This specification has the effect of providing an encryption method for proof of transaction history and transfer of ownership based on blockchain by utilizing computing.

This specification has the effect of providing efficient transactions by configuring a private blockchain based on real assets and issuing digital securities through the private blockchain.

This specification has the effect of registering digital securities for real assets and generating tokens based on them to support transactions between users.

This specification has the effect of providing a method of recording real assets in a blockchain based on a plurality of private nodes.

This specification has the effect of providing efficient transactions by generating non-fungible token (NFT) tokens for real assets and issuing digital securities based thereon.

This specification has the effect of providing a method of issuing digital securities for real assets based on a private chain and trading the issued securities based on a side chain.

It should be understood that the effects of the present specification are not limited to those described above, and can be extended to various contents that can be derived from the detailed description of the embodiments of the present invention below.

1 is a diagram illustrating an example of an operating environment of a system according to an embodiment of the present specification.
2 is a block diagram illustrating an internal configuration of a computing device 200 according to an embodiment of the present specification.
3 is a diagram illustrating a method of proving ownership of real assets and storing transaction details by utilizing distributed computing in an embodiment of the present specification.
4 is a diagram illustrating a method of proving ownership of a real asset and issuing digital securities by utilizing distributed computing based on a block chain in an embodiment of the present specification.
5 is a diagram illustrating a method of proving ownership of a real asset and storing transaction details based on a non-fungible token in an embodiment of the present specification.
6 is a diagram illustrating a method of performing a transaction of digital securities by utilizing distributed computing in an embodiment of the present specification.
7 is a diagram illustrating a method of recording transaction details and updating proof of ownership based on digital securities transactions according to an embodiment of the present specification.
8 is a diagram showing an interface for trading digital securities based on real assets in an embodiment of the present specification.
9 is a diagram illustrating a method of verifying authenticity of electronic securities in an embodiment of the present specification.
10 is a diagram illustrating a method of verifying and recording transaction details in one embodiment of the present specification.
11 is a diagram illustrating a method of processing a transaction of a digital securities owner according to an embodiment of the present specification.
12 is a diagram illustrating a method of configuring an agreement node for transaction processing according to an embodiment of the present specification.
13 is a diagram illustrating a method of configuring an agreement node according to an embodiment of the present specification.
14 is a diagram illustrating a method of trading digital securities based on a main chain and a side chain in an embodiment of the present specification.
15 is a diagram illustrating a method of proving ownership by utilizing distributed computing and dividing and transacting the verified ownership according to an embodiment of the present specification.
16 is a diagram illustrating a method of performing proof of ownership of a real asset based on a private blockchain in an embodiment of the present specification.
17 is a diagram illustrating a method of distributing expected profits based on proof of ownership in an embodiment of the present specification.
18 is a flowchart of an encryption method for blockchain-based transaction details proof and ownership transfer using distributed computing.

In describing the embodiments of the present specification, if it is determined that a detailed description of a known configuration or function may obscure the gist of the embodiment of the present specification, the detailed description thereof will be omitted. And, in the drawings, parts not related to the description of the embodiments of the present specification are omitted, and similar reference numerals are attached to similar parts.

In the embodiments of the present specification, when a component is said to be "connected", "coupled" or "connected" with another component, this is not only a direct connection relationship, but also an indirect connection between which another component exists. It may also include a causal connection. In addition, when a component "includes" or "has" another component, this means that it may further include another component without excluding other components unless otherwise stated. .

In the embodiments of the present specification, terms such as first and second are used only for the purpose of distinguishing one component from another, and do not limit the order or importance of components unless otherwise specified. don't Therefore, within the scope of the embodiments herein, a first component in an embodiment may be referred to as a second component in another embodiment, and similarly, a second component in an embodiment may be referred to as a first component in another embodiment. can also be called

In the embodiments of the present specification, components that are distinguished from each other are intended to clearly describe each characteristic, and do not necessarily mean that the components are separated. That is, a plurality of components may be integrated to form a single hardware or software unit, or a single component may be distributed to form a plurality of hardware or software units. Therefore, even if not mentioned separately, such an integrated or distributed embodiment is also included in the scope of the embodiments of the present specification.

In this specification, a network may be a concept including both wired and wireless networks. In this case, the network may refer to a communication network through which data exchange between devices, systems, and devices may be performed, and is not limited to a specific network.

The embodiments described herein may have aspects that are entirely hardware, part hardware and part software, or entirely software. In this specification, “unit”, “apparatus” or “system” refers to computer-related entities such as hardware, a combination of hardware and software, or software. For example, in this specification, a unit, module, device, or system, etc., refers to a running process, processor, object, executable file, thread of execution, program, and/or computer. (computer), but is not limited thereto. For example, both an application running on a computer and a computer may correspond to parts, modules, devices, or systems of the present specification.

In addition, in the present specification, a device may be a fixed device such as a PC or a home appliance having a display function, as well as a mobile device such as a smart phone, a tablet PC, a wearable device, and a head mounted display (HMD). Also, as an example, the device may be an in-vehicle cluster or an Internet of Things (IoT) device. That is, in this specification, a device may refer to devices capable of operating an application, and is not limited to a specific type. In the following, for convenience of description, a device in which an application operates is referred to as a device.

In this specification, the communication method of the network is not limited, and connections between components may not be connected in the same network method. The network may include not only a communication method using a communication network (eg, a mobile communication network, wired Internet, wireless Internet, broadcasting network, satellite network, etc.), but also short-distance wireless communication between devices. For example, a network may include objects and all communication methods that objects may network, and is not limited to wired communication, wireless communication, 3G, 4G, 5G, or other methods. For example, a wired and/or network may include Local Area Network (LAN), Metropolitan Area Network (MAN), Global System for Mobile Network (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Zigbee, Wi-Fi, Voice over VoIP Internet Protocol), LTE Advanced, IEEE802.16m, WirelessMAN-Advanced, HSPA+, 3GPP Long Term Evolution (LTE), Mobile WiMAX (IEEE 802.16e), UMB (formerly EV-DO Rev. C), Flash-OFDM, iBurst and It may refer to a communication network using one or more communication methods selected from the group consisting of MBWA (IEEE 802.20) systems, HIPERMAN, Beam-Division Multiple Access (BDMA), Wi-MAX (World Interoperability for Microwave Access), and ultrasonic communication. However, it is not limited thereto.

Components described in various embodiments do not necessarily mean essential components, and some may be optional components. Accordingly, embodiments composed of a subset of components described in the embodiments are also included in the scope of the embodiments of the present specification. In addition, embodiments including other components in addition to the components described in various embodiments are also included in the scope of the embodiments of the present specification.

Hereinafter, with reference to the drawings, look at the embodiments of the present specification in detail.

1 is a diagram showing an example of an operating environment of a system according to an embodiment of the present specification. Referring to FIG. 1 , one or more user devices 110 - 1 and 110 - 2 and one or more servers 120 , 130 and 140 are connected through a network 1 . 1 is an example for explanation of the invention, and the number of user devices or servers is not limited as shown in FIG. 1 .

One or more user devices 110-1 and 110-2 may be fixed terminals implemented as computer systems or mobile terminals. The one or more user devices 110-1 and 110-2 may be, for example, a smart phone, a mobile phone, a navigation device, a computer, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), and a portable multimedia player (PMP). , tablet PC, game console, wearable device, internet of things (IoT) device, virtual reality (VR) device, augmented reality (AR) device, and the like. As an example, in embodiments user device 110 is one of a variety of physical computer systems capable of communicating with other servers 120 - 140 over network 1 using substantially wireless or wired communication schemes. can mean

Each server may be implemented as a computer device or a plurality of computer devices that communicate with one or more user devices 110-1 and 110-2 through the network 1 to provide commands, codes, files, contents, services, and the like. there is. For example, the server may be a system that provides each service to one or more user devices 110-1 and 110-2 connected through the network 1. As a more specific example, the server provides a service (for example, information provision, etc.) for which the application is intended through an application as a computer program installed and driven in one or more user devices 110-1 and 110-2. (110-1, 110-2). As another example, the server may distribute a file for installing and running the above-described application to one or more user devices 110-1 and 110-2, receive user input information, and provide a corresponding service.

Figure 2 is a block diagram for explaining the internal configuration of the computing device 200 in one embodiment of the present specification. This computing device 200 may be applied to one or more user devices 110-1 and 110-2 or servers 120-140 described above with reference to FIG. 1, and each device and server may add some components or By being configured except for, it may have the same or similar internal configuration.

Referring to FIG. 2 , a computing device 200 may include a memory 210 , a processor 220 , a communication module 230 and a transceiver 240 . The memory 210 is a non-temporary computer-readable recording medium, and is a non-perishable large-capacity memory such as RAM (random access memory), ROM (read only memory), disk drive, SSD (solid state drive), flash memory, and the like. A permanent mass storage device may be included. Here, a non-perishable mass storage device such as a ROM, SSD, flash memory, disk drive, etc. may be included in the above-described device or server as a separate permanent storage device distinct from the memory 210 . In addition, the memory 210 stores an operating system and at least one program code (for example, a browser installed and driven on the user device 110 or a code for an application installed on the user device 110 to provide a specific service). It can be. These software components may be loaded 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.

In another embodiment, software components may be loaded into the memory 210 through the communication module 230 rather than a computer-readable recording medium. For example, at least one program is a computer program installed by files provided by developers or a file distribution system (eg, the above-described server) that distributes installation files of applications through the network 1 (eg, a server). It may be loaded into the memory 210 based on the above-described application).

The processor 220 may be configured to process commands of a computer program by performing basic arithmetic, logic, and input/output operations. Instructions may be provided to processor 220 by memory 210 or communication module 230 . For example, processor 220 may be configured to execute received instructions according to program codes stored in a recording device such as memory 210 .

The communication module 230 may provide a function for the user device 110 and the servers 120 to 140 to communicate with each other through the network 1, and the device 110 and/or the servers 120 to 140, respectively. A function for communicating with other electronic devices may be provided.

The transceiver 240 may be a means for interface with an external input/output device (not shown). For example, the external input device may include devices such as a keyboard, mouse, microphone, and camera, and the external output device may include devices such as a display, a speaker, and a haptic feedback device.

As another example, the transceiver 240 may be a means for interface with a device in which functions for input and output are integrated into one, such as a touch screen.

Also, in other embodiments, the computing device 200 may include more components than those of FIG. 2 depending on the nature of the device to which it is applied. For example, when the computing device 200 is applied to the user device 110, it is implemented to include at least some of the above-described input/output devices, or a transceiver, a Global Positioning System (GPS) module, a camera, various sensors, It may further include other components such as databases and the like. As a more specific example, when the user device is a smartphone, various devices such as an acceleration sensor, a gyro sensor, a camera module, various physical buttons, buttons using a touch panel, input/output ports, and a vibrator for vibration are generally included in the smartphone. It may be implemented to include more components.

In the following, a computing device operating based on FIGS. 1 and 2 will be described as a reference. Here, the computing device 200 and the aforementioned server may be one node. For example, a node may mean a connection point or an end point and redistribution point of data transmission in a network. In addition, the aforementioned node may be a node that operates based on a block chain. Here, data to be managed may be a block. At this time, distributed computing technology in which small-scale data of data to be managed creates a distributed data storage environment based on a chain-type link created based on a P2P method so that it is impossible to modify arbitrarily and the results of data change are recorded. The underlying ledger management technology may be blockchain. That is, blockchain may be a form of distributed data storage technology, and continuously changing data may be recorded in all of the above-mentioned nodes. That is, all records related to data processing are recorded in all nodes included in the blockchain, so that any manipulation is impossible. That is, the above-described computing device 200 and server may be one node constituting a block chain, and each computing device 200 and server have a ledger for data processing such as data creation and change based on the block chain. includes, and can be recorded. For example, the node described below may be the above-described computing device and server, and devices that perform data transmission and reception based on the above-described transmission and reception unit and record and store blockchain-related ledgers may all be nodes, and specific It may not be limited to the form. In the following, related technologies are described centering on blockchains and nodes for convenience of explanation, but this may not be limited to specific devices.

3 is a diagram illustrating a method of proving ownership of real assets and storing transaction details by utilizing distributed computing in an embodiment of the present specification.

Referring to FIG. 3 , ownership of a real asset 310 may be proved, and transactions between users may be performed based on a block chain using distributed computing. More specifically, the real asset 310 may be movable property or real estate. As another example, the real assets 310 may be intellectual property rights or other intangible assets that are not in physical form. That is, the real asset 310 may not be limited to a specific form. However, in the following, for convenience of description, the case in which the real asset 310 is real estate is described, but may not be limited thereto.

For example, the transaction of the real asset 310 may be carried out when a single owner owns the entire ownership of the real asset 310 or a plurality of owners share or jointly own the ownership of the real asset 310 .

For example, ownership of the real asset 310 may be proven by holding the actual real asset 310 . As a specific example, ownership of a movable property can be proven by the fact that the owner owns the actual real asset 310 . In addition, for example, for assets with a large value, such as automobiles or real estate, proof of ownership may be made by recording them in a certified copy of a register or a book protected by other laws. Here, general investors may be restricted from investing in high-value assets such as real estate due to limited funds, or there are restrictions on transactions such as trading only by some asset owners. Considering the foregoing, a method of issuing digital securities for a real asset 310 such as real estate and transferring ownership through a transaction by a plurality of users will be described below. For example, the number of digital securities of the real asset 310 may be issued as a preset number based on the value of the real asset 310 or a number guaranteed by the registration entity 350 . At this time, the number of issued digital securities and the value of each digital security may be determined by the value of the real asset 310 . As a specific example, the number of digital securities and the value of each digital security may be determined such that a value obtained by multiplying the number of digital securities by the value of each digital security becomes the value of the real asset 310 .

As another example, the number of digital securities and the value of each digital security may be set to be larger or smaller than the value of the real asset 310 . As a specific example, referring to FIG. 3 , real assets 310 may be delegated based on trust contract information or trust related information with blockchain node A 320 . At this time, the block chain node A 320 may be a node operated by a subject that processes real asset 310 trust or trust related information. For example, blockchain node A 320 may be a node managed by a trust company. At this time, the blockchain node A 320 may acquire information on the ownership of the real asset 310 based on trust or entrustment, and transfer the information on the acquired ownership to the platform 330 . For example, the platform 330 may prove ownership through a private blockchain based on information on ownership acquired from the blockchain node A 320, which will be described later.

In addition, the platform 330 may issue, manage, and process digital securities for real assets 310 . Here, the platform 330 may also operate as one node for a private blockchain. That is, the platform 330 may be implemented as a single node while having the above-described functions, and is not limited to a specific form.

For example, when the platform 330 selects blockchain node A (320, that is, a node related to trust of the real asset 310), the platform 330 selects blockchain node A 320 from among a plurality of blockchain node types. You can choose. As a specific example, each of a plurality of trust companies in relation to the blockchain node A 320 may provide information about each blockchain node to the platform 330 . At this time, each blockchain node related to the trust company is of the same type, and only each entity (ie, the trust company) may be different. For example, the platform 330 may select a specific blockchain node from among blockchain nodes for a plurality of trust companies capable of performing management tasks for specific real assets. After that, the selected blockchain node may obtain information on the ownership of the real asset 310 as the above-described blockchain node A 320 and transmit it to the platform 330 .

As another example, blockchain node types provided to the platform 330 may be different. For example, the blockchain node type may be a type that prioritizes security. As another example, the blockchain node type may be a type that prioritizes data processing speed. As another example, the blockchain node type may be a type that prioritizes data capacity. As another example, the blockchain node type may be a type that prioritizes whether or not to provide utility. As an example, utility may be information related to providing a service based on a blockchain node. For example, it may be a node capable of creating an anonymous block chain or a block chain node associated with a community or mainnet, and is not limited to a specific form. The types of blockchain nodes may be different, and the platform 330 may select a specific blockchain node among different blockchain node types as the aforementioned blockchain node A 320 . That is, in the case of selecting a blockchain node related to the trust of the real asset 310, the type information of the blockchain node may be further considered.

Also, as an example, the platform 330 may determine a blockchain node type based on the type of real asset 320 . As a specific example, when the real asset 310 is high in value, such as real estate, and the number of issued digital securities is large, the platform 330 selects a block chain node type with high data processing speed and large data capacity as block chain node A 320. can be selected with As another example, if the value of the real asset 310 is small and the number of issued digital securities is small, a blockchain node type with high security may be selected as the blockchain node A 320 . That is, the platform 330 may determine a blockchain node type suitable for proof of ownership of the real asset 310 in consideration of the characteristics and types of the real asset 310 and select it as the blockchain node A 320 . After that, the blockchain node A 320 may perform an ownership proof operation by obtaining information on the ownership of the real asset 310 and transferring it to the platform 330 as described above.

For example, based on the selected blockchain node A (320), a public offering of digital securities for the real asset (310) may be delivered to the platform (330). Here, blockchain node A 320 may register the digital securities with registration entity 350 . The registration entity 350 may be an entity 350 that secures the issuance of digital securities. For example, the registration entity 350 may be an entity of Korea Securities Depository. As another example, the registration entity 350 may be another entity for securing the issuance of digital securities of the real asset 310, and is not limited to a specific form. Here, the digital securities may be digital securities issued based on the ownership of real assets 310 . For example, existing digital securities may be issued for a specific company in consideration of corporate value, but may also be issued for real assets 310 whose ownership has been verified. That is, digital securities are issued based on the ownership of real assets 310, and registration can be performed with the registration entity 350 to secure them.

Here, as an example, the registration entity 350 may determine whether to register the digital securities in consideration of verification of the real assets 310 and whether the issued digital securities can be secured. As a specific example, the registration entity 350 may obtain information related to the real asset 310 to verify the real asset 310 . For example, the information related to the real asset 310 includes at least one of the owner, asset location, asset appraisal information, asset bank record information, asset collateral information, volatility information, asset insurance information, and asset management information on the register of the real asset 310. It may include one, and is not limited to the above-described embodiment. Here, the above-described information may be information recorded when a private blockchain related to the real asset 310 is created.

As a specific example, the above-described registration entity 350, blockchain node A 320, and platform 330 create a private blockchain for the real asset 310 for initial registration of the real asset 310, based thereon. After issuing the digital securities, the digital securities may be registered with the registration entity 350 . Here, the owner on the register of the real asset 310 may be the operating entity of the aforementioned blockchain node A 320. In addition, as an example, the owner of the real asset 310 on the register may be a third party, and based on the private blockchain created by the registration entity 350, blockchain node A 320 and platform 330, collateral It can be a subject that becomes. That is, information about the registered owner of the real asset 310 may be considered, and the registration entity 350 may determine whether to register the digital registered securities by checking the information therefor.

As another example, whether to register digital securities may be determined based on other information of the real asset 310 . For example, the collateral value of the real asset 310 may be different from the trading reversibility of the real asset 310 . That is, the assessed value of the real asset 310 may be smaller than the collateral value. Therefore, when the number of digital securities and the value of individual digital securities are determined according to the value of the real asset 310, since the value of the actual real asset 310 may not be able to secure the digital security, the registration entity 350 uses the above information You can decide whether to register digital securities by taking into account. In addition, as an example, there is a need to reflect the appraisal value of the real asset 310, insurance records, and other transaction history information. That is, verification of the real asset 310 may be required, and the registration entity 350 may determine whether to register the digital securities in consideration of the verification information of the real asset 310 . Here, as an example, the verification information for the real asset 310 described above may be configured as a private block chain. For example, the node that creates the private blockchain for the real asset 310 may be the platform 330 and the blockchain node A 320 . That is, the platform 330 and the blockchain node A 320 may be consensus nodes that create a private blockchain for the real asset 310 . At this time, ownership of the real asset 310 can be proven through a private blockchain created based on the platform 330 and the blockchain node A 320, and the corresponding information can be delivered to the registration entity 350. there is. At this time, the registration entity 350 may determine whether to allow issuance of digital securities based on private blockchain information and real asset 310 related information.

As another example, the node generating the private blockchain may be the platform 330 , the blockchain node A 320 and the registration entity 350 . For example, the registration entity 350 may also operate as a node for forming a private blockchain to allow registration of digital securities as a node, and is not limited to a specific form. At this time, since the registration entity 350 is a consensus node of the private block chain that proves ownership of the real asset 310, information related to the real asset can be obtained in advance. For example, the node of the registration entity 350 may not agree to create a private blockchain for the real asset 310 if it does not meet the preset conditions or preset criteria, and the private blockchain for the real asset 310 may not be created. That is, ownership of the real asset 310 may not be proven, and digital securities may not be registered. On the other hand, when the registration entity 350 participates as a node in the private blockchain and meets predetermined conditions and criteria and generates a block of real assets 310 through consensus, the block of real assets 310 Ownership can be proven based on a private blockchain, and issuance of digital securities can also be considered permitted. That is, the node of the registration entity 350 is a consensus node of the private blockchain and performs verification of the real asset 310 during the block creation process, so when the block for the real asset 310 is generated, digital securities issuance registration is permitted. can be regarded as

As another example, nodes generating a private blockchain may be a platform 330 , a blockchain node A 320 , a registration entity 350 , and a blockchain node B 360 . For example, blockchain node B 360 may be an account-related node. Also, as an example, the blockchain node B 360 may be a node that manages transaction records or ledgers, and is not limited to a specific form. That is, the registration entity 350 and the blockchain node B 360 may also be consensus nodes for generating a private blockchain for issuing digital securities for the above-described real asset 310, thereby ensuring security. can

As another example, information related to the real asset 310 recorded in the private blockchain may be determined based on artificial intelligence and information acquired through the cloud.

For example, reliable information related to the real asset 310 may be required to secure the issuance of digital securities for the real asset 310 . However, if the real asset 310 is a breakable movable property or an asset whose value is declining due to aging, such as an apartment, it may be necessary to secure the reliability of the real asset 310. In consideration of the above, real asset 310 information recorded in the private blockchain can be derived through artificial intelligence based on similar real asset 310 related information and other asset value information, It can be recorded as a private blockchain. Here, the registration entity 350 may also determine whether to allow registration of digital securities by checking whether the number of digital securities of the real asset 310 and the value of individual digital securities are suitable based on the information derived based on the above.

Here, as an example, the block chain may include a public block chain and a private block chain, and the block chain for the real asset 310 may be created based on the private block chain. As an example, the public blockchain may be a blockchain in which anyone can participate using various computer equipment such as PCs, laptops, smartphones, servers, and computer miners connected to the Internet without authorization from an authoritative organization. At this time, participation or withdrawal from the blockchain network is determined based on the free will of the participants, and since a large number of people participate, transparency and security can be enhanced. On the other hand, a private blockchain may be a blockchain in which only authorized persons with legal responsibility can participate in the blockchain network. That is, only authorized nodes such as the aforementioned platform 330 and blockchain node A 320 can participate in the blockchain network, and the consensus node may be a private blockchain node.

Based on the foregoing, when digital securities are issued based on the private blockchain of the real asset 310 and the digital securities are granted to the registration entity 350, the platform 330 may perform a public offering of digital securities. At this time, the digital securities offered by the platform 330 may be purchased and distributed by the investor 340 . For example, the investor 340 may pay the public offering price based on the platform 330, and the platform 330 may process information about this based on the account-related information of the blockchain node A 320, which Through this, each digital securities can be allocated. At this time, as an example, the investors 340 may trade the allocated digital securities based on the buyer 370-1 and the seller 370-2, which will be described later. Also, as an example, when digital securities are issued to investors 340, information about them may be transmitted to the blockchain node B 360. Here, the blockchain node B 360 may be a node that manages account information of the investor 340 or the buyer 370-1/seller 370-2. For example, the blockchain node B 360 may be a node of which a financial institution is a subject. As another example, the blockchain node B 360 may be a node of a legally approved entity. That is, the blockchain node B 360 may be a node that manages the account information of the investor 340 or the buyer 370-1/seller 370-2, and may be a trusted node with verification completed. there is. Here, the blockchain node B 360 can secure reliability by managing the account information of the investor 340 or the buyer 370-1/seller 370-2 in association with the above-described registration entity 350. .

Based on the foregoing, when digital securities for the real assets 310 are issued, the digital securities can be traded through the exchange node, and the profits of the real assets 310 can be distributed to the owners of the digital securities. In this regard, it will be described later.

4 is a diagram illustrating a method of proving ownership of a real asset and issuing digital securities by utilizing distributed computing based on a block chain in an embodiment of the present specification. For example, as described above, ownership of the real asset 310 may be created by recording it in a private block chain using distributed computing. That is, ownership of the real asset 310 may be proven through a private block chain using distributed computing.

Here, as a specific example, as described above, block generation of the private blockchain may be generated based on a preset consensus node (or member node). Also, as an example, changing a rule by reading a block or checking a record of a private blockchain may be performed based on a member node. Therefore, the processing speed of the private blockchain may be faster than that of the public blockchain. Also, as an example, the consensus algorithm of the private blockchain may be PBFT (Practical Byzantine Fault Tolerance), through which security may be increased. Considering the above points, when the ownership of the real asset 310 is proved and a block is generated based on a private blockchain, the configuration of a consensus node (or member node) participating in block generation may be important. For example, consensus nodes participating in block generation need to be nodes whose reliability can be guaranteed, and at least a minimum number of nodes whose reliability can be guaranteed may be required.

Considering the above, referring to FIG. 4 , when a block is generated through a private blockchain based on real assets 310, blockchain node A 320, platform node 330, and blockchain node B 360 may be configured as a consensus node for block generation. Here, the blockchain node A (320) may be a node containing trust-related information of the real asset 310, and the blockchain node B (360) is a node related to investors and other traders based on the value of the real asset (310). It may be a node containing account information. That is, a node that generates a block based on a private blockchain may be a node that manages trust information for the real asset 310, a node that manages account information, and a platform node, through which reliability can be ensured. Here, a block may be created through the private blockchain for the real asset 310 based on the above-described agreement, and digital securities may be issued based on the corresponding block.

In addition, as an example, the registration entity 350 may not be a node included in block generation based on a private blockchain, but may provide information related to a trust and an account with a blockchain node A 320 and a blockchain node B 360. It is possible to secure the issuance of digital securities based on blocks generated during exchange, and through this, digital securities for real assets 310 can be issued. Also, as an example, a block generated based on a private blockchain may include real asset 310 related information. As another example, rules related to transaction processing and profit distribution in a block generated based on a private blockchain may be set based on the aforementioned consensus node, which will be described later. In addition, the digital securities issued based on the above may be provided to the buyer 370-1 and the seller 370-2 through the exchange node 410, and through this, the issued digital securities for the real asset 310 Securities can be traded.

As another example, FIG. 5 is a diagram illustrating a method of proving ownership of a real asset and storing transaction details based on a non-fungible token in an embodiment of the present specification. For example, NFTs for real assets 310 may be issued. For example, a non-fungible token (NFT) is a non-fungible token and includes a unique recognition value for each digital asset, and based on this, a non-fungible digital asset can be formed. In other words, specific digital assets can be distinguished from other assets by giving unique rights.

Here, the real asset 310 may be created as a non-fungible digital asset based on NFT. That is, a digital asset corresponding only to the real asset 310 may be created. For example, the NFT for the real asset 310 may be generated based on the aforementioned blockchain node A 320, platform node 330, and blockchain node B 360. That is, the node subjects that generate the NFT for the real asset 310 may be the blockchain node A 320, the platform node 330, and the blockchain node B 360. In addition, as an example, the blockchain node A 320 is a node in charge of trust-related information of the real asset 310 and can update management and change information of the real asset 310 corresponding to the NFT in real time. As a specific example, the NFT may have a unique value as a unique digital asset corresponding to the real asset 310 and may not be copied. Real assets 310 may change. For example, the value of real estate may decrease or the value may change or volatility may occur, such as depreciation of a car. Here, as an example, volatility information on the real asset 310 needs to be reflected in the NFT, and this information can be updated through the blockchain node A 320. As a specific example, the blockchain node A 320 may periodically update information related to the real asset 310 and determine whether to update the NFT based on a preset reference value. For example, the blockchain node A 320 updates the NFT based on the information when a serious defect occurs in the real asset 310 based on a preset reference value or a legal dispute occurs based on a preset reference value. can be done Here, the node performing the NFT update may be the aforementioned blockchain node A 320, platform 330, and blockchain node B 360. That is, the NFT can be updated by comparing the information of the real asset 310 acquired based on the blockchain node A 320 and the reference value information, and through this, the change information of the real asset 310 can be reflected in the NFT. can At this time, when the NFT is updated, the platform 330 may provide the updated information to the exchange node 410, the investor 340, and the buyer 370-1 / seller 370-2, through which the information can be shared. In addition, as an example, the above-described blockchain node A 320, platform 330, and blockchain node B 360 may process a transaction for a block or NFT generated based on a smart contract, which will be described later. do.

6 is a diagram illustrating a method of performing a transaction of digital securities by utilizing distributed computing in an embodiment of the present specification. Referring to FIG. 6 , as described above, the platform 330 may select a real asset 310 trust-related blockchain node A 320 . At this time, the blockchain node A (320) may form an off-chain based on the real asset (310). Here, as described above, the off-chain may be a chain that generates a block related to the real asset 310 or an NFT based on a private blockchain, as described above. Thereafter, blockchain node A 320 may register the digital securities with the registration entity 350 and issue a public offering to distribute the digital securities to investors through the platform 330 . Here, the ledger/record and account information for the investor 340 and the buyer 370-1/seller 370-2 can be managed in the blockchain node B 360, as described above. At this time, as an example, when a profit is generated in the real asset 310, the block chain node A 320 may provide the profit to the investors 340 through the platform 330, and information about this may be stored in a ledger or record. can be managed

Also, as an example, FIG. 7 is a diagram illustrating a method of recording transaction details and updating proof of ownership based on digital securities transactions in an embodiment of the present specification. Referring to FIG. 7, as described above, digital securities issued through blocks generated based on real assets 310 are transferred to other buyers 370-1 and sellers 370-2 through the initial investor 340. can be exchanged by That is, general users can buy and sell digital securities of real assets 310 . More specifically, the buyer 370-1 and the seller 370-2 may input buying and selling of digital securities based on the front end of the platform (Platform F/E, 330-1). For example, the front end of the platform may be implemented in conjunction with the exchange node 410 engine. For example, when the seller 370-2 sells digital securities, the digital securities held by the seller 370-2 are frozen and converted to a state in which transfer of ownership is impossible and can be registered as an offer price of the exchange node 410. there is. In addition, when the buyer 370-1 purchases digital securities, the KRW asset used by the buyer 370-1 is frozen by the corresponding amount and converted to a state in which withdrawal is impossible, and is registered as a bid of the exchange node 410 It can be. Here, when the bid and ask prices match, execution can occur, and the execution information is linked to the exchange backend 410-1 and the frontend 720-1 and backend 720-2 of the transaction back-office. can be performed based on That is, buying and selling contracts are issued based on the exchange engine, and contract information may be transmitted to the platform backend 330-2 through the exchange backend 410-1. At this time, the platform backend 330 - 2 may deposit the seller's digital securities and deposit the buyer's won. Then, the platform backend 330-2 may update the asset and deliver the updated asset information to the exchange 410 and the buyer 370-1/seller 370-2. In addition, asset update information may be delivered to the front end 710-1 and the back end 710-2 of the funding training system, through which digital securities may be purchased and sold. Here, as an example, digital securities may be implemented in the form of tokens (or cryptocurrencies, hereinafter tokens). More specifically, as described above, the real asset 310 may be implemented as a block or NFT based on a private blockchain. At this time, digital securities may be issued based on blocks or NFTs and registered with the registration entity 350, as described above. For example, digital securities may be set as tokens based on the number of digital securities. That is, as many tokens as the number of digital securities can be set, and as many tokens as the number of digital securities can be issued in one real asset 310 . At this time, the seller 370 - 2 proceeds with the sale based on the platform 330 and the exchange node 410 through the token, and the buyer purchases the token in Korean won, so that the transaction can be performed. That is, a token may be formed for each individual real asset 310, and a transaction may be performed.

As another example, the token may be converted into a unified form of token based on the platform 330 and the exchange node 410 . More specifically, if a token is generated for each individual real asset 310, the number of types of tokens may increase exponentially based on the real asset 310 being traded, and trading may be restricted. Considering the above points, the platform 330 and the exchange node 410 may consider digital securities issued for individual real assets 310 and convert them into unified exchange tokens. That is, the seller 370-2 and the buyer 370-1 can trade various types of real assets with the same token based on the platform 330 and the exchange node 410, thereby enhancing user convenience. there is.

Also, as an example, FIG. 8 is a diagram illustrating an interface for trading digital securities based on real assets in an embodiment of the present specification. For example, as described above, based on the platform 330 and the exchange node 410, the seller 370-2 and the buyer 370-1 may sell and buy based on the same token. At this time, as an example, even when a transaction is performed based on the same token as described above, information on the real asset 310 needs to be provided. That is, the target real asset 310 can be confirmed, and a transaction for the target real asset 310 can be performed through the same token. To this end, the platform 330 may provide an interface for real asset 310 information. As a specific example, the platform 330 may provide an interface for classifying the types of real assets 310 and classifying them for each real asset. That is, the user of the platform 330 can check the desired real asset type and check information on the real asset 310 in the corresponding section. As a specific example, referring to FIG. 8 , when a real asset is real estate, the platform 330 may provide a real estate section and provide real asset information based on a map interface related to real estate. That is, the real asset 310 may be a real tangible asset, and since the user needs to check information about it, the platform 330 may provide information about it. At this time, the platform 330 may provide different interfaces based on real asset types. For example, if the real asset type is a car or other movable property, the platform 330 may allow the user to recognize it through an interface that provides a picture of the real asset or other necessary information.

On the other hand, if the real asset is real estate, the platform 330 may provide location information or other information of the real asset in association with a map interface. In addition, the platform 330 may provide other information such as satellite imagery or real image information, and may not be limited to a specific form. Here, the platform 330 may convert the value of digital securities for individual real assets into tokens of the same type based on the map interface and provide the value to the user. That is, the user can obtain real asset-related information through an interface provided by the platform 330 and check tokens and other information.

As another example, the platform 330 may also provide similar real asset list information based on real asset information. For example, the platform 330 may provide information on real assets and token price information of the same or similar amount based on the total value or appraised value of the real assets, so that the user can compare them with other real assets. As another example, the platform 330 may provide real assets having the same token price per share or other information, and is not limited to a specific form. As another example, the platform 330 may also provide information on a real asset associated with a target real asset. When the platform 330 provides information about an apartment as a real asset, surrounding commercial buildings associated with the apartment may be provided as related information. For example, a user may be highly likely to purchase a real asset associated with or related to a real asset of interest, and the platform 330 may provide such information through an interface. In addition, the linked real asset information may be in various forms such as real estate-real estate/real estate-movable/movable-movable property, and may not be limited to a specific form. That is, the platform 330 may enable users to trade digital securities for real assets with the same token by providing information related to real assets to users through an interface.

As a specific example, referring to FIG. 8 , the platform 330 is registered with the registration entity 350 through the platform 330 near Gangnam Station and provides information on real assets 810, 820, 830 where digital securities are issued to the user. can provide At this time, the user can select a specific real asset (e.g. building A, 810) and view related information. Also, as an example, when the user selects a specific real asset 810, the platform 330 may allow the transaction to proceed while providing bid/ask information, and the transaction method is as described above.

9 is a diagram illustrating a method of verifying authenticity of electronic securities in an embodiment of the present specification. As described above, the private blockchain node for the real asset 310 is the blockchain node A 320, the platform 330, and the blockchain node B 360, based on which the block for the real asset 310 this can be created.

Here, as an example, whether or not authenticity or verification of digital securities using a block chain may be required. Considering the above points, the registration entity 350 may participate as a node as a node generating a block based on a private blockchain. That is, the registration entity 350 constitutes one node and can directly perform authenticity and verification of digital securities by directly participating as a consensus node generated by a block based on a private blockchain. As another example, when the registration entity 350 does not participate as a consensus node of the private blockchain, a block is created based on the blockchain node A 320, the platform 330 and the blockchain node B 360, , information about this may be delivered to the registration entity 350. That is, the authenticity of the digital securities can be directly proven if the registration entity 350 directly participates as a private blockchain consensus node, and if the registration entity 350 does not participate as a consensus node, blockchain node A 320 ) and block-related information generated by the blockchain node B 360, the platform 330 transmits to the registration entity 350 for verification, thereby performing authenticity and verification tasks. Through this, the authenticity and verification of digital securities can be guaranteed, and ownership can be proven.

10 is a diagram illustrating a method of verifying and recording transaction details in one embodiment of the present specification. For example, based on a private blockchain, block creation for real assets 310 and authenticity of digital securities issuance, as well as transaction of buyers 370-1 and sellers 370-2 and data processing for each user Verification and proof may be required.

More specifically, referring to FIG. 10 , a buyer 370 - 1 and a seller 370 - 2 may trade digital securities or tokens through an exchange node 410 . For example, it is also possible to directly trade digital securities, tokens can be configured based on digital securities, and tokens can be traded. However, in the following, for convenience of description, the case in which tokens are traded is described as standard, but is not limited thereto, and the same may be applied to digital securities. Here, as an example, after a block for the real asset 310 is created based on the private blockchain, digital securities or tokens are created and traded based thereon, so verification of the transaction may be required. That is, it may be necessary to record information that changes based on tokens issued based on blocks as well as block generation. Here, as an example, each transaction may be one transaction. Also, as an example, an operation in which specific data processing is performed in relation to a generated block as well as a transaction may be a transaction. For example, a transaction may refer to a unit of work or a series of operations to be performed to perform one logical function of transforming the state of a database. That is, a transaction can be a logical unit of database system processing. Accordingly, an operation that causes a change to a block based on a block and processing of a token issued based on the block may be a transaction.

For example, each of the operations in Table 1 below of the investor 340 and the buyer 370-1/seller 370-2 in relation to a block generated based on the real asset 310 and a token issued based thereon may be performed based on one transaction. However, this is only one example and is not limited to the following examples. That is, a transaction may be a unit of work as a series of operations that generate block changes, and may not be limited to Table 1 below. Also, as an example, an agreement may be performed based on a pre-set condition based on a transaction, and contents of the performed agreement may be recorded in a block. Here, an operation in which an agreement is performed based on a preset condition may be performed based on a smart contract. As an example, a smart contract may be a system in which the contents agreed upon in advance by contracting parties are programmed in advance and recorded in an electronic contract document, and the contents of the contract are automatically executed when all contract conditions are met. In other words, based on the private blockchain, consensus nodes related to blocks record transaction-related smart contracts in the ledger in advance, and when the smart contract is satisfied based on the corresponding transaction, the contract can be automatically executed. can be recorded in That is, transactions for blocks and block-related tokens can operate only when the consensus nodes satisfy the pre-set conditions, and through this, the transaction details of the investor 340 and the buyer 370-1/seller 370-2 stored and verifiable authenticity.

[Table 1]

As a specific example, referring to FIG. 10 , the buyer 370-1 and the seller 370-2 may perform a transaction based on the exchange node 410, and the corresponding transaction operation is as described above. Here, the transaction between the buyer 370-1 and the seller 370-2 may be one transaction. That is, a transaction may occur based on a transaction between the buyer 370-1 and the seller 370-2. At this time, as an example, the exchange node 410 and the platform 330 may not be nodes capable of ensuring reliability.

More specifically, the exchange node 410 may be relatively easy to attack from the outside because the platform 330 may be a public node where actual transactions are conducted open to a plurality of users. Therefore, authenticity verification may be unclear when the exchange node 410 and the platform 330 process blocks and issued tokens on their own. Accordingly, approval based on a private blockchain node may be required based on a transaction that has occurred in order to verify authenticity of the real asset 310 and to approve an actual transaction. For example, when a transaction occurs in consideration of the above-described operation, the consensus node constituting the private blockchain may verify the transaction. Here, transaction verification can be automatically performed based on a smart contract created based on the consensus node, and when the smart contract is performed based on this, a block in which transaction information is recorded can be created and verification can be completed. . At this time, the platform 330 transfers the aforementioned block information and verification information to the exchange node 410, and the exchange node 410 can confirm the final transaction.

As another example, FIG. 11 is a diagram illustrating a method of processing a transaction of a digital securities owner according to an embodiment of the present specification. Referring to Table 1 described above, a transaction may occur based on a transaction between the buyer 370-1 and the seller 370-2. Also, as an example, a transaction may be generated by user 1110 . Here, the user 1110 may refer to the above-described computing device 200 of FIG. 2 or other devices used by a specific subject, and is not limited to a specific form. However, for convenience of description, it is described as the user 1110. As an example, a case in which the user 1110 changes information or performs other operations as shown in Table 1 may be considered.

Here, as an example, the platform 330 may check the transaction type of the user 1110. More specifically, the platform 330 may check whether the transaction is unrelated to the block of the real asset 310, such as a simple personal information change of the user 1110. At this time, in the case of a transaction unrelated to the real asset 310, the platform 330 may process the corresponding information alone. On the other hand, if the transaction of the user 1110 is a transaction related to the real asset 310, the platform 330 may process the transaction based on verification between consensus nodes of the private blockchain. That is, the platform 330 can determine whether to directly process the transaction by checking whether the transaction of the user 1110 is linked to a block based on the private blockchain, and through this, the authenticity of the block of the real asset 310 can be determined. can be verified

As another example, FIG. 12 is a diagram illustrating a method of configuring an agreement node for transaction processing according to an embodiment of the present specification. Referring to FIG. 12, consensus nodes for transaction processing based on a private blockchain may be configured in various ways. As a specific example, the platform 330 can be accessed by a number of users as described above and may be in an open form, so security may be weak. Therefore, the platform 330 may be excluded from the consensus node of the private blockchain in consideration of the above points. That is, when a block of the real asset 310 is generated or an agreement on a smart contract is performed based on a transaction, except for the platform 330, the blockchain node A 320, the blockchain node B 360 and It may be performed through at least one or more of the registration entities 350 . As another example, a verified node may be added to the consensus node of the private blockchain. For example, the verified node may be a node operated by a government agency or other pre-verified entity, and authenticity can be guaranteed by participating in the consensus node of the private blockchain. In addition, legal reliability and legal regulatory conditions may be satisfied based on the verification node described above, but may not be limited thereto.

As another example, referring to FIG. 12 , nodes of initial investors 1210-1, 1210-2, and 1210-3 may be included as consensus nodes of the private blockchain. Here, the initial investors 1210-1, 1210-2, and 1210-3 may refer to the node of an investor who actually purchased digital securities for the first time by publically issuing digital securities for the real asset 310. For example, the initial investors 1210-1, 1210-2, and 1210-3 may be highly related to the real asset 310, so they may be involved in actual block generation and may be included as consensus nodes of a private blockchain. Here, as an example, if the initial investors (1210-1, 1210-2, 1210-3) trade all tokens and do not hold any tokens for the block of the real asset 310, they are excluded from the private blockchain consensus node It can be. On the other hand, if the initial investors (1210-1, 1210-2, 1210-3) hold some of the tokens, the initial investors (1210-1, 1210-2, 1210-3) have the consensus node status of the private blockchain. It can be maintained, and may not be limited to a specific form.

As another example, the initial investors (1210-1, 1210-2, 1210-3) are nodes of subjects related to real assets 310, and may mean nodes that actually process digital securities public offering and issuance related data. there is. That is, the initial investors (1210-1, 1210-2, 1210-3) are not the users who first received the digital securities or tokens by paying the amount after the digital securities are issued, but are involved in the block and token generation of the real asset 310 It can refer to one node. That is, the initial investors (1210-1, 1210-2, 1210-3) may be nodes that process data related to the real asset 310 with close relevance to the real asset 310, and for this, the private blockchain consensus Node status can be given. Also, as an example, the initial investors 1210-1, 1210-2, and 1210-3 may be nodes that actually manage real assets 310 and check profits or other changes. That is, when the volatility of the real asset 310 occurs, it may be a node that generates and reflects information about it. In addition, when revenue is generated based on the real asset 310, it may be a node that reflects revenue information and performs actual distribution work. That is, the initial investors 1210-1, 1210-2, and 1210-3 may be nodes that process information related to the real asset 310, and may also be given a consensus node of the private blockchain. That is, as the consensus node of the private blockchain, not only blockchain node A (320), which is a trust-related subject, and blockchain node B (360), which is a subject related to account and ledger records, but also nodes related to real assets (310) can be added, Through this, security can be increased and an operation associated with the real asset 310 can be processed.

Also, as an example, FIG. 13 is a diagram illustrating a method of configuring an agreement node in an embodiment of the present specification. Referring to FIG. 13 , a verification node 1310 may be included as an agreement node of the private blockchain described above. For example, the verification node 1310 may be a government agency or other previously verified nodes. More specifically, the verification node 1310 is not related to the real asset 310 itself, but may be a node of a subject that performs management based on the real asset 310 . For example, when the real asset 310 is real estate, it may be a node created based on a court that manages a register or another subject capable of verification. That is, the verification node 1310 may be a node unrelated to the actual real asset 310 itself, but may be a node participating in verification of a block based on a private blockchain. Through the above, verification of the block of the private blockchain can be performed.

Here, as an example, the verification node 1310 may check block generation or other transaction processing based on the real asset 310 . That is, the verification node 1310 can record and view block-related information, and can continuously perform verification of blocks and tokens generated based thereon. Also, as an example, the verification node 1310 may transmit information about the impossibility of verification to the platform 330 when verification is impossible. That is, the verification node 1310 can check the recorded information and exchange information with the platform 330 to monitor the platform 330, thereby securing the reliability of the platform 330.

As another example, FIG. 14 is a diagram illustrating a method of trading digital securities based on a main chain and a side chain in an embodiment of the present specification. For example, when all of the transactions generated based on transactions, etc., are processed in the consensus node of the private blockchain as described above, data processing delay or load may be increased. In addition, for example, if actual transactions are frequent, if there is no need for the consensus node of the private blockchain to recognize all transactions, only necessary transactions can be confirmed. Considering the above points, the platform 330 may configure the main blockchain 1410 based on the private blockchain and configure the side blockchain based on the exchange node 410 . Here, the main block chain 1410 may be a block chain constructed by an agreed node based on the aforementioned private block chain. For example, the main blockchain 1410 may process only transactions that require processing in relation to the real asset 310 without checking all transactions generated based on the side blockchain 1420 . For example, when revenue distribution occurs based on real assets 310, the main blockchain 1410 may process revenue distribution-related transactions based on digital securities or token ratios. In addition, as an example, a transaction that needs to be processed among transactions generated based on the side blockchain 1420 may be processed, and is not limited to a specific embodiment. Here, as an example, the side blockchain 1420 is composed of a public blockchain and may be implemented through individual user nodes based on the exchange node 410 . That is, the side blockchain 1420 is a public blockchain, and anonymous nodes can participate in transaction processing and process data based on smart contracts.

For example, the exchange node 410 may generate an exchange token corresponding to the above-described digital securities or tokens and link them. At this time, the exchange token is a token generated based on the public blockchain and can be freely traded by users in the exchange node 410 . For example, the side block chain 1420 may record information about exchange token changes by configuring each of the block chains 1420-1, 1420-2, and 1420-3 to process and record each transaction. Here, since the link between the exchange token and the real asset token may be in a certain form, the main block chain 1410 may not be involved in changes between exchange tokens. On the other hand, in order to process the linkage information for the real asset token and the exchange token, the transaction may be processed based on the private blockchain consensus node in the main blockchain 1410, as described above.

That is, by configuring the side blockchain 1420 as a public blockchain, data processing efficiency can be increased and reliability of the private blockchain of the real asset 310 can be increased.

15 is a diagram illustrating a method of proving ownership by utilizing distributed computing and dividing and transacting the verified ownership according to an embodiment of the present specification.

Referring to FIG. 15 , digital securities for real assets 310 may be issued, and initial investor tokens may be allocated. For example, fund information may be registered from the FTS front end 710-2 to the FTS back end 710-1 based on the blockchain node A 320. At this time, if the fundraising conditions are satisfied based on the FTS, the ownership of the real asset 310 can be transferred based on the blockchain node A 320, and information about it can be verified. Then, as described above, a block is created based on the private blockchain, and digital securities or tokens can be issued based on the created block. At this time, the back end 330-2 of the platform may check fund information from the initial investors through the front end 330-1 of the platform, and deliver tokens issued based on the fund deposit information to the initial investors. In addition, the back end 330-2 of the platform can register the issued token in the exchange, and the back end 410-1 of the exchange transmits information about this to the exchange back-off back end 720-2 and the exchange. The token can be finally registered by passing it to the back-off-front end 720-1. Through the above, initial investors can be allocated tokens based on deposits of funds, and can trade the allocated tokens through an exchange. Here, as an example, token issuance may be performed according to a block generated based on a private blockchain as described above.

As an example, FIG. 16 is a diagram illustrating a method of performing proof of ownership of a real asset based on a private blockchain according to an embodiment of the present specification. As an example, the private blockchain may record information about the real asset 310 as described above. For example, at least one of asset location information, asset appraisal information, asset bank record information, asset collateral information, volatility information, asset insurance information, and asset management information may be recorded in the private blockchain 1610 .

Here, as an example, when the platform 330 issues digital securities and allocates them to initial investors, information on the private blockchain 1610 may be transmitted to initial investors. For example, each of the initial investors may also be a node, and each node may exchange information with the platform 330 . More specifically, the platform 330 may deliver information about the real asset 310 and information about the private blockchain 1610 to each initial investor node. In addition, as an example, the platform 330 may further generate specific information in the private blockchain 1610 related to the real asset 310, and may also transmit information about this to each initial investor node. After that, the initial investors can check information related to the real asset 310 and the private blockchain 1610, and deliver information on investment agreement and fund deposit information to the platform 330, through which the platform Allocate to early investors.

17 is a diagram illustrating a method of distributing expected profits based on proof of ownership in an embodiment of the present specification.

Referring to FIG. 17, when profits are generated in real assets 310, dividends can be made to users who have digital securities or tokens. For example, when the real asset 310 is real estate, real estate may generate revenue based on a rental business or the like. At this time, as an example, blockchain node A 320 may perform a dividend for the generated revenue.

As a specific example, referring to FIG. 17 , revenue for real assets 310 may occur. Here, as an example, the blockchain node A 320 may generate dividend information based on the revenue for the real asset 310 . For example, real assets 310 may generate costs as well as revenue. As a specific example, in the case of real estate, management fees, taxes, and other expenses may occur, and processing may be required. Accordingly, the blockchain node A 320 may determine the dividend by considering the information on the generated revenue and the cost information on the real asset 310 without allocating all of the revenue generated by the real asset 310 . Here, as an example, the blockchain node A 320 may directly determine the dividend amount in consideration of the revenue information and the cost information. As another example, the blockchain node A 320 may calculate revenue information and cost information for a predetermined period or a certain period of time, and determine a dividend amount based thereon. As another example, whether to pay dividends and the amount of dividends may be determined based on consensus nodes participating in blockchain nodes. For example, revenue information and cost information occurring in real assets 310 may be flexible, and if expenses occur after all assets are allocated, the means for paying them may be limited. Accordingly, there is a need to determine whether or not a dividend and a dividend amount are determined based on the revenue information and the cost information in consideration of the above points. For example, the nodes participating in the private blockchain can automatically determine whether or not to pay dividends and the amount of dividends based on revenue information and cost information based on smart contracts, and record this information in blocks. As another example, blockchain node A (320) determines whether or not to pay dividends and the amount of dividends based on revenue information and cost information on its own, receives approval from nodes participating in the private blockchain, and distributes dividends. It may be, and may not be limited to a specific form.

At this time, referring to FIG. 17, whether or not to allocate a dividend is determined, and when the dividend proceeds, the back end 330-2 of the platform reads the dividend information from a block generated based on the private blockchain based on the real asset 310. can come After that, the allocation-related information can be processed based on the FTS back end 710-1 and the FTS front end 710-2, and allocated to each user through the platform 330 and the exchange node 410. It can be. Then, when the dividend is completed, a transaction may occur, and the transaction may be performed based on the smart contract of the private blockchain and recorded in a block.

As a specific example, when the above-described main blockchain 1410 and side blockchain 1420 exist, the transaction between the buyer 370-1 and the seller 370-2 through the exchange node 410 is performed on the side blockchain. (1420). On the other hand, since the dividend is a transaction performed based on real assets 310, it can be performed in the main block chain 1410. Here, as an example, the main block chain 1410 may determine a user to be distributed in a preset period or at a preset time. More specifically, in the case of frequent transactions through the exchange node 410, since the token subject may change from time to time, it may be necessary to determine the subject to receive the dividend. Considering the foregoing, the main block chain 1410 may determine a dividend subject at a specific point in time or in a specific section and distribute the dividend. As a specific example, the main blockchain 1410 may determine the subject of allocation based on the point in time when a specific block height is created in the ledger as the created block is updated. In addition, as an example, a specific block height section may be determined, and a dividend subject may be determined based on the determined block height section, and dividend may be performed, and may not be limited to a specific form. That is, dividends generated based on real assets 310 may be allocated to token owners at a specific point in time.

18 is a flowchart of an encryption method for blockchain-based transaction details proof and ownership transfer using distributed computing.

Referring to FIG. 18, it is possible to provide an encryption method for proof of transaction details and transfer of ownership based on blockchain by utilizing distributed computing. At this time, based on the first asset information, a first asset block may be generated through a preset consensus node of the private blockchain (S1810). At this time, the first asset may be the above-described real asset 310, which is As described above. Next, at least one token corresponding to the digital securities may be generated based on the first asset block (S1820), and the at least one token may be distributed to at least one or more initial investors (S1830). Next, at least At least one or more tokens distributed to one or more initial investors may be registered in the exchange node, as described above. (S1840) At this time, as an example, the first asset information includes asset location information, asset appraisal information, and asset bank It may include at least one or more of record information, asset collateral information, volatility information, asset insurance information, and asset management information, as described above. In addition, the first asset block may be generated based on the first asset block through a private blockchain.

In addition, as an example, when distributing at least one or more tokens to at least one or more initial investors, the platform converts the first asset block information generated based on the first asset information and the private blockchain to each of the at least one or more initial investors. node can be transmitted. Thereafter, the platform receives fund deposit information based on investment agreement information and token information to which each of the initial investors is allocated based on the first asset information and the first asset block information from the node of each of the at least one or more initial investors. can After that, the platform may distribute at least one or more tokens to each node of the at least one or more initial investors based on the consent information and the fund deposit information, as described above.

Also, as an example, the preset consensus node of the private blockchain may include a first node, a second node, and a platform node, and a first asset block may be generated based on the preset consensus node. Here, the first node is the above-described blockchain node A 320 and is a node that processes the trust information of the first asset, and the second node is the above-described blockchain node B 360 and is verified based on at least one token. It may be a node that processes fund information to be used.

In addition, as an example, when the registration entity node is included in the preset consensus node of the private blockchain, the first asset block is generated based on the platform node, the first node, the second node, and the registration entity node, and the first asset At least one or more tokens issued on a block basis may be registered as digital securities without verification by the registration entity node.

On the other hand, when the registration entity node is not included in the preset consensus nodes of the private blockchain, the first asset block is generated based on the platform node, the first node and the second node, and the platform is based on the first asset block At least one token is issued, at least one token information is delivered to a registration entity, and the registration entity can determine whether to register as a digital security based on the received at least one or more token information, as described above.

Also, for example, when at least one or more tokens distributed to at least one or more initial investors are registered in an exchange node, the at least one or more initial investors may perform transactions for at least one or more tokens based on the exchange node. At this time, when a transaction is performed, a transaction occurs, and the transaction may be recorded and updated in the first asset block based on the private blockchain, as described above.

The embodiments described above may be at least partially implemented as a computer program and recorded on a computer-readable recording medium. Computer-readable recording media on which programs for implementing the embodiments are recorded include all types of recording devices in which data readable by a computer is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, and optical data storage devices. In addition, computer-readable recording media may be distributed in computer systems connected through a network, and computer-readable codes may be stored and executed in a distributed manner. In addition, functional programs, codes, and code segments for implementing this embodiment can be easily understood by those skilled in the art to which this embodiment belongs.

The present specification reviewed above has been described with reference to the embodiments shown in the drawings, but this is only exemplary, and those skilled in the art will understand that various modifications and variations of the embodiments are possible therefrom. However, such modifications should be considered within the technical protection scope of the present specification. Therefore, the true technical protection scope of the present specification should be determined to include other implementations, other embodiments, and equivalents to the claims by the technical spirit of the appended claims.

Claims (7)

In the encryption method for blockchain-based transaction history proof and ownership transfer using distributed computing,
Generating a first asset block through a preset consensus node of a private blockchain based on first asset information;
generating at least one token corresponding to a digital security based on the first asset block;
distributing the at least one or more tokens to at least one or more initial investors; and
Registering the at least one or more tokens distributed to the at least one or more initial investors in an exchange node; including, an encryption method for proof of transaction details and transfer of ownership.
According to claim 1,
The first asset information includes at least one or more of asset location information, asset appraisal information, asset bank record information, asset collateral information, volatility information, asset insurance information, and asset management information;
The first asset block is generated based on the first asset information through the private blockchain, encryption method for proof of transaction details and transfer of ownership.
According to claim 2,
Distributing the at least one or more tokens to at least one or more initial investors;
Transmitting, by a platform, first asset block information generated based on the first asset information and the private blockchain to each node of the at least one or more initial investors;
The platform provides fund deposit information based on investment consent information based on the first asset information and the first asset block information from the node of each of the at least one or more initial investors and token information to which each of the initial investors is allocated. receiving; and
Distributing, by the platform, the at least one or more tokens to the node of each of the at least one or more initial investors based on the consent information and the fund deposit information; including, an encryption method for proof of transaction details and transfer of ownership .

According to claim 1,
The preset consensus node of the private blockchain includes a first node, a second node, and a platform node, and the first asset block is generated based on the preset consensus node,
The first node is a node that processes trust information of a first asset, and the second node is a node that processes fund information verified based on the at least one or more tokens, an encryption method for proof of transaction details and transfer of ownership. .
According to claim 4,
When the preset consensus node of the private blockchain includes a registration entity node, the first asset block is generated based on the platform node, the first node, the second node, and the registration entity node; the at least one or more tokens issued based on the first asset block are registered as digital securities without verification by the registration entity node;
When the registered entity node is not included in the predetermined consensus node of the private blockchain, the first asset block is generated based on the platform node, the first node and the second node, and the platform issue the at least one or more tokens based on a first asset block and communicate the at least one or more token information to the registration entity;
Wherein the registration entity determines whether to register as a digital security based on the received at least one token information, the encryption method for proof of transaction details and transfer of ownership.
According to claim 1,
When the at least one or more tokens distributed to the at least one or more initial investors are registered in the exchange node, the at least one or more initial investors perform transactions for the at least one or more tokens based on the exchange node,
When the transaction is performed, a transaction occurs, and the transaction is recorded and updated in the first asset block based on the private block chain.
A computer program stored in a computer readable medium combined with hardware to execute an encryption method for blockchain-based transaction history proof and ownership transfer by utilizing the distributed computing according to any one of claims 1 to 6.

Images