Squid Router

The main tables that I have used for Squid data are Flipside's Arbitrum, Avalanche, Binance Smart Chain, Ethereum and Polygon .core.fact_event_logs tables with filtering the origin_to_address to the Squid Router (0xce16f69375520ab01377ce7b88f5ba8c48f8d666 in all chains). So, every Squid transaction and also its users are now extractable from tx_hash and origin_from_address columns. For calculating the $USD volume of transfers, firstly we have to identify the transferred assets via Squid router. For this, We have to filter the event_name column to ‘Transfer’ and origin_to_address to the Squid Router contract. The event_inputs column gives us the value of transfers but since there are multiple events for a single transaction, we have to only extract 1 value for each transaction which can be extracted by filtering the event_inputs:to to the Squid Router address '0xce16f69375520ab01377ce7b88f5ba8c48f8d666' or origin_from_address to event_inputs:from. So, the contract_address column of the result table will be the actual contract address of the Transferred asset via Squid router. I have manually searched the contract address of tokens in each blockchain’s explorer (Arbiscan.io (Arbitrum), Snowtrace.io (Avalanche), BSCScan.com (Binance Smart Chain), Etherscan.io (Ethereum), Polygonscan.com (Polygon)) in order to identify the symbol of the transferred asset via Squid Router. Then, I joined the result table with ethereum.core.fact_hourly_token_prices table in order to extract the USD value and also the Decimals of each token (those which were available). To identify the transfer paths, we have to extract data from the input_data column for each transaction and convert the HEX value of this column to String. Based on the Squid app, There are currently limited available sources & destinations for transfers via this router (more will be coming soon) which are: Ethereum, Avalanche, Arbitrum, Polygon, Binance Smart Chain, Fantom, Celo & MoonBeam. Also, There are different origin_function_signatures for transfers via Squid Router. Call Bridge Call (0x8ca3bf68) & Bridge Call (0x3c659741) is used when the user wants to transfer an asset from one chain to another asset in another chain. Execute With Token (0x1a98b2e0) is used when the user wants to transfer an asset from one chain to the same asset in another chain. So, the extraction process of the destination & source chains from each origin_function_signature is different.

Satellite Bridge

I have used Flipside's axelar.core.fact_msg_attributes table to extract the activity over the satellite bridge. I have used attribute_key column in order to extract data about the origin and the destination of bridges. As far as I understood, the data about the source wallet address of the bridger is not contained within axelar.core.fact_msg_attributes table but the actual destination wallet address of the bridger (as well as its chain) is included in this table. To calculate wallet balance, I had to use ethereum.core.ez_current_balances and osmosis.core.fact_daily_balances tables for Ethereum and Osmosis chains since there is no daily balance table for other chains, Anyway, we can expand the results to the other chains too.

Axelar Post-op Interop