Hypercore Sign

Sign hypercore signing requests using public/private key cryptography, and verify the signatures.

The flow is:

• The signer creates a public/private key pair, and shares the public key
• The signer signs Hypercores (for example to approve of their content at a certain length), and shares the signed message.
• Anyone with the public key can verify that the hypercore was indeed approved by the signer.

Install

npm i -g hypercore-sign

Run

Setup keys

Run this only once, to setup a public/private key pair.

By default, keys are written to:

• secret key: ~/.hypercore-sign/default
• public key: ~/.hypercore-sign/default.public

hypercore-sign generate-keys

# you will be prompted for password
> Password: ...

Sign Hypercores

hypercore-sign <z32SigningRequest>

Sign a hypercore signing request with your private key.

Expects the signing request to be z32-encoded

For example:

hypercore-sign yr8oytuhdpmg4e511nj8thyo9mju1uaw8npox9dtzpo6ndu73w9xir69yryyyyebybywj5ifg81e8ikqbokxj1uehb1r6pkuex9s91axybjybajc47dhsgtjr9p58q8perk758qmxqn3idu5hiu5xw1iutce8xhmtmi6oxx3

# you will be prompted for password
> Password: ...

Verify Signatures

hypercore-verify <signed-message> <signer-public-key>

Verify the signed message against the given public key.

For example:

hypercore-verify dd89etw5o34f7bej6omrr9cxnwcd5fz6xwgamjpeyp469jq53i5yrjbxg4cftogtyyq9j1zthrsxt6mad6gwc5c6udh7n16n5gy6ayobbhyrc9y5k3s1ghwo1jhxyr844chw6fbaucd9ahp5c8ooh9qp857j8zabyyyynyeyefnq7jjth1b7kuocnu4cw48yct8ukw4d97zhsdaykeyqnmgze9ftwkj85q35t5kbnzq35155ospeh69fc657richmnb59nhk7xwd56e hu3rzup73iwuf35n458e54i3opmzo7wbbgisbuwmz7jr7jotgexo