An implementation of IPNS for Helia
IPNS operations using a Helia node
With IPNSRouting routers:
import { createHelia } from 'helia'
import { ipns } from '@helia/ipns'
import { unixfs } from '@helia/unixfs'
const helia = await createHelia()
const name = ipns(helia)
// store some data to publish
const fs = unixfs(helia)
const cid = await fs.addBytes(Uint8Array.from([0, 1, 2, 3, 4]))
// publish the name
const { publicKey } = await name.publish('key-1', cid)
// resolve the name
for await (const result of name.resolve(publicKey)) {
console.info(result.record.value) // /ipfs/QmFoo
}A recursive record is a one that points to another record rather than to a value.
import { createHelia } from 'helia'
import { ipns } from '@helia/ipns'
import { unixfs } from '@helia/unixfs'
import { generateKeyPair } from '@libp2p/crypto/keys'
const helia = await createHelia()
const name = ipns(helia)
// store some data to publish
const fs = unixfs(helia)
const cid = await fs.addBytes(Uint8Array.from([0, 1, 2, 3, 4]))
// publish the name
const { publicKey } = await name.publish('key-1', cid)
// publish the recursive name
const { publicKey: recursivePublicKey } = await name.publish('key-2', publicKey)
// resolve the name recursively - it resolves until a CID is found
for await (const result of name.resolve(recursivePublicKey)) {
console.info(result.record.value) // /ipfs/QmFoo../foo.txt
}It is possible to publish CIDs with an associated path.
import { createHelia } from 'helia'
import { ipns } from '@helia/ipns'
import { unixfs } from '@helia/unixfs'
import { generateKeyPair } from '@libp2p/crypto/keys'
const helia = await createHelia()
const name = ipns(helia)
// store some data to publish
const fs = unixfs(helia)
const fileCid = await fs.addBytes(Uint8Array.from([0, 1, 2, 3, 4]))
// store the file in a directory
const dirCid = await fs.addDirectory()
const finalDirCid = await fs.cp(fileCid, dirCid, '/foo.txt')
// publish the name
const { publicKey } = await name.publish('key-1', `/ipfs/${finalDirCid}/foo.txt`)
// resolve the name
for await (const result of name.resolve(publicKey)) {
console.info(result.record.value) // /ipfs/QmFoo../foo.txt
}Additional IPNS routers can be configured - these enable alternative means to publish and resolve IPNS names.
One example is the PubSub router - this requires an instance of Helia with libp2p PubSub configured.
It works by subscribing to a pubsub topic for each IPNS name that we try to resolve. Updated IPNS records are shared on these topics so an update must occur before the name is resolvable.
This router is only suitable for networks where IPNS updates are frequent and multiple peers are listening on the topic(s), otherwise update messages may fail to be published with "Insufficient peers" errors.
import { createHelia, libp2pDefaults } from 'helia'
import { ipns } from '@helia/ipns'
import { pubsub } from '@helia/ipns/routing'
import { unixfs } from '@helia/unixfs'
import { floodsub } from '@libp2p/floodsub'
import { generateKeyPair } from '@libp2p/crypto/keys'
import type { PubSub } from '@helia/ipns/routing'
import type { Libp2p } from '@libp2p/interface'
import type { DefaultLibp2pServices } from 'helia'
const libp2pOptions = libp2pDefaults()
libp2pOptions.services.pubsub = floodsub()
const helia = await createHelia<Libp2p<DefaultLibp2pServices & { pubsub: PubSub }>>({
libp2p: libp2pOptions
})
const name = ipns(helia, {
routers: [
pubsub(helia)
]
})
// store some data to publish
const fs = unixfs(helia)
const cid = await fs.addBytes(Uint8Array.from([0, 1, 2, 3, 4]))
// publish the name
const { publicKey } = await name.publish('key-1', cid)
// resolve the name
for await (const result of name.resolve(publicKey)) {
console.info(result.record.value)
}$ npm i @helia/ipnsLoading this module through a script tag will make its exports available as HeliaIpns in the global namespace.
<script src="https://unpkg.com/@helia/ipns/dist/index.min.js"></script>Licensed under either of
- Apache 2.0, (LICENSE-APACHE / http://www.apache.org/licenses/LICENSE-2.0)
- MIT (LICENSE-MIT / http://opensource.org/licenses/MIT)
Contributions welcome! Please check out the issues.
Also see our contributing document for more information on how we work, and about contributing in general.
Please be aware that all interactions related to this repo are subject to the IPFS Code of Conduct.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
