specs
specs copied to clipboard
ipfs
Technical specifications for the IPFS protocol stack
https://specs.ipfs.tech/ipns/ipns-record/ searching for "dns" & "domain" don't turn up any results, only mention of dnslink is in https://specs.ipfs.tech/ipns/ipns-record/#value-bytes related to https://github.com/ipfs-shipyard/is-ipfs/pull/95#discussion_r1594631494
Renaming resource to follow latest libp2p spec draft and go-libp2p: https://github.com/libp2p/specs/pull/508#discussion_r1550303385 https://github.com/libp2p/specs/pull/508/commits/3c0ac4033dd640425e047ee448771dbca244ba68 https://github.com/libp2p/go-libp2p/pull/2757
I think we should use the [CC-BY-SA 4.0 International license.](https://creativecommons.org/licenses/by-sa/4.0/) But I am not a lawyer.
This is a placeholder issue for writing spec and tracking implementation. The need is to expose equivalent of `ipfs files stat`'s `Size` and `CumulativeSize` on HTTP gateway somehow, allowing light...
I think it would be pretty useful if ipns recognized the [signing prefix used by ethereum wallets](https://web3js.readthedocs.io/en/v1.7.5/web3-eth-personal.html#sign). That way users with metamask or other wallets could sign ipns records to...
## Problem IPNS Record spec lists Validity, TTL and Seq as uint64: - https://specs.ipfs.tech/ipns/ipns-record/#ttl-uint64 - https://specs.ipfs.tech/ipns/ipns-record/#sequence-uint64 - https://specs.ipfs.tech/ipns/ipns-record/#validity-type-uint64 ..but this only applies to the protobuf fields from IPNS v1. For...
Closes https://github.com/ipfs/specs/issues/467 by updating `Last-Modified` section. We forgot to do that as part of TTL cleanup, and that created contradiction reported by @SgtPooki (thx!)
## TLDR Extends Gateway specs with optional `Ipfs-Path-Affinity` request header. That is all. If header is present in request, gateway can leverage this optional hint to improve content routing. The...
Previous work reduced the scope of IPIP-337 to read operations only. The changes here re-introduce the write operations originally written by @guseggert back into IPIP-337. The specification documents the ability...
https://github.com/ipfs/specs/blame/937754aa4b7aa96763be40e1503a4fda3f766ad6/src/http-gateways/path-gateway.md#L401-L402 > No matter if TTL value is known or not, implementations should always send a [Last-Modified](https://specs.ipfs.tech/http-gateways/path-gateway/#last-modified-response-header) header with the timestamp of the record resolution. and the link points to...