-
Notifications
You must be signed in to change notification settings - Fork 1.2k
A way to sign things using IPFS keys #2880
Comments
@whyrusleeping thoughts? |
This would require exposing a new API. |
@richardschneider has been working a ton on the |
Hopefully the Key API #1133 will be merged soon. Then the options |
A bunch of folks have also requested signed pubsub messages. |
@richardschneider Is it merged? If so, where is documentation how to use it? I would like to be able to sign some arbitrary data by one node private key, so it can be attributed forever to that node by any other node just by verification of signature. |
To be frank, I did a interview with protocol labs and they never got back to me. After a month I reached out and got a "Oh sorry we don't need you response". This after a year+ of contributing to the projects. I suggest you take a look at https://github.com/libp2p/js-libp2p-keychain Also, https://github.com/richardschneider/ipfs-encryption contains my original designs and questions |
I wish to use keystore and node keys in other software Any clarification is welcome. |
js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide. Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterward (see #4336). @achingbrain this sounds like something we should probably support in Helia. I'm not sure if it's already there, so assigning to you for either migrating this issue, creating new Helia specific issue for signing messages using keys in helia, or telling us it's already possible! |
When you export a key from the libp2p keychain you can access the raw public/private keys so this is possible without an API change. Closing as completed 👍 |
So each peer has its own key (and optional additional keys), but it seems there is no API which would allow one to sign messages using those keys (except by storing them inside IPNS).
The text was updated successfully, but these errors were encountered: