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.

Sign up for GitHub

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

Jump to bottom

docs: validity follows expiration window #354

Merged
merged 2 commits into from
Feb 13, 2023
Merged

docs: validity follows expiration window #354

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
615456e
docs: validity follows expiration window
hacdias Dec 13, 2022
ba619e8
style: clarify value >48h is ignored by dht
lidel Feb 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion ipns/IPNS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,8 @@ A logical IPNS record is a data structure containing the following fields:
- Implementations MUST support `validityType = 0` and include this value in both `IpnsEntry.validityType` and inside the DAG-CBOR document at `IpnsEntry.data[validityType]`.
- **Validity** (bytes)
- When `validityType = 0`
- Expiration date of the record with nanoseconds precision.
- Expiration date of the record with nanoseconds precision. Expiration time should match the publishing medium's window.
- For example, IPNS records published on the DHT should have an expiration time set to within 48 hours after publication. Setting the expiration time to longer than 48 hours will not have any effect, as DHT peers only keep records for up to 48 hours.
- Represented as an ASCII string that follows notation from [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) (`1970-01-01T00:00:00.000000001Z`).
- Implementations MUST include this value in both `IpnsEntry.validity` and inside the DAG-CBOR document at `IpnsEntry.data[validity]`.
- **Sequence** (uint64)
Expand Down