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

ipns publish: lower the default TTL #10718

Open
5 tasks done
Tracked by #10685
lidel opened this issue Feb 15, 2025 · 3 comments
Open
5 tasks done
Tracked by #10685

ipns publish: lower the default TTL #10718

lidel opened this issue Feb 15, 2025 · 3 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature need/triage Needs initial labeling and prioritization topic/ipns Topic ipns

Comments

@lidel
Copy link
Member

lidel commented Feb 15, 2025

Checklist

  • My issue is specific & actionable.
  • I am not suggesting a protocol enhancement.
  • I have searched on the issue tracker for my issue.

Description

Never-ending complains about IPNS being slow usually boil down to the implicit default of --ttl in ipfs name publish RPC being set to 1h.

It may not be the best default for Kubo and also not the best recommendation in Specs (https://specs.ipfs.tech/ipns/ipns-record/)

We may look into the default setting big DNS providers have (afaik Cloudflare uses 5 minutes for the same reason – a tradeoff between caching and user complaints due to slow propagation), and change spec recommendation and Kubo default to more pragmatic value.

Ref.

TODO

@lidel lidel added kind/enhancement A net-new feature or improvement to an existing feature need/triage Needs initial labeling and prioritization topic/ipns Topic ipns labels Feb 15, 2025
@lidel lidel moved this to Todo in @lidel's IPFS wishlist Feb 17, 2025
@lidel lidel mentioned this issue Feb 17, 2025
42 tasks
@2color
Copy link
Member

2color commented Feb 26, 2025

Never-ending complains about IPNS being slow usually boil down to the implicit default of --ttl in ipfs name publish RPC being set to 1h.

What exactly do you mean by IPNS being slow in this context? Slow propagation of changes? or Slow to resolve?

IIUC, you're referring to users that can't see their newly published IPNS record propagated, because nodes aren't looking up the new record due to the one hour TTL?

@lidel
Copy link
Member Author

lidel commented Feb 26, 2025

Yes. In my subjective experience, virtually every "ipns is slow" argument I've heard in past 5 years ended up being TTL-related, upon closer inspection. TTL was set to default 1h, or raised to 24h, I've even seen someone setting validity and TTL to a year, and then complaining "IPNS is broken". All those issues went away when TTL was lowered.

Filled related ipfs/ipfs-docs#2002

lidel added a commit to ipfs/boxo that referenced this issue Feb 26, 2025
lidel added a commit to ipfs/specs that referenced this issue Feb 26, 2025
@lidel
Copy link
Member Author

lidel commented Feb 26, 2025

Triage note:

lidel added a commit to ipfs/boxo that referenced this issue Feb 28, 2025
chore(ipns): lower DefaultRecordTTL to 5m

See rationale in ipfs/kubo#10718
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature need/triage Needs initial labeling and prioritization topic/ipns Topic ipns
Projects
None yet
Development

No branches or pull requests

2 participants