Jump to content

at3n

Member
  • Content Count

    493
  • Joined

  • Last visited

1 Follower

About at3n

  • Rank
    Regular

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm sorry to hear that, I hope you didn't lose too many XRP. To make sure you're aware, the real Toast wallet is discontinued and no longer available. The destination address you posted certainly looks like it's related to a scam. Lots of deleted accounts sending XRP there as their final act You could help the community by reporting the address here: https://xrplorer.com/forensics/submit/r3Ke7BFJGeB7gBZT2r4fpquFXLQmtMWb6V and providing as much detail about the scam as possible.
  2. I believe so, it's the same one I have, although I've never actually used it. I followed the links from Wietse's Twitter (the developer) and ended up at the same app so I think it's the right one. Still, don't trust me, make sure you trust it before you download.
  3. Do you mean that you now have 0 XRP in the account? That would be strange because that error should not cause anything to be taken from the account. If you look up your wallet address on Bithomp.com, does it show any transactions that may have caused this? Also, are you sure you're using the real Toast wallet? There's at least one fake scam version available at the moment, called "Toast Plus".
  4. When you transfer to an exchange, you do not activate a new XRP address on the exchange. You send the XRP to the same XRP address as everyone else on the exchange, and the destination tag helps the exchange assign your XRP to your account. Because of this, you do not lose 20 XRP on the exchange. You only lose the 20 XRP left behind in the wallet that you send from. This doesn't work with at least some exchanges, because the delete transaction is different to a payment transaction and the exchanges' systems don't recognise it.
  5. Yes, unfortunately this does appear to be a scam company, I'm sorry to hear about your loss. See this thread for some more information:
  6. Try not to panic, there's clear evidence that their transaction failed and it's their fault, it's easy to prove it. I'm sure that once they have had time to check, they will put the XRP back in your account.
  7. What's your question?
  8. In the case of the typical Gateways on the XRPL, such as Gatehub (which is Party A in this case): Party B first sends the IOUs back to Party A, and then Party A delivers the underlying asset to party B (by bank transfer, or crypto transaction, depending on the IOU).
  9. @Sharkey There can be multiple "issuers" of the same IOU on the XRPL. This is represented by a dot after the IOU name, followed either by the name of the issuing entity, or by the address of the wallet that issued it. So for example it's vague to say that you own USD on the XRPL, but accurate to say that you own USD.Gatehub or USD.Bitstamp. Before you trade on the DEX, you should be made aware by your wallet software who the issuer of that particular IOU that you're buying is. The issuer is the entity that "owes" you the value of the IOU. Even though you may have no contract with Bit
  10. I'm pretty sure that Gatehub stores your wallet information in encrypted form, and they don't store the decryption key. The only way to decrypt it is with the recovery key or the password, and if you lose both of them, Gatehub should not have the ability to do a reset, even if they wanted to. However, you should open a support ticket with them to check.
  11. Do you control the issuing address of the IOU? If so, then the information is here: https://xrpl.org/transfer-fees.html. Use an AccountSet transaction to set the TransferRate field. The fee is returned to the issuing wallet. This only works in percentages though, I don't think you can set a fixed fee. For anything more complex I think you'll need to create an off-ledger solution.
  12. It potentially means that something is sitting in between you and the Ledger servers attempting to listen to or modify your communications. It may be some sort of firewall/antivirus (especially if you're using a work computer), but it could easily be malicious and you should proceed with extreme caution. Whatever it is, it may be able to read all of the data you send to all websites and online services, even encrypted data to HTTPS sites, including usernames, passwords and two factor authentication. From a security point of view, you should stop using this computer/phone for anything
  13. I think the biggest challenge to deciding when to lower the reserve is that it will subsequently be much harder to raise it again in response to a significant price drop. If the reserve is ever raised again, then inevitably you're going to be locking people's XRP in the higher reserve, which I think should ideally never occur (angry users/bad PR: "Ripple locked my XRP" etc...). Not to mention the fact that some people may actually be impacted personally by losing access to even a small amount of their assets like that. So if I was running a validator and voting on the reserve, I'd want to
  14. This is a good point. Although it's not Ripple's fault, it's understandable that the blog post may contribute to this happening. A reminder in the post that this isn't the same transaction type as a payment, and may not be correctly handled by exchanges, would be a good addition IMO. @mDuo13 would you consider updating the blog post with a warning (if you can)? @QuopiusHave you asked the exchange if they will send it back to you manually?
  15. Yeah you'll need to replace that reference as you noticed. Just replace bf.getCaseNumber() with a 1 or something, I think that will work, it's not important, just for displaying the progress bar which isn't needed anymore as you only want to try one password.
×
×
  • 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.