[BIP Proposal] Add BIP-0093 (Codex32) as application to BIP-0085

Posted by Aneesh Karve

Sep 7, 2025/23:13 UTC

In a recent discussion on the Bitcoin Development Mailing List, the topic of simplification and clarification of derivation paths in the BIP-85 specification was brought up. The conversation highlighted the potential complexity of these paths, specifically noting that they might become the longest within the BIP-85 spec. Suggestions were made to explore avenues for making these derivation paths more straightforward without compromising their integrity or purpose. The idea centers around whether there is a possibility to embody the principle of "less is more" within the construction of these paths, particularly regarding the derivation of single bech32 characters.

Further analysis suggested that the method of drawing characters could be made more efficient and clearer, especially in relation to the "Bytes Length Table" provided within the specification. It was pointed out that it should be more explicitly stated whether the table refers to bytes drawn or retained, among other possible clarifications. Additionally, the consistency in utilizing the same Digital Random Number Generator (DRNG) instance for all draws was mentioned as a point that could use further explanation. This specificity could aid in understanding and implementing the spec more accurately, especially when compared to other sections of BIP-85 where the methodology differs, such as the RSA key generation which does not predetermine the number of draws due to its inherent uncertainty.

The discourse also touched upon the technicalities of the drawing process itself, contemplating whether implementers could benefit from drawing bytes in bulk ((chars * 5) // 8 bytes at a time) rather than individually per character. This approach would potentially reduce the total number of iterations and reads required, streamlining the process. However, concerns were raised about the readability and writeability of such a method, suggesting that if the proposed changes compromise these aspects, it may be preferable to adhere to the current methodology.

Link to Raw Post
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback