hypercore | Hypercore is a secure , distributed append-only log | Cryptography library

Is there a convenient function to get a hypercore's discovery key from its public key?

I know I can use myCore.key and myCore.discoveryKey in hypersdk

But if you just had a key as a hex string (e.g. "778f8d955175c92e4ced5e4f5563f69bfec0c86cc6f670352c457943666fe639"), how would you get the discovery key?

Is there a convenience function in one of the hypercore-protocol modules?

Note, the discovery key is the blake2b-256 hash of the public key.

What is the key scheme used in the hypercore protocol?

I didn't find a quick/good answer on searching so adding the question here.

I'm trying to use hyperdb in browser with swarming via webrtc and signalhub. The code is pretty strait forward, but there is some issue with hyperdb replicate where the connecting is killed because of a sameKey check in hypercore. So, I'm thinking ... I'm not properly juggling my discovery keys and id keys so the peers know they should be sync'd. Here is some sample code, it is a bit of a mess but the relevant bits are the hyperdb initialization and the webrtc/signalhub stuff (I think) ... the key at the top is the discovery key of the other peer:

I want to port a number of packages written for NodeJS to React Native.

For this purpose I created a RN project using the popular Ignite boilerplate, then used the ReactNativify method and shim Node API objects mostly reusing existing browserify shims.

(For details and some useful tips see Can we use nodejs code inside react native application?)

Some Node objects are still replaced with empty mocks after transpilation, such as fs. Done in .babelrc as follows: