McCoy on Nostr: BIP45 doesn’t introduce a new extended key prefix because: It works with standard ...
BIP45 doesn’t introduce a new extended key prefix because:
It works with standard xpubs (or ypubs/zpubs if the multisig is wrapped in SegWit or native SegWit, though BIP45 itself was designed around P2SH).
It’s a layer above key format. The xpub/ypub/zpub tells you what address type the key produces; BIP45 tells you how multiple people agree on which addresses to produce.
Published at
2026-07-15 20:13:56 UTCEvent JSON
{
"id": "4d8c5312245d9c9d8ba04c524633e4d8e2f8a53cd771cec3f617447c9ace37a7",
"pubkey": "392316041be345b2bac5c4d1f44c7701385d62bfaac742d94273d10a6434eaac",
"created_at": 1784146436,
"kind": 1,
"tags": [
[
"client",
"Primal iOS"
]
],
"content": "BIP45 doesn’t introduce a new extended key prefix because:\n\nIt works with standard xpubs (or ypubs/zpubs if the multisig is wrapped in SegWit or native SegWit, though BIP45 itself was designed around P2SH).\nIt’s a layer above key format. The xpub/ypub/zpub tells you what address type the key produces; BIP45 tells you how multiple people agree on which addresses to produce.",
"sig": "6f0e8fb0e2fed2dd632c3f068756211bbf1862e2b22a220bd829cb750c33cd5002a56c84bae8ec53689fb93def200b6279f7ee6f226b4ed9d62f08b0e6607c2b"
}
