Trading system
The introduction of 'ThingsToken' using ERC-3525 addresses the challenge of handling diverse objects in IoT transactions, enabling efficient and scalable management of objects and users through smart contracts.
Patent Information
- Application Number
- JP2023114703
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-07-12
- Publication Date
- 2025-07-25
- Estimated Expiration
- 2043-07-12
AI Technical Summary
Existing systems struggle to handle transactions involving objects that are not directly related to IoT devices, as they often involve unrelated participants and a vast number of diverse objects, making it difficult to apply IoT technology effectively.
A token called 'ThingsToken' is introduced to describe the currency relationship of objects, using ERC-3525 (Semi-fungible Token) to incorporate securities and enable smart contracts, allowing for the management of a large number of objects and users while ensuring scalability and diversity.
This approach enables efficient handling of a large number of objects and users, ensuring diversity and asynchronous participation, overcoming the limitations of conventional systems by integrating security information directly into the object tokens.
Smart Images

Figure 0007713244000001 
Figure 0007713244000002 
Figure 0007713244000003
Abstract
Description
Technical Field
[0001] The present invention relates to a trading system for conducting transactions of things. In particular, the present invention relates to a trading system that can handle things not directly related to IoT devices while using IoT technology.
Background Art
[0002] In recent years, the Internet of Things (IoT), which is the internet of things, has been widely used. The data obtained by sensors and the like on this IoT is used for various purposes. A device that provides IoT data is called an IoT device. Also, transactions of data generated by this IoT device are actively conducted.
[0003] For example, in Patent Document 1 below, a system for connecting IoT devices via LPWAN and trading points is disclosed. Also, in Patent Document 2 below, a method for conducting financial transactions using IoT devices is disclosed.
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Patent Document 2
Summary of the Invention
Problems to be Solved by the Invention
[0005] As described above, using IoT technology to trade intangible things such as points and finance has been widely proposed. However, in the real world, when trying to build an industrial system related to Things (hereinafter, particularly referred to as things), it is often necessary to incorporate things and people not directly related to IoT devices. Even if an IoT device is attached to the object, unrelated participants or ordinary people may participate in the transaction, and as the market expands, the number of such ordinary people is also increasing. In addition, objects that have nothing to do with IoT (devices, simple goods) will also increase as the market expands. In other words, most of the objects in the world are devices (mere objects, (goods)) that have nothing to do with IoT. If such a situation cannot be dealt with, it is difficult to apply IoT technology to the object transaction system. To address such issues, the inventor of the present application considered that the following devices were necessary. (1) It is necessary to handle the currency relationships (related parties, especially investors, beneficiaries, and intervening parties) related to the objects as described above. (2) Also, the number of objects in the real world is enormous (so enormous that it cannot be compared with the number of IoT devices), and it is essential to realize the ability to handle objects exceeding the scale of several trillion. (3) Also, the related parties of the industrial system (transaction system) are diverse (for example, the jurisdictions to which they belong are also diverse, etc.), and a method that can handle them without contradiction is essential.
[0006] In view of such circumstances, an object of the present invention is to provide a transaction system that can construct a transaction system for general objects using IoT technology.
Means for Solving the Problems
[0007] (Basic Principle) Specifically, to solve the above problems, a means of issuing a token "ThingsToken" (hereinafter referred to as "object token") that describes information handling the currency relationship related to the object is adopted. As a result, since the currency relationship is originally described in the object, there is no need to separately refer to the currency rules, and it becomes possible to handle a huge number of objects and users. As a result, it becomes possible to reasonably apply blockchain economics including objects to the real world. (Comparison with Conventional Blockchain) Compare the conventional transaction management system using blockchain with the structure of the present invention. (Conventional System) Conventionally, "thing tokens" and "currency tokens, security tokens" were defined as separate tokens. As a result, information regarding things and information regarding currency were managed and executed as separate databases. (System of the Present Invention) In the present invention, "tokens with embedded securities" are used as "thing tokens". As a result, the relationship between participants with respect to things can be executed using tokens and smart contracts.
[0008] (Example of Implementation Method) By leveraging ERC-3525 (Semi-fungible Token), securities can be incorporated into ThingsToken (thing token), or a separate smart contract can be implemented as ThingsProtocol to endow ThingsToken with both the non-fungibility as a thing and the fungibility as a security. By having various stakeholders participate in ThingsProtocol, it is possible to simultaneously realize diverse contractual relationships and scalability between Things and participants.
[0009] (Regarding ERC-3525) ERC-3525 is one of the token standards of Ethereum. It is often called SFT (Semi-fungible Token). It is an important type of token along with NFT (Non-fungible Token) (ERC-721), FT (Fungible Token) ERC-20, etc. ERC-3525 (SFT) can be used as a currency like an FT or can be given a unique ID that shows distinguishability like an NFT. ERC-3525 can support multiple tokens in one smart contract. Also, ERC-3525 has the feature of facilitating the splitting and integration of tokens and is considered suitable for finance, for example. In this embodiment, the description will center around ERC-3525, but any SFT (Semi-fungible Token) with similar features can be used. Also, in this patent, the system using Ethereum will be mainly described, but any system in which the same transactions are possible can be used. Note that "ETHEREUM" is a registered trademark.
[0010] (Principle Diagram) The principle diagram of the present invention is shown in FIG. 12. As shown in this figure, in a conventional transaction system using a blockchain such as Ethereum, the token 10 representing an object, the security information 12, and the service user 14 are configured separately. Here, the token 10 representing an object includes the account of the object, the DT, and the information of the object. DT is Device Token, and the information of the object is, for example, DAT (Device Asset Token), etc. Also, the security information 12 preferably includes, in addition to the security information itself, a program, the account information of the object, the account information of the service user, etc. Also, the service user 14 has the account of that user. Under such a configuration, a bottleneck may occur in the processing of the security information 12, and it is assumed that it may not be scalable. Also, it is considered difficult to provide diversity for the user 14.
[0011] In contrast, the transaction system of the present invention (Figure 12) is composed of a physical token 100 incorporating security into the physical object and a service user 14. Here, the token 100 representing the physical object includes the account of the physical object, the DT, and the information of the physical object. The DT is a Device Token, and the information of the physical object is, for example, a DAT (Device Asset Token) or the like. Also, since security is incorporated, as shown in Figure 12, security information 120 is added to the physical token 100. Similar to the security information 12 in the conventional configuration, the security information 120 preferably includes, in addition to the security information itself, a program, the account information of the physical object, the account information of the service user, and the like. With such a mechanism, no bottleneck occurs and it is possible to scale. Also, with respect to the use related to the physical object, diversity can be ensured by the direct contact of the user 14.
[0012] (Advantages of the Present Invention) 1. Both physical objects and users can be handled even if their numbers become extremely large. As described with reference to Figure 12 above, in the prior art, a database for handling security information is required, and it is necessary to separately manage the relationship between physical objects and participants. However, in the present invention, such management is unnecessary. As a result, even if the number of physical objects and users increases, it can be handled. 2. Diversity of physical objects and participants can be realized As described above, according to the principle of the present invention, management of the relationship between physical objects and participants is unnecessary. As a result, diversity of physical objects and participants can be ensured. 3. Participants can participate asynchronously. As described above, according to the principle of the present invention, management of the relationship between physical objects and participants is unnecessary. As a result, participants can participate asynchronously according to their own convenience.
[0013] (Explanation of FT and NFT) The conceptual diagrams of FT (Fungible Token) (e.g., ERC-20) and NFT (Non-fungible Token) (e.g., ERC-721) are shown in FIG. 13. FT (Fungible Token) 130, also called a fungible token, is mainly used as currency on a trading system. For example, it can be ERC-20 or the like. NFT (Non-fungible Token) 132, also called a non-fungible token, is mainly used as an NFT item. For example, it can be ERC-721 or the like. As shown in FIG. 13, for FT 130, for example, ERC-20 is used as currency or banknotes, and ERC1400 is used as securities (e.g., corporate bonds, commodity vouchers), etc. Thus, FT has the characteristic of value (amount) 140.
[0014] As shown in FIG. 13, for NFT 132, for example, ERC-721 and ERC-1155, etc., are used as NFT art items. Thus, in addition to the characteristic of value (amount) 140, NFT 132 also has the data of the owner (account) 142. Furthermore, NFT 132 also has the content 144 as art items, etc. This content 144 can be text data or non-text data. And FT and NFT are linked by a smart contract 134. The smart contract 134 stipulates the conditions 146 that form the content of the contract.
[0015] (Specific Configuration) Specifically, the present invention adopts the following configuration.
[0016] The trading system according to the present invention (for example, a system including PTPF200 described later, IS240 which is an account on PTPF200, TO242, SH500, etc.) uses a blockchain to preserve and manage a trading contract of an item, and includes a data transaction unit (for example, PTPF200 described later) that executes the trading contract of the item, an item owner account (for example, TO242 described later) that owns the item, an issuer account (for example, IS240 described later) that issues an item token (for example, item token 100 described later) for the item owned by the item owner, and one or more stakeholder accounts (for example, SH500 described later) that conduct the transaction of the item. The data transaction unit executes the trading contract using the item token among the stakeholder accounts in order to conduct the transaction of the item, and the item token is a Semi-fungible Token.
[0017] The item token may be a token having security fungibility and non-fungibility as an item.
[0018] The item token may be a token having an item account, a Device Token, a Device Asset Token, and security information.
[0019] The data transaction unit includes a brand account (for example, B238 described later) that conducts transactions for a predetermined type of item. The brand account and the issuer account enter into a contract, and based on the contract, the issuer account may supply the issued item token to the brand account.
[0020] The trading system further includes a brand DAO (for example, Brand DAO described later) which is a rule interface that defines rules between one or more of the brand accounts and other accounts. The brand may enter into a contract with the issuer account according to the rules defined by the brand DAO.
Effect of the Invention
[0021] According to the present invention, a transaction system related to general items can be provided by using a transaction system that can be constructed using IoT technology.
Brief Description of the Drawings
[0022] [Figure 1] It is a conceptual diagram of PTPF, which is the data transaction infrastructure adopted in the transaction system of this embodiment. [Figure 2] It is a conceptual diagram of PTPF of this embodiment. [Figure 3] It is a conceptual diagram of PTPF of this embodiment. [Figure 4] It is an explanatory diagram of ThingsProtocl. [Figure 5] It is a conceptual diagram of ThingsOwner. [Figure 6] It is a conceptual diagram for explaining the roles of AC / DB and IS in this embodiment. [Figure 7] It is an explanatory diagram of Brand DAO in this embodiment. [Figure 8] Brand DAO: It is an explanatory diagram showing the state of Things (approved) that can be referred to by Brand. [Figure 9] It is an explanatory diagram of the architecture that separates the brand interface X and the Things interface Y. [Figure 10] It is a conceptual diagram showing the relationship between ThingsDAO and Stakeholder. [Figure 11] It is an explanatory diagram showing an implementation example of the transaction system according to this embodiment. [Figure 12] It is a conceptual configuration diagram of the conventional transaction system and the transaction system of this patent. [Figure 13] It is an explanatory diagram of FT and NFT.
Embodiments for Carrying Out the Invention
[0023] Hereinafter, embodiments of the present invention will be described based on the drawings.
[0024] Overview of the 1st PTPF (Payload Transaction Platform) In this embodiment, as described above, a transaction system that enables efficient transactions for things is proposed, and as its basis, the PTPF (Payload Transaction Platform) developed by the inventors of the present invention is adopted. Therefore, first, this PTPF will be briefly described. Fig. 1 shows a conceptual diagram of the PTPF 200. The PTPF 200 is a data transaction infrastructure that utilizes the blockchain 202 to realize the information circulation with transaction information added to a large amount and various types of IoT data. The PTPF 200 is premised on cooperating with the DEXPF 204 also developed by the inventors of the present invention. The DEXPF 204 is a data transmission infrastructure. The PTPF 200 is so to speak in charge of transaction contracts, and the DEXPF 204 is in charge of the actual data transmission. However, since the DEXPF 204 has no direct relation to the present patent application, the description thereof will be omitted. As shown in Fig. 1, if a transaction is concluded between Company G and Company E, the PTPF 200 exchanges transaction data between Company G and Company E, and the DEXPF transmits and receives the IoT data of the transaction target based on the contract.
[0025] By this mechanism, an IoT data transaction infrastructure is realized in which various transaction information such as ownership is securely added to the transmitted IoT data by blockchain technology, and control such as the destination of the data is made possible. As a result, the circulation of IoT data is promoted, and the cooperation between data and physical objects becomes possible. The PTPF 200 is a protocol using blockchain. By using the PTPF 200, it is possible to realize IoT data transmission that absorbs the differences in services between different businesses and the differences in procedures between platforms, such as the differences in IoT devices and their manufacturer protocols, which were problems in conventional IoT systems. According to the PTPF 200, various transaction information such as ownership, usage rights, and price is added to the transmitted IoT data, control such as the destination of the data is made possible, and the cooperation between data and physical objects is realized.
[0026] (2) Application in this Embodiment The trading system of this embodiment uses PTPF200 as a data trading infrastructure, and is an explanatory diagram of NFT that can be deployed there. And an explanatory diagram of related software is shown in FIG. 2. As shown in FIG. 2, PTPF200 is on the base blockchain 206 and includes DT208, MDT210, etc. in addition to the protocol 200a of PTPF. DT (Device Token) 208 represents a device. For example, it may be an extended token of ERC-721 (NFT). MDT (Meta Data Token) 210 represents data information to be traded. For example, it may be an extended token of ERC-721 (NFT). The protocol 200a of PTPF is a smart contract protocol and performs functions such as holding data trading information and settlement.
[0027] FIG. 3 shows a more detailed software configuration diagram. On the base blockchain 206, PTPF200, the protocol 200a of PTPF, MDT210, and DT2-8 are provided. On the blockchain 202, various devices are virtualized (tokenized) and represented.
[0028] 2. PTPF in this Embodiment What is characteristic of PTPF200 in this embodiment is that it uses the ThingsProtocol. This is shown in the explanatory diagram of FIG. 4. (i) AC (Acquirer) 234 issues a sell offer to PTPF200 on behalf of DO (Device Owner) 230. (ii) DB (Data Broker) 236 issues a buy offer to PTPF200 on behalf of SP (Service Provider) 232 that uses data. (iii) PTPF200 performs matching to form and manage a contract. (iv) B (Brand) 238 is an organization that conducts transactions on the trading system provided by PTPF200. In this embodiment, in particular, it corresponds to a sake brewing cooperative or the like that sells sake (liquor). (v) What is characteristic in this embodiment is that the IS (Issuer) 240 issues the physical token 100 to the TO (Things Owner) 242. The TO 242 is, for example, an individual wine bottle. As a result, the TO 242 can execute a transaction contract regarding the sale of the item using the physical token 100 on the PTPF200.
[0029] This physical token 100 is a token with very favorable properties for handling passive "things" that do not emit data. Thus, what is characteristic in this embodiment is that it introduces a new concept of a token that can flexibly describe the attribution relationship of the rights of things. (vi) Also, in this embodiment, a ThingsDAO 220 is set up. This ThingsDAO 220 is a decentralized autonomous organization for physical transactions. Wholesalers and individual liquor stores can smoothly conduct physical (sake) transactions by participating in this ThingsDAO 220. In FIG. 4, the ThingsDAO 220 is shown by a dashed line. That is, the portion surrounded by the dashed line in FIG. 4 constitutes the ThingsDAO 220. Also, in FIG. 4, W represents a configuration necessary for IoT data transmission, and Z represents a new configuration for using the physical token 100. Note that AC234, DB236, DO230, SP232, IS240, TO242, and B238 are all accounts of the PTPF200.
[0030] (1) Token types (overall) of ThingsProtocol In the trading system using the blockchain in this embodiment, the tokens to be used are described. (a) Sensing device · DAT (Device asset Token), for example, ERC - 721, etc. DT (Device token) 208: Represents the device as described above. For example, it may be an extended token of ERC-721 (NFT). MDT (Meta data Token) 210: Represents the data information to be traded as described above. For example, it may be an extended token of ERC-721 (NFT).
[0031] (b) Things · TT ERC-3525 (ThingsToken) What is characteristic in this embodiment is to use a things token (ThingsToken) which is a token for an individual thing. This things token can use ERC-3525 (SFT), etc. Also, the things token may be referred to as TT. (c) Value · TCX In this embodiment, this TCX is used as a thing that plays the role of value, that is, currency. That is, TCX is the Utility Token of the ThingsProtocol. For example, ERC-20, etc. can be used. (d) Organization · ThingsDAO ThingsDAO220 is as described above, and is a framework for contracts and smart contracts. In this embodiment, basically, by participating in ThingsDAO220, transactions of things can be executed. ThingsDAO220 refers to a program or a collection of rules that describe the relationships of each participant and stakeholder and embody them in a contract (Nexus of Contract).
[0032] FIG. 5 shows a detailed conceptual diagram of a TO (Things Owner) 242 and the like. As shown in this figure, the TO 242 manages a plurality of TTs (Thing Tokens) 100 issued for the things (mono) 100m it manages. Similarly, the DO 230 manages a plurality of Dev (devices) 400 it manages. And the SP 232 provides benefits to the Bnf 402. The Bnf represents a Beneficiary and may also be expressed as "beneficiary". The other B238, IS240, AC234, DB236, etc. have the same configuration as in FIG. 4 and the like.
[0033] (2) Roles of AC / DB and IS FIG. 6 shows a conceptual diagram for explaining the roles of AC / DB and IS in this embodiment. The AC 230 approves the accounts of the DOs. It also issues DT208 and MDT210. The DB 236 approves the accounts of the SP238. The IS 240 approves the accounts of the TO (Things Owner) 242. It also issues a TT (ThingsToken). This TT is the thing token described so far. In this embodiment, by issuing the TT, it is possible to efficiently handle individual things. Note that the IS 240 represents an issuer as shown in FIG. 6. This means issuing a TT (ThingsToken) to the TO (Things Owner).
[0034] (3) Brand operation: Contract relationship regarding B (Brand DAO) FIG. 7 shows a conceptual diagram for explaining the Brand DAO in this embodiment. Note that DAO represents a Decentralized Autonomous Organization and is called a decentralized autonomous organization in Japanese. The Brand DAO in this embodiment is a constituent unit of the actual operation of the ThingsProtocol. That is, it is a contract unit. In this embodiment, this Brand DAO is described using the framework of ThingsDAO220. The rule interface of the ThingsProtocol for each Brand is the Brand DAO. As shown in FIG. 7, B238 is the rule setter.
[0035] AC234 and DB236 are participants who execute the agency actions of B238 against DO230 and SP232. DO230 and SP232 are participants who actually perform Data transmission and service provision under the rules of B238. Although Brand DAO is a decentralized autonomous organization of a given brand, depending on the purpose of its business, it may also use (combine) protocols, mechanisms, laws, and rules other than PTPF200.
[0036] For example, in order to conduct transactions related to alcohol, it is also suitable to make a liquor cooperative (voluntary organization) function as the initial B238 to form a Brand DAO. If necessary, it is also suitable to add members, etc. at a later date. Such Brand DAO assumes that various Brand DAOs will be created depending on the industry. A clothing DAO, a food DAO, etc. may be constructed on the transaction system according to this embodiment. Note that Brand DAO may generally be composed of multiple participants, but it may also be composed of a single company. If an ecosystem can be operated by a single company, it is also possible to form a single-company DAO.
[0037] (4) Brand DAO: Approval of Things (objects) that can be referenced by the Brand Now, in Brand DAO, B238 may set various rules. Specifically, for example, approval of referenceable Things can be mentioned. An explanatory diagram showing this is shown in FIG. 8. As shown in Fig. 8, AC 234 / DB 236 and DO 230 / SP 232 exist in the rule interface (Brand DAO) of ThingsProtocol for each Brand 238. As shown in Fig. 7, multiple B 238s can exist. In Fig. 8, B1, B2, B3, ... Bn are depicted. The operation in Fig. 8 will be described below. (a) Each B238 can use Things from each Brand DAO by entering into a contract with an IS (issuer) 240. (b) Each B238 can use Things of TO242 under IS240 to participate in each B238's ecosystem by entering into a contract with IS240. This enables the provision of value related to Things to participants of B238.
[0038] (c) Distribute the generated value to each stakeholder. For example, a part of the value can be distributed to the TO 242, and another part of the value can be distributed to the IS 240. That is, it can be configured so that the IS 240 can also receive the distributed revenue. Distribution can be freely made to each stakeholder, and the ratio can also be freely determined. In addition, an IS 240 may participate in multiple Brand DAOs. In the example of Figure 8, IS1-240 participates in B1-238, B2-238, and B3-238, and ISn participates in B1-238 and Bn-238. For example, to trade alcohol, a lead company would initially be IS240 and each sake brewery could be certified as TO242. This IS40 could then issue a ThingsToken (TT) for each bottle of sake handled by each brewery.
[0039] (5) Use of TT (physical token) from B A distinctive feature of this embodiment is that a trading system suitable for trading goods is realized by adopting SFT (e.g., ERC-3525) as a token. This item token (also referred to as TT) 100 is issued by IS240 for each TO242. Now, B238 (for example, a sake brewing association) concludes contracts with AC234, D236, etc. via PTPF200. On the other hand, IS240 issues item token 100 for TO242. At this time, item token 100 is issued for each item handled by each TO242 (Fig. 9). Fig. 9 is an explanatory diagram regarding the use from B238 to TT100 in this way. As shown in this Fig. 9, in this embodiment, an architecture that separates brand interface X and Things interface Y is adopted. Fig. 9 is also a conceptual diagram of the architecture using brand interface X and Things interface Y in this way. Note that the interface means Domain.
[0040] In this embodiment, under such an architecture, Issuer (IS) 240 issues TT (item token) 100 as described above. Which TT100 is to be participated by which B238 depends on the conditions between TO242 and B238. If the conditions are met, IS240 permits the connection of the said TT100 to the brand interface X of the said B238. By such a mechanism, the use of TT (item token) 100 becomes possible from B238. Also, as shown in Fig. 9, IS240 can manage a plurality of TO242. Also, TT (item token) 100 issued by IS240 can be issued for each item of each TO242, for example, each wine bottle (the bottle corresponds to an individual Thing).
[0041] In this embodiment, as the Thing Token (TT) 100, a token called Semi-fungible Token (SFT) (for example, ERC-3525) is adopted. As described above, SFT enables easy splitting and integration of tokens. Therefore, for example, even when there are a large number of bottles of the same type of liquor, each bottle can be easily managed by splitting them. Also, when a large number of liquor bottles are grouped together in a container, they can be grouped (integrated), and the liquor bottles in one container can be represented by one token, enabling smoother circulation management. As a result, transactions of things can be carried out more smoothly than before.
[0042] 3. ThingsToken (Thing Token) 100 and ThingsDAO 220 Hereinafter, the relationship between the ThingsToken (Thing Token) 100 and the ThingsDAO 220 will be described in more detail. (1) The TT (ThingsToken) 100 is a token that behaves in a kind of security-like manner and can describe various rights and relationships associated with the thing while being the thing as an individual item. This point is a characteristic matter in this embodiment, and for example, a token called Semi-fungible Token (SFT) (for example, ERC-3525) can be used. (2) On the other hand, in a transaction system using a blockchain such as the PTPF 200, the DAT (Device Asset Token) has conventionally been treated as a thing that generates data such as IoT, that is, sensor devices. That is, it functions as a token for handling IoT devices.
[0043] (3) The ThingsProtocol refers to the overall program and rules that enable value transactions and contract executions among various stakeholders surrounding a blockchain that operates the ThingsToken (Thing Token) 100, a blockchain that does not necessarily operate the ThingsToken (Thing Token), tokens (such as NFTs), etc. (4) TCX (Things Transaction Currency) is a general-purpose value unit (Transaction Currency) that can exchange consideration when various stakeholders participate, starting from ThingsToken (Thing Token) 100. TCX functions as a currency unit that provides common currency and utility to the ecosystem related to ThingsToken 100.
[0044] (5) The architecture of ThingsToken defines a series of roles for participants through which participants can create value through ThingsToken and TCX. List each role. (a) Participants related to IoT, "DO230 / SP232, AC234 / DB236", (b) Participants related to Thing (TT = ThingsToken) 100, "TO242 = Things Owner" and "IS240 = issuer", and (c) There are seven types of players, the rule describer who bundles them = "B238 (Brand)" as the platform. (6) "ThingsDAO" is a Nexus of Contract including a program that defines economic rules and legal relationships between (a) tokens (TT, DAT, TCX), (b) participants (AC, DB, DO, SP, B, IS) using ThingsProtocol, and other external communities, and is a virtual self-governing organization (decentralized autonomous organization) (= DAO).
[0045] SH (Stakeholder) is the account of ThingsDAO 220 Figure 10 shows a conceptual diagram indicating the relationship between ThingsDAO220 and Stakeholder. The account (holder) of ThingsDAO220 is called SH (Stakeholder) 500. In Figure 10, B238, which is one type of the account of ThingsDAO220, is shown, and this B238 is also a type of SH500. Also, SH500 is a person related to ThingsDAO220.
[0046] SH500 is a person related to ThingsDAO220, and this person may include various types of participants and related parties. (i) First, there are the following participants related to B238 (brand). B238, AC234, DB236, DO230, SP232, Bnf402, Dev400, etc. (ii) Next, there are the following related parties related to Things. IS240, TO242, etc. (iii) Furthermore, in addition to the above two types of participants and related parties, any participants related to Things other than the above two types, such as producers, consumers, influencers, auditors, developers, etc., may be included. All of these (i), (ii), and (iii) are collectively referred to as SH500. The transaction contract regarding Things in this embodiment is first carried out between TO (Things Owner) 242 and SH (Stakeholder) 500. Furthermore, in this embodiment, not only between TO (Things Owner) 242 and SH (Stakeholder) 500, but also between SH500 and SH500, that is, between stakeholders, a transaction contract can be carried out. That is, the transaction (transaction contract) regarding Things in this embodiment includes not only simple buying and selling, but also all transactions regarding various Things such as the delivery, import and export, inspection, publicity, advertising, display, promotion, etc. of that Thing.
[0047] 4. Implementation Example of the Transaction System (Token Economics) According to this Embodiment FIG. 11 shows an implementation example of the transaction system according to this embodiment. First, there can be multiple types of various DAOs in ThingsDAO220. There may be a DAO for furniture, a DAO for clothing, and various other DAOs. In each type of DAO, as described in FIG. 10, SH500 exists as an account (see FIG. 11).
[0048] In ThingsDAO220, there may be a developer community 244. There may also be a governance organization 246 that manages tokens for transactions. In ThingsDAO220, a predetermined B (Brand) 238 is provided. This B238 corresponds to various business entities, such as a liquor council. IS240 contracts with ThingsDAO220 and B238 to conduct transactions. As described above, IS240 issues the physical token (TT) 100 which is an SFT. This enables the smooth conduct of physical transactions. The governance organization 246 may perform various management tasks, such as issuing TCX300.
[0049] B238 can receive the above-mentioned TT100 and TCX330, and use them to contract with AC234, DB235, DO230, SP232, and TO242 to execute transactions. As described in FIG. 5, DO230 is provided with one or more Dev400. Also, as described in FIG. 5, SP232 is provided with one or more Bnf402.
[0050] What is characteristic in this embodiment is that a physical token (TT) 100 using an SFT is used to conduct physical transactions. As a result, it is possible to smoothly handle a large number of the same type of items, and actual retail stores and the like can easily use a transaction system using blockchain, so the possibility of transactions can be dramatically improved.
[0051] As described above, the embodiments of the present invention have been described, but the present invention is not limited to the foregoing embodiments. Also, the effects described in this embodiment are merely an enumeration of the most suitable effects resulting from the present invention, and the effects of the present invention are not limited to those described in this embodiment.
Explanation of Reference Numerals
[0052] 10... (physical) token 12, 120... security information 14……User 100……Thing Token (TT) 130……FT 132……NFT 134……Smart Contract 140……Value (Amount) 142……Owner (Account) 144……Content (Text·Non - text) 146……Condition 200……PTPF 200a……Protocol of PTPF 202……Blockchain 204……DEXPF 206……Base Blockchain 208……DT 210……MDT 220……ThingsDAO 230……DO 232……SP 234……AC 236……DB 238……B 240……IS 242……TO 244……Developer Community 246……Governance Organization 300……TCX 400……Dev (Device) 402……Bnf (Beneficiary) 500……SH W……Configuration required in IoT data transmission Z……New configuration for using Thing Token 100 X……Brand Interface Y……Things Interface
Claims
1. A transaction system for preserving and managing a transaction contract of an item using a blockchain, comprising a data transaction unit for executing the transaction contract of the item, an item owner account that owns the item, an issuer account that issues an item token for the item owned by the item owner account, and one or more stakeholder accounts for trading the item. The data transaction unit executes the transaction contract using the item token among the stakeholder accounts for trading the item. The item token is a Semi-fungible Token, and further, the item token is a token having an item account, a Device Token, a Device Asset Token, and securities information. The item owner account manages the item tokens issued for each item owned by the item owner account. Transaction system.
2. The item token can be divided by the number of items owned by the item owner account. The transaction system according to Claim 1.
3. When the item owner account groups the items it owns into containers, the item tokens can be integrated and represented by one item token for each container. The transaction system according to Claim 1.
4. The item token is a token having security fungibility and non-fungibility as an item. The transaction system according to Claim 1.
5. The data transaction unit includes a brand account for conducting transactions on items of a predetermined type. The brand account and the issuer account enter into a contract. Based on the contract, the issuer account supplies the item tokens issued by the issuer account for the item to the brand account. The brand account summarizes the contracts of the items owned by the item owner using the item tokens. The transaction system according to any one of Claims 1 to 4.
6. A brand DAO, which is a rule interface that defines rules between one or more of the brand accounts and other accounts. The transaction system further includes: The brand enters into a contract with the issuer account according to the rules defined by the brand DAO. The transaction system according to Claim 5.
Citation Information
Patent Citations
Data transaction system
JP2021189903A
Method for processing secure financial transactions using commercial off-the-shelf or internet of things devices
JP2021519471A
Point trading system
JP2022109163A
System, method, and storage medium for configuring a data storage and retrieval system for managing data related to tokenized assets
JP2022536445A
The method and appartus for storing transaction history and proof of onwership utilizing distributed computing
KR1020230040731A