Bitcoin Forum
May 04, 2024, 03:32:39 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: January 07, 2021, 05:25:06 AM
I was able to locate the address on Ian Coleman by using my YPUB in the BIP32 Root Key and then going to BIP 141 and changing the Script Semantics to P2WPKH and the address is there
In addition to the depth field as per the decoded key in pooya's post... When you put the YPUB in as the BIP32 Root Key, what is the "BIP32 derivation path" showing under the "BIP141" when you can see your address? Huh

So I cheated, I had a more technical friend help me out and ultimately as discussed he made me find it using the Bip 32 Root key derived from my YPUB and going to Bip 141 and then if we changed the script semantics to P2WPKH the address was there. He then had me upload my mnemonic offline and get the private key for that specific address and we imported it into Electrum and got it out.

According to the exchange "We convert the extended public key according to the user selection (3... or bc1...), because the x/y/z stuff is not set in stone but a loose convention. For example, some wallets produce "x"pubs even though they should by "z"pubs - so we can't rely on the "x" or "y" or "z" input. Therefore the user's selection is very important. Since you selected bc1 here, it impacted our derivation path."

They said they will make a change to their service and make users type and confirm the address prior to approving the Y/XPUB.
2  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: January 04, 2021, 07:06:59 AM
Is this only something that Swan can tell me because for me it’s a needle in a haystack scenario?
Yes, that is something that they can tell you easily by knowing how their platform works under the hood. Otherwise you will have to go through the most common derivation paths one by one to see if you can reproduce the same address. That is assuming their system didn't have any bugs and didn't give you a wrong key that can't be reproduced through conventional methods.


I was able to locate the address on Ian Coleman by using my YPUB in the BIP32 Root Key and then going to BIP 141 and changing the Script Semantics to P2WPKH and the address is there, but when I put my mnemonic in to try and get the private key it changes the paths and I cannot pull of the private key for the address which I hoped to import into Electrum and get the BTC the hell out of there..I guess I am getting closer..
3  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: January 03, 2021, 03:22:43 PM
Is this only something that Swan can tell me because for me it’s a needle in a haystack scenario?
Yes, that is something that they can tell you easily by knowing how their platform works under the hood. Otherwise you will have to go through the most common derivation paths one by one to see if you can reproduce the same address. That is assuming their system didn't have any bugs and didn't give you a wrong key that can't be reproduced through conventional methods.

Got it. I’ll keep you posted they are looking into it Monday.
4  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: January 03, 2021, 06:34:05 AM
so I do not know how they got a bech32 from the YPUB ?

xpub, ypub, zpub strings don't add any kind of restriction on the type of address that can be derived from the extended key. They are more like guidelines, otherwise the actual data they contain (public key + chaincode) that is used in deriving keys is the same for all of them. The interpreter has to check the version int and decide which address type to derive from that data, which it fails in this case to check it.

Thank you. I didn’t really know that was possible. So my question is how’d I locate the BTC? That seems to be what they did they took my YPUB created a Bech32 series of addresses but I can’t recover it. Is this only something that Swan can tell me because for me it’s a needle in a haystack scenario?
5  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: January 03, 2021, 02:06:12 AM
I was able to recreate what I did and it was the YPUB not an XPUB (Just like the sample posted), and it was all bech32 addresses that were produced for wallet addresses that the funds would be sent to.
This is indeed quite confusing....

XPUB = Legacy ("1" type) Addresses
YPUB = Nested SegWit ("3" type) Addresses
ZPUB = Native SegWit ("bc1" type) bech32 Addresses

Quite how you got bech32 addresses from a YPUB master public key is a mystery... it would point to some sort of issue within the code/library generating the addresses, as it is technically doing "non-standard" things Undecided


I must be screwing up the derivation path. I'm putting in m/84'/0'/X' (X representing the account # on my Trezor) but nothing.
Note that "X" should not be the same as the account # in the Trezor wallet... the derivation path is 0-indexed... so "Account #1" on the Trezor is actually m/84'/0'/0'... "Account #2" would be m/84'/0'/1' etc.

So I emailed them to get this raised up because I am concerned that this point that this is just not operator error (me). I put in the derivation as you listed above and nothing. I used the Ian Coleman tool offline and generated the YPUB that I had uploaded to them and it only produces "Nested SegWit" (3 type) so I do not know how they got a bech32 from the YPUB ? I still created the ZPUB corresponding with my Trezor just to see and that address that they sent the BTC to was not produced. So I think I have a problem. I have emailed them and they are raising it but I really thank everyone who responded for at least confirming that I am not just making some obvious error.

The BTC is just sitting in the wallet.

Regardless of what happens I will update this thread with the outcome.
6  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: January 03, 2021, 01:53:00 AM
They don't look like a scam to me.

Regardless of whether they have bad intentions or not.
I wouldn't trust a new exchange with no history, no security audits, nothing.

When trusting a centralized service with your money, i'd at least go for trusted ones with good security practices which exist longer than a year.

I understand. Ironically my intentions were pure to go with a smaller startup that is more grass roots bitcoin only. And the people behind it are reputable I just hope that my issue is not some type of their code/library issue like HCP indicated.
7  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: January 02, 2021, 03:33:22 AM
Happy New year.

Thank you for the replies.

I was able to recreate what I did and it was the YPUB not an XPUB (Just like the sample posted), and it was all bech32 addresses that were produced for wallet addresses that the funds would be sent to. The first addresses listed is where the BTC was withdrawn to, but I still cannot locate the BTC via Electrum. I must be screwing up the derivation path. I'm putting in m/84'/0'/X' (X representing the account # on my Trezor) but nothing.
I used Swan because they are good to stack (daily/weekly) and just automatically have it sent to cold storage. Instead of selecting most compatible I chose cheapest transaction cost which is why it was sent to the bech32.

I will use the tools provided to see if I can sort out how to get my hands on the BTC. 

8  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: January 01, 2021, 02:18:11 AM
They are 100% legit. I reenacted loading the YPUB to their site and I have the right YPUB and the deposit address is listed as the first address BUT I cannot pull it up and access the address and the funds. Again, I have been using BTC since 2016 but this one got me.

https://www.swanbitcoin.com/
9  Bitcoin / Bitcoin Technical Support / Re: XPUB Debacle on: December 31, 2020, 09:32:36 PM
It’s Swan they “don't store the xpub that you uploaded, because doing so would be a privacy issue. Instead, it statelessly generates the addresses in your browser.”

I’ve been happy with them and like their  service. I just don’t know where the BTC went and they don’t store XPUB so I’ve looked at all the possible derivation paths for the wallets on my Trezor and Ledger using Electrum, but still nothing.  The BTC is just sitting there. I’m gonna keep trying to locate where it could’ve landed the next few days.

I made the mistake of setting this up at 1:30 am and was not thinking about address types etc I saw the Bech32 address and I confirmed it so ultimately it’s on me but I just don’t know where the BTC landed.
10  Bitcoin / Bitcoin Technical Support / XPUB Debacle on: December 31, 2020, 06:23:15 AM
I’m not new to BTC but not very technical ..just enough to get myself into trouble. I signed up for an exchange that offered automatic threshold withdrawals and you had an option to enter your XPUB to avoid address reuse. I opted for this and late one night I either used my Ledger or Trezor to enter my XPUB.  An automatic withdrawal was made I confirmed it, and although I noticed it was a bech32, I didn’t realize that it was odd. When I went into my Trezor,  the transaction couldn’t be found. I hooked it up to Electrum thinking that somehow the derivation was screwed up but nothing. I checked my Ledger and nothing.

I know I provided the XPUB from one of these 2 devices and most likely the Trezor. I have no idea where the bech32 address came from. The exchange says they don’t store the XPUBS and told me that a Trezor wouldn’t provide a bech32. The address and the funds are on the blockchain and have not been moved. I have not been the victim of any SIM swap or other fraud.

It wasn’t a tremendous sum but enough that it’s pretty irritating. Any thoughts other than I’m an idiot are greatly appreciated.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!