Skip to content
This repository has been archived by the owner on Oct 25, 2021. It is now read-only.

Open Source Node Explorer #9

Closed
EdwardAThomson opened this issue Jul 17, 2018 · 7 comments
Closed

Open Source Node Explorer #9

EdwardAThomson opened this issue Jul 17, 2018 · 7 comments
Labels
Development: General Component Development - General ecosystem component requires development Engagement: Sought Engagement - W3F is seeking engagement from external teams

Comments

@EdwardAThomson
Copy link
Contributor

EdwardAThomson commented Jul 17, 2018

We would like to collaborate with teams in order to bring about an open source node explorer for the Polkadot network.

Take inspiration from Ether Nodes:
https://www.ethernodes.org/network/1

Useful information to display:
Client types, client versions, locations and any other info. This will require some fancy node crawling to figure out whats going on.

Difference between a node explorer and a block explorer:
A node explorer is looking at the network, while block explorers are looking at the data stored within the blocks of the chain itself.

@EdwardAThomson EdwardAThomson added Development: General Component Development - General ecosystem component requires development Ecosystem: Polkadot Engagement: Sought Engagement - W3F is seeking engagement from external teams labels Jul 17, 2018
@aj07
Copy link

aj07 commented Aug 20, 2018

I would like to work on this project along with my other 2 teammates.

Background:
Myself, Ankit is working in Blockchain ecosystem from last 2.5 years. I had worked with Red Hat on Distributed System (GlusterFS) and on RPC protocol in GSoC. Also, I was the grantee from Eth Foundation in wave1 to work on solidity. Previously we have created some node explorer for private Blockchain project. We are exploring more on Web3 from last 3 months. After exploring it we would like to dive more into it by diving into this issue and complete it.

Things we are seeking from Web3:

  • Point of contact whom we can discuss our progress.
  • Regular feedback.
  • Grant (will like to discuss on mail)

If you suggest we will share the few mock ups and design for node explorer for it in few days and start the discussion on riot.

I will be reachable on riot with name atmosphere. :)

Ankit Raj
LinkedIn

@EdwardAThomson
Copy link
Contributor Author

That sounds awesome! :-) We can try to help you coordinate with the right people. Obviously you can find the devs in the usual watercooler chat, otherwise you can also try in Substrate Technical.

I'd say dive right in! Feel free to drop thoughts here, or you can mail them over.

@aj07
Copy link

aj07 commented Aug 23, 2018

Thanks @EdwardAThomson I have been active on riot. Please , put me touch with right person.

@EdwardAThomson
Copy link
Contributor Author

Cool. Let me reach out to someone at Parity to find out who the best person is for you to speak to. If you don't hear anything from Parity by end of next week then drop me a message here or on riot (@edwardt:matrix.org).

@emielsebastiaan
Copy link
Contributor

@EdwardAThomson please explain what sets a 'node explorer' apart from a 'block explorer'. I find that I am having difficult making a hard distinctions and explain this to ppl. It may be a spectrum and a bit blurred... Appreciate the input!!

@EdwardAThomson
Copy link
Contributor Author

Something along the lines of https://www.ethernodes.org/network/1

Client types, client versions, locations and any other info. This will require some fancier node crawling to figure out whats going on.

A node explorer is looking at the network, while block explorers are looking at the data stored within the blocks of the chain itself.

@EdwardAThomson
Copy link
Contributor Author

This issue is a candidate for our grants program. For details on how to apply, see your grants page: https://grants.web3.foundation

@Noc2 Noc2 closed this as completed May 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development: General Component Development - General ecosystem component requires development Engagement: Sought Engagement - W3F is seeking engagement from external teams
Projects
None yet
Development

No branches or pull requests

4 participants