XRP Ninja

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. https://t.co/g6CDp1Gkiq — 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

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: https://github.com/r0bertz/ripple-client-desktop/releases If you want to try it, please try it with testnet account, account with small balance

I just published the scripts that I used to prepare tax for XRP sales. With no or minimal changes, it should work for any crypto, any exchange. The repo is at https://github.com/r0bertz/node-xrp-tax Below is the contents of README.md: XRP Tax This is a collection of scripts to prepare tax for crpyto (not necessarily XRP) sales. A majority of this project deals with XRP Ledger, so it is called "XRP Tax". The end product is a csv file that can be uploaded to http://www.easytxf.com . Things to note Terminology: Symbol : The currency being traded. Currency : The currency you paid/got when buying/selling Symbol. USDT is considered USD. The csv format (except that of the end product) is bitcoin.tax format 1 . The Source column is overloaded. If Action is SEND, Source is actually destination. Only LIFO (Last-In, First-Out) method is implemented. LIFO method is universally applied for a Symbol no matter where the trade actually happened. Like-kind exchange

I just made a website https://orderbook.xrp.ninja . I have explained why I did it in the front page. I am going to record some of the problems that I had and how I solved them in this post. Prod code doesn't work The code works in development mode. But it doesn't after minified. The error message was: Uncaught Error: [$injector:modulerr] Failed to instantiate module rp due to: Error: [$injector:unpr] Unknown provider: e I found a post on stackoverflow and fixed it like this . Add domain to an existing Letsencrypt cert $ certbot certonly --cert-name rippled.xrp.ninja -d rippled.xrp.ninja,ripple.xrp.ninja,www.xrp.ninja,xrp.ninja,orderbook.xrp.ninja Redirect http traffic to https on lighttpd Add this to lighttpd.con and also enable mod_redirect . $HTTP["scheme"] == "http" { # capture vhost name with regex conditiona -> %0 in redirect pattern # must be the most inner block to the redirect rule $HTTP["host"] =~ ".*&qu

https://www.npmjs.com/package/gulp-bash-completion I tried this. I followed the instructions on the above page, but it didn't work. Then I did the following and it worked: Locate the gulp-completion.bash file installed by the package. Change the echo_gulp_tasks variable in gulp-completion.bash file to gulp --tasks-simple Copy gulp-completion.bash to /etc/bash_completion.d and source the file in current shell. Now try type gulp [space] and hit [enter] , the completion should work. At this time, this npm package is no longer required. So you can uninstall it.

Update: as of Jan 15, 2019, trading is working. https://github.com/r0bertz/ripple-client-desktop The first goal is to make it fully functional with RippleAPI . Current status is most read only operations are working except order book. Please follow this twitter thread for the most recent updates: 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

As you may know, my rippled validator runs on GCE. So I use stackdriver to monitor it. I created two custom metrics for it. One metric is uptime with rippled version as a label. Here's a live graph for this metric. From this graph, you can easily tell what the current version is and when it was upgraded to that version. You can also correlate this with other graphs to see if new version may have caused certain changes in rippled behavior. The other metric is the percentage of current uptime that rippled has been in a certain state. Normally the curve for "full" state should asymptotically approach 100. If it is not, then rippled is in trouble.