Latest posts of: ykt

Bitcoin Forum

October 01, 2025, 03:04:54 PM

Welcome, Guest. Please login or register.

News: Latest Bitcoin Core release: 29.0 [Torrent]

Home

Help

Search

Login

Register

More

Show Posts
Pages: [1]

1

Bitcoin / Electrum / Re: Is initial xpub scan mandatory when building watch-only wallets?

on: November 03, 2022, 12:31:53 AM

Thank you for your replies, folks. It starts to make a bit more sense now. I ran into an interesting case today with a sample xpub that I'm using - Code: xpub6BkMTgBrwVvFZ8bDfVCKv88Fineb2sy74eNnWBWwe ppSjSmg17bHzrjHBANWASEjKbRuB7KWuyoDMgyFr2YVLSbKLCFLiNc4XbuQUaXXXJa When scanning it with https://github.com/LedgerHQ/xpub-scan, I'm getting bc1 addresses like Code: bc1qvu7duj8v5gu6tq2ysjatvudp8ftm7qzrwk53mj , which shouldn't be a part of the xpub, only zpubs. How does that work?

2

Bitcoin / Electrum / Is initial xpub scan mandatory when building watch-only wallets?

on: November 02, 2022, 12:40:24 AM

Hi, I’m coming from the perspective of someone who would hypothetically like to build service yet another to track all the transactions for a given xpub. And I wonder if there is a way to circumvent initial address scanning. For example https://blockpath.com/wallets/local/101?action=appxpub says Quote This mode will scan over 3915 possible addresses within different possible derivation paths. If a used derivation path is found, we automatically increase the gap limit from 20 to 150 to be sure all used addresses are found. Please be patient. This scan takes about 2-3 minutes to finish! Which seems to be quite a heavy process if I understand it right: - start scanning at 0 depth until gap conditions are met - take all addresses with txs from previous step and scan their deviation spaces until gap conditions are met - repeat The service above provides the following illustration of what it’s doing Code: Paths Scanned: m/0-19+ m/0-50/0-19+ m/0/0-20/0-19+ m/0/0-10/0-10/0-19 Does every watch-only service out there go through a similar procedure? (for example, tax assistance platforms)

3

Bitcoin / Development & Technical Discussion / How to get all addresses and associated txs for an XPUB with Blockchain.com API?

on: October 16, 2022, 01:45:35 PM

Hi, I'm trying to get all addresses and their transactions for an xpub using Blockchain.com API, and right now pretty much drown drowning under the amount of new information So hope somebody can clarify this for me. As a first step, I'm sending a `multiaddr` request like this Code: GET https://blockchain.info/multiaddr?active=xpub... And in return, I'm getting a JSON struct with three keys - `addresses`, `wallet` and `txs` Code: { "addresses":[ { "address":"<sample xpub>", "change_index":10, "account_index":18, "final_balance":0, "n_tx":32, "total_received": <obfuscated>, "total_sent":<obfuscated> } ], "wallet":{ "final_balance":0, "n_tx":32, "n_tx_filtered":32, "total_received":<obfuscated>, "total_sent":<obfuscated> }, "txs":[...] } Every item under the `txs` list has inputs and outputs, and that's about the point where I'm stuck right now. How do I figure out whether this is a "spend" or "receive" transaction in relation to a given xpub and what is the associated address? Thank you.

4

Bitcoin / Bitcoin Discussion / Recurring payments with Bitcoin

on: June 29, 2017, 06:02:40 PM

Hello, As a software developer, I recognize the importance of being able to establish a subscription for the user, i.e. facilitate recurring charges for consumed goods or services. This is the basic requirement for any SaaS platform. The only option that I have seen so far is to send a user an email at the end of the current billing cycle to remind to make next payment and that simply doesn't work. Also, as far as I understand, the only option to have recurring payments is to have them supported by the wallets/network and thus I wonder if it is something that is on the roadmap or not?

Pages: [1]

Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines