the private key for signing the record.
content to be stored in the record.
number representing the current version of the record.
expiration datetime for record in the [RFC3339]https://www.ietf.org/rfc/rfc3339.txt with nanoseconds precision.
Optionaloptions: CreateV2OrV1Optionsadditional creation options.
Same as create(), but instead of generating a new Date, it receives the intended expiration time WARNING: nano precision is not standard, make sure the value in seconds is 9 orders of magnitude lesser than the one provided.
The passed value can be a CID, a PublicKey or an arbitrary string path e.g. /ipfs/... or /ipns/....
CIDs will be converted to v1 and stored in the record as a string similar to: /ipfs/${cid}
PublicKeys will create recursive records, eg. the record value will be /ipns/${cidV1Libp2pKey}
String paths will be stored in the record as-is, but they must start with "/"
the private key for signing the record.
content to be stored in the record.
number representing the current version of the record.
expiration datetime for record in the [RFC3339]https://www.ietf.org/rfc/rfc3339.txt with nanoseconds precision.
additional creation options.
Same as create(), but instead of generating a new Date, it receives the intended expiration time WARNING: nano precision is not standard, make sure the value in seconds is 9 orders of magnitude lesser than the one provided.
The passed value can be a CID, a PublicKey or an arbitrary string path e.g. /ipfs/... or /ipns/....
CIDs will be converted to v1 and stored in the record as a string similar to: /ipfs/${cid}
PublicKeys will create recursive records, eg. the record value will be /ipns/${cidV1Libp2pKey}
String paths will be stored in the record as-is, but they must start with "/"
the private key for signing the record.
content to be stored in the record.
number representing the current version of the record.
expiration datetime for record in the [RFC3339]https://www.ietf.org/rfc/rfc3339.txt with nanoseconds precision.
additional creation options.
Same as create(), but instead of generating a new Date, it receives the intended expiration time WARNING: nano precision is not standard, make sure the value in seconds is 9 orders of magnitude lesser than the one provided.
The passed value can be a CID, a PublicKey or an arbitrary string path e.g.
/ipfs/...or/ipns/....CIDs will be converted to v1 and stored in the record as a string similar to:
/ipfs/${cid}PublicKeys will create recursive records, eg. the record value will be/ipns/${cidV1Libp2pKey}String paths will be stored in the record as-is, but they must start with"/"