Non-homogenized token (NFT) purchase and transfer system

By providing multiple digital wallets and APIs supporting multi-token standards on the decentralized blockchain, the purchase and transfer process of NFT is simplified, the problem of high user participation threshold is solved, and the market liquidity and user experience are improved .

CN118901076APending Publication Date: 2024-11-05PAYPAL INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028967.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-21
Filing Date
2023-03-10
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

On decentralized blockchain, the purchase and transfer process of non-fungible tokens (NFTs) is complex, especially for first-time or inexperienced users, which requires understanding of the NFT market and private key management, resulting in a threshold for participation Higher, hindering user participation.

Method used

By providing multiple digital wallets, users can access the non-fungible token market, support different token standards, such as ERC-20, ERC-721, ERC-1155, etc., use API to realize the composability of tokens, and use the tokens to be combinable through Service providers provide users with simplified purchasing and sales processes, including group buying and off-chain trading mechanisms, reducing user operation complexity.

Benefits of technology

It simplifies the purchase and transfer process of NFT, lowers the technical threshold for users, improves the participation and liquidity of the decentralized market, and enhances the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901076A_ABST
    Figure CN118901076A_ABST
Patent Text Reader

Abstract

The present disclosure provides methods and systems for implementing off-chain transactions through a non-homogenous token (NFT) marketplace. Access to the NFT marketplace is provided to a plurality of digital wallets associated with a service provider. The NFT marketplace corresponds to a decentralized blockchain associated with an entity different from a service provider. A request is received from a first user of the service provider associated with the first identifier and the first digital wallet to perform a transaction involving purchasing an NFT associated with the specified source address via the NFT marketplace. In response to determining that the specified source address corresponds to a second user of a service provider associated with the second identifier and the second digital wallet, the identifier associated with the NFT is updated from the second identifier associated with the second user to the first identifier associated with the first user.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to blockchain technology and, more particularly, to systems and methods for purchasing and transferring non-fungible tokens between users of a decentralized blockchain. Background Art

[0002] Blockchain has become a popular computer data structure for storing transaction data due to its inherent peer-to-peer and immutable properties. For example, blockchain has been used as a decentralized ledger to record transaction data associated with various cryptocurrencies, smart contracts, and other types of transaction data. Copies and / or portions of a blockchain can be stored on different computer nodes, where each computer node can be configured to verify transactions and add new transaction data to the blockchain. When a new transaction is made, one or more computer nodes can be configured to verify the new transaction (e.g., through a proof-of-work or proof-of-stake mechanism, etc.). Once a new transaction is confirmed, the transaction data for the new transaction can be packaged into a block and attached to a copy of the blockchain by one or more computer nodes.

[0003] Some blockchains (e.g., the Ethereum blockchain) feature smart contract functionality and include decentralized replicated virtual machines that can execute smart contracts. A smart contract is a program stored on a blockchain that is executed when predetermined conditions are met. Smart contracts can be used to implement different types of tokens on the blockchain for various purposes. Each token type can implement its own token standard. For example, token standards on the Ethereum blockchain (introduced as the Ethereum Request for Comments (ERC)) include, but are not limited to: the ERC-20 standard for homogeneous tokens, the ERC-721 standard for non-homogeneous tokens, and the ERC-1155 standard for homogeneous tokens and non-homogeneous tokens. Homogenous tokens (e.g., virtual currencies) are interchangeable and essentially indistinguishable from each other. In contrast, a non-homogeneous token (NFT) represents a unique, non-interchangeable asset that is completely digital or a tokenized version of a real-world asset. NFTs can be traded through an NFT market that connects buyers and sellers.

[0004] However, in such a marketplace, the buying and selling of NFTs generally requires prior knowledge and familiarity with how NFTs and the NFT transfer process work. For example, buyers of NFTs need to know how to connect their digital wallets to the NFT marketplace and configure the wallets to control the private keys required to access the NFTs. As a result, first-time or inexperienced users may be discouraged from participating in transactions involving the purchase or sale of NFTs. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The accompanying drawings, which are included to provide a further understanding and are incorporated in and constitute a part of this specification, illustrate the disclosed embodiments and, together with the description, serve to explain the principles of the disclosed embodiments. In the drawings:

[0006] Figure 1 is a block diagram illustrating an example of a distributed computing system for facilitating one or more blockchain-based transactions.

[0007] Figure 2 is a block diagram illustrating an example of a blockchain network.

[0008] Figure 3 is a block diagram illustrating an example of a blockchain.

[0009] Figure 4 is a diagram of a sample transaction message.

[0010] Figure 5 is a diagram of a sample transaction broadcast to the blockchain network.

[0011] Fig. 6A is a flow chart of an example process for performing a blockchain-based transaction.

[0012] Figure 6B is a flow diagram of another example process for performing a blockchain-based transaction.

[0013] Figure 7 is a flowchart of a process for facilitating transactions involving users of a service provider purchasing non-fungible tokens (NFTs) via an NFT marketplace according to an embodiment of the present disclosure.

[0014] Figure 8 According to an embodiment of the present disclosure, Figure 7 A flowchart of the process of group purchasing of NFTs involved in the transaction.

[0015] Fig. 9 According to an embodiment of the present disclosure, a method for facilitating a user of a service provider to Figure 7 A flowchart of the process of selling a second transaction of an NFT marketplace.

[0016] Fig.10 An example of the workflow of an NFT marketplace transaction involving the purchase and transfer of NFTs between buyers and sellers who are different users of the service provider is shown.

[0017] Fig.11 Shows holding and display by Fig.10 An example of a workflow for a user of a service provider to purchase an NFT.

[0018] Fig.12Another example of the workflow of an NFT marketplace transaction is shown, which involves Fig.10 The purchase and transfer of NFTs between buyers who are users of the service provider and sellers who are users of third-party decentralized wallets.

[0019] Fig.13 Another example of the workflow of an NFT market transaction is shown, which involves Fig.10 The sale and transfer of NFTs between sellers who are users of the service provider and buyers who are users of third-party decentralized wallets.

[0020] Fig.14 is a block diagram illustrating an example of a client-server system in which embodiments of the present disclosure may be implemented.

[0021] Fig.15 is a block diagram illustrating an example of a computing device in which embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION

[0022] In the following description of various embodiments, reference is made to the accompanying drawings identified above, which form a part hereof, and in which are shown by way of illustration various embodiments in which the aspects described herein may be practiced. It should be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope described herein. Various aspects are capable of other embodiments and may be practiced or performed in a variety of different ways.

[0023] Figure 1-Figure 5 , Fig. 6A , Figure 6B , Fig.14 and Fig.15 Certain aspects of blockchain operations according to some embodiments of the present disclosure are described. Figure 7-Figure 13Certain other aspects related to the purchase and transfer of non-fungible tokens (NFTs) by users of a service provider according to some embodiments are described. As will be described in further detail below, a service provider may provide multiple digital wallets for users of the service provider to access a non-fungible token (NFT) market corresponding to a decentralized blockchain associated with an entity other than the service provider. It should be understood that NFTs according to various embodiments of the present disclosure may be implemented according to any of a variety of token standards. For example, NFTs may be implemented according to the ERC-20 standard, the ERC-721 standard, the ERC-994 standard, the ERC-998 standard, the ERC-1155 standard, and / or any other token standard configured for an Ethereum blockchain network or any other blockchain network including a virtual machine for executing contract bytecodes on its blockchain, which is apparent to those skilled in the art of the present disclosure. Each token standard may have different feature requirements: a token must be considered a token that implements the standard and may be used by a smart contract or application that is also generated according to the token standard.

[0024] In some implementations, NFTs and smart contracts that implement various token standards can be tag-based and exported by application programming interfaces (APIs). Therefore, the composability of these token standards is achieved through APIs. Composability means that the token has the ability to combine parts or elements. For example, if a first smart contract generates a token that implements the ERC-20 standard, the first smart contract can be used by other smart contracts, or the first smart contract can be docked with an existing smart contract on the blockchain to use the API from within the first smart contract or interact with the existing smart contract.

[0025] In the broadest sense, blockchain refers to a framework that supports a trusted ledger that is stored, maintained, and updated in a decentralized manner in a peer-to-peer network. For example, in cryptocurrency applications such as Bitcoin or Ethereum, Ripple, Dash, Litecoin, Dogecoin, zCash, Tether, Bitcoin Cash, Cardano, Stellar, EOS, NEO, NEM, Bitshares, Decred, Augur, Komodo, PIVX, Waves, Steem, Monero, Golem, Stratis, Bytecoin, Ardor, or in digital currency exchanges such as Coinbase, Kraken, CEX.IO, Shapeshift, Poloniex, Bitstamp, Coinmama, Bisq, LocalBitcoins, Gemini, etc., where a decentralized ledger represents each transaction and units of cryptocurrency are transferred between entities. For example, using a digital currency exchange, users can purchase any value of digital currency or exchange any digital currency held for global currency or other digital currencies. Each transaction can be verified through the distributed ledger, and only verified transactions are added to the ledger. (Note that other digital asset transfers can also be achieved through other blockchain schemes; various cryptocurrency examples are used in this article for ease of illustration and understanding.) This ledger, and many aspects of the blockchain, can be called "decentralized" because there is generally no central authority. Because of this, the accuracy and integrity of the ledger cannot be attacked in a single central location. In order to protect the integrity of the ledger, it is difficult to modify all or most of the location where the ledger is stored. This is largely because the individuals associated with the nodes that make up the peer-to-peer network have a vested interest in the accuracy of the ledger. Of course, as discussed further below, many uses of blockchain distributed ledgers are possible besides cryptocurrencies.

[0026] Although maintaining cryptocurrency transactions in a distributed ledger may be the most recognizable use of blockchain technology today, the ledger can be used in a variety of different areas. In fact, blockchain technology is suitable for any application that can access any type of data, as long as the accuracy of the data is guaranteed. For example, a supply chain can be maintained in a blockchain ledger, where the transfer of each component from one party to another and from one location to another can be recorded in the ledger for later retrieval. Doing so allows for easier identification of the source of a defective part and where other such defective parts have been delivered. Similarly, food can be tracked from farm to grocery store to purchaser in a similar manner. Other data and other digital assets can be maintained, recorded and / or transferred according to various blockchain schemes.

[0027] Implementations of the present disclosure will now be described in detail with reference to the accompanying drawings.

[0028] It should be understood that the words and terms used herein are for descriptive purposes and should not be considered limiting. Rather, the words and terms used herein are to be given their broadest interpretations and meanings. The use of "including" and "comprising" and variations thereof is meant to encompass the items listed thereafter and their equivalents as well as additional items and their equivalents.

[0029] Computing architecture

[0030] As described above, the decentralized ledger in the blockchain framework is stored, maintained, and updated in a peer-to-peer network. In one example, the decentralized ledger maintains multiple blockchain transactions. Figure 1 An example of a distributed computing system 100 for facilitating blockchain-based transactions is shown. As will be described in further detail below, such transactions may include transactions involving the purchase and transfer of non-fungible tokens (NFTs) via an NFT marketplace. Figure 1 As shown in the example of FIG. 1 , system 100 includes a client device 110 of user 115, a client device 120 of user 125, a client device 130 of user 135, a server 150, a server 160, and an Internet of Things (IoT) device 170 interconnected via a network 140. Each of client devices 110, 120, and 130 may be any of a variety of computing devices including at least one processor and a memory. Examples of such computing devices include, but are not limited to, a mobile phone, a tablet computer, a laptop computer, a desktop computer, or a workstation. Each of servers 150 and 160 may be any of a variety of types of computer servers, such as a cluster of computers in a server farm, capable of providing data to other computing devices including client devices 110, 120, and 130 via network 140. Network 140 may be any of a variety of available networks, such as the Internet, and represents a global collection of networks and gateways that support communication between devices connected to network 140. IoT device 170 may be any of a variety of devices having connection hardware to connect and exchange data with other IoT devices. Examples of such IoT devices include, but are not limited to: vehicles, home appliances, embedded electronics, software, sensors, actuators, thermostats, light bulbs, door locks, refrigerators, RFID implants, RFID tags, pacemakers, wearable devices, smart home devices, cameras, trackers, pumps, POS devices, and fixed and mobile communications equipment.

[0031] In one or more embodiments, the system 100 may also include one or more decentralized or peer-to-peer (P2P) networks, such as blockchain networks 145a-c (collectively referred to as blockchain networks 145). Figure 1 As shown, blockchain networks 145a and 145b may be public blockchain networks included within network 140. For example, blockchain network 145c may be a separate private blockchain network connected to server 150. The private blockchain network and server 150 in this example may be associated with a service provider. As will be described in further detail below, the service provider may use server 150 to facilitate various blockchain-based transactions for users of the service provider (e.g., users 115 and 125 of client devices 110 and 120, respectively). In contrast, user 135 of client device 130 may be, for example, a third-party user associated with a decentralized digital wallet.

[0032] In one example, a blockchain-based transaction may involve different entities or users (e.g. Figure 1 The server 150 may include one or more applications, such as a transaction application configured to facilitate transactions between entities by utilizing a blockchain associated with one of the blockchain networks 145. As an example, the first user 115 may request or initiate a transaction with the second user 125 via a user application executed on the first client device 110. The transaction may be related to the transfer of value or data from the first user 115 to the second user 125. The first client device 110 may send a request for a transaction to the server 150. The server 150 may send the requested transaction to one of the blockchain networks 145 for verification and approval, which will be discussed further below. Each blockchain network 145 in this example may include multiple interconnected devices (or nodes), which will be referred to as Figure 2 As mentioned above, a ledger or blockchain is a decentralized database used to maintain a growing list of records containing any type of information. Figure 3 In more detail, the blockchain may be stored on at least one or more nodes (or devices) of the blockchain network 145.

[0033] In another example, a blockchain-based transaction may involve the purchase or sale of an NFT via an NFT market 165. The NFT market 165 may be associated with, for example, a third-party broker or other entity other than the service provider described above. The NFT market 165 may be a decentralized application or blockchain-integrated e-commerce website hosted on the server 160 that provides an online market for buyers and sellers to purchase and sell NFTs via a corresponding decentralized blockchain. In one or more embodiments, users 115, 125, and 135 may access the NFT market 165 through the network 140 via a web browser executable at their respective client devices 110, 120, and 130. Client devices 110, 120, and 130 may also execute a digital wallet application (or simply "digital wallet") associated with each user. In some implementations, the digital wallet application may be a browser extension associated with a web browser executable at each client device. Alternatively, the digital wallet application may be implemented as a standalone application executable at each client device. In one or more embodiments, a digital wallet application at each client device can be used to establish a connection between the client device and the NFT marketplace 165 via the network 140, for example, to exchange secure communications related to blockchain-based transactions involving the purchase or sale of NFTs via the NFT marketplace 165.

[0034] In some embodiments, access to the NFT marketplace 165 may be provided to a digital wallet associated with a service provider via, for example, an application programming interface (API) connection of the service provider. Such digital wallets may correspond to different users of the service provider. In some implementations, information associated with the users of the service provider and their corresponding digital wallets may be stored in a database 155 coupled to the server 150. The database 155 may be any type of data storage device for storing various data. The information stored in the database 155 may be accessed by the server 150 to facilitate transactions initiated by users of the service provider involving the purchase or sale of NFTs, which will be referred to below. Figure 7-Figure 13 Described in further detail.

[0035] Blockchain Network

[0036] Figure 2 An example blockchain network 200 is shown that includes a plurality of interconnected nodes or devices 205a-h (generally referred to as nodes 205). Each node 205 may include a computing device, such as Fig.15 The computing device 1500 is described below. Figure 2A single device is shown, but each node 205 may include multiple devices (e.g., a pool). The blockchain network 200 may be associated with a blockchain 220. Some or all of the nodes 205 may replicate and store an identical copy of the blockchain 220. For example, Figure 3 Nodes 205b-e and 205g-h are shown storing copies of blockchain 220. As described below, nodes 205b-e and 205g-h can independently update their respective copies of blockchain 220.

[0037] Blockchain node types

[0038] A blockchain node (e.g., node 205) can be a full node or a lightweight node. Full nodes such as nodes 205b-e and 205g-h can act as servers in the blockchain network 200 by storing a copy of the entire blockchain 220 and ensuring that transactions published to the blockchain 220 are valid. Full nodes 205b-e and 205g-h can publish new blocks on the blockchain 220. Lightweight nodes such as node 205a and node 205f can have fewer computing resources than full nodes. For example, IoT devices often act as lightweight nodes. Lightweight nodes can communicate with other nodes 205, provide information to full nodes 205b-e and 205g-h, and query the status of blocks of the blockchain 220 stored by full nodes 205b-e and 205g-h. However, in this example, as Figure 2 As shown, lightweight nodes 205a and 205f may not store a copy of blockchain 220 and therefore may not publish new blocks on blockchain 220.

[0039] Blockchain network types

[0040] The blockchain network 200 and its associated blockchain 220 may be public (unauthorized), federated or consortium, or private. If the blockchain network 200 is public, any entity may read and write the associated blockchain 220. However, if controlled by a single entity or organization, the blockchain network 200 and its associated blockchain 220 may be federated or consortium. In addition, any node 205 that can access the Internet may be restricted from participating in transaction verification on the blockchain 220. If access to the blockchain network 200 and blockchain 220 is limited to specific authorized entities, such as organizations or groups of individuals, the blockchain network 200 and its associated blockchain 220 may be private (permissioned). In addition, read permissions to the blockchain 220 may be public or restricted, while write permissions may be limited to the controlling or authorized entity.

[0041] Blockchain

[0042] As described above, blockchain 220 may be associated with blockchain network 200. Figure 3 An example blockchain 300 is shown. The blockchain 300 may include a plurality of blocks 305a, 305b, and 305c (collectively referred to as blocks 305). The blockchain 300 includes a first block (not shown), sometimes referred to as a genesis block. Each block 305 may include a record of one or more submitted and verified transactions. The blocks 305 of the blockchain 300 may be linked together and cryptographically protected. In some cases, post-quantum cryptographic algorithms that change dynamically over time may be utilized to reduce the ability of quantum computing to crack current cryptographic schemes. Examples of various types of data fields stored in blockchain blocks are provided below. Copies of the blockchain 300 may be stored locally, in the cloud, on a grid, as files, or in a database, for example, by nodes 205b-e and 205g-h.

[0043] Block

[0044] Each block 305 may include one or more data fields. The organization of blocks 305 within blockchain 300 and the corresponding data fields may be implementation specific. For example, blocks 305 may include respective headers 320a, 320b, and 320c (generally referred to as headers 320) and block data 375a, 375b, and 375c (generally referred to as block data 375). Headers 320 may include metadata associated with their respective blocks 305. For example, headers 320 may include respective block numbers 325a, 325b, and 325c. Figure 3 As shown, block number 325a of block 305a is N-1, block number 325b of block 305b is N, and block number 325c of block 305c is N+1. The header 320 of block 305 may include a data field (not shown) including a block size.

[0045] Blocks 305 may be linked together and cryptographically protected. For example, the header 320b of block N (block 305b) includes a data field (previous block hash 330b) that includes a hash representation of the header 320a of the previous block N-1. The hash algorithm used to generate the hash representation may be, for example, a secure hash algorithm 256 (SHA-256), which produces an output of a fixed length. In this example, the hash algorithm is a one-way hash function, wherein it is computationally difficult to determine the input of the hash function based on the output of the hash function. Additionally, the header 320c of block N+1 (block 305c) includes a data field (previous block hash 330c) that includes a hash representation of the header 320b of block N (block 305b).

[0046] The header 320 of the block 305 may also include a data field containing a hash representation of the block data, such as block data hashes 370a-c. The block data hashes 370a-c may be generated, for example, by a Merkle tree and by storing hashes or by using a hash based on all block data. The header 320 of the block 305 may include respective random numbers 360a, 360b, and 360c. In some implementations, the values ​​of the random numbers 360a-c are arbitrary strings concatenated (or appended) to the hash of the block. The header 320 may include other data, such as a difficulty target.

[0047] Block 305 may include respective block data 375a, 375b, and 375c (generally referred to as block data 375). Block data 375 may include a record of verified transactions that have been integrated into blockchain network 200 via a consensus model (described below). As described above, in addition to verified transactions, block data 375 may also include a variety of different types of data. Block data 375 may include any data, such as text, audio, video, images, or files, that may be represented digitally and stored electronically.

[0048] Blockchain transactions

[0049] In one example, blockchain-based transactions may generally involve the transfer of data or value or interactions between entities, which will be described in more detail below. Figure 1 , each of the servers 150 and 160 may include one or more applications, for example, a transaction application configured to facilitate blockchain transactions between entities. Entities may include users, devices, etc. A first user 115 may request or initiate a transaction with a second user 125 via a user application executed on the first client device 110. The transaction may be associated with a transfer of value or data from the first user 115 to the second user 125. The value or data may represent money, contracts, property, records, rights, states, supplies, demands, alerts, triggers, or any other asset that can be represented in digital form. The transaction may represent an interaction between the first user 115 and the second user 125.

[0050] Figure 44 is a schematic diagram of a transaction 465 generated by a transaction application. The transaction 465 may include a public key 415, a blockchain address 430 associated with the first user 115, a digital signature 455, and transaction output information 460. The transaction application may derive the public key 415 from the private key 405 of the first user 115 by applying a cryptographic hash function 410 to the private key 405. The cryptographic hash function 410 may be based on AES, SHA-2, SHA-3, RSA, ECDSA, ECDH (elliptic curve encryption), or DSA (finite field encryption), although other cryptographic models may also be utilized. More information about cryptographic algorithms may be found in the Federal Information Processing Standards Publication (FIPSPUB 180-3), Secure Hash Standard. The transaction application may derive an address or identifier, such as a blockchain address 430, for the first user 115 by applying a hash function 420 to the public key 415. In short, a hash function is a function that can be used to map data of any size to data of a fixed size. The value may also be referred to as a digest, a hash value, a hash code, or a hash. To indicate that the first user 115 is the initiator of the transaction 465, the transaction application may generate a digital signature 455 of the transaction data 435 using the private key 405 of the first user 115. The transaction data 435 may include information about the asset to be transferred and a reference to the source of the asset, such as an identification of a previous transaction or event that generated the asset in which the asset was transferred to the first user 115. Generating the digital signature 455 may include applying a hash function 440 to the transaction data 435, generating hashed transaction data 445. The hashed transaction data 445 and the transaction data 435 may be encrypted (via an encryption function 450) using the private key 405 of the first user 115, thereby generating the digital signature 455. The transaction output information 460 may include the asset information 470 and an address or identifier of the second user, such as a blockchain address 475. The transaction 465 may be sent from the first client device 110 to the server 150.

[0051] The specific type of cryptographic algorithm used can change dynamically based on various factors, such as length of time, privacy concerns, etc. For example, the type of cryptographic algorithm being used can change yearly, weekly, daily, etc. The type of algorithm can also change based on different privacy levels. For example, the owner of the content can achieve a higher level of protection or privacy by utilizing a stronger algorithm.

[0052] Blockchain address

[0053] The blockchain network can use blockchain addresses to indicate entities using the blockchain or the start and end points of a transaction. For example, the blockchain address of the first user 115 (in Figure 4The blockchain address 430 shown as the sender in the first user 115 may include an alphanumeric string derived from the public key 415 of the first user 115 based on applying a cryptographic hash function 420 to the public key 415. The method used to derive the address may vary and may be specific to the implementation of the blockchain network. In some examples, the blockchain address may be converted into a QR code representation, barcode, token, or other visual representation or graphical description to enable a mobile device, wearable device, sensor, camera, etc. to optically scan the address. In addition to addresses or QR codes, there are many ways to identify individuals, objects, etc. represented in the blockchain. For example, individuals can be identified through biometric information such as fingerprints, retinal scans, voice, facial ID, body temperature, heart rate, gestures / movements unique to an individual, and other types of identification information such as account numbers, home addresses, social security numbers, formal names, etc.

[0054] Broadcasting transactions

[0055] Server 150 may receive transactions from users of blockchain network 145. Transactions may be submitted to server 150 via a desktop application, smartphone application, digital wallet application, web service, or other software application. Server 150 may send or broadcast transactions to blockchain network 145. Figure 5 An example transaction 502 is shown being broadcasted by the server 150 to the blockchain network 145. The transaction 502 may be broadcasted to a plurality of nodes 205 of the blockchain network 145. In general, once the transaction 502 is broadcasted or submitted to the blockchain network 145, it may be received by one or more nodes 205. Once the transaction 502 is received by one or more nodes 205 of the blockchain network 145, it may be propagated by the receiving node 205 to other nodes 205 of the blockchain network 145.

[0056] A blockchain network can operate according to a set of rules. These rules can specify the conditions under which a node can accept a transaction, the types of transactions that a node can accept, the types of compensation that a node receives for accepting and processing a transaction, etc. For example, a node can accept a transaction based on transaction history, reputation, computing resources, relationship with a service provider, etc. The rules can specify the conditions under which a transaction is broadcast to a node. For example, a transaction can be broadcast to one or more specific nodes based on criteria related to the node's geography, history, reputation, market conditions, ticker / latency, technology platform. These rules can be dynamically modified or updated (e.g., turned on or off) to address issues such as latency, scalability, and security conditions. Transactions can be broadcast to a subset of nodes as a form of compensation to entities associated with those nodes (e.g., by receiving compensation for adding a block of one or more transactions to the blockchain).

[0057] Transaction verification - user authentication and transaction data integrity

[0058] Due to issues such as latency, not all full nodes 205 can receive the broadcasted transaction 502 at the same time. In addition, not all full nodes 205 receiving the broadcasted transaction 502 can choose to verify the transaction 502. Nodes 205 can choose to verify a specific transaction, for example, based on the transaction fee associated with the transaction 502. The transaction 502 may include the sender's blockchain address 505, public key 510, digital signature 515, and transaction output information 520. The node 205 can verify whether the transaction 502 is legal or complies with a predefined set of rules. The node 205 can also verify the transaction 502 based on establishing user authenticity and transaction data integrity. User authenticity can be established by determining whether the sender indicated by the transaction 502 is actually the actual initiator of the transaction 502. The authenticity of the user can be proved by cryptography, for example, asymmetric key cryptography using a pair of keys (e.g., a public key and a private key). When establishing user authenticity, additional factors such as user reputation, market conditions, history, transaction speed, etc. can be considered. The data integrity of transaction 502 may be established by determining whether the data associated with transaction 502 has been modified in any way. Figure 4 When the transaction application creates transaction 465 , it may indicate that first user 115 is the initiator of transaction 465 by including digital signature 455 .

[0059] Node 205 may decrypt digital signature 515 using public key 510. The result of the decryption may include hashed transaction data 540 and transaction data 530. Node 205 may generate hashed transaction data 550 based on applying hash function 545 to transaction data 530. Node 205 may perform a comparison 565 between first hashed transaction data 540 and second hashed transaction data 550. If result 570 of comparison 565 indicates a match, data integrity of transaction 502 may be established, and node 205 may indicate that transaction 502 has been successfully verified. Otherwise, the data of transaction 502 may have been modified in some way, and node 205 may indicate that transaction 502 has not been successfully verified.

[0060] Each full node 205 can build its own block and add the verified transaction to the block. Therefore, the blocks of different full nodes 205 can include different verified transactions. As an example, a full node 205f can create a first block including transactions "A", "B" and "C". Another full node 205b can create a second block including transactions "C", "D" and "E". However, only one block can be added to the blockchain, otherwise the transactions that these blocks may have in common (such as transaction "C") may be recorded twice, resulting in problems such as double spending when the transaction is executed twice. One problem that may occur in the above example is that transactions "C", "D" and "E" may be excessively delayed when added to the blockchain. This can be solved in a variety of different ways discussed below.

[0061] Protect the key

[0062] Private keys, public keys, and addresses can be managed and protected using software such as digital wallets. Private keys can also be stored and protected using hardware. Digital wallets can also enable users to conduct transactions and manage balances. Digital wallets can be stored or maintained online or offline, using software or hardware, or both. Without public / private keys, users cannot prove ownership of assets. In addition, anyone who has access to a user's public / private keys can access the user's assets. Although assets may be recorded on the blockchain, without the private key, users may not be able to access them.

[0063] Establishing User Identity

[0064] While a digital signature can provide a link between a transaction and the owner of the transferred asset, it may not provide a link to the owner's true identity. In some cases, it may be necessary to determine the true identity of the owner of the public key corresponding to the digital signature. The true identity of the public key owner can be verified, for example, based on biometric data, passwords, personal information, etc. Biometric data can include any physical identification information, such as fingerprints, facial and eye images, voice samples, DNA, human body movements, gestures, gait, expressions, heart rate characteristics, temperature, etc.

[0065] Publishing and validating blocks

[0066] As described above, the full nodes 205 can each build their own blocks including different transactions. Nodes can build blocks by adding verified transactions to the blocks until the blocks reach a specific size specified by the blockchain rules. However, only one of the blocks can be added to the blockchain. The blocks to be added to the blockchain and the order of the blocks can be determined based on the consensus model. In the proof of work model, two nodes can compete to add their respective blocks to the blockchain by solving complex mathematical puzzles. For example, as described above, such a puzzle can include determining a random number so that the hash (using a predetermined hash algorithm) of the block to be added to the blockchain (including the random number) has a value that satisfies the range limit. If two nodes solve the puzzle at the same time, then a "fork" can be created. When the full node 205 solves the puzzle, it can publish its block to be confirmed by the confirmation node 205 of the blockchain network 145.

[0067] In a proof-of-work consensus model, for example, a node verifies a transaction by checking or searching the current ledger stored in the blockchain. The node will create a new block for the blockchain, which will include data on one or more verified transactions (see, for example, Figure 3 375). In blockchain implementations such as Bitcoin, the size of blocks is constrained. Return to reference Figure 3, in this example, the block will include a previous block hash 330, which represents the hash of the current last block in the blockchain. The block may also include a hash 370 of its own transaction data (e.g., a so-called Merkle hash). According to a specific algorithm, all or selected data from the block may be hashed to create a final hash value. According to an embodiment of the proof-of-work model, the node will seek to modify the data of the block so that the final hash value is less than a preset value. This is achieved by adding a data value called a random number 360. Because the final hash value cannot be predicted based on its input, it is impossible to estimate the appropriate value of the random number 360, which will result in a final hash value less than the preset value. Therefore, in this embodiment, a computationally intensive operation is required at the node to determine the appropriate random number value through a "brute force" trial and error method. Once a successful random number value is determined, the completed block is published to the blockchain network for verification. If verified by a majority of nodes in the blockchain network, the completed block is added to the blockchain of each participating node. When a node's block is not added to the blockchain, the block is discarded and the node continues to build a new block. Transactions in a discarded block may be returned to the queue, waiting to be added to the next block. When a transaction is discarded or returned to the queue, the asset associated with the discarded transaction is not lost, as a record of the asset will exist in the blockchain. However, when a transaction is returned to the queue, the return can cause a delay in completing the transaction. Reducing the time to complete a transaction can be important. A set of blockchain rules or rewards / compensation for nodes processing returned transactions can determine how returned transactions are processed. When a transaction is placed into a pool, it can have priority, but then the rules may dictate that the transaction priority must exceed a threshold level. The priority of returned or discarded transactions can be increased. Another way to reduce the time to complete a transaction is for the system, service provider, transaction participant, or merchant to pay additional incentives to nodes to process returned transactions. For example, a service provider may identify a network of preferred miners based on geography or based on a volume discount perspective. By routing returned transactions to specific preferred nodes, the time to complete a transaction can be optimized. Transactions can be associated with addresses that restrict which preferred node will process the transaction if it is returned due to being included in a discarded block. Value can be associated with a transaction so that it goes to a preferred miner in a specific geographic location. Additionally, returned transactions can be processed based on preset rules. For example, a rule may dictate a commitment to process a specific number of returned transactions to receive additional incentives or compensation.

[0068] Blockchain confirmation

[0069] After a block including a transaction is added to the blockchain, a blockchain confirmation may be generated for the transaction. A blockchain confirmation may be a number of blocks added to the blockchain after the block including the transaction. For example, when a transaction is broadcast to the blockchain, there will be no blockchain confirmation associated with the transaction. If the transaction is not verified, the blocks that make up the transaction will not be added to the blockchain, and the transaction will continue to have no blockchain confirmation associated with it. However, if the block including the transaction is verified, each transaction in the block will have a blockchain confirmation associated with the transaction. Therefore, when a block is verified, the transactions in the block will have one blockchain confirmation associated with it. When a block is added to the blockchain, each transaction in the block will have two associated blockchain confirmations. As more verified blocks are added to the blockchain, the number of blockchain confirmations associated with the block will increase. Therefore, the number of blockchain confirmations associated with a transaction may indicate the difficulty of rewriting or reversing the transaction. Higher value transactions may require a large number of blockchain confirmations before they can be executed.

[0070] Consensus Model

[0071] As described above, the blockchain network can determine which full node 205 publishes the next block to the blockchain. In a permissionless blockchain network, the nodes 205 can compete to determine which one publishes the next block. Based on a consensus model, a node 205 can be selected to publish its block as the next block in the blockchain. For example, the selected or winning node 205 can receive a reward, such as a transaction fee, for publishing its block. Various consensus models can be used, such as a proof of work model, a proof of stake model, a delegated proof of stake model, a polling model, a proof of authority or proof of identity model, and a proof of elapsed time model.

[0072] In the proof-of-work model, a node can publish the next block by being the first to solve a computationally intensive mathematical problem (e.g., the mathematical puzzle mentioned above). The solution serves as a "proof" that the node has spent the appropriate amount of effort to publish the block. The solution can be verified by all nodes before the block is accepted. However, the proof-of-work model may be vulnerable to the 51% attack described below. Compared to the proof-of-work model, the proof-of-stake model is generally less computationally intensive. Unlike the proof-of-work model, which is open to any node with computing resources for solving mathematical problems, the proof-of-stake model is open to any node that has a stake in the system. The stake can be the amount of cryptocurrency that a blockchain network node (user) may have invested in the system. The likelihood of a node publishing the next block can be proportional to its stake. Since the model utilizes fewer resources, the blockchain can give up rewards as an incentive to publish the next block. Permissioned blockchain networks typically use a polling model. Using this model, nodes can take turns publishing new blocks. In the elapsed time proof model, each publishing node requests a waiting time from the secure hardware within its computer system. The publishing node can become idle during the waiting time, then create a block and publish it to the blockchain network. For example, a hybrid blockchain network can switch between fully or partially permissioned and permissionless where speed and / or scalability is needed (e.g., in an enterprise environment). The network can switch based on various factors, such as latency, security, market conditions, etc.

[0073] Fork

[0074] As mentioned above, consensus models can be used to determine the order of events on a blockchain, such as which node starts adding the next block and which node's transactions are validated first. When there is a conflict related to the ordering of events, the result may be a fork in the blockchain. A fork may result in two versions of the blockchain existing at the same time. Consensus methods usually resolve conflicts related to the ordering of events, thereby preventing forks from occurring. In some cases, a fork may be unavoidable. For example, with the proof-of-work consensus model, only one of the nodes competing to solve the puzzle can win by solving its puzzle first. The winning node's block is then validated by the network. If the winning node's block is successfully validated by the network, it will be the next block added to the blockchain. However, it is also possible that two nodes solve their respective puzzles at the same time. In such a case, the blocks of the two winning nodes can be broadcast to the network. Since different nodes can receive notifications of different winning nodes, nodes that receive notification that the first node is the winning node can add the first node's block to their copy of the blockchain. Nodes that receive notification that the second node is the winning node can add the second node's block to their copy of the blockchain. This results in two versions of the blockchain or a fork. This type of fork can be resolved by the longest chain rule of the proof-of-work consensus model. According to the longest chain rule, if two versions of a blockchain exist, the network with the chain with the larger number of blocks can be considered the valid blockchain. The other version of the blockchain may be considered invalid, discarded, or orphaned. Because blocks created by different nodes may include different transactions, a fork may result in a transaction being included in one version of the blockchain but not in the other. Transactions in blocks of the discarded blockchain may be returned to the queue and wait to be added to the next block.

[0075] In some cases, a fork may stem from changes related to the blockchain implementation, for example, changes to the blockchain protocol and / or software. Forks may be more disruptive for permissionless and globally distributed blockchain networks than for private blockchain networks because they affect more users. A change or update to a backwards-compatible blockchain implementation may result in a soft fork. When there is a soft fork, some nodes may execute the updated blockchain implementation while other nodes may not. However, nodes that have not updated to the new blockchain implementation can continue to transact with updated nodes.

[0076] Changes to a backwards-incompatible blockchain implementation may result in a hard fork. While hard forks are usually intentional, they may also be caused by unintentional software bugs / errors. In such a case, all publishing nodes in the network may need to update to the new blockchain implementation. While publishing nodes that have not updated to the new blockchain implementation may continue to publish blocks based on the previous blockchain implementation, these publishing nodes may reject blocks created based on the new blockchain implementation and continue to accept blocks created based on the previous blockchain implementation. As a result, nodes on different hard forked versions of the blockchain may not be able to interact with each other. If all nodes move to the new blockchain implementation, the previous version may be discarded or abandoned. However, it may not be practical or feasible to update all nodes in the network to the new blockchain implementation, for example, if the update renders the specialized hardware used by some nodes inoperable.

[0077] Blockchain-based applications: Cryptocurrency

[0078] Cryptocurrency is a type of cryptocurrency that can be stored on a blockchain (e.g. Figure 1 A medium of exchange created and stored electronically in a blockchain 145a in a blockchain 145a). Bitcoin is an example of a cryptocurrency, however there are several other cryptocurrencies. Various cryptographic techniques can be used to create units of cryptocurrency and verify transactions. As an example, a first user 115 may own 10 units of cryptocurrency. The blockchain 145a may include a record indicating that the first user 115 owns 10 units of cryptocurrency. The first user 115 may initiate a transfer of 10 units of cryptocurrency to the second user 125 via a wallet application executed on the first client device 110. The wallet application may store and manage the private key of the first user 115. Examples of wallet devices include personal computers, laptop computers, smart phones, personal digital assistants (PDAs), etc.

[0079] Fig. 6A is shown for use in Figure 1 Flowchart of steps of an example process 600 for performing a blockchain transaction between entities such as a first user 115 of a first client device 110 and a second user 125 of a second client device 120 in FIG. The steps of process 600 may be performed by Figure 1 Alternatively or additionally, some or all of the steps of process 600 may be performed by one or more other computing devices. The steps of process 600 may be modified, omitted, and / or performed in another order, and / or additional steps may be added.

[0080] At step 605, the wallet application may generate transaction data for transferring 10 units of cryptocurrency from the first user 115 to the second user 125. The wallet application may generate a public key for the transaction using the private key of the first user 115. To indicate that the first user 115 is the initiator of the transaction, a digital signature may also be generated for the transaction using the private key of the first user 115. Figure 4 As discussed, transaction data may include information such as the sender's blockchain address 430, digital signature 455, transaction output information 460, and the sender's public key 415. The transaction data may be sent from the first client device 110 to the server 150.

[0081] The server 150 may receive transaction data from the first client device 110. At step 610, the server 150 may broadcast the transaction to the blockchain network 145a. The transaction may be received by one or more nodes 205 of the blockchain network 145a. At step 615, upon receiving the transaction, the node 205 may choose to verify the transaction, for example, based on a transaction fee associated with the transaction. If the transaction is not selected for verification by any node 205, the transaction may be placed in a queue and wait to be selected by a node 205.

[0082] At step 620, each node 205 that selected the transaction may verify the transaction. Verifying the transaction may include determining whether the transaction is legitimate or complies with a predefined set of rules for the transaction, establishing user authenticity, and establishing transaction data integrity. At step 625, if the node 205 successfully verifies the transaction, the verified transaction is added to the block constructed by the node 205. As described above, since different nodes 205 may choose to verify different transactions, different nodes 205 may construct or assemble blocks that include different verified transactions. Thus, a transaction associated with a transfer of 10 units of cryptocurrency from the first user 115 to the second user 125 may be included in some blocks but not in other blocks.

[0083] At step 635, the blockchain network 145a may wait for the block to be published. The verified transactions may be added to the block assembled by the node 205 until it reaches a minimum size specified by the blockchain. If the blockchain network 145a utilizes a proof-of-work consensus model, the nodes 205 may compete for the right to add their respective blocks to the blockchain by solving complex mathematical puzzles. The node 205 that solves its puzzle first wins the right to publish its block. As compensation, the winning node may receive a transaction fee associated with the transaction (e.g., from the wallet of the first user 115). Alternatively or additionally, the winning node may receive compensation as the amount of cryptocurrency added to the account associated with the winning node from the blockchain network (e.g., a "new" unit of cryptocurrency entering circulation). The latter method of compensation and issuing new cryptocurrency units into circulation is sometimes referred to as "mining". At step 640, if the block has not yet been published, the process 600 returns to step 635 and waits for the block to be published. However, at step 640, if the block has already been published, the process 600 proceeds to step 645.

[0084] At step 645, the published block is broadcast to the blockchain network 145a for verification. At step 650, if the block is verified by the majority of nodes 205, then at step 655, the verified block is added to the blockchain 220. However, at step 650, if the majority of nodes 205 do not verify the block, the process 600 proceeds to step 675. At step 675, the block is discarded, and the transactions in the discarded block are returned to the queue. The transactions in the queue can be selected by one or more nodes 205 for the next block. The node 205 that built the discarded block can build a new next block.

[0085] At step 660, if the transaction is added to the blockchain 220, the server 150 may wait to receive a minimum number of blockchain confirmations for the transaction. At step 665, if the minimum number of confirmations for the transaction have not yet been received, the process may return to step 660. However, if at step 665, the minimum number of confirmations have been received, the process proceeds to step 670. At step 670, the transaction may be executed, and the assets from the first user 115 may be transferred to the second user 125. For example, after the transaction receives at least three confirmations, 10 units of cryptocurrency owned by the first user 115 may be transferred from the financial account of the first user 115 to the financial account of the second user 125.

[0086] Smart Contracts

[0087] The smart contracts discussed in this article are agreements that are stored in the blockchain and automatically executed when the predetermined terms and conditions of the agreement are met. The terms and conditions of the agreement can be visible to other users of the blockchain. When the predefined rules are met, the relevant code is automatically executed. The agreement can be written as a script using programming languages ​​such as Java, C++, JavaScript, VBScript, PHP, Perl, Python, Ruby, ASP, Tcl, etc. The script can be uploaded to the blockchain as a transaction on the blockchain.

[0088] As an example, a first user 115 (also referred to as tenant 110) may rent an apartment from a second user 125 (also referred to as landlord 115). A smart contract may be utilized between tenant 110 and landlord 115 to pay rent. The smart contract may indicate that tenant 110 agrees to pay next month's rent of $1,000 by the 28th of the month. The agreement may also indicate that if tenant 110 pays the rent, landlord 115 provides tenant 110 with an electronic receipt and digital door key to the apartment. The agreement may also indicate that if tenant 110 pays the rent by the 28th of the month, the door key and rent are issued to tenant 110 and landlord 115, respectively, on the last day of the month.

[0089] Figure 6B is a flow chart illustrating steps of an example process 600B for executing a smart contract transaction between entities such as tenant 110 and landlord 115. The steps of process 600B may be performed by Figure 1 Alternatively or additionally, some or all of the steps of process 600B may be performed by one or more other computing devices. The steps of process 600B may be modified, omitted, and / or performed in another order, and / or other steps may be added.

[0090] At step 676, an agreement or smart contract between the tenant 110 and the landlord 115 may be created and then submitted as a transaction to the blockchain network 145a. The transaction may be added to a block mined by the node 205 of the blockchain network 145a, and the block including the transaction may be verified by the blockchain network 145a and then recorded in the blockchain 220 (e.g., Fig. 6A The protocol associated with the transaction may be assigned a unique address for identification.

[0091] At step 678, process 600B waits to receive information regarding conditions associated with the agreement. For example, process 600B may wait to receive a notification that $1000 was sent from a blockchain address associated with tenant 110 and received at a blockchain address associated with landlord 115 before the 28th of the current month. At step 680, if no such notification is received, process 600B returns to step 678. However, if a notification is received at step 680, process 600B proceeds to step 682.

[0092] At step 682, based on determining that the received notification satisfies the conditions required to trigger the execution of the various terms of the smart contract, process 600B proceeds to step 684. However, at step 682, if it is determined that the received notification does not satisfy the conditions required to trigger the execution of the smart contract, process 600B returns to step 678. At step 683, process 600B creates a transaction associated with the execution of the smart contract. For example, the transaction may include information about the payment received, the date the payment was received, the identification of the tenant 110, and the identification of the landlord 115. The transaction may be broadcast to blockchain network 145a and recorded in blockchain 220 (e.g., Fig. 6A 610-655 of process 600). If the transaction is successfully recorded in blockchain 220, the transaction can be executed. For example, if the payment is received on the 28th, an electronic receipt can be generated and sent to tenant 110. However, on the last day of the month, the digital door key and rent are issued to tenant 110 and landlord 115, respectively.

[0093] Smart contracts can be executed based on data received from entities that are not on the blockchain or off-chain resources. For example, a smart contract can be programmed to execute when a temperature reading from a smart sensor or IoT sensor is below 10 degrees. Smart contracts cannot extract data from off-chain resources. Instead, such data needs to be pushed to the smart contract. In addition, since smart contracts are replicated on multiple nodes of the network, even small changes in the data can be problematic. For example, the first node may receive a temperature reading of 9.8 degrees and the second node may receive a temperature reading of 10 degrees. Since the validation of transactions is based on consensus among nodes, even small changes in the received data may cause the conditions of the smart contract to be evaluated as not satisfied. Third-party services can be utilized to retrieve off-chain resource information and push it to the blockchain. These third-party services can be called oracles. Oracles can be software applications, such as big data applications, or hardware, such as IoT or smart devices. For example, an oracle service can pre-evaluate the received temperature reading to determine if the reading is below 10 degrees and then push this information to the smart contract. However, using an oracle can introduce another possible point of failure in the entire process. The oracle may be buggy, push incorrect information, or even shut down.

[0094] Because blockchains are immutable, it can be challenging to modify or update smart contracts that reside in a blockchain and therefore more expensive and / or more restrictive than text-based contracts.

[0095] Internet of Things (IoT)

[0096] An IoT network can include devices and sensors that collect data and forward it to each other through gateways. Gateways can translate between different protocols of devices and sensors and manage and process the data. For example, IoT devices can collect information from their environment such as movements, gestures, sounds, voices, biometric data, temperature, air quality, humidity, and light. The collected information is sent over the internet for further processing. Typically, IoT devices use low-power networks, Bluetooth, Wi-Fi, or satellites to connect to the internet or “cloud.” Some IoT-related issues that blockchain may be able to detect include a lack of compliance during the manufacturing phase of IoT devices. For example, blockchain can track whether IoT devices have been adequately tested.

[0097] As described above, information from off-chain resources, including IoT devices, can be pushed into a smart contract by a third-party entity known as an oracle. For example, a smart refrigerator can monitor the usage of items stored in the refrigerator, such as milk. Various sensors within the refrigerator can be used to periodically determine the amount of milk stored in the refrigerator. A smart contract stored in the blockchain can indicate that if the weight of the stored milk falls below 10 ounces, a new carton of milk is automatically purchased and delivered. The refrigerator sensors can periodically send readings to a third-party service or oracle. The oracle can evaluate the sensor readings to determine if a condition has been met to purchase a new carton of milk. Upon determining that the weight of the stored milk is below 10 ounces, the oracle can push information to the smart contract indicating that a condition has been met to execute the smart contract. The smart contract can be executed, and a new carton of milk can be automatically purchased. Both the execution of the smart contract and the purchase of the new carton of milk can be recorded in the blockchain. In some cases, the condition can be the occurrence of an event, such as demand or expected demand, or a convenience factor, such as a delivery day, cost, promotion, or incentive.

[0098] Some of the issues associated with integrating blockchain into IoT include transaction speed and computational complexity. When an IoT network with hundreds or thousands of connected devices is operating and transacting simultaneously, the speed at which transactions are executed on the blockchain can be important. IoT devices are often designed for connectivity rather than computation, and therefore may not have the processing power to support blockchain consensus algorithms such as proof of work. IoT devices are also vulnerable to attacks from internet hackers and / or physical tampering. For example, IoT devices may be more vulnerable to DDoS and malware attacks. Hackers may target a specific network and start spamming the network in a short period of time. Due to the surge in traffic, the bandwidth may quickly be overloaded and the entire system may crash.

[0099] Tokens

[0100] A token may refer to an entry in a blockchain that belongs to a blockchain address. The entry may include information indicating ownership of an asset. A token may represent money, a contract, a property, a record, access rights, a state, a supply, a demand, an alert, a trigger, a reputation, a ticket, or any other asset that can be represented in digital form. For example, a token may refer to an entry related to a cryptocurrency used for a specific purpose, or may represent ownership of a real-world asset, such as a fiat currency or real estate. A token contract refers to a cryptographic token that represents a set of rules encoded in a smart contract. A person who possesses a private key corresponding to a blockchain address can access the token at that address. Therefore, a blockchain address may represent the identity of a person who owns the token. Only the owner of a blockchain address can send a token to another person. The owner may access the token through the owner's wallet. The owner of a token may send or transfer the token to a user through a blockchain transaction. For example, the owner may sign a transaction corresponding to a token transfer with a private key. When a user receives the token, the token may be recorded in the blockchain at the user's blockchain address.

[0101] Different token standards can be used to define standard interfaces for different types of tokens on a decentralized blockchain. For example, tokens on the Ethereum blockchain can be implemented according to the ERC-20 standard for homogeneous tokens, the ERC-721 standard for non-homogeneous tokens, the ERC-994 standard, the ERC-998 standard, the ERC-1155 standard, and / or any other token standard configured for the Ethereum blockchain network or other blockchain networks including a virtual machine for executing contract bytecodes on its blockchain, which is obvious to those skilled in the art of the present disclosure. It is obvious to those skilled in the art of the present disclosure that a homogeneous token is a token that cannot be distinguished from another token of the same type, while a non-homogeneous token (NFT) is a unique token that can be distinguished from another token. Tokens that implement the ERC-994 standard and the ERC-994 standard can be considered non-homogeneous and can be layered with other tokens that implement the ERC-994 standard. In other words, tokens can form a tree structure of parent / child NFTs. In other examples, tokens implementing the ERC-1155 standard can be issued from a single smart contract, rather than having to generate a smart contract for each token as required in many other standards. As a result, smart contracts implementing the ERC-1155 standard can be used to generate both non-fungible tokens and fungible tokens.

[0102] NFT Market Trading

[0103] Figure 7 is a flow chart of a process 700 for facilitating a transaction involving the purchase of an NFT via an NFT marketplace according to an embodiment of the present disclosure. For purposes of discussion and explanation, as described above, Figure 1Process 700 is described with reference to system 100. As described above, process 700 may be performed by, for example, server 150 of system 100. However, process 700 is not intended to be limited thereto. Figure 7 The described process 700 and operations may be performed by any suitable computer system or combination of computer systems, including those described in various embodiments of the present disclosure. As described above, the NFT in this example may represent any unique digital data that can be tracked using a decentralized blockchain ledger. Such digital data may include, for example, tokenized versions of any various digital assets or non-digital assets. Examples of such assets include, but are not limited to, digital images and videos, music, collectibles and other digital art, and personal property deeds, event tickets, legal documents, and other real-world items.

[0104] like Figure 7 As shown, process 700 begins at block 702, which includes providing access to an NFT marketplace (e.g., as described above) to a plurality of digital wallets associated with a service provider. Figure 1 NFT marketplace 165). Multiple digital wallets may correspond to different users of a service provider, for example. The NFT marketplace in this example may correspond to a decentralized blockchain associated with an entity different from the service provider. It should be understood that the decentralized blockchain may support any of a variety of token standards for managing the creation and transfer of NFTs, for example, as a result of a transaction involving the purchase or sale of an NFT via the NFT marketplace. Multiple digital wallets may be configured to hold NFTs and other types of tokens, such as homogeneous cryptocurrency tokens associated with the decentralized blockchain of the NFT marketplace. Therefore, it should also be understood that these digital wallets may support any of the various types of tokens and token standards required for a particular implementation. In some implementations, the type of token may include a governance token representing a fractional share of a single NFT, which may be distributed to groups of users, as will be referenced below. Figure 8 Described in more detail.

[0105] In one or more embodiments, each user of the service provider may be associated with a unique identifier, such as an identifier distributed to the user during the initial registration process for the user account with the service provider. The identifier associated with each user may also be used to manage the user's corresponding digital wallet. In some implementations, multiple digital wallets may be maintained as part of a single, comprehensive digital wallet associated with the service provider and shared with registered users of the service provider, such as as part of a digital wallet application or service provided by the service provider. Such a wallet application may enable each user to request transactions involving the purchase or sale of NFTs via the NFT marketplace. In some implementations, the wallet application may be executed at a client device of a corresponding user of the service provider, such as described above. Figure 1 The client devices 110 and 120 of respective users 115 and 125.

[0106] Thus, process 700 may proceed to block 704, which includes receiving a request from a first user of the service provider to perform a transaction involving purchasing an NFT associated with a specified source address via the NFT marketplace. The first user in this example may be associated with a first identifier and a first digital wallet of a plurality of digital wallets that are associated with the service provider and provided in block 702. The specified source address associated with the NFT may be used to identify the current owner of the NFT.

[0107] Block 706 of process 700 includes determining whether a specified source address of the NFT (e.g., a blockchain or wallet address that currently holds the NFT) corresponds to a service provider. If it is determined in block 706 that the specified source address does not correspond to a service provider, then this indicates that the current owner of the NFT is a third-party user, not a user of the service provider. In this case, it can be assumed that the specified source address corresponds to a decentralized wallet of the third-party user, and process 700 can proceed to block 714. In block 714, the transaction is processed as an on-chain transaction and broadcast to the appropriate blockchain network, such as Figure 1 The blockchain network 145a, as described above, initiates the transfer of the NFT from the decentralized wallet of the third-party user to the first digital wallet of the first user. The blockchain network in this example may include a network of nodes associated with a decentralized blockchain corresponding to the NFT market.

[0108] However, if it is determined in box 706 that the specified source address corresponds to the service provider, process 700 can proceed to box 708. Box 708 includes determining that the NFT is owned by a second user of the service provider, who can be associated with a second identifier. In this example, the second identifier can be used in box 710 to identify a second digital wallet corresponding to the second user among multiple digital wallets associated with the service provider. Process 700 can then proceed to box 712, which includes changing or updating the identifier associated with the NFT from a second identifier associated with the second user (or the second user's second digital wallet) to a first identifier associated with the first user (or the first user's first digital wallet). Therefore, the transaction in this case can be processed as an off-chain transaction without involving a blockchain network or having to pay gas fees that are typically associated with on-chain transactions. In some embodiments, the purchase involved in the transaction can be a group purchase made by multiple users of the service provider, which will refer to Figure 8 Described in further detail.

[0109] Figure 8 According to an embodiment of the present disclosure, Figure 7Flowchart 800 of the process of group purchasing NFTs involved in the transaction. Figure 7 The process 700, for the purpose of discussion and explanation, will use Figure 1 Process 800 is described with reference to system 100, but process 800 is not intended to be limited thereto. For example, similar to process 700, process 800 may be performed by server 150 of system 100, as described above. Figure 7 As described above with respect to process 700 , in some cases, the transaction requested by the first user at block 704 may include a group purchase initiated by the first user on behalf of a group including the first user and other users of the service provider.

[0110] Therefore, if Figure 8 As shown, process 800 may begin at block 802, which includes determining whether the purchase of the NFT in the requested transaction is a group purchase. If it is determined in block 802 that the transaction is not a group purchase, the transaction is processed according to process 700, as described above with reference to Figure 7 As described, and process 800 ends. In some implementations, the determination of whether the purchase is a group purchase in block 802 can be performed as part of block 712 of process 700, for example, as an initial step before updating the identifier associated with the NFT.

[0111] On the other hand, if it is determined in box 802 that the purchase of the NFT in the transaction is a group purchase, process 800 proceeds to box 804, which includes issuing a governance token corresponding to the NFT. The governance token in this example can represent a partial ownership share in the NFT purchased via the NFT market. The governance token can be implemented as a homogeneous token on a decentralized blockchain associated with the NFT market, for example, which uses an appropriate token standard, such as the ERC-20 standard for homogeneous tokens on the blockchain Ethereum, as described above. The NFT in this example can be implemented using different token standards, for example, the ERC-721 standard for non-homogeneous tokens on the Ethereum blockchain.

[0112] In one or more embodiments, the issued governance tokens may be distributed to the respective digital wallets of users in the group, including the first user, based on the amount each user paid or contributed to the purchase price of the NFT. Thus, process 800 may proceed to block 806, which includes determining the amount of the purchase price of the NFT paid by each user in the group. At block 808, the issued governance tokens are distributed to the respective digital wallets of users in the group in proportion to the amount paid by each user in the group to purchase the NFT. Although not described in Figure 8 , it should be understood that process 800 (e.g., in blocks 804, 806, or 808) may also include determining which users are in the group and identifying a corresponding digital wallet for each user determined to be in the group. Figure 8 800 (e.g., at block 808), may include associating the NFT with a list of identifiers corresponding to users in the group. Additionally, in some embodiments, the group of users may include only users of the service provider, users of the service provider and users of a second service provider (e.g., an associated service provider), decentralized users, or a mixture of any of the foregoing.

[0113] In some embodiments, the decentralized governance token may be freely transferred to other users of the service provider, including, for example, other users in the group who may later wish to own a substantial portion of the NFT. For example, the first user in the above example may initiate a transfer of a corresponding portion of the decentralized governance token from the first user's digital wallet (e.g., as described above, in Figure 7 A request is made to transfer the governance token from the first digital wallet of the first user to the third digital wallet of the third user corresponding to the service provider. Once the governance token is transferred from the first digital wallet of the first user to the third digital wallet of the third user, the list of identifiers associated with the NFT can be updated to include the third identifier associated with the third user to replace the first identifier associated with the first user. By providing a mechanism for group purchasing and partial ownership, governance tokens enable more users of the service provider to participate in NFT market transactions and own a portion of the NFT without having to pay the full purchase price. The homogeneity and transferability of these tokens also make NFTs liquid.

[0114] In some embodiments, a decentralized autonomous organization (DAO) associated with a service provider may be used to facilitate NFT liquidity through a dedicated platform for managing the ownership and exchange of fractional shares in an NFT, as represented by its corresponding governance token. Such a platform may use, for example, a dedicated decentralized blockchain network associated with the service provider (e.g., as described above). Figure 1 In this example, the platform's private decentralized blockchain can also be used to issue governance tokens corresponding to NFTs.

[0115] In some embodiments, as described above, the NFT may represent an income-earning digital asset owned by a group of users associated with the service provider, for example based on a list of identifiers associated with the NFT. The income associated with the asset may include, for example, royalties earned from the sale or resale of the NFT or a portion thereof. For example, a digital wallet of a plurality of digital wallets associated with the service provider may be identified that corresponds to a user in the group (e.g., as described above, such as Figure 7The total revenue earned by the digital asset over a period of time (e.g., over any predetermined or user-specified time period) may be determined and then distributed to the identified digital wallets in proportion to the governance tokens in each identified digital wallet.

[0116] Since the users in this group are the owners of the income-earning digital asset represented by the NFT in this example, the list of identifiers associated with the NFT can represent a list of the current owners of the income-earning digital asset. Such a list can be used to track any changes in ownership that may occur over time to ensure that the income earned by the digital asset is distributed to the legitimate owner of the asset when it is distributed. In some cases, notification of such a change in ownership can be received before the total income earned by the digital asset is distributed. The notification can indicate, for example, a portion of the governance tokens in the first digital wallet of the first user (e.g., as described above in Figure 8 In this case, the list of identifiers of the owners of the digital assets that earned the revenue can be updated to include the third identifier associated with the third user based on the portion of the governance tokens transferred to the third digital wallet. This ensures that the digital wallets identified before the total revenue is distributed include the third digital wallet of the third user. In some embodiments, the total revenue can be distributed to the identified digital wallets as a fungible cryptocurrency token associated with a decentralized blockchain corresponding to the NFT marketplace. The notification in the above example can be triggered by the sale of the NFT via the NFT marketplace, as will be described below with reference to Fig. 9 Described.

[0117] Fig. 9 According to an embodiment of the present disclosure, a method for facilitating the user of a digital wallet service provider to Figure 7 Flowchart 900 of the process of selling NFTs in an NFT marketplace. Similar to Figure 7 The process 700, for the purpose of discussion and explanation, will use Figure 1 Process 900 is described with reference to system 100. For example, similar to process 700, process 900 may be performed by server 150 of system 100, as described above. However, process 900 is not intended to be limited thereto. It may be assumed that the user of the service provider in this example is a request (as described above, in Figure 7 Box 704) involves a first user in an initial transaction purchasing an NFT via an NFT marketplace.

[0118] like Fig. 9As shown, process 900 begins at block 902, which includes receiving a second request to perform a second transaction involving selling an NFT now owned by a first user to a specified destination address, such as an address corresponding to a buyer or his digital wallet, via an NFT marketplace. Process 900 then proceeds to block 904, which includes determining whether the specified destination address corresponds to a service provider.

[0119] If the specified destination address corresponds to a service provider, process 900 proceeds to block 906, which includes identifying a third user of the service provider (different from the third user of the service provider described above). Figure 7 The process 900 then proceeds to block 908, which includes updating the identifier associated with the NFT from the first identifier associated with the first user to the third identifier associated with the third user. The process 900 then ends.

[0120] On the other hand, if it is determined in block 904 that the specified destination address corresponds to a decentralized wallet of a third-party user (or buyer) not associated with the service provider, process 900 proceeds to block 910. Block 910 includes broadcasting the second transaction to the appropriate blockchain network to initiate the transfer of the NFT to the specified destination address corresponding to the decentralized wallet of the third-party user. The blockchain network in this example can be a network of nodes associated with a decentralized blockchain corresponding to the NFT market. Process 900 then proceeds to block 912, in which the NFT is transferred to the specified destination address corresponding to the decentralized wallet of the third-party user.

[0121] Figure 10-13 is a diagram showing examples of different workflows in which the Figure 7 , Figure 8 and Fig. 9 Processes 700, 800, and 900 may be applied to facilitate transactions involving the purchase and transfer of NFTs between a buyer and a seller, respectively. The buyer or seller (or both) in each of these workflows may be a user of a digital wallet associated with a service provider. As described above, the digital wallet may be one of a plurality of digital wallets associated with the service provider, wherein each digital wallet may correspond to a different user of the service provider. In addition, as described above with respect to Figure 7 As described in block 702 of , multiple wallets may be provided access to an NFT marketplace associated with an entity other than the service provider. Furthermore, in some implementations, multiple wallets may be maintained as part of a single, integrated wallet associated with the service provider. Figure 10-13The workflows shown in each of the examples relate to indirect transactions between buyers and sellers via such an NFT marketplace, which is associated with a third-party broker, but it should be understood that the embodiments of the present disclosure are not limited thereto. These same workflows can also be applied to direct transactions, in which buyers and sellers can purchase and transfer NFTs directly to each other without involving a third-party broker or via an NFT marketplace.

[0122] Fig.10 An example of a workflow 1000 for a transaction involving the purchase and transfer of an NFT between a buyer and a seller of different users as a service provider is shown. Figure 7 In process 700, as described above, the buyer may be a first user of the service provider who requested the transaction in block 704, and the seller may be a second user of the service provider who is the owner of the NFT, as determined in block 708. In some embodiments, the request for the transaction may be made by the service provider via a device of the first user (e.g., a user of the NFT as described above). Figure 1 system 100) and the NFT marketplace (e.g., Figure 1 The NFT marketplace 165) is connected to the service provider's application programming interface (API) to receive. As described above, the NFT marketplace can be a decentralized application or blockchain-integrated e-commerce website hosted by a third-party broker that enables sellers to list and advertise their NFTs, and buyers to initiate transactions involving the purchase and transfer of NFTs via the corresponding decentralized blockchain. As described above, buyers and sellers can each access the NFT marketplace via, for example, a web browser or other independent applications that can be executed on each user's device.

[0123] In some implementations, as described above, buyers and sellers are able to utilize a service provider's API connection to buy and sell NFTs on the NFT marketplace platform without having to have a decentralized wallet connected to the marketplace or pre-load cryptocurrency in a wallet to pay for any transaction-related gas fees. The API connection may be made via, for example, a service provider's website (e.g., as described above, provided by Figure 1The service provider may provide a browser extension that provides functionality for establishing an API connection when a user accesses a third-party broker's website for the NFT market directly via a web browser at the user's device. Alternatively, such functionality may be integrated or embedded into the third-party broker's website. For example, an NFT marketplace may enable a buyer who is also a user of the service provider to request a transaction involving the purchase of an NFT via a checkout interface that integrates the service provider's API connection functionality for facilitating and processing the requested transaction. In one or more embodiments, the transaction processing performed by the service provider may include verification of each transaction and the NFT supply status of each user's digital wallet. Such processing may also include any of the various risk and compliance checks on the transaction required for a particular implementation.

[0124] because Fig.10 The buyer and seller in the example shown are both users of the service provider, so the transaction can be processed as an off-chain transaction by updating the identifier associated with the NFT from the identifier of the seller (second user) to the identifier of the buyer (first user), as in box 712 of the above process 700. Although the buyer or first user in this example can be associated with a first digital wallet and the seller or second user can be associated with a second digital wallet, both digital wallets can be maintained as part of a single comprehensive wallet associated with the service provider. Therefore, no actual transfer of the NFT occurs. Therefore, no transfer is registered on the blockchain, and there is no need to broadcast the transaction to the blockchain network or pay gas fees associated with such an on-chain transaction. In addition, transactions can be processed using any form of currency required by a particular implementation, without being limited to cryptocurrencies associated with decentralized blockchains.

[0125] In this example, the integrated wallet associated with the service provider can be a hot wallet. In some embodiments, the service provider can initiate additional (on-chain) transactions to transfer the NFT from the hot wallet (or the first digital wallet associated with the first user) to a corresponding cold wallet maintained by a trusted third-party custodian associated with the service provider. Fig.10 As shown, as part of this transfer, the NFT can be transferred through an intermediary hot wallet associated with a third-party custodian. Unlike off-chain transactions between different users of the same service provider, additional transactions are broadcast to the appropriate blockchain network (e.g., as described above). Figure 1 The blockchain network 145b or 145c) of the NFT market may be used to perform on-chain transactions, and thus will incur associated gas fees. As described above, the blockchain network in this example may include a node network associated with a decentralized blockchain corresponding to the NFT market.

[0126] Fig.11 Shows holding and display by Fig.10 1100 for an NFT purchased by a user of a service provider. The workflow 1100 may be based on, for example, displaying the NFT on a user device (e.g., as described above). Figure 1 The GUI may be used to provide a plurality of options selectable by the user for viewing or displaying images associated with the NFT purchased via the NFT marketplace. Fig.11 As shown, the image can be displayed in a gallery view 1102 along with images associated with other NFTs in the user's wallet. The options presented to the user via the GUI may also include an option to share the selected NFT image (or image collection) for viewing by other users of the NFT marketplace. For example, when the user selects the option of gallery view 1102, the service provider may coordinate with a third-party custodian via the blockchain network to retrieve the selected NFT and its associated assets. Such attributes may include, for example, but not limited to, a source address corresponding to the user's digital wallet, a transaction hash of the NFT, an identifier associated with the NFT (e.g., a distribution identifier for the user and current owner), an image or media file type, and any other metadata that may be associated with the NFT.

[0127] Fig.12 Another example of a workflow 1200 for an NFT marketplace transaction is shown involving the purchase and transfer of an NFT between a buyer who is a user of a service provider and a seller who is a user of a third-party decentralized wallet. Fig.13 Another example of a workflow 1300 for an NFT market transaction involving Fig.10 The sale and transfer of NFTs between sellers who are users of the service provider and buyers who are users of third-party decentralized wallets. As mentioned above, Fig.12 The buyer and Fig.13 The seller in the workflow 1300 may be, for example, Fig.10 The first user of the same service provider in workflow 1000 (e.g., Figure 1 A user 115 of a client device 110).

[0128] As mentioned above Fig.10 The off-chain transaction between the first user and the second user of the service provider in the workflow 1000 is different. Figure 1 and Figure 2 The transaction shown in each of the examples is conducted between a first user and a second user. Fig.12 and Fig.13 Is it related to third-party decentralized wallet users (for example, as mentioned above Figure 1 Thus, the transaction in each of these examples is broadcast to the appropriate blockchain network (e.g., Figure 1 145b or 145c), and thus will incur associated gas fees. Fig.12 As shown, workflow 1200 may include broadcasting a transaction to an appropriate blockchain network that includes purchasing an NFT owned by a third-party user and transferring it from a specified source address corresponding to a decentralized wallet of the third-party user to a digital wallet corresponding to the first user (the buyer in the transaction).

[0129] like Fig.13 As shown, workflow 1300 may include broadcasting a transaction involving the purchase of an NFT owned by a first user (the seller in this transaction) to the appropriate blockchain network to initiate the transfer of the NFT to a specified destination address corresponding to a third-party user's decentralized wallet. Since the NFT may be held in a cold wallet of a third-party custodian, one or more additional transactions may need to be broadcasted to the blockchain network (and additional gas fees paid) to retrieve the NFT from the third-party custodian's cold wallet or transfer it to a service provider's hot wallet, as it may be transferred to a specified destination address corresponding to a third-party user's decentralized wallet.

[0130] Client-Server System

[0131] Fig.14 A client-server system 1400 is shown. The system 1400 may include at least one client device 1410, at least one database system 1420, and / or at least one server system 1430 that communicate over a network 1440. It should be understood that the network connections shown are illustrative and any means of establishing a communications link between the computers may be used. Various network protocols such as TCP / IP, Ethernet, FTP, HTTP, and various wireless communication technologies such as GSM, CDMA, WiFi, and LTE are assumed to exist, and the various computing devices described herein may be configured to communicate using any of these network protocols or technologies. Using reference Fig.14 One or more computing systems described herein may implement, in whole or in part, any of the devices and systems described herein.

[0132] As described herein, client device 1410 can use one or more client applications (not shown) to access server applications and / or resources. Client device 1410 can be a mobile device, such as a laptop, smart phone, mobile phone, or tablet computer, or a computing device, such as a desktop computer or server, wearable device, embedded device. Alternatively, client device 1410 can include other types of devices, such as game consoles, cameras / recorders, video players (e.g., incorporating DVD, Blu-ray, red laser, optical and / or streaming media technologies), smart TVs, and other applicable network-connected devices.

[0133] The database system 1420 may be configured to maintain, store, retrieve, and update information for the server system 1430. In addition, the database system may provide information to the server system 1430 periodically or upon request. In this regard, the database system 1420 may be a decentralized database capable of storing, maintaining, and updating a large amount of data across a cluster of nodes. The database system 1420 may provide a variety of databases, including but not limited to relational databases, hierarchical databases, decentralized databases, in-memory databases, flat file databases, XML databases, NoSQL databases, graph databases, and / or combinations thereof.

[0134] The server system 1430 may be configured with a server application (not shown) that can interface with the client application and the database system 1420 as described herein. In this regard, the server system 1430 may be a standalone server, an enterprise server, or a server located in a server farm or cloud computing environment. According to some examples, the server system 1430 may be a virtual server hosted on hardware capable of supporting multiple virtual servers.

[0135] The network 1440 may include any type of network. For example, the network 1440 may include a local area network (LAN), a wide area network (WAN), a wireless telecommunications network, and / or any other communication network or combination thereof. It should be understood that the network connections shown are illustrative, and any means of establishing a communication link between computers may be used. It is assumed that there are various network protocols such as TCP / IP, Ethernet, FTP, HTTP, and various wireless communication technologies such as GSM, CDMA, WiFi, and LTE, and the various computing devices described herein may be configured to communicate using any of these network protocols or technologies.

[0136] The data transmitted to and from the various computing devices in the system 1400 may include secure and sensitive data, such as confidential files, customer personally identifiable information, and account data. Therefore, it may be desirable to use secure network protocols and encryption to protect the transmission of such data, and / or to protect the integrity of the data stored on the various computing devices. For example, a file-based integration solution or a service-based integration solution can be used to transmit data between various computing devices. Various network communication protocols can be used to transmit data. Secure data transmission protocols and / or encryption can be used in file transmission to protect the integrity of data, such as file transfer protocol (FTP), secure file transfer protocol (SFTP), and / or good privacy protocol (PGP) encryption. In many embodiments, one or more network services can be implemented in various computing devices. The network service can be accessed by authorized external devices and users to support data input, extraction, and manipulation between various computing devices in the system 1400. The network service built to support the personalized display system can be cross-domain and / or cross-platform, and can be built for enterprise use. Data can be transmitted using Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols to provide secure connections between computing devices. Network services can be implemented using the WS-Security standard, using XML encryption to provide secure SOAP messages. Specialized hardware can be used to provide secure network services. For example, a secure network device can include built-in features such as hardware-accelerated SSL and HTTPS, WS-Security, and / or firewalls. Such dedicated hardware can be installed and configured in front of one or more computing devices in system 1400 so that any external device can communicate directly with the dedicated hardware.

[0137] Computing equipment

[0138] Now go to Fig.15 , describes a computing device 1500 that can be used with one or more computing systems. The computing device 1500 may include a processor 1503 for controlling the overall operation of the computing device 1500 and its related components, including RAM 1505, ROM 1507, input / output (I / O) devices 1509, communication interfaces 1511, and / or memory 1515. A data bus may interconnect the processor 1503, RAM 1505, ROM 1507, memory 1515, I / O devices 1509, and / or communication interfaces 1511. In some embodiments, the computing device 1500 may represent, be incorporated into, and / or include a variety of devices, such as a desktop computer, a computer server, a mobile device such as a laptop computer, a tablet computer, a smart phone, any other type of mobile computing device, etc., and / or any other type of data processing device.

[0139] Input / output (I / O) devices 1509 may include a microphone, keypad, touch screen, and / or stylus motions, gestures, through which a user of computing device 1500 may provide input, and may also include one or more speakers for providing audio output and a video display device for providing text, audiovisual, and / or graphical output. Software may be stored in memory 1515 to provide instructions to processor 1503, thereby allowing computing device 1500 to perform various actions. For example, memory 1515 may store software used by computing device 1500, such as operating system 1517, application programs 1519, and / or associated internal databases 1521. Various hardware storage units in memory 1515 may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Memory 1515 may include one or more physical persistent memory devices and / or one or more non-persistent memory devices. The memory 1515 may include, but is not limited to, random access memory (RAM) 1505, read-only memory (ROM) 1507, electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technology, optical disk storage, magnetic cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the processor 1503.

[0140] The communication interface 1511 may include one or more transceivers, digital signal processors, and / or additional circuitry and software for communicating via any wired or wireless network using any of the protocols described herein.

[0141] The processor 1503 may include a single central processing unit (CPU), which may be a single-core or multi-core processor, or may include multiple CPUs. The processor 1503 and associated components may allow the computing device 1500 to execute a series of computer-readable instructions to perform some or all of the processes described herein. Fig.151500, but various elements within the memory 1515 or other components in the computing device 1500 may include one or more caches, for example, a CPU cache used by the processor 1503, a page cache used by the operating system 1517, a disk cache of a hard drive, and / or a database cache for caching content from the database 1521. For embodiments including a CPU cache, the CPU cache may be used by one or more processors 1503 to reduce memory latency and access time. The processor 1503 may retrieve data from the CPU cache or write data to the CPU cache instead of reading / writing to the memory 1515, which may increase the speed of these operations. In some examples, a database cache may be created, in which certain data from the database 1521 is cached in a separate smaller database in a memory separate from the database, such as in the RAM 1505 or on a separate computing device. For example, in a multi-tier application, a database cache on an application server may reduce data retrieval and data manipulation time because there is no need to communicate with a back-end database server over a network. These types of caches and other types of caches may be included in various embodiments and may provide potential advantages in certain implementations of the devices, systems, and methods described herein, such as faster response times and reduced dependence on network conditions when sending and receiving data.

[0142] Although the various components of computing device 1500 are described separately, the functionality of the various components may be combined and / or performed by a single component and / or multiple computing devices in communication without departing from the invention.

[0143] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are described as example implementations of the claims.

Claims

1. A system comprising: non-transitory memory; as well as one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising: Providing access to a non-fungible token (NFT) marketplace to a plurality of digital wallets associated with a service provider, wherein the NFT marketplace corresponds to a decentralized blockchain associated with an entity different from the service provider; receiving a request from a first user of the service provider to perform a transaction, the first user being associated with a first identifier and a first digital wallet of the plurality of digital wallets, the transaction involving purchasing an NFT associated with a specified source address via the NFT marketplace; determining that the specified source address corresponds to the service provider; and Based on determining that the specified source address corresponds to the service provider: determining that the NFT is owned by a second user of the service provider associated with a second identifier; identifying a second digital wallet among the plurality of digital wallets corresponding to the second user; and An identifier associated with the NFT is updated from the second identifier associated with the second user to the first identifier associated with the first user.

2. The system according to claim 1, wherein: The request for the transaction is received via an application programming interface (API) connection of the service provider, which is established between the first user's device and the NFT marketplace.

3. The system according to claim 1, wherein: The plurality of digital wallets are maintained as part of a single integrated digital wallet associated with the service provider.

4. The system according to claim 1, wherein: The first digital wallet of the first user is a hot wallet associated with the service provider, and the operations further include: An additional transaction is broadcast to a network of nodes associated with the decentralized blockchain to transfer the NFT from the first user's hot wallet to a corresponding cold wallet maintained by a trusted third-party custodian associated with the service provider.

5. The system according to claim 1, wherein: The purchase is a group purchase initiated by the first user on behalf of a group, the group including the first user and other users associated with the service provider, and wherein the operation further comprises: Issuing a governance token corresponding to the NFT; determining the amount of the purchase price of the NFT paid by each user in the group; and The issued governance tokens will be distributed to the corresponding digital wallets of the users in the group in proportion to the amount paid by each user in the group to purchase the NFT.

6. The system according to claim 5, wherein: The operations also include: associating the NFT with a list of identifiers corresponding to users in the group; receiving a second request from the first user to transfer a corresponding portion of the distributed governance tokens from a first digital wallet of the first user to a third digital wallet of the plurality of wallets, the third digital wallet corresponding to a third user of the service provider; transferring a corresponding portion of the governance tokens from the first digital wallet of the first user to a third digital wallet of the third user; and The list of identifiers associated with the NFT is updated to include a third identifier associated with the third user in place of the first identifier associated with the first user.

7. The system according to claim 5, wherein: The NFT represents an income-earning digital asset owned by the group, and the operations further include: Determine the total revenue earned by the digital asset over a period of time; identifying a digital wallet from among the plurality of digital wallets that corresponds to the user in the group; and The total revenue is distributed to the identified digital wallets in proportion to the governance tokens in each identified digital wallet.

8. The system according to claim 7, wherein: The users in the group are owners of the income-earning digital assets, and the operations further include: Associating the NFT with a list of identifiers corresponding to owners of the income-earning digital assets; Prior to distributing the total revenue earned from the digital asset, receiving a notification that a portion of the governance tokens in the first digital wallet of the first user have been transferred to a third digital wallet of a third user of the service provider; and updating the list of identifiers corresponding to owners of the income-earning digital assets to include a third identifier associated with the third user based on the portion of the governance tokens transferred to the third digital wallet, The identified digital wallet includes a third digital wallet of the third user.

9. The system according to claim 7, wherein: The total revenue is distributed to the identified digital wallets as fungible cryptocurrency tokens associated with the decentralized blockchain.

10. The system according to claim 1, wherein: The operations also include: receiving a second request to perform a second transaction involving selling the NFT owned by the first user of the service provider to a specified destination address via the NFT marketplace; Determining that the specified destination address corresponds to a decentralized wallet of a third-party user of the NFT marketplace; and Based on determining that the specified destination address corresponds to the decentralized wallet of the third-party user: broadcasting the second transaction to a network of nodes associated with the decentralized blockchain to initiate a transfer of the NFT to the specified destination address corresponding to the decentralized wallet of the third-party user; and Transfer the NFT to the designated destination address corresponding to the decentralized wallet of the third-party user.

11. A method comprising: Providing access to a non-fungible token (NFT) marketplace to a plurality of digital wallets associated with a service provider, wherein the NFT marketplace corresponds to a decentralized blockchain associated with an entity different from the service provider; receiving a request from a first user of the service provider to perform a transaction, the first user being associated with a first identifier and a first digital wallet of the plurality of digital wallets, the transaction involving purchasing an NFT associated with a specified source address via the NFT marketplace; In response to determining that the designated source address corresponds to the service provider, identifying a second user of the service provider as having ownership of the NFT, wherein the second user is associated with a second identifier and a second digital wallet of the plurality of digital wallets; and Transferring ownership of the NFT from the second user to the first user by updating an identifier associated with the NFT from the second identifier associated with the second user to the first identifier associated with the first user.

12. The method according to claim 11, wherein: The first digital wallet and the second digital wallet of each of the first user and the second user are part of a single integrated digital wallet associated with the service provider, and the transaction between the first user and the second user is processed as an off-chain transaction outside the decentralized blockchain.

13. The method according to claim 11, wherein: The purchase is a group purchase initiated by the first user on behalf of a group, the group including the first user and other users associated with the service provider, and the method further comprises: Issuing a governance token corresponding to the NFT; determining the amount of the purchase price of the NFT paid by each user in the group; and The issued governance tokens will be distributed to the corresponding digital wallets of the users in the group in proportion to the amount paid by each user in the group to purchase the NFT.

14. The method according to claim 13, further comprising: associating the NFT with a list of identifiers corresponding to users in the group; receiving a second request from the first user to transfer a corresponding portion of the distributed governance tokens from a first digital wallet of the first user to a third digital wallet of the plurality of wallets, the third digital wallet corresponding to a third user of the service provider; transferring a corresponding portion of the governance tokens from the first digital wallet of the first user to a third digital wallet of the third user; as well as The list of identifiers associated with the NFT is updated to include a third identifier associated with the third user in place of the first identifier associated with the first user.

15. The method according to claim 13, wherein: The NFT represents an income-earning digital asset owned by the group, and the method further comprises: Determine the total revenue earned by the digital asset over a period of time; identifying a digital wallet from among the plurality of digital wallets that corresponds to the user in the group; and The total revenue is distributed to the identified digital wallets in proportion to the governance tokens in each identified digital wallet.

16. The method according to claim 11, further comprising: Transferring the NFT to a trusted third-party custodian associated with the service provider for long-term storage in a cold wallet maintained by the trusted third-party custodian on behalf of the first user.

17. The method according to claim 11, further comprising: Multiple options are provided via a graphical user interface (GUI) displayed at the first user's device for viewing images associated with the NFT and sharing the images for viewing by other users of the NFT marketplace.

18. A non-transitory machine-readable medium having machine-readable instructions stored thereon, the machine-readable instructions being executable to cause a machine to perform operations comprising: Providing access to a non-fungible token (NFT) marketplace to a plurality of digital wallets associated with a service provider, wherein the NFT marketplace corresponds to a decentralized blockchain associated with an entity different from the service provider; receiving a request from a first user of the service provider to perform a transaction, the first user being associated with a first identifier and a first digital wallet of the plurality of digital wallets, the transaction involving purchasing an NFT associated with a specified source address via the NFT marketplace; determining that the designated source address corresponds to a second user of the service provider, the second user being associated with a second identifier and a second digital wallet of the plurality of digital wallets; and An identifier associated with the NFT is updated from the second identifier associated with the second user to the first identifier associated with the first user.

19. The non-transitory machine-readable medium of claim 18, wherein: The purchase is a group purchase initiated by the first user on behalf of a group of users, the group including the first user and other users associated with the service provider, and the operations further include: Issuing a governance token corresponding to the NFT; determining the amount of the purchase price of the NFT paid by each user in the group; and The issued governance tokens will be distributed to the corresponding digital wallets of the users in the group in proportion to the amount paid by each user in the group to purchase the NFT.

20. The non-transitory machine-readable medium of claim 18, wherein: The operations also include: receiving a second request to perform a second transaction involving selling the NFT owned by the first user of the service provider to a specified destination address via the NFT marketplace; and In response to determining that the specified destination address corresponds to a decentralized wallet of a third-party user of the NFT marketplace: broadcasting the second transaction to a network of nodes associated with the decentralized blockchain to initiate a transfer of the NFT to the specified destination address corresponding to the decentralized wallet of the third-party user; and Transfer the NFT to the designated destination address corresponding to the decentralized wallet of the third-party user.