Skip to content

Build a consensus mechanism #2

Description

@sh-rn

Scenario:
Currently cc daemon gets info from one single end point and this needs changing to get data from some hard-coded servers provided by Blocknet (IPs to be provided). Note: this would be a temporary solution that’s not decentralised but is distributed and requires consensus from a minimum of 3 blocknet team-owned snodes.

To do:

  • design a basic (diagram and document the specs and features) consensus mechanism
  • build the consensus mechanism

More info to follow...

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status
    To do

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions