Systems and methods for efficiently and securely processing, accessing, and transmitting data via a blockchain network

Abstract

The present invention provides improved methods and corresponding systems for sharing, storing, creating, and accessing data stored on a blockchain. It can form part of a protocol for searching for content / data on a blockchain. The method according to the present invention can be used to associate or link data stored in (separate / different) blockchain transactions so as to enable identification, retrieval, and / or sharing of the data stored therein. Additionally or alternatively, it helps to identify the transactions (Tx) in the blockchain that store the content / data that needs to be shared, transmitted, stored, and / or accessed by a user. Such a method includes the steps of mapping a mnemonic to: 1) a public key (PK) associated with a transaction (Tx); and 2) a transaction ID (TxID) of the transaction (Tx).

Description

Technical Field

[0001] The present invention generally relates to improvements in data communication and exchange across electronic networks, particularly peer-to-peer networks such as blockchain networks and the like. It relates to data storage, access, retrieval, and processing, and particularly to such data-related activities on a blockchain. The present invention is particularly suitable for but not limited to use when processing data in a manner similar to that provided by websites and web pages, but using a blockchain as the underlying mechanism or platform instead of a web server. Thus, the present invention provides a secure, efficient, cryptographically implemented alternative infrastructure for data processing and transfer. Background Art

[0002] In this document, we use the term "blockchain" to include all forms of electronic computer-based distributed ledgers. These include consensus-based blockchain and transaction chain technologies, permissioned and unpermissioned ledgers, shared ledgers, and their variants. The term "user" in this context can refer to a person or a processor-based resource.

[0003] A blockchain is a peer-to-peer electronic ledger that is implemented as a computer-based decentralized distributed system composed of blocks, which in turn are composed of transactions. Each transaction is a data structure that encodes the transfer of digital asset control rights between participants in the blockchain system and includes at least one input and at least one output. Each block contains the hash value of the previous block, such that the blocks are linked together to create a permanent, immutable record of all transactions that have been written to the blockchain since its inception. Transactions contain small programs called scripts embedded in their inputs and outputs that specify how and by whom the output of the transaction can be accessed.

[0004] In order to write a transaction to the blockchain, it must be "validated". Network nodes perform work to ensure that each transaction is valid, and invalid transactions are rejected by the network. The software client installed on the node performs this validation work on unspent transactions (UTXOs) by executing their locking scripts and unlocking scripts. If the execution evaluation of the locking script and unlocking script is true (TRUE), then the transaction is valid and the transaction is written to the blockchain. Thus, in order to write a transaction to the blockchain, it is necessary to: i) validate the transaction by the first node receiving the transaction - if the transaction is verified, the node relays it to other nodes in the network; ii) add the transaction to a new block; and iii) the transaction is added to the public ledger of past transactions.

[0005] Blockchains in applications can leverage the benefits of blockchains (e.g., permanence of events, tamper-proof records, distributed processing, etc.) while having more uses in their applications.

[0006] One such area of concern is the use of blockchain to store, share, access, and control data among users. Currently, this is achieved via the Internet, where servers host websites and pages that users typically access through search engines to access the desired data.

[0007] However, some observers have begun to envision using blockchain to address certain drawbacks of the Internet, such as the control of large amounts of data and content by centralized parties. For example, see "Life After Google: The Fall of Big Data and the Rise of the Blockchain Economy", George Gilder, Gateway Editions, July 2018, ISBN-10: 9781621575764 and ISBN-13: 978-1621575764. SUMMARY OF THE INVENTION

[0008] Accordingly, it is desirable to provide an arrangement that enables the advantageous use of the distributed, immutable, and permanent nature of blockchain to store, process, retrieve, search, and / or share such data on the blockchain. Such an improved solution has now been devised.

[0009] Embodiments of the present disclosure provide at least alternative efficient and secure techniques for implementing blockchain solutions and for storing, processing, searching, and / or retrieving data thereon or therefrom. Embodiments also provide at least a technical infrastructure for alternative blockchain implementations for storing, processing, retrieving, sending, searching, and / or sharing data between computing nodes.

[0010] Embodiments also provide solutions for securely controlling access to digital resources on technically different and improved computing platforms that include a blockchain and a blockchain protocol. Additionally, multiple associated or logically linked transactions on the blockchain can be processed efficiently, securely, and quickly. Logically associated transactions may not be stored on the blockchain at consecutive block heights, but they can be easily and securely identified and / or accessed.

[0011] The invention is defined in the appended claims.

[0012] According to the present invention, a computer / blockchain-implemented method and a corresponding system can be provided. The method can be described as a method for enabling or controlling the processing, storage, retrieval, identification, and / or sharing of data via a blockchain. Additionally or alternatively, it can be described as a method for associating or linking data stored in (separate / different) blockchain transactions to achieve the identification, retrieval, and / or sharing of the data. In this context, "sharing" can include providing, sending, communicating, transmitting a part of the data to a node or user or providing access to a part of the data.

[0013] Additionally or alternatively, it can be described as a method for enabling the identification of data and / or transactions (Tx) in a blockchain. The blockchain can be a peer-to-peer blockchain operating on a peer-to-peer network. A transaction can store the content / data that needs to be shared, transmitted, stored, and / or accessed by a user, or store a reference to such content / data.

[0014] The method can include the step of providing a mnemonic.

[0015] The method can include the following steps:

[0016] Mapping the mnemonic to:

[0017] A public key (PK) associated with a transaction (Tx); and

[0018] A transaction ID (TxID) of the transaction (Tx).

[0019] The mnemonic can be a human-readable identifier, term, or label. This provides the advantage that, compared to the prior art, the search for content on the blockchain can be performed more easily, more quickly, and with fewer input errors, thus providing an enhanced and improved search / storage / sharing / scheme and architecture.

[0020] As will be readily understood by a person skilled in the art, each blockchain transaction has its own unique identifier (ID) so that it can be identified on the blockchain. Advantageously, the present invention combines this existing ID and the public key (PK) associated with and / or provided in the transaction such that the combination forms the unique identifier of the transaction. Then it can be mapped to a mnemonic to at least provide the above advantages.

[0021] Preferably, the mapping step includes:

[0022] Using the public key (PK) and the transaction ID (TxID) as operands for an operation that produces an output, and

[0023] Mapping the mnemonic to the output.

[0024] Therefore, the public key and the transaction ID can be processed in some way before being mapped to the mnemonic. This can include: hashing the output before mapping to the mnemonic. This operation can be a concatenation operation.

[0025] Preferably, the public key (PK) includes a human-readable prefix. This can be the "vanity address" known in the prior art. This provides the following advantages: the public key includes a part of the text that is easier for people to read or recognize, making searching, processing, accessing, and retrieving easier, faster, and less error-prone.

[0026] The method can also include the step of searching for a transaction (Tx) in the blockchain. Additionally or alternatively, the method can include the following steps: identifying the transaction and / or a part of the data associated with, in, or referenced from the transaction. This can be performed using a combination of the public key (PK) and the transaction ID.

[0027] The method can include the following steps: sending data associated with the transaction from a computing resource to another computing resource. Any one or both of these resources can be a node on the blockchain network.

[0028] The method can include the following steps: processing at least one blockchain node transaction (Node):

[0029] Protocol flag;

[0030] Discretionary public key (DPK); and

[0031] Discretionary transaction ID (DTxID).

[0032] This combination of features enables each data part stored in the node transaction to be identified on the blockchain and, when provided in multiple transactions, can also be linked / associated with each other. It enables the construction of a graph or tree structure that reflects the hierarchical relationship between the data parts, thus facilitating their storage, processing, and sharing. This enables data to be stored, identified, communicated, and retrieved across multiple nodes and transactions on a peer-to-peer network (blockchain) in an improved manner that was not possible before the present invention was designed. Since the present invention enables the blockchain network to be used in a new way and provides improved technical effects, the present invention provides an improved blockchain-implemented network.

[0033] Preferably, a blockchain transaction (Tx) includes a portion of data or a reference to a portion of data. The reference to a portion of data may be a pointer, address, or other indicator of the location where the data is stored. The portion of data may be any type of data or digital content, such as, for example, a computer-executable item, text, video, image, sound file, etc. The portion of data may be referred to as "content". The portion of data or the reference thereto may be in a processed form. For example, it may be a hash digest of the portion of data. The data may be stored on-chain or off-chain (i.e., "off-chain") of the blockchain.

[0034] The discretionary public key (DPK) and / or the discretionary transaction ID (DTxID) may be "discretionary" in that they are provided as part of the present invention and not as an essential part of a transaction as prescribed by the underlying blockchain protocol. In other words, according to the underlying blockchain protocol, they are not required for a transaction to be valid. They are additional non-essential items provided as part of the present invention and not because the blockchain protocol requires them.

[0035] Preferably, the protocol flag is associated with and / or indicates a blockchain-based protocol for searching one or more blockchain transactions, storing and / or retrieving data in one or more blockchain transactions. The protocol flag may be an indicator or a marker. It may indicate that a transaction is formed according to a predetermined protocol. This may be a protocol other than the underlying blockchain protocol. It may be a search protocol according to any of the embodiments described herein (i.e., the search protocol of the "meta-network" protocol described herein).

[0036] The term "processing" should be construed to mean any activity related to a transaction, including generating, transmitting, verifying, accessing, searching, and / or identifying.

[0037] According to an embodiment of the present invention, the discretionary transaction ID may be an identifier, label, indicator, or marker associated with a transaction (Tx). We use the term "indicator" to include all of these terms. It should be noted that, as is known in the art and as will be readily understood by those skilled in the art, each transaction on a blockchain is uniquely identified by an identifier, which is typically referred to in the art as a TxID. The TxID is an essential, necessary, and non-discretionary part of the underlying blockchain protocol. This non-discretionary TxID should not be confused with the discretionary transaction ID (DTxID) mentioned herein.

[0038] The method may further include the steps of: identifying one or more additional transactions having the same public key as a transaction (Tx). Advantageously, if two or more transactions have the same public key, they can be interpreted as different versions of the same content / data. Thus, the present invention provides a simple but powerful mechanism for version control of content on a blockchain. This can ensure both data integrity and avoid errors due to using the correct version of the data, and less processing is required because there is less searching for the correct version of the data to be performed.

[0039] In one or more embodiments, the public key of a transaction (Tx) and the public keys of additional transactions are provided in the inputs of the one or more additional transactions. This enables the identification of siblings in the graph.

[0040] In one or more embodiments, the public key of a transaction (Tx) is provided within the input of the transaction; and the public keys of one or more additional transactions are provided in the outputs of the one or more additional transactions.

[0041] In this case, the public keys of the additional transactions are discretionary in the sense that they are provided not as specified or required by the underlying blockchain protocol in a transaction, but as part of the protocol of the present invention. This enables the identification of logical parents and / or the association of logical children in the graph with logical parents.

[0042] In one or more embodiments, the public key of a transaction (Tx) is provided in the output of the transaction; and the public keys of one or more additional transactions are provided in the inputs of the one or more additional transactions. This also enables the identification of logical parent nodes and / or the association of logical child nodes with logical parent nodes.

[0043] In one or more embodiments, the public key of a transaction (Tx) is provided in the output of the transaction; and the public keys of one or more additional transactions are provided in the outputs of the one or more additional transactions. This enables the identification of transactions that contain or include different versions of the same content / data.

[0044] The method may further include the steps of: examining the transaction (Tx) and one or more additional transactions to determine which is the most recent transaction. The determination may be made or performed using or in accordance with / reference to aspects of the underlying blockchain's protocol. The most recent transaction may be determined by any suitable metric, including:

[0045] block height; or

[0046] proof of work; or

[0047] the ordering of transactions within a block.

[0048] The present invention also provides a corresponding system, which is arranged and configured to perform the steps of any embodiment of the methods described herein. It may include a computer-implemented system, which includes:

[0049] a processor; and

[0050] a memory including executable instructions, which, when executed by the processor, cause the system to perform any embodiment of the computer-implemented methods described herein.

[0051] The present invention also provides a non-transitory computer-readable storage medium having stored thereon executable instructions, which, when executed by a processor of a computer system, cause the computer system to perform at least any embodiment of the methods described herein.

[0052] Accordingly, the present invention may be an improved solution for searching, identifying, and / or accessing or transmitting data via a blockchain. The method provides improvements for data communication and exchange across electronic networks, particularly blockchain networks.

[0053] Some embodiments of the method / system of the present invention may include one or more of the features described below, particularly the features in the section entitled "Naming and Addressing". BRIEF DESCRIPTION OF THE DRAWINGS

[0054] These and other aspects of the present invention will become apparent from and be elucidated with reference to the embodiments described herein. Embodiments of the present invention will now be described, by way of example only, and with reference to the accompanying drawings, in which:

[0055] Figure 1 illustrates a blockchain transaction embodying the present invention, in which data is stored in multiple outputs;

[0056] Figure 2 illustrates a blockchain transaction embodying the present invention, in which data is stored in inputs.

[0057] Figure 3 illustrates a series of blockchain transactions embodying the present invention, in which data is stored on the outputs of multiple blockchain transactions;

[0058] Figure 4 illustrates a blockchain transaction embodying the present invention, which transfers a payment to allow access to data by means of an atomic swap;

[0059] Figure 5 illustrates a blockchain transaction embodying the present invention for Figure 4 exchanging the payment of a transaction;

[0060] Figure 6 Shows the secret values stored by participants in a blockchain transaction embodying the present invention, the blockchain transaction issuing tokens to allow access to data by means of atomic swaps;

[0061] Figure 7 and Figure 8 Shows a blockchain transaction embodying the present invention for issuing tokens to allow access to data by means of atomic swaps;

[0062] Figure 9 and Figure 10 Shows a blockchain transaction embodying the present invention for redeeming tokens issued by the transaction of Figure 7 and Figure 8 ;

[0063] Figure 11 and Figure 12 Shows a blockchain transaction for accessing the secrets exchanged by the transaction of Figure 9 and Figure 10 ;

[0064] Figure 13 Provides an illustration of the meta-network graph structure according to an embodiment of the present invention.

[0065] Figure 14 Shows an illustration of a meta-network graph tree for the domain "bobsblog" including an MURL search path according to an embodiment of the present invention.

[0066] Figure 15 Provides a diagram showing how to perform a search for content within the infrastructure of an embodiment of the present invention.

[0067] Figure 16 Shows an illustrative interaction between a local full-copy peer and a global full-copy peer according to an embodiment of the present invention.

[0068] Figure 17 Shows a meta-network tree (or graph) for use in reference to the illustrative use cases described below.

[0069] Figure 18 Shows a flowchart that illustrates the process embodied by the illustrative use case provided below.

[0070] Figure 19 Is a schematic diagram showing a computing environment in which various embodiments may be implemented. Detailed Description

[0071] In the remainder of this document, the protocol that determines the operation of the embodiments of the present invention will be referred to as the "meta-network protocol".

[0072] According to an embodiment of the present invention, the terms "content", "digital content", and "data" may be used interchangeably herein to refer to data stored in a blockchain transaction / referenced via a blockchain transaction or otherwise accessed. The data is additional / discretionary data that is transmitted, communicated, or stored via the blockchain, as opposed to data required by the underlying blockchain protocol or data that is part of the transaction code itself.

[0073] Overview

[0074] As described above, there has been a recognized need for an improved and / or alternative infrastructure for storing, writing, accessing, and viewing data between and by computing nodes. Leveraging the inherent advantages of blockchain technology (e.g., immutable records, cryptographically enforced control and access, built-in payment mechanisms, ability to publicly inspect the ledger, distributed architecture, etc.) would be advantageous. However, building an "Internet enabled by blockchain" is challenging from many technical perspectives.

[0075] These challenges may include, but are not limited to: how to locate a specific portion of data in the network; how to protect and control access to data so that only authorized parties can gain access; how to transfer data from one party to another in a peer-to-peer manner; how to arrange data such that it can be logically related but still stored in different locations within the network and subsequently how to combine it from different locations to provide an overall and enhanced result; how to provide and / or store data in a hierarchical manner; how to allow users and parties with different computing platforms to access the required data; how to store, provide, and share data across (potentially global) computing networks without relying on or requiring large storage servers and centralized data controllers.

[0076] The present invention provides such an improved solution in such a way that is in some respects similar to the Internet, but uses a platform of hardware components and software components that are completely different from those known in the prior art and achieves its results in a completely different way. According to an embodiment of the present invention, the servers that store Internet / network data and provide it to end users are replaced by blockchain exchanges residing on a blockchain network. To achieve this, several innovations must be designed. These will be described in the following sections.

[0077] Inserting Data into the Blockchain "Meta-Network" Referenced Figure 1, shows a blockchain transaction embodying the present invention, in which first data to be stored on the blockchain is stored in one or more first outputs of the transaction, and second data representing attributes of the first data is stored in one or more second outputs of the transaction. One or more first parts <Content 1> of the first data are stored in spendable outputs of the transaction. Data <Attribute 1> and <Attribute 2> representing corresponding attributes of the first data and a flag indicating that data is being stored according to the MetaNet protocol are stored in a second non-spendable output of the transaction. The term "non-spendable" is used to indicate that at least one of the first and / or second outputs of the transaction may include a script opcode (OP_RETURN) that is used to mark the output as invalid for subsequent use as an input to a subsequent transaction.

[0078] It is advantageous to store the content and attribute parts of the data separately in separate outputs of the transaction.

[0079] Figure 2 shows a blockchain transaction embodying the present invention, in which first data <Content 1> to be stored on the blockchain is stored in the input of the transaction. The MetaNet flag and attribute data <Attribute 1> and <Attribute 2> are stored in non-spendable outputs of the transaction in a manner similar to Figure 1 the arrangement shown.

[0080] Data Insertion

[0081] Data Insertion Method

[0082] It is desired to be able to insert the following data into the blockchain

[0083] a) MetaNet flag

[0084] b) Attributes

[0085] c) Content

[0086] The content is the data to be stored on the blockchain. The MetaNet flag is a 4-byte prefix that serves as an identifier for any data related to the MetaNet protocol, and the attributes contain index, permission, and encoding information about the content. This can include, but is not limited to, data type, encryption, and / or compression scheme. Such attributes are commonly also referred to as metadata. To avoid confusion with transaction metadata, this term will be avoided in this document.

[0087] The following techniques can be used to embed this data into the blockchain script:

[0088] 1. OP_RETURN - In this method, all data (attributes and content) is placed after OP_RETURN in the locking script of a provably non-spendable transaction output.

[0089] An example of an output script using this operator is as follows:

[0090] UTXO0:OP_RETURN<Metanet Flag> <attributes> <content>

[0091] 2. OP_RETURN with OP_DROP - In this case, OP_RETURN contains attributes, and the content is stored in the spendable transaction script (lock or unlock) before OP_DROP. The content can be split into multiple data packets in the transaction inputs and outputs. However, it is advantageous to insert the data into the transaction output because only the output script can be signed in the blockchain protocol. If the data is inserted into the transaction input, OP_MOD can be used as a checksum for the data instead of network node verification to ensure its validity. For example, a 32-bit OP_MOD operation can be performed and checked if it equals a pre-computed value.

[0092] In this case, the attributes can contain information on how to reconstruct the content data packets. Additionally, providing the hash of the reconstructed data packet H(content1 + content2) as an attribute enables verification that the recommended reconstruction scheme has been used.

[0093] Figure 1 A transaction implementing the second data insertion method is shown. For simplicity, the transaction only includes inserting the content in its output, which is signed by its single input. Using Figure 2 the method shown to use the OP_DROP statement can also insert the content into additional inputs.

[0094] If the content is large, it may be advantageous to split it over multiple transactions. Such an arrangement is shown in Figure 3 In Figure 3 A pair of blockchain transactions embodying the present invention is shown, in which the first data <content> to be stored on the blockchain is split into two chunks <content chunk1> and <content chunk2>, which can then be recombined into <content> = <content chunk1> ∥ <content chunk2>, where the operator "∥" concatenates the content data of the two chunks. This concatenation operator can be replaced by any desired bitwise or similar segmented binary operator. Then the two chunks <content chunk1> and <content chunk2> are stored in the corresponding spendable outputs of separate blockchain transactions, while the data related to the attributes of the content data is stored in the corresponding unspendable outputs of the blockchain transactions. Again, the attributes can contain information on the recombination scheme. For example, the content can be raw data, an executable program, or an HTML web page. Additionally, content1 can include a pointer to the location of content2 on the blockchain, which functions in the same way as an embedded HTML link within a web page.

[0095] Note that both transactions will take the same public key P (and ECDSA signature) as input, such that although <Chunk of content 1> and <Chunk of content 2> are stored in different transactions with TxID1 and TxID2 respectively, they can be related by the same public key P.

[0096] Function of Verifying Using Network Nodes

[0097] Here, the transaction verification process performed by network nodes is used to gain an advantage when storing this data. This is because all data in the transaction output will be signed by the owner of the public key P in at least one transaction input (if the SIGHASH|ALL flag is present), and this signature will be checked during the transaction verification process performed by all network nodes.

[0098] This ensures

[0099] · Data integrity - If the data is corrupted, the CHECKSIG operation will fail.

[0100] · Data authenticity - The owner of P has provably witnessed and signed the data.

[0101] This is especially beneficial for content split across multiple transactions, as the input signature of P provides a provable link between the split components of the data, as described by the arrangement shown in the reference above Figure 3 as described.

[0102] Rabin Signature

[0103] Another way to ensure data authenticity is to use Rabin signatures, which can be used to sign the data itself rather than the entire message. This can be beneficial because the signer does not need to sign each individual transaction in which the data appears, and the signature can be reused across multiple transactions.

[0104] Rabin signatures can be easily verified in a script. By inserting Rabin signature verification before the OP_DROP command, these can be incorporated into case (2) above, i.e.

[0105] <content1><Rabin Sig(content1)>FUNC_CHECKRABSIG OP_DROP<H(P1)>[CheckSigP1]

[0106] Note that this cannot be done in the case (1) above because, in any case, the script containing OP_RETURN fails and thus verification cannot be achieved.

[0107] Specific Example of Using Rabin Signature

[0108] Introduction

[0109] Digital signatures are a fundamental part of blockchain protocols. They ensure that any transaction recorded on the blockchain has been authorized by the legitimate holder of the tokens being sent. In standard blockchain transactions, the transaction message is signed using the Elliptic Curve Digital Signature Algorithm (ECDSA). However, ECDSA signatures are typically applied to the entire transaction.

[0110] There are some use cases for blockchains where participants from outside the network may want to provide signatures for arbitrary data types, which can then be used by network participants. By using Rabin digital signatures, any data segment can be signed - even if it originates outside the blockchain - and then placed in one or more transactions.

[0111] Now it will be shown how data can be directly signed and verified in a script by leveraging the algebraic structure of the Rabin cryptosystem.

[0112] Rabin Digital Signature

[0113] Rabin Digital Signature Algorithm

[0114] Background Mathematics

[0115] Definition - Integers mod p

[0116] The integers modulo p are defined as the following set

[0117]

[0118] Fermat's Little Theorem

[0119] Let p be a prime number. Then for any integer a, the following condition applies

[0120] a p-1 ≡ 1 mod p

[0121] Euler's Criterion

[0122] Let p be a prime number. Then r is a quadratic residue mod p if and only if the following equation is satisfied

[0123]

[0124] Modular square root (p = 3 mod 4)

[0125] Let p be a prime number such that p ≡ 3 mod 4. Then for any integer r satisfying Euler's criterion, if a is an integer, then such that

[0126] a 2 ≡ r mod p

[0127] Then, a has a solution in the form of the following formula

[0128]

[0129] Chinese Remainder Theorem

[0130] Given pairs of relatively prime positive integers n1, n2, …, n k and arbitrary integers a1, a2, …, a k , the system of simultaneous congruences

[0131]

[0132] has a unique solution modulo N = n1n2…n k . As a special case of the Chinese Remainder Theorem, it can be shown that

[0133] if and only if

[0134] x ≡ r mod n1·n2, then

[0135] x ≡ r mod n1 and x ≡ r mod n2 Rabin Digital Signature Algorithm

[0136] The Rabin digital signature algorithm can be described as follows:

[0137] For any message m, let H be a collision-resistant hash algorithm with k output bits.

[0138] To generate the key, select prime numbers p and q, each with a bit length approximately k / 2, such that p ≡ 3 mod 4, q ≡ 3 mod 4 and calculate the product n = p·q. The private key is (p, q), and the public key is n = p·q.

[0139] To sign the message m, the signer selects padding U such that H(m||U) satisfies

[0140]

[0141] The signature S is calculated using the following formula

[0142]

[0143] The signature of message m is the pair (S, U). Verification can be simply performed by checking, for a given m, U, and S, the following formula

[0144] H(m||U) ≡ S 2 mod n (Equation 1).

[0145] This is true if and only if there exists an integer λ in the range 0,…, n - 1 such that

[0146] H(m||U) + λ·n = S 2 (Equation 2).

[0147] The factor λ can be safely included in the signature to provide the combination (S, λ, U).

[0148] The advantageous features of the Rabin signature scheme are as follows:

[0149] a) Signature generation is computationally expensive, while signature verification is computationally easy.

[0150] b) The security of the signature depends only on the difficulty of integer factorization. Thus, the Rabin signature is inherently unforgeable (unlike RSA).

[0151] c) The hash function value H(m||U) must have a size similar to the public key n.

[0152] Verification in the script is straightforward because it only requires squaring the given signature, performing modular reduction, and then checking whether the result is equal to H(m||U).

[0153] Proof of Rabin Signature

[0154] Let p, q be relatively prime, and n = p·q. By the Chinese Remainder Theorem, it can be shown that

[0155] if and only if

[0156] S 2 ≡ H(m||U) mod p

[0157] S 2 ≡ H(m||U) mod q, then

[0158] then

[0159] S 2 ≡ H(m||U) mod n

[0160] Using the following equation

[0161]

[0162] It can be shown that:

[0163] S 2 ≡ H(m||U) mod q

[0164] Therefore

[0165]

[0166] wherein, it has been assumed that H(m||U) satisfies the Euler's criterion. By similar calculations, it can also be shown that:

[0167] S 2 ≡ H(m||U) mod p.

[0168] Rabin Signature in Blockchain

[0169] Signature Verification in Script

[0170] A small number of arithmetic and stack manipulation opcodes are required to verify a Rabin signature. Consider a redemption script of the following form

[0171] OP_DUP OP_HASH160 <H 160 (n)> OP_EQUALVERIFY OP_MUL OP_SWAP OP_2OP_ROLL OP_CAT FUNC_HASH3072 OP_ADD OP_SWAP OP_DUP OP_MUL OP_EQUAL

[0172] where n is the public key of the signer. This will evaluate to true if and only if the following inputs are available

[0173] <s> <m><λ> <n>

[0174] where m is any message and (S, λ, U) is a valid Rabin signature. Alternatively, if the Rabin signature is checked using Equation 1 above, the redemption script is given by:

[0175] OP_DUP OP_HASH160<H 160 (n)>OP_DUP OP_TOALTSTACK OP_SWAP<roll index>OP_ROLL OP_CAT FUNC_HASH3072 OP_SWAP OP_MOD OP_SWAP OP_DUP OP_MUL OP_FROMALTSTACK OP_MOD OP_EQUAL

[0176] In this case, this will evaluate to true if and only if the following inputs are present

[0177] S> <m> <n>

[0178] In both of these exchange scripts, the 3072-bit hash projection function "FUNC_HASH3072" is used. For a given message / padding concatenation, the following script is used to generate the FUNC_HASH3072 hash projection:

[0179] OP_SHA256{OP_2OP_SPLIT OP_SWAP OP_SHA256 OP_SWAP}(x11)

[0180] OP_SHA256 OP_SWAP OP_SHA256{OP_CAT}(x11)

[0181] Data Compression

[0182] Internet data consists of JavaScript and common file types (e.g., text files (SML, HTML, etc.), video files (MPEG, M-JPEG, etc.), image files (GIF, JPEG, etc.), and audio files (AU, WAV, etc.)), as described in more detail, for example, at the following link: https: / / www.doc.ic.ac.uk / ~nd / surprise_97 / journal / vol1 / mmp / #text Using the above data insertion techniques, these different data types can also be embedded on the blockchain.

[0183] Before embedding a larger file size on the blockchain, it can be compressed using one of several existing coding schemes. Lossless data compression algorithms such as run-length and Huffman coding can be used for several applications, including ZIP files, executable programs, text documents, and source code.

[0184] Depending on the specific input data, there are many different algorithms. Apple Lossless and Adaptive Transform Acoustic Coding can be used to compress audio files, PNG and TIFF for graphic files, and movie files can be compressed using one of many lossless video codecs. Flags within the attributes can be used to indicate any compression of the data content. For example, the flag for the LZW lossless coding scheme in the attribute would be <lzw>。

[0185] Decryption of Encryption and Payment

[0186] Data Encryption

[0187] The owner of the content can choose to protect the content before embedding it on the blockchain. This ensures that the content cannot be viewed without obtaining the necessary permission.

[0188] There are many well - recognized techniques for encrypting data (plaintext or other data types). These techniques can be classified as asymmetric encryption or symmetric encryption.

[0189] Elliptic Curve Cryptography (ECC) is asymmetric because it relies on a public - key / private - key pair. It is one of the most secure cryptographic systems. For ECC cryptography, the Koblitz algorithm can be used to encrypt data.

[0190] In a symmetric scheme, a single key is used to both encrypt and decrypt data. The Advanced Encryption Standard (AES) algorithm is considered one of the most secure symmetric algorithms seeded by such a secret, as described in more detail, for example, in Chapter 4 of C. Paar and J. Pelzl, "Understanding Cryptography", Springer - Verlag Berlin Heidelberg, 2nd Edition, 2010, pp. 87 - 118.

[0191] When encrypting data stored on the blockchain, there are advantages to using the same cryptographic system as the underlying blockchain. These advantages are:

[0192] - The security level of the encryption is the same as the underlying system on which the data is stored.

[0193] - The software architecture required to store encrypted data will have a smaller codebase.

[0194] - Key management in the wallet can be used for both transactions and encryption / decryption.

[0195] - Since the same key can be used for encryption and payment, it is more efficient and thus fewer keys are required. This also reduces storage space.

[0196] - The ability to exchange / purchase decrypted data may require fewer communication channels.

[0197] - Since the keys used for encryption and transactions are the same data structure, security is improved and thus targeted attacks on specific key types are mitigated.

[0198] For illustrative purposes, describe how the Koblitz algorithm can be used to encrypt data using ECC.

[0199] Koblitz Algorithm

[0200] Given an ECC key pair P1 = S1·G, the Koblitz algorithm allows anyone to use the public key P1 to encrypt a message such that only the person who knows the corresponding private key S1 can decrypt the message.

[0201] Suppose it is desired to encrypt the plaintext message 'hello world' using the Koblitz method. This is done character by character. Encrypt and decrypt the first character 'h' as follows.

[0202] 1. The character 'h' is mapped to a point on the secp256k1 curve. This can be achieved by mapping the plaintext character to an 8-bit number using the ASCII convention. Then, the point on the curve is calculated by multiplying the base point G by that number. In this example, 'h' maps to 104 in ASCII, and the elliptic curve point is given by P m = 104·G.

[0203] 2. Then, the public key P1 is used to encrypt the point P m This is done by choosing a random temporary key k0 and calculating the point pair C m = {k0·G, Q} (where Q := P m + k0·P1), and then this point pair can be broadcast.

[0204] 3. The owner of the private key S1 can decrypt the original point by calculating P m = Q - S1·k0·G. Then, they can recover the original ASCII number by trial and error or with the help of a lookup table to establish which number x corresponds to P m = x·G.

[0205] Using Blockchain to Purchase Licenses

[0206] Storing data on the blockchain has the obvious advantage of having a payment mechanism built into the system. Payments can be used to purchase

[0207] - decrypting data for viewing / use

[0208] - permission to insert data at a specific address

[0209] In both cases, the buyer uses tokens to purchase the secret that grants them permission to do something. The secret can be a hash preimage or a private key.

[0210] An efficient and secure way to make such a purchase is to use an atomic swap. This keeps the secure communication channel minimal and ensures that payment is made to the seller and the secret is revealed to the buyer, or that nothing happens.

[0211] It is also convenient to purchase a license using an access token. This is a secret value (usually a hash preimage) that the buyer has and can use to make a purchase. The buyer can purchase a large number of such access tokens in advance and then activate them when they actually want to use the license.

[0212] Now reference will be made to Figure 4 and Figure 5 to describe how to perform an atomic swap.

[0213] Atomic Swap Using Hash Puzzle or Private Key Puzzle

[0214] Suppose Alice is the owner of the secret. The secret can be a hash preimage of a known hash digest or a private key of a known public key. Suppose Bob wants to use a token to buy the secret from Alice. Describe a mechanism called an atomic swap that enables this transaction to occur. This is atomic in the sense that either Alice receives a token for payment and reveals the secret to Bob, or nothing happens.

[0215] The method is as follows:

[0216] Alice has a public key / private key pair P A = S A ·G's private key S A , and Bob has a public key / private key pair P B = S B ·G's private key S B .

[0217] Alice has a secret that is either the preimage X of a known hash digest H(X) or the private key S1 of a known public key P1 = S1·G.

[0218] They agree that Alice will sell the secret to Bob at the token price.

[0219] Before that, Bob must set up the transaction to send a temporary key k0 to Alice outside the block so that Alice can calculate the component r0 of the digital signature.

[0220] Now refer to Figure 4 ,

[0221] 1. Bob transfers the token locked by the following redemption script R (written schematically) to Alice:

[0222] For the hash preimage:

[0223] R = [Hash Puzzle H(X)][CheckSig P A

[0224] This forces the preimage X to be exposed in the input of the redemption script.

[0225] For the private key:

[0226] R = [Private Key PuzzleP1, r0][CheckSig P A

[0227] This forces the private key S1 to be computable from the input of the redemption script. In this case, Bob and Alice must agree on a temporary key k0 used to construct r0, where (r0, R y ) = k0·G.

[0228] 2. Since Alice knows her secret (X or S1), she can spend her funds on the blockchain with the help of Figure 5 the transaction shown. This allows Bob to determine her secret.

[0229] As an optional security feature, Alice and Bob can use their public keys P A , P B to establish a shared secret S known only to the two of them. This can be achieved in the manner outlined in International Patent Publication No. WO 2017 / 145016. In this case, S can be added to the preimage X in the hash puzzle so as not to publicly disclose X on the blockchain. Similarly, in the private key puzzle, S can be used as the temporary key k0 to ensure that only Alice or Bob can compute the private key.

[0230] If Alice decides not to spend her funds, a time-locked refund can be introduced into the program to prevent Bob's funds from being locked by Alice.

[0231] Purchase Using Tokens

[0232] Assume the same situation as described above, but Bob wishes to redeem a pre-purchased access token in exchange for a secret.

[0233] The procedure that Alice and Bob must follow is similar to the situation described in the previous section, but uses a sequence of similar atomic swaps. The process has two phases; token issuance and token redemption.

[0234] Phase 1: Token Issuance

[0235] The token issuance phase is actually Bob's single purchase of a token. For example, consider the following scenario: Alice has 10 different secrets X1, X2, …, X 10 ​​, and Bob wishes to purchase 10 tokens T1, T2, …, T that each grant him access to a corresponding secret in a single purchase 10 .

[0236] First, Bob generates a set of 10 tokens from a secret seed value known only to him. These tokens are created by hashing the sequence of the seed to form a hash chain, where each token is computed as:

[0237] T i = H 10-i (Y) for i ∈ {1, 2, …, 10}.

[0238] Alice and Bob now each have 10 secret values that can be revealed in a hash puzzle for, e.g., redeeming tokens. However, to publish these tokens, they must also generate secret initialisation values I Alice and I Bob . These values are given as follows:

[0239]

[0240] I Bob = H 10 (Y).

[0241] It should be noted that Alice's initialiser is simply a random integer with no specific meaning, but Bob's initialiser should be the hash of his first token T1 = H 9 (Y). Extending the token chain to the initialisation value in this way allows token publication to also define the tokens to be used for subsequent redemption later. Figure 6 All the secret values held by each participant are shown in

[0242] Now Alice and Bob can agree to purchase 10 tokens at a price of 10 units. The purchase of these tokens can be made in various ways, and here atomic swap is used for illustration. The atomic swap starts by Alice and Bob broadcasting the transactions shown in Figure 7 and Figure 8 respectively, where the outputs in both transactions require the solutions of two hash puzzles and valid signatures.

[0243] Once the two transactions appear in the blockchain, Alice and Bob can share their shared initialisation values I Alice and I Bob , and complete the atomic swap for token publication.

[0244] Due to this atomic swap, Alice receives the payment for purchasing 10 tokens and the two initialisation value secrets are revealed. It should be noted that here only Bob's secret I Bob = H 10 (Y) is meaningful because it will define the first hash puzzle [Hash Puzzle (T1)] to be solved, and its solution is the initial value H 10 The preimage H of (Y) 9 (Y).

[0245] Phase 2: Token Exchange

[0246] At some future point, Bob wants to exchange his first token T1 = H 9 (Y) and receive his first secret X1, but as mentioned earlier he has already paid for this secret by purchasing a valid token. The process of exchanging the token will take the form of another atomic swap, where the solution to the locked hash puzzle is the token T i and the corresponding secret X i .

[0247] To exchange his token, Bob should broadcast the transaction shown in Figure 9 , the output of which is locked by two hash puzzles. When Alice sees this transaction, she broadcasts her own similar transaction as shown in Figure 10 , the output of which is locked by the same two hash puzzles. The two participants can now exchange their secrets T1 and X1 and unlock the outputs of these transactions. The two parties can now exchange the nominal fee x by providing the correct unlocking scripts that also expose the two secrets. Figure 11 and Figure 12 show the transactions with these unlocking scripts.

[0248] The completion of this atomic swap for token exchange reveals Alice's first secret X1 to Bob, reveals Bob's first token T1 to Alice, and, given that the amount x is large enough to encourage both parties to spend the locked output, results in a net-zero exchange of funds. Crucially, this also establishes that the next token Bob can use must be the solution T2 of the hash puzzle [Hash Puzzle H(T2)], where the target hash H(T2) = T1 has just been revealed to Alice. This process can be recursively repeated until Bob has used his last token T 10 = Y.

[0249] Naming and Addressing

[0250] Node and Edge Structure

[0251] It has been explained above how data can be inserted into the blockchain by providing data within a transaction. Now a protocol for structuring these transactions in a logical manner is presented, which allows for node addressing, permissioning, and content version control. The structure of this distributed peer-to-peer network is similar to the existing Internet.

[0252] It should be noted that this is a "tier-2" protocol that does not modify the protocol or consensus rules of the underlying blockchain.

[0253] The goals of the structure described here are:

[0254] (i) Associating related content from different transactions to enable search, identification and access to data

[0255] (ii) Allow human-readable keyword searches to identify content to improve search speed, accuracy, and efficiency

[0256] (iii) Building and simulating server-like structures in blockchain

[0257] Our approach is to structure the data associated with the meta-network as a directed graph. The nodes and edges of this graph correspond to:

[0258] Node - Transactions associated with the Metanet Protocol. Nodes store content. (The terms "content" and "data" are used interchangeably in this document).

[0259] The node is included by<Metanet Flag> Each node is assigned a public key P node The combination of the public key and the transaction ID uniquely specifies the index ID of the node. node :=H(P node ||TxID node ).

[0260] The hash function used should be consistent with the underlying blockchain protocol that the present invention will use with SHA-256 or RIPEMD-160.

[0261] Edge - the association of a child node with a parent node.

[0262] Edge in Signature Sig P parent It is created when it appears in the input of a MetaNet transaction, so only the parent can give permission to create an edge. All nodes can have at most one parent, and a parent node can have any number of children. In the language of graph theory, the indegree of each node is at most 1, and the outdegree of each node is arbitrary.

[0263] It should be noted that edges are aspects of the metanet protocol and are not themselves transactions associated with the underlying blockchain.

[0264] A valid metanet node (with a parent) is given by a transaction of the following form:

[0265]

[0266] The transaction contains all the information required to specify the indices of the following nodes and their parents:

[0267] ID node = H(P node || TxID node ),

[0268] ID parent = H(P parent || TxID parent ).

[0269] In addition, since the signature of the parent node is required, only the parent can create the edge to the child. If the <TxID parent > field does not exist or it does not point to a valid meta-network transaction, the node is an orphan. There is no higher-level node that can reach it.

[0270] Additional attributes can be added to each node. These attributes can include flags, names, and keywords. These attributes are discussed later in this document.

[0271] As shown, the index of a node (transaction) can be divided into

[0272] a) public key P node , which we interpret as the address of the node

[0273] b) transaction ID TxID node , which we interpret as the version of the node

[0274] This structuring results in two advantageous features:

[0275] 1. Version control - If there are two nodes with the same public key, we interpret the node with the transaction ID that has the maximum proof of work as the latest version of the node. If the nodes are in different blocks, this can be checked by the block height. For transactions in the same block, this is determined by the topological transaction ordering rule (TTOR).

[0276] 2. Permission - A child of a node can be created only if the owner of the public key P node signs the transaction input when creating the child node. Thus, P node represents not only the address of the node but also the permission to create a child node. This is deliberately similar to a standard blockchain transaction - the public key is not only an address but also the permission associated with that address.

[0277] It should be noted that since the parent node's signature appears in the UXTO unlocking script, it is verified through the standard network node verification process when the network accepts the transaction. This means that the permission to create the child node is verified by the blockchain network itself.

[0278] It is worth noting that a standard Internet Protocol (IP) address is unique only within a network at a certain point in time. On the other hand, the index of a node in a metanet is unique at all times, and there is no concept of separate networks, which allows data to be permanently anchored to a single object ID. node .

[0279] The node and edge structure allows the meta-network to be visualized as a graph, e.g. Figure 13 shown.

[0280] Domain, Naming and Location Content in Meta-Network

[0281] The hierarchical structure of the metanet graph allows for a rich domain-like structure to emerge. We interpret orphan nodes as top-level domains (TLDs), children of orphan nodes as subdomains, grandchildren as sub-subdomains, etc., and childless nodes as end-points. Figure 13 .

[0282] Domain name is interpreted as ID node Each top-level domain in the metanet can be viewed as a tree, where the root is an orphan node and the leaves are childless nodes. The metanet itself is a global collection of trees that form a graph.

[0283] The MetaNet protocol does not specify that any node contains content data, but leaf (childless) nodes represent the end of a directed path on the data tree and will therefore typically be used to store content data. However, content can be stored at any node in the tree. Protocol-specific flags included as attributes in the node can be used to specify the role of a node in the data tree (disk space, folder, file, or permission change).

[0284] As mentioned earlier, the Internet uses the Domain Name System (DNS) to associate human-readable names to Internet Protocol (IP) addresses. DNS is decentralized in a sense, although in practice it is controlled by a small number of key players (e.g., governments and large companies). Depending on your DNS provider, the same name can take you to different addresses. This problem is inherent in mapping short human-readable names to computer-generated numbers.

[0285] We assume that there is a decentralized index ID that maps human-readable top-level domains to root nodes root In other words, there is a 1-1 function κ that maps human-readable names to metanet root node indices, such as:

[0286] κ('bobsblog') = ID bobsblog (= H(P bobsblog ||TxID bobsblog ))

[0287] The input on the left is a human-readable word, while the output on the right is a hash digest, which will typically be a 256-bit data structure. Note that P bobsblog and TxID bobsblog are not usually human-readable either. In the standard IP protocol, this would be a mapping of the IP address from www.bobsblog.com to the corresponding domain within the network.

[0288] The mapping κ should be interpreted as a measure to ensure backward compatibility between the metanet and the Internet when replicating the human readability of DNS-published domain names, but the naming and addressing scheme providing the structure of the metanet does not explicitly depend on this mapping.

[0289] Possible existing forms of the mapping function include the DNSLink system employed by the InterPlanetary File System (IPFS) or the OpenNIC service (https: / / www.openic.org). This mapping can be stored as part of DNS in an existing TXT record. This is similar to DNSLink in IPFS, see https: / / docs.ipfs.io / guides / concepts / dnslink / . However, generally speaking, these sacrifice some elements of decentralization in order to provide a 1-1 mapping, see https: / / hackernoon.com / ten-terrible-attempts-to-make-the-inter-planetary- file-system-human-friendly-e4e95df0c6fa

[0290] Vanity Address

[0291] The public key used as the address of a metanet node is not a human-readable object. This can make the search, reference, and input activities of human users error-prone and slow. However, a human-recognizable public key address - a vanity address P vanity - can be created, which includes a plaintext prefix that can be directly interpreted by the user. Vanity addresses are known in the prior art.

[0292] The difficulty of creating such an address depends on the character length of the required prefix. This means that human-recognizable vanity addresses can be used as node addresses that depend only on the creation effort of the owner rather than central publication. For a given prefix, there are many different vanity addresses due to the remaining characters in the suffix, so many node addresses can share a common prefix while still remaining unique.

[0293] Examples of vanity addresses with the required prefix are:

[0294] P bobsblog :bobsblogHtKNngkdXEeobR76b53LETtpyT

[0295] Prefix: bobsblog

[0296] Suffix: HtKNngkdXEeobR76b53LETtpyT

[0297] The above vanity address can be used to sense-check the mapping from the name 'bobsblog' to the node index ID bobsblog and assist the metanet nodes through the searchability of the address. It should be noted that the prefix is not unique here, but the entire address itself is a unique entity.

[0298] The selected address P vanity in combination with the TxID forms an ID node whose combination is also beneficial because it means that there is no central publisher of domain names (TxIDs are generated by decentralized proof-of-work), and the names are recoverable from the blockchain itself. Advantageously, there are no longer points of failure that exist within the Internet DNS.

[0299] Since the metanet domain already provides a permissioning system (public key), there is no need to publish credentials to prove ownership. It has been explored, for example, in Namecoin ( https: / / namecoin.org / ) to use the blockchain for this purpose. However, according to the present invention, there is no need to use a separate blockchain for this function because everything can be achieved within one blockchain.

[0300] Compared to the prior art, this significantly reduces the amount of resources (hardware, processing resources, and energy) required by the present invention. In terms of the arrangement of device and system components, it also provides a completely different architecture.

[0301] The advantage of this naming system is that users can identify the top-level domains in the metanet by memorable words (e.g., company names) rather than hash digests. This also makes searching for domains faster because searching by keywords is faster than by hash digests. This also reduces input errors, thus providing an improved search tool for the data stored in the blockchain.

[0302] Given the mapping from domain names to node indices, we can establish a resource locator similar to the Internet's Uniform Resource Locator (URL). We call this the metanet URL (MURL), and it has the following form

[0303] MURL ='mnp:' + ′ / / domain name ′+′ / path′ + ′ / file′.

[0304] Each component of a URL - protocol, domain name, path, and file - has been mapped to the structure of an MURL, making the object more user - intuitive and enabling its integration with the existing structure of the Internet.

[0305] This assumes that each node has a name associated with its public key (address), which is unique at its level within the domain tree. This name is always the right - most component of the MURL for a given node. If two nodes at the same level in the tree have the same name, they will have the same public key and thus the latest version is taken.

[0306] The following table gives the analogy between the Meta - Web protocol and Internet protocols:

[0307]

[0308] Table: Summary of the analogy between Internet protocols and Meta - Web protocols

[0309] Search Meta-Network

[0310] We have defined the Meta - Web graph structure of the exemplary embodiments such that each node has a unique index and can have a name assigned to it. This allows content to be located using MURLs. To also implement a fast search function, we allow additional keywords to be assigned to nodes.

[0311] The fixed attributes of a node are the index and the index of the parent node, and the optional attributes are the name and keywords.

[0312] Node attributes

[0313]

[0314] In one example, a utility method for searching the Meta - Web could be to first trawl through the blockchain using a block detector and identify all transactions via Meta - Web flags, check if they are valid Meta - Web nodes, and if so, record their indices and keywords in a database or other storage resource. The database can then be used to efficiently search for nodes by the desired keywords. Once the index of a node is found by the desired keyword, its content can be extracted from the block detector and viewed.

[0315] For example, consider Figure 14 branch P1, where the nodes corresponding to public keys P0, P1, and P 1,1 represent the home page, a topic page, and a sub - topic page respectively. These nodes are given the names ‘bobsblog’, ‘summer’, and ‘caribbean’, and their attributes are as follows:

[0316] Home page node P0

[0317]

[0318] Sub - topic page node P 1,1

[0319]

[0320]

[0321] In this example, leaf nodes P 1,1,1 , P 1,1,2 and P 1,1,3 are given the names 'beaches', 'nightlife' and 'food' respectively and are used to store individual blog posts. The complete domain structure is shown in the diagram overleaf, including the MURL search paths associated with each node in the tree.

[0322] We should note that the meta - web can also be incorporated into a content - addressable network (CAN) by storing the hash of the content stored by node transactions as an additional attribute. This means that meta - web nodes can also be indexed and searched by content hash.

[0323] The naming and addressing methods described above offer numerous technical advantages over the prior art, including:

[0324] 1. Public - key addresses - The system uses the same public - key - private - key pairs as the blockchain to assign node addresses. This means that the same set of keys is used for both the management of funds and the permissioning of content data. This provides an efficient and secure solution.

[0325] 2. Decentralized domains - The publication of domain names is fully decentralized by including TxIDs that can only be generated by proof - of - work node and can also incorporate human - recognizable public keys P vanity (vanity addresses) that achieve a fair distribution of the required domain public keys. Again, this solution provides enhanced efficiency and security.

[0326] 3. Graph structure - The naming and addressing architecture specifies a graph that can be constructed from a subset of the blockchain data including meta - web nodes. This design uses an ordered structure to map the complexity of the Internet onto the blockchain, such that the blockchain fully replicates its functionality and scalability while maintaining security.

[0327] Browser Wallet Application

[0328] As previously described, in the Metaweb protocol, all data exists directly on the blockchain itself. In this section, we provide examples of illustrative computer applications that can effectively access, display, and interact with Metaweb data stored on the blockchain, which will be referred to herein for convenience simply as a "browser wallet".

[0329] We will first discuss how the browser wallet interacts with the core components and functionality of the distributed peer-to-peer Internet interface, and then provide a more detailed description in the remainder of this section.

[0330] Overview

[0331] Components

[0332] The browser wallet is an application designed to allow end-users to interact with the Metaweb infrastructure on the blockchain. This application should allow for exploratory searches of the Metaweb graph to find specific content embedded within the tree. Additionally, the browser wallet will handle the retrieval, decryption, recombination, and caching (optional) of content.

[0333] The browser wallet will include the following core elements combined into a single computer application.

[0334] Blockchain Search Engine - Supports third-party search engines to query Metaweb nodes through various indexes (including ID node , node name, keyword, block height, and TxID).

[0335] Display Window - Software that unpacks the content returned by the full copy of the blockchain peer to the browser. This covers the decryption, recombination, caching, and redemption of access tokens.

[0336] Access Key / Token Wallet - Dedicated key management for access keys or tokens used for purchases. The key or token can be hidden from the user to allow for expiration at a later time. This can be achieved by using a trusted execution environment. Timed access can be guaranteed by synchronizing with the blockchain and querying the current block height.

[0337] Blockchain Search Engine

[0338] Search Engine – Prior Art

[0339] Search engines (SEs) known in the prior art rely on powerful web crawlers to locate, index, and rate web content based on user queries. (The same basic principle can be extended to third-party blockchain SEs that crawl the Metaweb).

[0340] The SE searches for relevant HTML meta - tags and content by keywords in the query. Subsequently, it indexes the crawling results, where any embedded images / videos / media files are analyzed and cataloged. Then, considering the user's location, language, and device, it programmatically rates the most relevant results in the index.

[0341] A typical SE should have the following functionality:

[0342] 1. Crawling - Identify Internet data and crawl it using relevant metadata such as domain names, linked pages, and relevant keywords. Discover new Internet content through existing content and also crawl for any relevant information.

[0343] 2. Indexing - Analyze and catalog content data. This information is stored in a database.

[0344] 3. Serving and rating - Rate the content index in order of relevance to the user's query.

[0345] Block explorer

[0346] The blockchain analogue closest to an Internet search engine (SE) is the blockchain explorer, which is sometimes referred to as a 'block explorer' or 'blockchain browser'. A blockchain explorer is a web application that enables user - friendly queries on the blockchain at a high level and functions similarly to a web browser, but connects to the blockchain instead of the Internet.

[0347] In most cases, these explorers allow blocks (indexed by the hash of the block header), transactions (indexed by TxID), addresses, and unspent transaction outputs (UTXOs) to be input and searched for. Many explorers also provide their own application programming interfaces (APIs) for retrieving raw transaction and block data. See https: / / blockexplorer.com / api-ref .

[0348] Block explorers, while varying in capabilities, are generally useful for cataloging transactions in a user - friendly extractable form and displaying their basic information - for example, the monetary value of the transaction, coin confirmations and history, and addresses. Many explorers also allow viewing of the individual inputs and locking scripts of a transaction, although there is an inconsistency between these explorers and how more advanced sites (e.g., Blockchair https: / / blockchair.com / ) choose to present this information.

[0349] Recently, there have been many extensions to the basic blockchain explorers for running web applications based on blockchain data. These applications (e.g., Memo.cash https: / / memo.cash / protocol and Matter https: / / www.mttr.app / Home )Cataloging and organizing blockchain transactions containing specific protocol identifiers like a block explorer, and displaying the data encoded within those specific transactions.

[0350] However, there are two important problems with using a blockchain explorer, and embodiments of the present invention solve these problems:

[0351] 1. Generalizability - There is currently no industry standard for browsing content data stored in transactions. Content data refers to any data that does not pertain to the protocols used to create and secure the underlying blockchain.

[0352] 2. Keyword search - The content data stored in transactions needs to be retrievable by human-readable keywords. This is generally not a function of current block explorers, as current block explorers are used to query the protocol-based nature of transactions (e.g., block height, TxID, and address), rather than using keywords as search inputs. (However, some explorers like Blockchair can search for words if they are directly included in the transaction's script).

[0353] Importantly, as described above, the powerful naming and addressing structure of the present invention facilitates and enables the construction of a blockchain explorer that is more complex than those known in the art.

[0354] Proposed Meta-Network Search Engine

[0355] The browser wallet application communicates with a third-party search engine to discover node identities (ID node ). It is contemplated that this third party can provide a powerful and versatile service that replicates the capabilities of existing Internet search engines.

[0356] The MetaNet search engine third party maintains a database of all MetaNet transactions mined into the blockchain that can be identified by MetaNet protocol flags. This database can catalog all MetaNet nodes through a range index including ID node , node name, keyword, TxID, and block height.

[0357] There already exist services such as BitDB https: / / bitdb.network / that continuously synchronize with the blockchain and maintain transaction data in a standard database format. The browser wallet transfers the responsibility of crawling, indexing, serving, and rating MetaNet transactions to this third party and connects to its service when locating content stored on the MetaNet graph.

[0358] Efficiency can be saved by having a database dedicated only to metanet data. Different from Bit DB, this database will not store data associated with all transactions, but only store those data containing metanet flags. Some databases such as non-relational databases like MongoDB may be more efficient in storing the graph structure of the metanet. This will allow for faster queries, lower storage space, and more efficient association of relevant content within the metanet domain.

[0359] Figure 15 Illustrates how the browser wallet interacts with a third-party search engine when a user searches for content within the metanet infrastructure. Importantly, it should be noted that, in contrast to the Internet, there is no need for routing, so the present invention provides important advantages in terms of efficiency, speed, processing, and required resources.

[0360] The process is as follows:

[0361] 1. The end user enters a keyword in the search bar of the browser wallet.

[0362] 2. The browser wallet sends the keyword query to the third-party SE.

[0363] 3. The SE checks the keyword against its database and returns the IDs of any metanet nodes containing relevant content node . The third party can also return other indexes on each node to the user and provide suggestions for relevant content.

[0364] 4. The browser wallet uses the node identifier and the domain name associated with it to construct an MURL.

[0365] 5. The browser wallet requests the content belonging to the specified node from any network peer having a full copy of the blockchain.

[0366] 6. The network peer provides the requested content to the browser wallet. Since the peer has a copy of the blockchain, it must also have a copy of the content, so only one request is made and the request is never forwarded to other network peers.

[0367] It should be emphasized that the third-party SE is only responsible for indexing and maintaining the property records of the metanet nodes, while the original content data stored on the nodes is stored by network peers (e.g., full-copy peers, archives) having a full copy of the blockchain.

[0368] Content Display - Meta-Network Browser

[0369] The browser wallet application emulates the same front-end capabilities that any typical web browser should provide. These functions include but are not limited to:

[0370] 1. Search - Provide access to a search engine (SE) to locate content.

[0371] 2. Retrieval - Communicate with the server to facilitate the transfer of content using a known protocol (e.g., Hypertext Transfer Protocol (HTTP)).

[0372] 3. Interpretation - Parse the original code (e.g., in JavaScript) and execute it.

[0373] 4. Rendering - Efficiently display the parsed content for the end - user to view.

[0374] 5. User Interface (UI) - Provide an intuitive interface for the user to interact with the content, including action buttons and mechanisms for user input.

[0375] 6. Storage - Local temporary storage capacity for caching Internet content, cookies, etc., to improve repeated access to content.

[0376] In certain embodiments, the software component of the browser wallet application that acts as a web browser is capable of performing the above - mentioned functions on the meta - web content embedded in the blockchain, which is searchable (using SE) and retrievable (from peers) using its attributes.

[0377] Reorganization, Decompression and Decryption

[0378] According to certain embodiments of the present invention, the web browser software component of the browser wallet application is capable of handling all operations required to be performed on a given meta - web content. Generally speaking, there are many such operations to be performed, but we assume that at least the following operations are performed by the application using the meta - web protocol and infrastructure.

[0379] Re - assembly - In the case where the meta - web content needs to be split and inserted into multiple separate node transactions, the application will request the content from all relevant nodes and reconstruct the original content. The sorting and structure of the fragmented content can be encoded using additional flags in the attributes of each node.

[0380] De - compression - In the case where the content data is stored in compressed form on the blockchain, a flag indicating which standard compression scheme has been used should be included. The application will decompress the content according to this flag.

[0381] De - encryption - In the case where the content is encrypted, a flag should be used to indicate the encryption scheme. The application will locate the key from its decryption key wallet (discussed below) and decrypt the content data for use according to the encryption scheme used.

[0382] When performing these operations on content data, flags can be used to indicate to the browser wallet that a given operation needs to be performed. This applies to any other operation, for which a suitable <operation_flag> can be included as part of the attributes of the node to which the operation is applied.

[0383] Cache

[0384] The caching of local files and cookies is a common and important feature of typical web browsers. The browser wallet application also uses local storage in a similar way to optionally save records of the IDs of the content of interest node and other node attributes. This allows for more efficient lookup and retrieval of content from frequently accessed metaweb nodes.

[0385] The metaweb addresses the inherent problem of caching Internet data, which is variable and can be changed or pruned by web browsing software according to the provider. When caching metaweb data, users can always easily verify that the data is in the same state as when it was originally included in the blockchain as an immutable record.

[0386] Hierarchical Deterministic Key Management

[0387] A deterministic key Dk is a private key initialized from a single "seed" key. The seed is a randomly generated number that acts as the master key. A hash function can be used to combine the seed with other data (e.g., an index number or "chain code") (see, HD Wallet - BIP - 32 / BIP - 44) to derive deterministic keys. These keys are related to each other and can be fully recovered from the seed key. If a user wishes to use an external wallet in combination with the metaweb browser wallet, this seed also allows for easy import / export of the wallet between different wallet implementations, thus giving additional freedom.

[0388] Hierarchical deterministic (HD) wallets are a well - known method for deriving deterministic keys. In an HD wallet, a parent key generates a series of child keys, which in turn generate a series of grandchild keys, and so on. This tree - like structure is a powerful mechanism for managing several keys.

[0389] In a preferred embodiment, the HD wallet can be incorporated into Figure 15 the metaweb architecture shown.

[0390] Advantages of using an HD wallet include:

[0391] 1. The structure can use different branches of child keys to express additional organizational meaning for different purposes. For example, a user can dedicate different branches (and their corresponding child keys) to different types of data.

[0392] 2. Security Users can create a series of public keys without the corresponding private key, enabling the HD wallet to have the function of only receiving capabilities and being suitable for use on insecure servers. Moreover, since less secrets need to be stored, the exposure risk is lower.

[0393] 3. Recovery If the key is lost / damaged, it can be recovered from the seed key.

[0394] Read and Write Meta-Network Transactions

[0395] The essential advantage of the MetaNet is that it uses the same data structure - blockchain - to record both payment and content data.

[0396] The native wallet built into the application can write transactions to the blockchain, which are more complex compared to typical Simplified Payment Verification (SPV) clients. The wallet allows users to directly write MetaNet node transactions from the application to the blockchain by selecting the content data to be embedded in the blockchain from their computer.

[0397] Since the browser wallet application has a user interface (UI), it allows the wallet component to create and broadcast transactions including content data that has been pre-constructed in the browser component or on the user's computer. It would be very difficult for a specially configured wallet that processes on its own to achieve this function.

[0398] Access Key / Token Wallet

[0399] As previously described, built into the MetaNet protocol is the ability to encrypt content using ECC key pairs or AES symmetric key pairs, as well as the ability to purchase the corresponding decryption keys or tokens. We refer to these keys or tokens as access keys or access tokens.

[0400] These keys / tokens grant users permission to view or edit content (single-use or multi-instance use). For this reason, it is beneficial to introduce a new wallet for storing and managing access keys and tokens.

[0401] The concept of timed access to MetaNet content can also be introduced by allowing access keys / tokens to be burned after a certain period of time. This can be achieved by requiring access keys / tokens to be stored in a Trusted Execution Environment (TEE) and not directly accessible to users.

[0402] Decryption keys and access tokens can be deterministically stored and managed to facilitate efficient processing and deployment. Decryption keys (e.g., ECC private keys) can be generated and recovered by subsequent addition to the master key, while access tokens can be reconstructed using a hash chain seeded by some initial tokens.

[0403] Block Height Permission

[0404] A time lock can be included in the scripting language to achieve block height permission. The op_code OP_CHECKLOCKTIMEVERIFY (CLTV) sets the block height at which a transaction output (UTXO) can be spent.

[0405] The advantages of block height permission are twofold:

[0406] 1. Version control - In the MetaNet protocol, the latest version of a node can be identified from the maximum block height of the node. Browser wallets can be set to display only the most recent version of a file by block height, thus achieving proof-of-work version control.

[0407] 2. Timed access - Browser wallet applications can periodically burn decryption keys purchased atomically by the user. This ensures that viewers can access content data only during the period for which they have made a payment. Cloning of the decryption key can be prevented by storing it in a trusted execution environment (TEE). Additionally, atomic swaps involve the purchase of a deterministic key Dk (for decrypting content data). Although this deterministic key is publicly visible, the TEE can be used to sign the combination of Dk and the securely enclaved private key.

[0408] A browser wallet can be arranged to synchronize with the current state of the blockchain so as to use the block height as its own time proxy, rather than relying on any external clock or third-party time announcements.

[0409] Bypass Network Server

[0410] The present invention allows for a new mechanism for browsers (clients) and web servers to communicate and exchange information via distributed peer-to-peer Internet communication bypassing the Domain Name System (DNS) servers and typical network routers. See http: / / www.theshulers.com / whitepapers / internet_whitepaper / The present invention provides a new network architecture including peers that maintain a full copy of the blockchain, from which content can be provided to browser wallet applications.

[0411] Local Full-Copy Peer

[0412] Consider a system of local peers in each geographical area (e.g., postal district, town, city). We assume that within this local area network, at least one peer maintains a full copy of the blockchain, which we refer to as the local full-copy peer (LFCP). For our purposes, the LFCP only needs to store blockchain transactions including the MetaNet flag, but is not limited to this.

[0413] All users by default send 'acquire' requests to the LFCP. Since the peer maintains a complete and up-to-date copy of the entire blockchain, all requests can be satisfied because any node ID queried will be available to the LFCP. It should be noted that if the SE is powerful enough and large enough to store the metanet content and perform the main functions of a typical SE, the metanet search engine can also act as an LFCP.

[0414] In the simplest case, each LFCP will have the same storage and disk space overhead because each will need to be able to store the entire blockchain (about 200GB when written). The difference between each LFCP is that the LFCP should expand its capabilities to respond to the requirements of local requests from metanet users. So, if by default every metanet user in the world queries their closest LFCP, each LCFP should strive to expand its operating capabilities to meet its local requirements. Populated areas such as cities will require LFCP operations that include many cluster servers, while sparsely populated areas such as small towns will require fewer LCFP operations.

[0415] It is important to note that the disk space requirements are universal, while the CPU requirements for each LFCP adapt to the local area network needs. This is an example of an adaptive network, for example, Freenet - see https: / / blockstack.org / papers / .

[0416] One advantage of such a system is that when retrieving content associated with a given ID node the user only needs to make a single (local) connection to their LFCP. The LFCP does not need to forward the request to other peers because it is guaranteed to be able to provide the required content itself.

[0417] The metanet offers many advantages over the Internet - for example, decentralization and removal of duplicates - similar to other peer-to-peer (P2P) file sharing services such as IPFS. However, the metanet improves these existing P2P models by ensuring immutability and, crucially, by removing the need to flood the network with requests for a given piece of content.

[0418] The metanet infrastructure is also robust to the failure of any one LFCP by employing a network of these peers. This means that if an LFCP is taken offline, the end user simply defaults to using their next closest LFCP. This can be made more efficient if the LCFPs communicate with each other to indicate at any given time which nearby peers are below or above capacity in terms of requests. This can allow users to send their requests to the most appropriate peer and establish a dynamic balance of request distribution among nearby LCFPs.

[0419] Global Full-Copy Peer

[0420] Now consider the scenario when the general disk space requirements become too large for smaller peers, which occurs as the meta-network part of the blockchain expands and grows with adoption.

[0421] In this case, the smaller LFCPs should use their disk space capacity to store meta-network node transactions based on a popularity system (there is existing technology for rating content by request volume and nature). This means that the LFCPs now trim both their CPUs (for request processing capabilities) and their storage allocations (for content serving capabilities) to adapt to their local geographical requirements in terms of both content volume and nature.

[0422] To address the fact that LFCPs can no longer store all meta-network transaction content, the concept of a Global Full-Copy Peer (GFCP) can be utilized. A GFCP is a full-copy peer with the following properties:

[0423] 1. The GFCP grows its disk space capacity to always maintain a full copy of the blockchain.

[0424] 2. The GFCP has considerable CPU resources such that, compared to LFCPs, it can handle significantly more requests. In case many LFCPs are compromised, the global full-copy peer should be able to handle a sudden increase in demand.

[0425] The GFCP has two main functions. First, it acts as a fail-safe for user requests for meta-network content when requests overflow from LFCPs. Second, the GFCP acts as an archival peer to store all meta-network content mined historically, which ensures that any meta-network node content can be accessed even if many LFCPs omit some content from their local storage provisions.

[0426] Global database (data bank)

[0427] The concept of the GFCP is powerful and illustrates how the overall architecture of the meta-network provides a solution to existing problems; creating a global database that covers everything.

[0428] Prior to this, it was not possible to securely construct a general and globally accessible database because a central authority was required to maintain the database. This central authority injected points of failure and trust into the system. Crucially, if we rely on one organization to store and maintain all Internet data, we need to trust that the organization operates correctly and legally without corrupting the information.

[0429] Through the meta-network infrastructure, the two issues of trust and centrality are effectively removed from the concept of a global data center. Now, a GFCP can be created because it is only relied upon to provide the disk space required for storage without verifying and authenticating the information to be stored.

[0430] With the meta-network, the process of verifying stored content is carried out by network nodes, so the general global database can be trusted because it cannot corrupt blockchain information. The GFCP does not need to be trusted and only needs to provide storage.

[0431] The fact that all GFCPs can store the same information that is always verifiable and provable for the blockchain itself means that the information can be replicated among many such GFCPs.

[0432] This means that the problem of having a single point of failure is also solved by having many global databases exist in parallel and provably store the same information.

[0433] Figure 16 A system with two LFCPs and one GFCP is shown, and how each peer can support another peer in a network that is robust to the corruption of individual peers is illustrated.

[0434] Aspects of the present invention that can be implemented in the above-described embodiments of the browser wallet application provide many distinguishing features and advantages over the prior art, including but not limited to:

[0435] 1. Deterministic keys - Hierarchical deterministic key management for both tokens and meta-network addresses is performed in the same wallet component of the application. This allows organizing keys by reducing their storage requirements and implementing multiple functions for key recovery.

[0436] 2. Payment mechanism - The application allows consumers to pay directly to merchants without pointing to another application or third-party payment service that would conventionally authenticate and provide trust. This allows for the purchase and delivery of digital content via the same blockchain platform.

[0437] 3. Bypassing network servers - The application facilitates bypassing of conventional network servers that would conventionally handle large amounts of traffic, requests, and routing. This is because the application only needs to request content from a single LFCP, which ensures that requests do not need to be forwarded to other LFCPs to serve users. This reduces the total traffic and the completion time for each request.

[0438] 4. Timed access - The application facilitates timed access to content by synchronizing with the blockchain and using the blockchain to enforce access permissions based on its current state. This removes the need for third-party services to monitor user privileges over time while protecting the rights of the original owner.

[0439] Use Case - Decentralized Application Store (Swapp Store)

[0440] The first use case (for illustrative purposes only) of the meta-network architecture presented here is for decentralized payment and distribution for an application (app).

[0441] Consider the following scenario: app developer Alice and consumer Bob wish to trade with each other. The trade will take the form of an atomic swap, in which a token is exchanged for a secret key that grants Bob access to the app data. The encrypted app data has been made public as part of a metanetwork node transaction.

[0442] The app being swapped at the atomic level is called a Swapp. A third-party platform (the Swapp Store) can be used to catalog and advertise apps that exist on the metanetwork, but the payment for and transfer of the access key to the user (e.g., Bob) does not need to involve any third party and can be done directly between the merchant and the consumer.

[0443] The following sections detail the process for buying and selling Swapps from when Alice creates the app to when Bob deploys it. Throughout the process, Alice and Bob will use their respective browser wallets to interact with the metanetwork.

[0444] Release

[0445] 1. Alice writes the app. The data that makes up the app is <app>The content represented. She also uses the secret key S k to encrypt it as <e(App)>.

[0446] 2. Alice creates a node transaction ID AliceApp to set up her first meta-network domain (tree). She generates 1AliceAppHtKNngkdXEeobR76b53LETtpy(P that will be used as the node address AliceApp ).

[0447] 3. Then, Alice creates the children of the first node to form a tree that corresponds to the meta-network library of her application. Alice's tree domain is shown in Figure 17 .

[0448] One of the leaf nodes on this tree corresponds to her application with index ID App <app>node. In this node, Alice inserts the encrypted application data <e(App)> into the input script (scriptSig) of the node. Using the secret key s k to encrypt the app data using the Koblitz method.

[0449] The node transaction is as follows.

[0450]

[0451] 4. Alice publicly broadcasts the ID AliceApp , P AliceApp and the domain name 'AliceApp'. This can be achieved via social media, internet websites, or by using a third-party meta website.

[0452] Purchase

[0453] 1. Bob wants to download a puzzle game and sees Alice's app listed on the meta website (Swapp Store) viewed on his browser wallet.

[0454] 2. Then, Bob uses the information from the website to communicate with Alice and sets up an atomic swap. The swap is designed such that Bob will pay Alice the agreed-upon price, and Alice will reveal the secret key s k , or neither of these events will occur.

[0455] 3. The atomic swap is completed, and Bob's browser wallet stores the secret key s k in its access key / token wallet.

[0456] Deployment

[0457] Bob now has the key s k that will allow him to decrypt the application data previously released by Alice. To download and deploy the app, Bob does the following.

[0458] 1. Bob uses the meta web search engine (SE) to find the MURL associated with the encrypted app data <e(App)>. He uses the keywords 'AliceApp' and 'App' as the input to the search bar in his browser wallet. The third-party SE parses the query and returns the following MURL:

[0459] mnp: / / aliceapp / games / puzzle / app

[0460] This locator corresponds to the unique meta web node ID App , which includes the encrypted app data in its input script.

[0461] 2. Bob's browser wallet receives the MURL and then sends a request to the nearest appropriate LFCP. This peer provides Bob with the requested data <e(App)>.

[0462] 3. The browser wallet processes the data according to the attributes of the ID App This includes using the secret key s k to decrypt the application data and process <app>。

[0463] 4. Bob will apply <app>Downloaded from his browser to his computer. Now, Bob can deploy the application locally without having to repurchase access rights.

[0464] Figure 18 Illustrates the entire process outlined in the above illustrative use case. The flowchart shows two action branches: Alice's branch (starting on the left) and Bob's branch (starting on the right). The branch corresponding to Alice shows the initial release phase and Bob's branch shows the phase of setting up the purchase via atomic swap.

[0465] On Bob's branch, he broadcasts the following transaction TxID Bob As the atomic swap setup phase:

[0466]

[0467] In this transaction, the output is locked by a private key puzzle that requires the secret decryption key s k To be revealed to Bob so that Alice can spend.

[0468] The branches of Alice and Bob in this figure converge at the point where Alice successfully completes the atomic swap transaction. This is achieved when Alice broadcasts the transaction TxID Alice When:

[0469]

[0470] Once this transaction is broadcast, the action branches of Alice and Bob diverge again. Alice receives payment of x tokens, while Bob receives the secret decryption key s k And is able to retrieve and decrypt Alice's application from the metanet.

[0471] Now turning to Figure 19 FIG. 2600 provides an illustrative simplified block diagram of a computing device 2600 that can be used to practice at least one embodiment of the present disclosure. In various embodiments, the computing device 2600 can be used to implement any of the systems shown and described above. For example, the computing device 2600 can be configured to function as a data server, a network server, a portable computing device, a personal computer, or any electronic computing device. As Figure 19 As shown, the computing device 2600 may include one or more processors (collectively 2602) having one or more levels of cache memory and a memory controller, which may be configured to communicate with a storage subsystem 2606 including a main memory 2608 and a permanent storage device 2610. As shown, the main memory 2608 may include dynamic random access memory (DRAM) 2618 and read only memory (ROM) 2620. The storage subsystem 2606 and the cache memory 2602 may be used to store information, such as details associated with transactions and blocks described in this disclosure. The (one or more) processors 2602 may be used to provide the steps or functions of any of the embodiments described in this disclosure.

[0472] (One or more) processors 2602 may also communicate with one or more user interface input devices 2612, one or more user interface output devices 2614, and a network interface subsystem 2616.

[0473] The bus subsystem 2604 may provide a mechanism for enabling the various components and subsystems of the computing device 2600 to communicate with each other as expected. Although the bus subsystem 2604 is schematically shown as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses.

[0474] The network interface subsystem 2616 may provide an interface to other computing devices and networks. The network interface subsystem 2616 may serve as an interface for receiving data from other systems different from the computing device 2600 and for transmitting data to other systems. For example, the network interface subsystem 2616 may enable a data technician to connect a device to a network such that the data technician may transmit data to and receive data from the device while located at a remote location (e.g., a data center).

[0475] The user interface input device 2612 may include one or more user input devices, such as a keyboard; a pointing device such as an integrated mouse, trackball, touchpad, or graphics tablet; a scanner; a barcode scanner; a touch screen incorporated into a display; an audio input device such as a voice identification system, microphone; and other types of input devices. In general, the use of the term "input device" is intended to include all possible types of devices and mechanisms for inputting information into the computing device 2600.

[0476] One or more user interface output devices 2614 can include a display subsystem, a printer, or a non-visual display such as an audio output device. The display subsystem can be a cathode ray tube (CRT), a flat panel device such as a liquid crystal display (LCD), a light emitting diode (LED) display, or a projector, or other display devices. Generally, the use of the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from the computing device 2600. One or more user interface output devices 2614 can be used, for example, to present a user interface to facilitate interaction of a user with an application that performs the described processes and variations thereof, when such interaction is appropriate.

[0477] The storage subsystem 2606 can provide a computer-readable storage medium for storing the basic programming and data constructs that can provide the functionality of at least one embodiment of the present disclosure. When executed by one or more processors, application programs (programs, code modules, instructions) can provide the functionality of one or more embodiments of the present disclosure and can be stored in the storage subsystem 2606. These application program modules or instructions can be executed by one or more processors 2602. Additionally, the storage subsystem 2606 can provide a repository for storing data used in accordance with the present disclosure. For example, the main memory 2608 and the cache memory 2602 can provide volatile storage for programs and data. The permanent storage device 2610 can provide permanent (non-volatile) storage for programs and data and can include flash memory, one or more solid state drives, one or more magnetic hard disk drives, one or more floppy disk drives with associated removable media, one or more optical drives (e.g., CD-ROM or DVD or Blue-Ray) with associated removable media, and other similar storage media. Such programs and data can include programs for performing the steps of one or more embodiments as described in the present disclosure and data associated with the transactions and blocks described in the present disclosure.

[0478] The computing device 2600 can be of various types, including a portable computer device, a tablet computer, a workstation, or any other device described below. Additionally, the computing device 2600 can include another device that can be connected to the computing device 2600 through one or more ports (e.g., USB, headphone jack, Lightning connector, etc.). The device that can be connected to the computing device 2600 can include a plurality of ports configured to accept fiber optic connectors. Thus, the device can be configured to convert an optical signal into an electrical signal that can be transmitted through the port connecting the device to the computing device 2600 for processing. Due to the ever-changing nature of computers and networks, Figure 19 The description of the computing device 2600 depicted is intended only as a specific example for the purpose of illustrating the preferred embodiments of the device. Many other configurations with more or fewer components than the Figure 19 system depicted are possible.

[0479] It should be noted that the above embodiments illustrate rather than limit the invention, and those skilled in the art will be able to design many alternative embodiments without departing from the scope of the invention as defined by the appended claims. In the claims, any reference signs in parentheses shall not be construed as limiting the claim. The word "comprising" etc. does not exclude the presence of elements or steps other than those listed in any claim or the whole specification. In this specification, "comprise" means "include or consist of", "comprising" means "including or consisting of". The singular form of an element does not exclude the plural form of such element and vice versa. The invention can be implemented by means of hardware including several distinct elements as well as by a suitably programmed computer. In a device claim enumerating several components, several of these components may be embodied by one and the same item of hardware. The fact that certain means are recited in mutually different dependent claims does not indicate that a combination of these means cannot be used to advantage.< / app> < / app> < / app> ​< / app> < / lzw> < / n> < / m> < / n> < / m> < / s> < / content> < / attributes>

Claims

1. A method for identifying a blockchain transaction (Tx) in a blockchain, the blockchain transaction comprising: A transaction index for identifying the blockchain transaction, the transaction index being specified by a blockchain-based search protocol for searching, storing, and / or retrieving data in one or more blockchain transactions; And A flag indicating that the blockchain transaction is formed according to the blockchain-based search protocol, The method includes the step of mapping a mnemonic to the transaction index, wherein: i) The mnemonic includes a human-readable identifier, term, or label; and ii) The transaction index includes a combination of: A public key (PK) associated with the blockchain transaction (Tx); and The transaction ID (TxID) of the blockchain transaction (Tx).

2. The method according to claim 1, wherein The mapping step includes: Using the public key (PK) and the transaction ID (TxID) as operands for an operation to generate the transaction index.

3. The method according to claim 2, further comprising the step of: Hashing the transaction index before mapping the mnemonic.

4. The method according to claim 2 or 3, wherein The operation is a concatenation operation.

5. The method according to any one of the preceding claims, wherein, The public key (PK) includes a human-readable prefix.

6. The method according to any one of the preceding claims, further comprising the step of: Searching for the blockchain transaction (Tx) in the blockchain.

7. The method according to any one of the preceding claims, further comprising the step of: Identifying one or more additional blockchain transactions having the same public key as the blockchain transaction (Tx).

8. The method according to claim 7, wherein: The public key of the blockchain transaction (Tx) is provided in the input of the blockchain transaction (Tx); and The public keys of the one or more additional blockchain transactions are provided in the inputs of the one or more additional blockchain transactions.

9. The method according to claim 7, wherein, The public key of the blockchain transaction (Tx) is provided in the input of the blockchain transaction; and The public keys of the one or more additional blockchain transactions are provided in the outputs of the one or more additional blockchain transactions.

10. The method according to claim 7, wherein, The public key of the blockchain transaction (Tx) is provided in the output of the blockchain transaction; and The public keys of the one or more additional blockchain transactions are provided in the inputs of the one or more additional blockchain transactions.

11. The method according to claim 7, wherein: The public key of the blockchain transaction (Tx) is provided in the output of the blockchain transaction; and The public keys of the one or more additional blockchain transactions are provided in the outputs of the one or more additional blockchain transactions.

12. The method according to any one of claims 7 to 11, comprising the step of: Examining the blockchain transaction (Tx) and the one or more additional blockchain transactions to determine which is the most recent blockchain transaction according to the protocol of the blockchain.

13. The method according to claim 12, wherein The most recent blockchain transaction is determined by: Block height; or Proof of work; or Transaction ordering within the block.

14. A computer-implemented system, comprising: a processor; and a memory including executable instructions which, when executed by the processor, cause the system to perform any implementation of the computer-implemented method according to any one of claims 1 to 13.

15. A non-transitory computer-readable storage medium having stored thereon executable instructions which, when executed by a processor of a computer system, cause the computer system to perform at least an implementation of the method according to any one of claims 1 to 13.

Images