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(polka-storage-provider): Add re-registration for p2p node #682

Open
aidan46 opened this issue Jan 17, 2025 · 2 comments
Open

feat(polka-storage-provider): Add re-registration for p2p node #682

aidan46 opened this issue Jan 17, 2025 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@aidan46
Copy link
Contributor

aidan46 commented Jan 17, 2025

Currently, if running a registration node in the p2p network, the node registers for DEFAULT_TTL seconds. Since the polka-storage-provider-server is a long-running process, we would want to add automatic re-registration after expiry.

@aidan46 aidan46 added the enhancement New feature or request label Jan 17, 2025
@aidan46 aidan46 added this to the Phase 3 milestone Jan 17, 2025
@aidan46 aidan46 self-assigned this Jan 17, 2025
@jmg-duarte
Copy link
Contributor

Is infinite TTL a thing?

@aidan46
Copy link
Contributor Author

aidan46 commented Jan 17, 2025

Is infinite TTL a thing?

We can set the TTL to u64::MAX, which is 5.845421e+11 years. The recommended max TTL for rendezvous protocol is 72 hours. I am trying the find out if there are any drawbacks for setting TTL to u64::MAX

@aidan46 aidan46 changed the title feat(polka-storage-provider): Add auto reregistration for p2p node feat(polka-storage-provider): Add longer TTL for p2p node Jan 17, 2025
@aidan46 aidan46 changed the title feat(polka-storage-provider): Add longer TTL for p2p node feat(polka-storage-provider): Add re-registration for p2p node Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants