Secret key

[Mikedizzle]

[Vertigo]

Thats two different wallets.. your point?

[cmbartley]

https://bithomp.com/explorer/rJSvXGdzougCwUo8odLk7MpGjjWhriyt5u

[Mikedizzle]

Somehow there are two ripple addresses attached to my secret key. I know this because I used desktop wallet and imported the secret key and it gave me a different address. I also tried importing my wallet to a new one in gatehub using the secret key and the address that has all the xrp is different from the address attached to the secret key. There is a glitch I just want my money safe. At this point I have tried the desktop wallet, ripple client and any other measure. I can't exchange to usd because it says invalid secret. Then I can't send funds because it says "disabled, watch only", I cannot connect trust lines, or connect to gateways. It seems to me that the secret key I was assigned is not the one assigned to my ripple address that has my funds, please reference the pictures. Any developers out there please help a brother out, it seems like gatehub is either busy or idk but they haven't got back to me about it in a while. 

 

 

[Roborovskii]

Perhaps Gatehub UI is showing you the wrong secret key in the 2nd photo (the one with your funds). Therefore using that secret key anywhere else, accesses the other account (with 20xrp). Have you tried logging out, clearing your browser of all cache, reboot and checking the secret key again? Perhaps it would show the correct one.

@enej

[Mikedizzle]

Yeah I tried that, it is still the same. On different computers too. 

[Mikedizzle]

@Vertigo two wallets, two addresses, same secret key. 

[Roborovskii]

So on the desktop wallet, the secret key gave you the account with 20xrps? Then I do believe that somehow your secret key for your main account is not showing correctly on gatehub. Hopefully they can check into it soon.

[Professor Hantzen]

Try putting the secret key in here the top field here:

https://jatchili.github.io/minimalist-ripple-client/

Then click "set identity".  One of the public addresses will come up.  You can be absolutely sure that the address that comes up is the one associated with that secret.  The above interface (source here:  https://github.com/jatchili/minimalist-ripple-client ) is the most bare-bones way I know of to check a secret keys associated public ripple address online. 

I'm guessing this is just some gatehub or browser display quirk/bug.  (For if it's not, then its possible all crypto in the known universe is broken...)

In the meantime - don't send anything to the other address!  Meaning, the one for which you don't apparently have the secret key.

[Guest]

I actually noticed the same thing as OP when fiddling around with paper wallets. I'd make a wallet in the ripply-eu paper wallet then copy it into the the jatchili minimalist client and the public key was different when I set identity. I did this one day and kept getting this behaviour but haven't been able to replicate it since. I thought it might have been some sort of deterministic wallet and they were both valid addresses for the key but one wallet client wasn't giving me the first address. I didn't use those wallets or test them with XRP though and wallets I made subsequently didn't seem to do this. My other though was that i'd somehow got a key generator that wasn't legit generator (which is why I compared the public keys in the first place to verify)

Edited April 7, 2017 by Guest

[Mikedizzle]

@Professor Hantzen I did that with ripple client and it says the identity could not be established. 

[rho12]

I have exactly the same issue, two wallets , 1 secret key and i don't have the right secret for the watch only wallet (where my funds are)

[Mercury]

If your feeling trustworthy maybe share your secret key with someone and see if they can make it work. If they can you can always move the funds to a new wallet

[cmbartley]

4 hours ago, aaksut said:

I actually noticed the same thing as OP when fiddling around with paper wallets. I'd make a wallet in the ripply-eu paper wallet then copy it into the the jatchili minimalist client and the public key was different when I set identity. I did this one day and kept getting this behaviour but haven't been able to replicate it since. I thought it might have been some sort of deterministic wallet and they were both valid addresses for the key but one wallet client wasn't giving me the first address. I didn't use those wallets or test them with XRP though and wallets I made subsequently didn't seem to do this. My other though was that i'd somehow got a key generator that wasn't legit generator (which is why I compared the public keys in the first place to verify)

@enej is working on this in another thread. But it might be interesting to have Ripple devs theorize as to how multiple public addresses may come to be associated with the same private key this might happen on more than one platform (Gatehub, jatchili, Ripply). @Tim @JoelKatz @nikb? I have a suspicion that it might have to do with two different cryptographic curves, secp256k1 and Ed25519 but I really have a very thin understanding of all of this. Perhaps @Sukrim or @T8493 have ideas about how this might happen?

Here is the other thread where this is being discussed. 

 

Edited April 7, 2017 by cmbartley

[Mercury]

2 minutes ago, cmbartley said:

@enej is working on this in another thread. But it might be interesting to have Ripple devs theorize as to how multiple public addresses may come to be associated with the same private key this might happen on more than one platform (Gatehub, jatchili, Ripply). @Tim @JoelKatz @nikb? I have a suspicion that it might have to do with two different cryptographic curves, secp256k1 and Ed25519 but I really have a very thin understanding of all of this. Perhaps @Sukrim or @T8493 have ideas about how this might happen?

Here is the other thread where this is being discussed. 

 

Yeah, I was considering merging the threads, but the other seems to be handled by @gatehub and this one had other members chiming. I too would be curious as to why this issue seems to popping up so often