BIP 392 fixes its silent payment descriptor examples to use the BIP 352 scan and spend paths
The draft BIP 392, which defines output script descriptors for silent payments, has corrected two of its examples. The commit by the BIP's author, Craig Raw, was merged into the bitcoin/bips repository on 9 November.
Silent payments, specified in BIP 352, give a receiver a static address while each payment lands in a fresh, unlinkable taproot output. A receiver needs two keys: a scan key to find incoming payments and a spend key to move them. BIP 392 adds a top-level sp() descriptor so that wallets can describe, back up and restore that key material in the descriptor framework other wallets already use. It accepts either a single bech32m-encoded key, spscan for watch-only use or spspend for a full wallet, or two separate key expressions for scan and spend.
The fix concerns the second form with BIP 32 extended keys. BIP 392 says that when key origin information is given, the scan and spend keys come from the child paths recommended in BIP 352: 1h/0 for scan and 0h/0 for spend. The old examples did not follow that. The watch-only example showed an extended private scan key and an extended public spend key both ending in /0h, and the full-wallet example derived both private keys the same way. The corrected watch-only example now reads sp([deadbeef/352h/0h/0h/1h]xprv.../0,[deadbeef/352h/0h/0h/0h]xpub.../0), and the full-wallet example uses xprv.../1h/0 for scan and xprv.../0h/0 for spend under the same origin. Two lines changed; the specification text itself did not.
BIP 352's own reasoning for these paths is that hardened derivation lets a wallet export the scan private key, which a scanning server needs, without exposing the master key or the spend key.

Why it matters
Examples in a BIP are what implementers copy. A wallet that followed the old ones would have produced descriptors that point at different keys than a BIP 352 wallet derives from the same seed, so a backup might restore but never find its payments. Fixing it while BIP 392 is still a draft keeps that mistake out of shipped code.