Showing posts from February, 2020

Has Tiffany Hayden been spreading FUD lately?

After a discussion with her, my conclusion is that there is a chance that she genuinely believes that she is not spreading FUD. But it's also not hard to see why many people see it that way. The discussion happened here: Something has happened to @haydentiff . This is for sure. I don't know what it is though. If this is not fear-mongering, I don't know what fear-mongering is. First, why would Ripple abandon XRP. Second, no validator would do that because it won't work. — r0bertz (@r0bertz) February 10, 2020 The initial tweet reflected my thought at the time I was posting the tweet. I am not going to change it. So now let me summary how it went. In the so called "FUD" tweet, Tiffany described a scenario "If Ripple abandoned XRP, the validators would vote to increase reserve to 25K XRP to freeze almost everyone else so we could cash out first". My response was: Ripple won't abandon XRP because it has every i

ripple-client-desktop ported to RippleAPI

Disclaimer: this work is provided "as-is" and is not endorsed by or affiliated with Ripple Inc. in anyway. RippleAPI was one of the APIs (the other one is core API) in ripple-lib  before version 0.13.0 which was released in 2015 and has been the only API since 0.13.0. ripple-client-desktop  was abandoned by Ripple Inc. in 2015. By the time it was abandoned, it could only work with core API. I started porting it to RippleAPI in late 2018.  The progress was recorded in this twitter thread: This weekend I tried to revive ripple-client-desktop. l I have reached a point at which I can run gulp without any warning on the command line. However, the app stuck at loading. Then I figured out that the client uses an ancient ripple-lib API. — r0bertz (@r0bertz) December 17, 2018 You can download the executable files at this link: If you want to try it, please try it with testnet account, account with small balance