Hot answers tagged

5

The balance checks are cut short based on a gap limit. A gap limit is usually set to 20, and is defined as a consecutive block of addresses with no transactions. Since HD wallets only give out a new address on explicit request, or automatically when the previously issued address has been used, it is assumed that someone will not leave a block of 20 ...


2

It all depends on the wallet. There is no rule saying they should even accept these strings or know what they correspond to and there is no consensus among wallets. Wallet A could accept zpub and know the desired path and script type while wallet B may accept the same zpub, ignore its version byte and use the default derivation path and a completely ...


1

Not all wallets are the same, but a good wallet should always follow standards. A standard for address-generation generally accepted is BIP44. In this way, you could scan the first consecutive addresses that a BIP44-compliant wallet would create. If the wallet supports Segwit, then you should look at BIP49 and BIP84 as well. As Raghav Sood pointed out in his ...


1

The zpub you get from electrum will be at that path itself (m/84'/0'/0'). It's not at m. You can't derive hardened paths from a zpub anyway. If you create a watch only wallet using the zpub electrum will treat it as m and derive public keys and addresses at m/j/i where j is 0 for external (receive) and 1 for change addresses and i is the index. In actuality ...


1

The base58.b58decode and base58.b58encode functions only do the Base 58 decode/encode. However xpubs are encoded with Base 58 Check encoding. The difference is that Base 58 Check encoding computes a checksum of the payload and appends the first 4 bytes of that to the payload before the base 58 encoding. You need to be using base58.b58decode_check and base58....


1

it seems like the process to calculate a checksum for an extended key is to decode the base58 string to data, If raw_xpub = version + depth + fingerprint + child + chain + DATA than to make the checksum you need to do doublehash of xpriv/xpub (sha256), in python: hashed_xpub = hashlib.sha256(raw_xpub).digest() hashed_xpub = hashlib.sha256(hashed_xpub)....


1

There are different explorers that support xpub that will show history as well as balance blockonomics blockpath smartbit


1

The easiest solution would be to use your Ledger via Electrum - it supports hardware wallets, will let you set the derivation path to match your address type, and has no limits on the history displayed.


1

Addresses derived by an HD wallet are intentionally not publicly linkable to one-another (that would be obviously terrible for privacy). Your wallet software will know the addresses are related (ie, it derived them all from the same seed), but a casual observer will not. Accordingly, when you pay some bitcoin to a child address, there is no associated ...


Only top voted, non community-wiki answers of a minimum length are eligible