Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Crown
  • crown-corecrown-core
  • Issues
  • #156

Closed
Open
Created Apr 04, 2018 by Artem B@artemOwner

Crown network crawler

Motivation

Sometime developers are blind of what is happening with the network. We only can use our own logs and run some commands to understand the state of the network. So we need a tool to collect information about the current status of the network. It's crucial so developers can collect information fast and mitigate the problems.

Suggestion

Implement a network crawler.

Specification

  • Total number of nodes in the network
  • Metadata about each node
    • IP address
    • ISP/hosting provider and location
    • Detect and flag phantom nodes
    • List of peers
    • Chain tips
    • SN, MN, or wallet
    • Protocol version
    • Client version string
    • Last update time, UTC
    • Period of time online
    • Votes for proposals
    • Votes for finalized budgets
    • Votes for the current/previous MN/SN payments
    • Statistics about MN/SN payments tied to the address
  • Information about offline nodes
    • ie: nodes which are "usually" or were recently online but are now offline
    • expect this would be based on IP address or collateral UTXO
    • time last seen
  • Sufficient documentation to allow someone else to perform maintenance in the future or enhance the feature set

Please add information to this spec.

Edited Jul 22, 2020 by Mark Brooker
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking