Datastore no longer retains self.data in v1 about js-libp2p

[marcus-pousette]

Also get the same behaviour. Previously by making the datastore persistant the peerid would persist between if recreating the client from the same directory. The new behaviour (since the keychgain no longer is shipped with the client) is that the peer id is not persisted even if that is the case.

Looking at the code that did the peerId load from datastore previously, and now is removed. Perhaps this change of behaviour should be documented in the migration guide on how to recover your previous PeerId given that it will now by default not be exported https://github.com/libp2p/js-libp2p/blob/main/doc/migrations/v0.46-v1.0.0.md#keychain.

Here is the previous code that will allow you to export the PeerId before creating the client, if you want to persist the PeerId. I suggest you to write that as pre-loading step before creating your client and pass the peerId to createLibp2p instead.

js-libp2p/packages/libp2p/src/libp2p.ts

Line 415 in fb8a6f1

const datastore = options.datastore as Datastore | undefined

[christroutner]

If the solution is to use the @libp2p/keychain library, I would appreciate a code example on how to generate a key and pass it on to createLibp2p().

If the data is generated by datastore or some other part of libp2p, I just need an example of how to find it and extract it. It's easy enough to write a JSON object to file. I just need some idea of how to go feeding some persisted private key to createLibp2p().