Prime Protocol
Tracking On Chain Metrics for Prime Protocol. Prime Protocol is revolutionizing decentralized finance with its cross-chain native prime brokerage. Users can borrow assets on any chain using their complete portfolio, backed by Axelar technology.
Introduction
Prime Protocol is a multichain defi with its cross-chain native prime brokerage. Users can borrow assets on any chain using their assets in their portfolio, backed by Axelar. The platform has launched on Arbitrum, Avalanche, and Ethereum Mainnet, enabling seamless token deposits and borrowing across these chains with other chains that Prime Protocol is available on.
The aim of our dashboard: Chain Breakdown: Comparing transactions across Arbitrum (ARB), Avalanche(AVAX), and Ethereum(ETH). Number of Transactions: Total number of Prime Protocol transactions on supported chains. Number of Depositors: Number of users depositing assets on each chain. Number of Borrowers: Count of borrowers accessing liquidity on each chain. TVL: Total Value Locked across supported chains - calculated as amount deposited less amount withdrawn. Volume by Asset Deposited: Aggregate volume of deposited assets by chain. Volume by Asset Borrowed: Total volume of borrowed assets by chain.
Methodology
We took a few different approaches to this.
1) The correcsponding addresses of deposits and withdraws
On Eth:
'0x67cec45eb8d9f059d4c974a4bdea357b68ad80ef' for USDC
'0xd833f882ca07f69c4c5a069675b6b65c235325c3' for ETH
On Avax:
'0x73c5c93e78cb8ca4939307e0d95e032631fb9eee' for USDC
'0x1bf6752282039ee82c06de64d094c9e35578a1a0' for WETH.e
'0x4ebba16380feb2083938c008aedd4b5ebea80f72' for USDT
On Arb:
'0xddc6df52f9749ed80966fb6a9d4c87264cc1e6c1' for USDC
'0xc01683398ffcc86264ba17bc36977f51a1d25e06' for WETH
Origin Signatures
'0x4b2084e3' for withdraws
'0x3bc1f1ed' for deposits
origin_to_address and contract_address
For the 3 addresses associated with the Prime Protocol smart contract on each respective chains.
Arbitrum: 0xbe54BaFC56B468d4D20D609F0Cf17fFc56b99913
Avalanche: 0x0cD070285380cabfc3be55176928dc8A55e6d2A7
Ethereum: 0xfb3330531E3f98671296f905cd82CC407d90CE97
We found that when contract_address
= 'address' and origin_to_address
!= 'address' then it is a deposit event.
Likewise for borrow events, both contract_address
and origin_to_address
will equal 'address
This was referenced with axelar scans and the numbers added up.