Hello, Zcash, privacy & cybersecurity news fans! A new version of the zCat - the Android app was released! Please check if you run the latest version 0.1.9. What is new? Let's have a look!
Rhea.Finance
NEAR ecosystem made quite some noise around Zcash thanks to the NEAR Intents exchange. Rhea.finance came shortly after to bring more DeFi features to the ZEC holders. It comes with liquidity providing to tokenized ZEC in Rhea's AMM pool or Lending market - similar to these with Aave on Ethereum.
DeFi section
Thanks to this, I could add a new section to the Market screen dedicated to DeFi projects for ZEC. You can find it when you tap the Market option in the bottom menu.

The DeFi Section has two sub-sections:
- Liquidity Pools for AMM
- Lending Pools
Liquidity Pools
Liquidity pools are displayed as the first subsection when the DeFi screen is displayed. Tap on the liquidity pool to see the details of the pool.

Swipe left to see more data sets about the liquidity pool, such as the last swaps, an update of the liquidity in the pool, or basic info about the Rhea project.

Lending Pools
Lending pools allow people to supply liquidity and earn interest rates on their deposits, while borrowers can borrow the deposited funds against their collateral. Currently, there is listed only Rhea lending pool.

You can see the basic statistics of the lending pool how it looks currently, and how it evolves during the time for some key figures.

Experimental implementation
Please be aware of that integration of the Rhea.finance data is mostly based on the sniffed request to their API. Maybe there is a better way how to fetch the data, but I needed to build a collector on the server side to pre-process the data. That means that it will work as long as they do not change the API used for their own UI. With the previous experiences with DeFI on Ethereum and other EVMs, this can change anytime.
Tor traffic
This looks like a neverending story. The stability and usage of the official TOR android library became quite a challenge. After the last update of the pURL app, I tried to apply lessons learned to try to improve TOR stability and handling the requests.
Binding the service to activities looks like leaving some memory leaks and crashes on rebinding/reconnection. I tried to attach the service to the context of the whole application rather than the activities themselves. This looks like a workaround that can survive for the whole lifecycle of the app. The complexity built around it will need to be simplified, so please bear with me for now since it may lead to unexpected behavior in some cases.
tl;dr
- Experimental support to track Rhea.Finance
- Tor traffic adaptation
- Smaller layout fixes
Conclusion
This update is focused on the Rhea finance integration and on the TOR traffic usage. This was originally planned for Easter, but as every dev, I suck with estimations. Please try and criticize. Any feedback is appreciated.
P.S. Thanks for the offers for help. But right now, I am in such a state that I need to clean up some of my mess.

