• Top
    • Documentation
    • Books
    • Boolean-reasoning
    • Projects
      • Apt
      • Zfc
      • Acre
      • Milawa
      • Smtlink
      • Abnf
      • Vwsim
      • Isar
      • Wp-gen
      • Dimacs-reader
      • Pfcs
      • Legacy-defrstobj
      • Proof-checker-array
      • Soft
      • C
      • Farray
      • Rp-rewriter
      • Instant-runoff-voting
      • Imp-language
      • Sidekick
      • Leftist-trees
      • Java
      • Taspi
      • Bitcoin
        • Bip32
          • Bip32-wallet-structure
          • Bip32-key-trees
            • Bip32-extend-tree
            • Bip32-valid-depths-p
            • Bip32-key-tree
            • Bip32-path-set-closedp
            • Bip32-valid-keys-p
            • Bip32-index-tree
            • Bip32-path-in-tree-p
            • Bip32-ckd*
            • Bip32-get-pub-key-at-path
            • Bip32-get-priv-key-at-path
            • Bip32-ckd-priv*
            • Bip32-ckd-pub*
            • Bip32-path
              • Bip32-key-tree-priv-p
              • Bip32-path-set
            • Bip32-key-serialization
            • Bip32-key-derivation
            • Bip32-executable-attachments
            • Bip32-extended-keys
            • Bip32-master-key-generation
          • Bech32
          • Bip39
          • Bip44
          • Base58
          • Bip43
          • Bytes
          • Base58check
          • Cryptography
          • Bip-350
          • Bip-173
        • Riscv
        • Des
        • Ethereum
        • X86isa
        • Sha-2
        • Yul
        • Zcash
        • Proof-checker-itp13
        • Regex
        • ACL2-programming-language
        • Json
        • Jfkr
        • Equational
        • Cryptography
        • Poseidon
        • Where-do-i-place-my-book
        • Axe
        • Bigmems
        • Builtins
        • Execloader
        • Aleo
        • Solidity
        • Paco
        • Concurrent-programs
        • Bls12-377-curves
      • Debugging
      • Std
      • Proof-automation
      • Macro-libraries
      • ACL2
      • Interfacing-tools
      • Hardware-verification
      • Software-verification
      • Math
      • Testing-utilities
    • Bip32-key-trees

    Bip32-path

    Paths in key trees.

    As explained in [BIP32], the derivation of child keys from parent keys give rise to key trees. Each key in a tree is designated by a list of zero or more unsigned 32-bit bytes, each of which is a key index i as used in the child key derivation functions; the empty path designates the root of the tree.

    This kind of path corresponds to the notation \mathsf{a/b/c} used in [BIP32]. However, we do not use any explicit \mathsf{H} subscripts to denote indices of hardened keys; we simply use indices whose most significant bit is set, e.g. 3_\mathsf{H} is index 2^{31}+3.

    Below we lift the key derivation functions from single indices to paths. These key derivation functions on paths designate keys in a tree, starting with a root. All the derivations in the path must be valid (i.e. return no error) in order for a path to designate a valid key; otherwise, as stated in [BIP32], the corresponding key is skipped.

    In our formalization of BIP 32, we use the library type ubyte32-list for paths.