Publish to network - example

[ipfs]

Publish to network - example

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[achingbrain]

Why does the IPNS entry data require two signatures?

It currently supports v1 and v2 signatures. At some point in the near future v1 will be retired and only v2 will be supported.

Once I have created an IPNS entry record how do I send this entry to the network?

You need to either use datastore-pubsub to broadcast the record, or libp2p-kad-dht to store the record and answer requests for it.

Assuming I'm running the js-ipfs module in the browser; is there an easy way to publish a custom signed entry?

Not via the core API, it just deals in the value to be published and the parameters to use in the sig, though you can roll your own version of the ipns subsystem to do it.

Sorry for the delay in replying - https://discuss.ipfs.io is usually a better venue for getting help than opening issues on this repo.