You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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
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.
The text was updated successfully, but these errors were encountered: