Xpubs don’t create random addresses. They’re a part of the Hierarchal Deterministic pockets construction.
Coinbin makes use of his personal library or wrapper so it might not work as you anticipate when attempting to hack it. To me it appears like you’re feeding an xpub right into a public key to handle conversion which is not how an prolonged public key (xpub) is used.
An HD derivation path appears like m/84’/0’/0’/0 for BIP84 bech32 addresses. The instance code in your query doesn’t comprise any derivation path directions, so you’ll all the time create the identical tackle.
As a way to deterministically create from an prolonged public key you must specify which change and index you’re utilizing within the derivation path which is the final two numbers within the path: m/84’/0’/0‘/0. The m/84’/0′ portion of the derivation path is already encoded in your xpub/zpub.
For instance:
The derivation path for the primary tackle within the keychain could be: m/84’/0’/0’/0
The derivation path for the second tackle within the keychain could be: m/84’/0’/0’/1
The derivation path for the primary change tackle: m/84’/0’/1’/0 …
and so forth.
Though utilizing a distinct library deriving from an xpub ought to look one thing extra just like the under (supply) the place derivation path parameters are wanted:
buidljs.fromXpub("zpub6sCAx5BGhzosvmBsLyj8P1xjQHmuwHMoFm4ykHMmeP16Zn6iKpxy4BBDsHPRj4RsU5YvXigGvnYRYo4n5sA4QH2kgZUoTgQVTmzt5XuC6qD",0,0)
`{addr: "bc1qzsg5xf3kmdrd8629p29vtvj39ep82rhjwx58dh"}`
Observe the final two parameters of the fromXpub operate communicates which change and index from the derivation path we would like, on this case the primary tackle within the keychain.
Additionally simply as a warning, don’t generate “random” derivation indexes. HD wallets have look-ahead gaps which might solely see about 20 tackle forward, sending funds to m/84’/0’/34’/251 for instance might presumably by no means be discovered by a pockets until you had a customized pockets that knew to look there.
