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

p2p/ws: connected peers REST endpoint and goal CLI #2

Open
urtho opened this issue Sep 4, 2024 · 2 comments
Open

p2p/ws: connected peers REST endpoint and goal CLI #2

urtho opened this issue Sep 4, 2024 · 2 comments

Comments

@urtho
Copy link
Member

urtho commented Sep 4, 2024

Status

Neither goal utility nor algod API have the ability to expose connected peers.

Expected

  • algod should have a REST endpoints under /v2/status/peers that lists all connected peers , their network (WS or P2P) and direction
  • goal should have a command that queries this endpoint and formats the output
@urtho
Copy link
Member Author

urtho commented Sep 4, 2024

REST endpoint implemented in d5c0053.
Needs

  • wrapping into a goal command under goal node connected-peers
  • proper tests

@urtho
Copy link
Member Author

urtho commented Sep 4, 2024

Testing P2P peers on current mainnet requires a catchup node and:

  • 2 extra lines in config.json
"DNSBootstrapID": "<network>.algonode.network",
"EnableP2P": true
  • fire up an algod compiled from peer-status branch

this will switch a mainnet participation node to P2P only mode.

a hybrid (P2P and WS) mode can be tested with EnableP2PHybridMode: true instead of EnableP2P: true

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