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

Add endpoint to Ceramic API for currently connected peers #608

Closed
5 tasks
nathanielc opened this issue Nov 20, 2024 · 0 comments
Closed
5 tasks

Add endpoint to Ceramic API for currently connected peers #608

nathanielc opened this issue Nov 20, 2024 · 0 comments

Comments

@nathanielc
Copy link
Collaborator

Description

To operate a node well we need to be able to inspect which peers are connected to the local node.

DOD

  • An API endpoint part of the ceramic API exists that lists connected peers and metadata about the peers
  • did:key of remote peer
  • Last connected time
  • Bytes sent/recv to peer since start (this may be optionally exposed via metrics)
  • Unit tests for the endpoint
nathanielc added a commit that referenced this issue Dec 6, 2024
With this change a new API endpoint is added for accessing connected
peers. The API is similar to the /api/v0/swarm/peers endpoint however it
allows for multiple addresses and does not have to remain Kubo RPC
compatible.

The endpoint allows posting an address and therefore connecting to a new
peer.

Fixes: #608
nathanielc added a commit that referenced this issue Dec 6, 2024
With this change a new API endpoint is added for accessing connected
peers. The API is similar to the /api/v0/swarm/peers endpoint however it
allows for multiple addresses and does not have to remain Kubo RPC
compatible.

The endpoint allows posting an address and therefore connecting to a new
peer.

Fixes: #608
nathanielc added a commit that referenced this issue Dec 6, 2024
With this change a new API endpoint is added for accessing connected
peers. The API is similar to the /api/v0/swarm/peers endpoint however it
allows for multiple addresses and does not have to remain Kubo RPC
compatible.

The endpoint allows posting an address and therefore connecting to a new
peer.

Fixes: #608
nathanielc added a commit that referenced this issue Dec 9, 2024
With this change a new API endpoint is added for accessing connected
peers. The API is similar to the /api/v0/swarm/peers endpoint however it
allows for multiple addresses and does not have to remain Kubo RPC
compatible.

The endpoint allows posting an address and therefore connecting to a new
peer.

Fixes: #608
github-merge-queue bot pushed a commit that referenced this issue Dec 9, 2024
With this change a new API endpoint is added for accessing connected
peers. The API is similar to the /api/v0/swarm/peers endpoint however it
allows for multiple addresses and does not have to remain Kubo RPC
compatible.

The endpoint allows posting an address and therefore connecting to a new
peer.

Fixes: #608
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant