Wallet providers

Traditionally, wallet providers have been instrumental in providing users with up-to-date information on their current holdings, but they may not have always been able to offer detailed historical financial data on the protocols that users have positions in.

This is where Archive Protocol comes in - revolutionizing the way users can access and analyze their web3 activity. Archive Protocol allows wallet providers to offer users a comprehensive view of their web3 activity, including detailed historical financial data on the protocols they have positions in. This means users can easily track their performance over time, analyze trends, and make more informed investment decisions.

What sets Archive Protocol apart is its ability to make sense of even the most complex web3 financial transactions and provide a wide range of historical financial metrics. Archive Protocol can accurately track and analyze transactions made by a user, providing an up-to-date and precise overview of their current and historical performance.

On this page, we’re exploring the benefits and some of the use cases of our data.

Benefits

  • Improved user experience: by offering a comprehensive view of users' web3 activity, including detailed historical data on the protocols they have positions in, wallet providers can enhance the user experience and create a more loyal user base.
  • Increased trust: wallet providers can establish trust with their users by providing users with access to their historical financial data. This can help to build a stronger relationship between users and the wallet provider, leading to increased user loyalty and retention.
  • Competitive advantage: offering historical financial data is a value-added service that can set a wallet provider apart from its competitors. By providing users with access to this information, wallet providers can differentiate themselves and attract new users.

Use cases

Handling complex web3 transactions

Our integrations can capture a wide range of on-chain financial transactions, identify protocol(s) involved, label the transactions (deposit, withdraw, income, transfer, other) and the tokens involved, calculate financial metrics, and make them available through our APIs.

Our integration can cover the following activities:

  • Trading
  • Liquidity providing
  • Farming
  • Staking and delegations
  • Lending and borrowing
  • Rebasing protocol transactions
  • Options
  • Vaults

Token pricing and valuation data

Making the user’s portfolio valuation more accurate by providing current and historical pricing information for DeFi assets, including but not limited to receipt token prices such as LP (liquidity pool) tokens.

We capture and store the daily holdings and valuations of user positions and make them available through our APIs.

Detailed historical position insights

Highlighting detailed performance metrics and data about a specific position captured daily and available since inception. Some example available fields:

  • Token balance information, including underlying tokens if any
  • Average cost basis
  • Net market gain
  • Impermanent loss
  • Collected rewards
  • Pending income
  • APY
  • Metrics comparing the position with an investment in ETH or BTC
Example Orca Position on Solana

Example Orca Position on Solana

Example Maker Dao Position on Ethereum

Example Maker Dao Position on Ethereum

Providing historical data:

  • Position income (farming rewards, fees)
  • Capital’s performance
  • Position APY (income APY)
  • Daily position data
  • Impermanent loss
  • Holdings, balances (underlying token data balances stored daily)
  • PnL
  • User transactions

Format:

  • Displayed as part of an existing user position page on the protocol’s website

Protocol-level user performance

Data:

  • Protocol-level user income tracking (farming rewards, fees)
  • Capital’s performance of all deposited assets
  • Historical user ROI in the protocol
  • Daily user protocol data
  • Impermanent loss
  • Holdings, balances
  • PnL
  • User transactions history

Hypothetical scenario analysis

Example Hypothetical Scenarios Chart

Example Hypothetical Scenarios Chart


Data:

  • HODL position value in ETH, BTC

Profit and loss calculation

Cost-basis calculation: we calculate the cost-basis of each pool position, taking additional deposits, withdrawals, and transfers into account. We use the average cost method for the cost basis.

Asset gains and losses: the asset gains or losses are the difference between the current asset value and the cost basis. For exited positions, we take the USD value at the time of exit and subtract the cost basis

Income: we track the collected and pending earned fees of each position. Collected fees are available with the date of claim, token amount, and USD value at the time of collection, plus transaction hash and more.

Data export capability (profit and loss, income report)

The output of our APIs can be used to generate export files (CSV) of a given user’s positions, providing financial data for various purposes.

Some CSV report examples:

  • Profit and loss report, see a sample here
  • Collected fees report, see a sample here

Multi-wallet support

Our protocol-level APIs can take multiple wallet addresses and return the historical financial data for these in a given protocol. This feature makes tracking financial performance across multiple wallets much easier for DeFi users.

Scalable API coverage

Our integration standards allow faster integration with web3 protocols, leading to better coverage in the long run.

In the future, our platform will be open-source, allowing anyone to build integrations and, after proper testing, provide historical financial data for any protocol through APIs.

API associations

It is a built-in feature of our new APIs that allows combining APIs with each other to provide a comprehensive performance overview of a Defi user’s positions.

Example use case:
The user provides liquidity on a given AMM and uses the receipt tokens to farm in another protocol. To get accurate historical financial data for this user, two APIs are needed:
For the AMM to get the liquidity-providing data
For the other protocol, where the user farms with the receipt tokens

Instead of looking at the financial performance of the user in these protocols separately, API association constructs a combined, more accurate historical performance.