-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
unassigning this so I can stay focused on Helia and IPFS stuff |
@wemeetagain was going to try to deploy on chainsafe infra but got stalled. |
@SgtPooki to deploy a bootstrapper on sgtpooki.com |
it could use some robustness and productionization, but it's deployed:
Fixed by #135 |
Does it need autonat? We can pre-configure it with public Though I guess we want it to function as a verifier for other autonat peers. |
FYI @achingbrain it looks like they may be correlated with TCP listener errors? |
Weirdly, I cannot resolve the peerID from the delegated routing endpoint: https://delegated-ipfs.dev/routing/v1/peers/12D3KooWQgrExcg6dkCdiTER3G3ARe14PZ4cLhinKtRcLHsvnk1Q |
Can or cannot? It's only returning If "can" is correct, why is that weird? |
I meant that I cannot resolve. |
Sharing an update here for public visibility:
|
@achingbrain I just deployed the latest main 7edbbcd |
Closing as this is now deployed |
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
The text was updated successfully, but these errors were encountered: