Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won

  1. T8493

    Safari/Key Bug Update

    This new C++ library doesn't have a command line tool which would generate a secret key?
  2. T8493

    Safari/Key Bug Update

    We don't know exactly what caused this bug. It looks like only ancient versions of ripple-lib have this bug, but more recent versions (starting with versions published way before this bug was reported on this forum) work ok. RL has added some code in ripple-lib which could catch such bugs in browsers. (this is the state from the last time I looked at this problem). The main problem with this bug is that some wallets (notably Jatchilli's wallet) still use ancient versions of ripple-lib.
  3. T8493

    Best practices for the security of your wallet

    Just give them your secret keys. Then they can create another key.
  4. T8493

    Validator not running consensus

    Is there something wrong with your setup? What doesn't work as expected? I'm not sure this observing mode can be controlled with the configuration variables.
  5. Who canceled the transaction? Exchange? Some exchanges don't allow sending XRPs to non-activated accounts.
  6. Where did you enter your tag? I couldn't see any field in the UI for the destination tag.
  7. T8493

    XRP recovery on Ledger Nano S

    If I remember correctly, there are some command line on github that can be used to sign transactions without having access to your Ledger. Just search this forum or post a new topic and maybe someone will post a link.
  8. By the way, this topic is labeled with the following tags: xrp fail scam xrpscam network down I'm removing all of them.
  9. This video just proves you didn't include destination tag and nothing else.
  10. There's no need to make a video. Your transactions are recorded on the ledger, but they failed.
  11. His transactions failed with the error tecDST_TAG_NEEDED They are clearly visible on xrpcharts.ripple.com https://xrpcharts.ripple.com/#/transactions/B4C05A27575A9DAF4A6CCE9E48A52DC56E9EF701F445AE14D46441C5F409B539
  12. Maybe you could post transaction id here so that we can investigate.
  13. He claimed that network was down without providing any reasonable proof.