Skip to content

PQ #945

Description

@hicaru

Question regarding PQ Signature BIP39 Key Derivation

Hi everyone,

I'm a developer at Bearby, a web3 wallet with a focus on quantum resistance (we've already implemented quantum-resistant key storage).

I've been reviewing TIP-899 and it looks great — the protocol-level details for ML-DSA-44 and FN-DSA-512 (including the fixed 666-byte padding solution for Falcon) are very thoroughly specified.

However, I noticed that the "BIP-39/32 derivation extension" is still listed under Open Questions.

Since standard BIP39/BIP44 derivation paths are built around ECDSA/secp256k1 and produce a 512-bit seed via PBKDF2, this doesn't directly map to the key generation requirements of lattice-based algorithms.

As wallet developers, we are very interested in how Tron plans to handle PQ key generation from a standard BIP39 mnemonic phrase. Specifically:

  • What Key Derivation Function (KDF) or seed expansion algorithm (e.g., SHAKE256, HKDF) is being considered to map the standard BIP39 seed into PQ private/public key pairs?
  • Are there any early drafts, specific repository discussions, or planned TIPs regarding this derivation standard that we can follow or contribute to?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions