Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Kolmogorov Proof of Concept #8

Closed
ghost opened this issue Jun 13, 2018 · 2 comments
Closed

[WIP] Kolmogorov Proof of Concept #8

ghost opened this issue Jun 13, 2018 · 2 comments
Labels
Admin Management of the repository

Comments

@ghost
Copy link

ghost commented Jun 13, 2018

.

@ghost
Copy link
Author

ghost commented Jun 13, 2018

Concept of the PoC

Enable the user to run a block explorer SPA in her browser, discovering kitsunet peers, connecting to them, and finally exchanging ethereum data from the network, in a p2p fashion.

PoC Feature Summary

  • Getting specific data from devp2p (as opposed to "all the data")
  • Availability of the above ethereum data in libp2p
  • Block Explorer SPA
    • Able to connect to kitsunet
    • Able to fetch data from kitsunet peers
    • Able to share data to kitsunet peers
  • Telemetry System
    • Probably (Nice to have), the openness of this system for any user's consuming

Layer breakdown

See the architecture documentation for a thorough understanding of which comprises each layer

Layer 1

  • Getting data from devp2p
    • Latest canonical block header
    • Ommers, transactions and transaction receipts
    • Specific ethereum account traversals
    • Specific ethereum smart contract storage traversals.

Layer 2

  • Placement of data in libp2p
    • IPFS nodes with IPLD plugin
  • Containerization of the above Bridges to boost the network
  • Hubs
    • Container systems running IPFS+IPLD
    • Discovery availability
    • Hot caching capacities
      • If we don't have a hash, we start to ask for it
      • Dynamic selection of specific accounts to pick

Layer 3

Block Explorer SPA

No named yet 😉

  • Connection to kitsunet
  • Consume and Visualize Data
    • Latest Block
    • Block Headers
    • Ommers
    • Transactions
    • Transaction Receipts
    • Show specific accounts
    • Show specific smart contract data
    • Execute smart contract code, access its data (ex. Token balance)
    • Send data to Telemetry server

Questions:

  • How do we know whats the latest block?
    • We can use pubsub and publish the latest block on a topic
      • How do we publish from multiple ipfs nodes?
        • Maybe, we can use ipfs cluster

Layer 4

We are not working on the CRS at this PoC stage.

Telemetry

  • Redundancy
  • Availability
  • Well Spacing
  • Clustering (i.e. "How far of my neighbourhood I have to go to get data?")
  • Data Exchange Rate

@ghost ghost mentioned this issue Jun 14, 2018
@ghost ghost deleted a comment from dryajov Jun 14, 2018
@ghost ghost added this to the Kolmogorov PoC milestone Jul 21, 2018
@ghost ghost added the Admin Management of the repository label Jul 21, 2018
@ghost
Copy link
Author

ghost commented Aug 29, 2018

PoC must be rethought

@ghost ghost closed this as completed Aug 29, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Admin Management of the repository
Projects
None yet
Development

No branches or pull requests

0 participants