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

feat: deploy js-libp2p bootstrapper #18

Closed
7 of 10 tasks
SgtPooki opened this issue Oct 3, 2023 · 15 comments
Closed
7 of 10 tasks

feat: deploy js-libp2p bootstrapper #18

SgtPooki opened this issue Oct 3, 2023 · 15 comments
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Oct 3, 2023

This issue is tracking the deployment of this bootstrap on our bifrost infra

discussed at https://pl-strflt.notion.site/mob-create-js-libp2p-based-Amino-DHT-bootstrapper-e7793d5a79764df6a08dbc0474935c4d?pvs=4

Tasks

@SgtPooki SgtPooki added enhancement New feature or request help wanted Extra attention is needed labels Oct 3, 2023
@SgtPooki SgtPooki changed the title feat: deploy on bifrost infra feat: deploy bootstrapper on bifrost infra Oct 3, 2023
@SgtPooki SgtPooki self-assigned this Oct 5, 2023
@SgtPooki SgtPooki removed their assignment Oct 16, 2023
@SgtPooki
Copy link
Member Author

unassigning this so I can stay focused on Helia and IPFS stuff

@dhuseby
Copy link

dhuseby commented Apr 30, 2024

@wemeetagain was going to try to deploy on chainsafe infra but got stalled.

@dhuseby
Copy link

dhuseby commented Apr 30, 2024

@SgtPooki to deploy a bootstrapper on sgtpooki.com

@SgtPooki SgtPooki changed the title feat: deploy bootstrapper on bifrost infra feat: deploy js-libp2p bootstrapper May 7, 2024
@SgtPooki
Copy link
Member Author

SgtPooki commented May 7, 2024

it could use some robustness and productionization, but it's deployed:

╰─ ✔ ❯ ./vole libp2p identify /ip4/147.75.198.229/tcp/4003/ws/p2p/12D3KooWQgrExcg6dkCdiTER3G3ARe14PZ4cLhinKtRcLHsvnk1Q                                  14.88   17.1G   64%   78%  ─╯
PeerID: "12D3KooWQgrExcg6dkCdiTER3G3ARe14PZ4cLhinKtRcLHsvnk1Q"
Protocol version: "ipfs/0.1.0"
Agent version: "libp2p/1.5.1 UserAgent=v20.13.0"
Listen addresses:
	- "/ip4/147.75.198.229/tcp/4001/p2p/12D3KooWQgrExcg6dkCdiTER3G3ARe14PZ4cLhinKtRcLHsvnk1Q"
	- "/ip4/147.75.198.229/tcp/4003/ws/p2p/12D3KooWQgrExcg6dkCdiTER3G3ARe14PZ4cLhinKtRcLHsvnk1Q"
Protocols:
	- "/ipfs/id/1.0.0"
	- "/ipfs/id/push/1.0.0"
	- "/ipfs/kad/1.0.0"
	- "/libp2p/autonat/1.0.0"
	- "/libp2p/circuit/relay/0.2.0/hop"
	- "/webrtc-signaling/0.0.1"

Fixed by #135

@SgtPooki
Copy link
Member Author

SgtPooki commented May 7, 2024

I got some graphs using the metrics dashboards from helia-http-gateway:

image image image

@SgtPooki
Copy link
Member Author

SgtPooki commented May 8, 2024

graph of last 24 hours (not full because it was only started yesterday afternoon) seems to show steadily increasing memory.

image

@achingbrain
Copy link
Member

achingbrain commented May 8, 2024

Does it need autonat? We can pre-configure it with public announce addresses, right? No need for it to try to detect what these are.

Though I guess we want it to function as a verifier for other autonat peers.

@SgtPooki
Copy link
Member Author

SgtPooki commented May 8, 2024

We could just announce the ip/domain for sure, but as a bootstrap node I think it makes sense to help any "startup" things needed by peers. I had autonat disabled at first, but enabled it when docker wasn't working with port publishing, and then just left it when switching to --network host

here's nodejs metrics from the same helia-http-gateway dashboards (-old is the blue increasing line):

image

@SgtPooki
Copy link
Member Author

SgtPooki commented May 9, 2024

FYI @achingbrain it looks like they may be correlated with TCP listener errors?

image

@2color
Copy link
Contributor

2color commented May 10, 2024

Weirdly, I cannot resolve the peerID from the delegated routing endpoint: https://delegated-ipfs.dev/routing/v1/peers/12D3KooWQgrExcg6dkCdiTER3G3ARe14PZ4cLhinKtRcLHsvnk1Q

@SgtPooki
Copy link
Member Author

Weirdly, I can resolve the peerID from the delegated routing endpoint: delegated-ipfs.dev/routing/v1/peers/12D3KooWQgrExcg6dkCdiTER3G3ARe14PZ4cLhinKtRcLHsvnk1Q

Can or cannot? It's only returning {"Peers":null} for me right now, but some of the DHT provide issues Alex recently fixed (talked about during Helia WG) may be related?

If "can" is correct, why is that weird?

@2color
Copy link
Contributor

2color commented May 13, 2024

I meant that I cannot resolve.

@2color
Copy link
Contributor

2color commented Sep 20, 2024

Sharing an update here for public visibility:

@2color
Copy link
Contributor

2color commented Sep 23, 2024

@achingbrain I just deployed the latest main 7edbbcd

@achingbrain
Copy link
Member

Closing as this is now deployed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Status: 🎉Done
Development

No branches or pull requests

4 participants