Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • P Penumbra
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • 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
  • l0nelyc0w
  • Penumbra
  • Issues
  • #21
Closed
Open
Issue created Jun 17, 2022 by l0nelyc0w@l0nelyc0wOwner

Design of federating protocol

A protocol that would allow the seednodes of operators of different Penumbra networks to intercommunicate in order to increase censorship resistance and move closer to structurally being a true DEX.

It should allow all networks to be listed in the application and gives the user the ability to choose which node to connect to.

Things to consider: Requirements be for an operator to join? (entry fee, hardware specs, availability etc) Penalties for bad/malicious operators?

Assignee
Assign to
Time tracking