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

fix!: require V2 signatures #180

Merged
merged 2 commits into from Sep 20, 2022
Merged

fix!: require V2 signatures #180

merged 2 commits into from Sep 20, 2022

Commits on Sep 12, 2022

  1. fix: require V2 signatures 

    This is part of deprecation described in ipfs/js-ipfs#4197
- record creation continues to create both V1 and V2  signatures
- record validation no longer accepts V1 signatures

Meaning:
- modern nodes are 100% V2, they ignore V1 signatures
- legacy nodes (go-ipfs < v0.9.0, js-ipfs before Jun 2021) are still
  able to resolve names created by js-ipns, because V1 is still present
    @lidel
    lidel committed Sep 12, 2022
    Configuration menu
    Copy the full SHA
    caa95eb View commit details
    Browse the repository at this point in the history

  2. docs: create output

    @lidel
    lidel committed Sep 12, 2022
    Configuration menu
    Copy the full SHA
    5e60f5d View commit details
    Browse the repository at this point in the history