Marvin ROGER

I do have the same issue... That's weird.

I can confirm the PR above is working fine.

It would, but having to duplicate the previous docs just does not feel right! If you have a rather large docs with pictures, it would quickly fill up the git...

That's right, we can share the assets. But still, the markdown files would be duplicated, as we have to create a new folder each time we release a new version....

I'm currently working on it, I'll add new optimized WASM functions

@rokanost what if you comment that line? https://github.com/marvinroger/nanocurrency-js/blob/a8d794af0242b0de64e0e7f3295a8f33106b217f/src/keys.ts#L41 If it's as simple as feeding the blake2b hash with a 128 chars seed instead of a 64 one, it would be...

Do you generate the work against the previous block hash? If this is the first block on the account chain, you have to use the account's public key.

Alright, so it's a bit more complicated than that. We can't generate a nano seed from a BIP39 mnemonic phrase. We can however derive private keys from the mnemonic phrase...

Initial work started in https://github.com/marvinroger/nanocurrency-js/pull/63

This is already supported by the lib, notably using `useNanoPrefix`. It’s not the default for backwards compatibility reasons, but I might reconsider this for a new version.