Sushiswap

Sushiswap is a decentralized exchange that has been created as a fork of Uniswap a few years ago.

Since then it implemented many new features that did not make it into Uniswap. SUSHI staking, Kashi lending, Miso token launchpad just to name a few.

Besides Ethereum Sushiswap has been deployed to other EVM-Chains and also to major L2 scaling solutions for Ethereum.

One of those is Arbitrum, a optimistic rollup framework that allows users to save fees and still enjoy the safety of the Ethereum blockchain.

With address / contract labels for Arbitrum still being incomplete within Flipside and also the Arbiscan explorer,

I will do my best to provide the required knowledge and possibly tooling to allow them to add those labels.

Identifiying Sushiswap Kashi Pairs on Arbitrum

Finding all Kashi pairs ended up being a lot more challenging than the swap pairs.

• I did not manage to find an analytics endpoint
• While there is a Kashi pair master contract it is not used to create pairs and does not hold the addresses of each existing pair

Those issues rule out 2 of the 3 method used to identify swap pairs.

So the first approach was the one I had to go for.

LogDeploy event

Each time a Kashi pair is created a LogDeploy event is emitted in the BentoBox contract. (Example Transaction)

Filtering for the origin being the BentoBox contract is important as some cauldron contracts seem to be emitting an event with the same topic0.

Both the master contract and the clone kashi pair address are part of the event data.

As the flipside tables do not contain less recent data they do not include the events of kashi pairs being created.

But there is an alternative available: The Arbiscan API.

Using that API you can filter for all events from a source address & containing a certain topic0.

Having those kashi pair addresses we can use the node rpc api to read the asset, collateral erc20 contracts and then read the symbol, name, decimals from those contract respectively.

I have added that mechanism to the tool I created for the swap pairs.

The application I wrote can be found here, the results including pair address, token addresses, decimals, name and symbol can be found in this gist.

A few statistics

There only are 24 kashi pairs deployed on Arbitrum.

Note

Due to the tables on flipside still being in lite mode and only a short timespan being available all the metrics will be referring to the week from 2022-06-27 to the 2022-07-03. (both sides inclusive)

Result

No kashi pairs did find use within that week.

(At the time of writing there is not a single borrow in the entire flipside Arbitrum database)