You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Hot Importer, in contrast to the "Cold" Importer, which gets data from a disconnected (hence cold) LevelDB, is designed to be able to bring current Ethereum data to be consumed by the IPFS network.
Vision
Initially thought as a hack to an Ethereum Client. This importer is a client on its own. The vision it represents is to become the Modular Blockchain Client for Storage and Networking, making possible to multiple blockchains, or any other application that relies heavily on content-addressed data, to just plug into the IPFS network to fulfill backend roles, allowing the clients of these blockchains to focus on their core competencies, namely state change computations and consensus. An ambitious goal that is implied as a possible logical step to the solution of several scalability problems.
As of 2017.10.17, the devp2p network consists on 24k nodes (Ethernodes see below), the bitcoin network has 9k nodes (Bitnodes see below), while it is reported that libp2p is made of 9k nodes. Once the way is made for multiple blockchains to enter the field and interoperation becomes common place, the concept of "pluggable networking" will reach relevance, and it will be positive to be prepared in advance by offering an easy to plug library or API for such effect.
Features
The Hot Importer aims to provide the following core features
Connect to devp2p as another node of the mesh. Identifying itself as mustekala with its version.
Send messages to its connected neighbors inquiring for
State Trie Data
Storage Trie Data
Block Headers
Transactions
Transaction Receipts.
Upon received data, this will be imported into IPFS as IPLD blocks, for further consumption of the libp2p network.
Additional features (nice to have)
Feed a floodsub subscription to inform its peer on new minted blocks.
Update tables such as the CHT (Canonical Hash Table), Transaction to Block and future needed tables that can improve the lookup process.
Provide an API for clients to be used either as a library, or as an independent program.
Other?
Objects Importing
Has
N/A
Wants
state trie nodes
storage trie nodes
block headers
transactions
transaction receipts
Sources
The text was updated successfully, but these errors were encountered:
ghost
changed the title
"Hot" Importer
Roadmap: Hot Importer
Oct 18, 2017
What is this
The Hot Importer, in contrast to the "Cold" Importer, which gets data from a disconnected (hence cold) LevelDB, is designed to be able to bring current Ethereum data to be consumed by the IPFS network.
Vision
Initially thought as a hack to an Ethereum Client. This importer is a client on its own. The vision it represents is to become the Modular Blockchain Client for Storage and Networking, making possible to multiple blockchains, or any other application that relies heavily on content-addressed data, to just plug into the IPFS network to fulfill backend roles, allowing the clients of these blockchains to focus on their core competencies, namely state change computations and consensus. An ambitious goal that is implied as a possible logical step to the solution of several scalability problems.
As of 2017.10.17, the devp2p network consists on 24k nodes (Ethernodes see below), the bitcoin network has 9k nodes (Bitnodes see below), while it is reported that libp2p is made of 9k nodes. Once the way is made for multiple blockchains to enter the field and interoperation becomes common place, the concept of "pluggable networking" will reach relevance, and it will be positive to be prepared in advance by offering an easy to plug library or API for such effect.
Features
The Hot Importer aims to provide the following core features
mustekala
with its version.Additional features (nice to have)
Objects Importing
Has
N/A
Wants
Sources
The text was updated successfully, but these errors were encountered: