Jump to content

xrp transaction not found


underscanrp
 Share

Recommended Posts

Hi, i transferred xrp to my other wallet, it's been 8 hours and still didn't receive my xrp . I checked the hash and it says, transaction not found. I entered the tag, this is the first time i experienced this. Please help, here's the hash;

E934626B223B3925E64175901018EE4C3E72579CF877E7E943CE42927F263EA7

https://xrpcharts.ripple.com/#/transactions/E934626B223B3925E64175901018EE4C3E72579CF877E7E943CE42927F263EA7

what i'm supposed to do ?

exchange.JPG

Link to comment
Share on other sites

39 minutes ago, underscanrp said:

Hi, i transferred xrp to my other wallet, it's been 8 hours and still didn't receive my xrp . I checked the hash and it says, transaction not found. I entered the tag, this is the first time i experienced this. Please help, here's the hash;

E934626B223B3925E64175901018EE4C3E72579CF877E7E943CE42927F263EA7

https://xrpcharts.ripple.com/#/transactions/E934626B223B3925E64175901018EE4C3E72579CF877E7E943CE42927F263EA7

what i'm supposed to do ?

exchange.JPG

If this was off an exchange and it hasn’t arrived then contact the exchange.  They didn’t get it submitted properly to the XRPLedger.

If it’s off a wallet then there is no problem.  It sent or it didn’t.  Look at both accounts in xrpscan or Bithomp.  It can’t be lost….    just sent or not sent.

 

Link to comment
Share on other sites

16 minutes ago, underscanrp said:

OK thanks i will contact the exchange it's so weird happens to me for the first time .

 

 

If it’s from an exchange then yeah….  you gotta contact them.  The XRPLedger just works….   if it’s submitted properly then three or four seconds later it’s at its destination.

All of the rest of any time it takes is the exchange….  XRPL itself is faultless and three seconds.

Link to comment
Share on other sites

Lots of exchanges behaving like this, these days. They say they sent it but simply didn't. Unless if there are approval/AML scan/.../review reasons (in which case they should state "pending" instead of "sent"), I think it's because they either didn't get their XRPL implementation right, or they are cheap and use public nodes instead of their own XRPL node (as the public ones can be quite busy at times)

Edited by Wietse
Link to comment
Share on other sites

12 hours ago, Wietse said:

Lots of exchanges behaving like this, these days. They say they sent it but simply didn't. Unless if there are approval/AML scan/.../review reasons (in which case they should state "pending" instead of "sent", I think it's because they either didn't their XRPL implementation right, or they are cheap and use public nodes instead of their own XRPL node (as the public ones can be quite busy at times)

Even if the transaction fails in any way possible, aren't the exchanges supposed to validate if the transaction was successful or not before telling the user the transaction was sent?

if you ask me, it doesn't matter if they run their own validator or not IF they had checked the transaction's validity :/

Link to comment
Share on other sites

3 minutes ago, wojake said:

Even if the transaction fails in any way possible, aren't the exchanges supposed to validate if the transaction was successful or not before telling the user the transaction was sent?

if you ask me, it doesn't matter if they run their own validator or not IF they had checked the transaction's validity :/

Which is what I mean by "didn't get their XRPL implementation right" ;) They simply don't RTFM. For most, both apply (didn't implement correctly & using public nodes)

Any arguments about batches & sequence numbers & parallel transaction processing are invalid now as well, as the Ticket amendment went live. They can create a Ticket, pre generate Sequence numbers and just submit them all at once. If one fails, the other sequence numbers are still valid even if there is now a gap. 

But with close to 0 exchanges supporting AccountDelete deposits (around for ages), most exchanges still screwing up Destination Tags (recipient account configuration, calling it "memo", etc.) I have a hard time believing these exchanges will ever really step up their game :( 

Edited by Wietse
Link to comment
Share on other sites

6 hours ago, Wietse said:

Which is what I mean by "didn't get their XRPL implementation right" ;) They simply don't RTFM. For most, both apply (didn't implement correctly & using public nodes)

Any arguments about batches & sequence numbers & parallel transaction processing are invalid now as well, as the Ticket amendment went live. They can create a Ticket, pre generate Sequence numbers and just submit them all at once. If one fails, the other sequence numbers are still valid even if there is now a gap. 

But with close to 0 exchanges supporting AccountDelete deposits (around for ages), most exchanges still screwing up Destination Tags (recipient account configuration, calling it "memo", etc.) I have a hard time believing these exchanges will ever really step up their game :( 


I agree with the lack of confidence in exchange integration improvements but speak up in defence of those greedy mfrs.   :) 

 

With so many new chains now,  and so much fast development and demands for new chain integrations,  it must be very hard to get around to fixing things that are limping along moderately well.

 

And employing more developers would eat into their golden faucet of profit flow so that’s just another crazy dev idea that won’t fly.

 

Hmmm,    maybe my defence of them is somewhat ambivalent.   :) 
 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share



×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.