> For the complete documentation index, see [llms.txt](https://astarfi.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://astarfi.gitbook.io/documentation/concepts-and-methodology/data-pricing-and-calculation-methodology.md).

# Data, Pricing, and Calculation Methodology

### Accounting start date

June 1, 2026 is the unified accounting start date for Astar Fi portfolio analytics.

For assets already held on that date, Astar Fi uses the June 1 portfolio snapshot as the opening position. The supported market price on June 1 is used as the opening Cost Basis.

For assets acquired after June 1, Cost Basis is determined from supported transaction history, the recognized acquisition value, or the applicable transfer logic described below.

Activity and performance before June 1, 2026 are not reconstructed in the current version.

### Data sources

Astar Fi combines:

* Onchain balances, transfers, event logs, and contract state.
* Protocol and product APIs or subgraphs.
* Market prices, APY, liquidity, issuer, and reference data.
* Internal indexing and supported historical records.
* Route and quote data for supported transactions.

The source used depends on the asset, network, product structure, data quality, update frequency, and whether the result can be reproduced and explained with reasonable clarity.

### Onchain data and analytics inputs

Onchain facts cannot be edited. These include wallet addresses, token amounts, transaction hashes, networks, timestamps, contracts, and whether a transaction occurred.

Eligible user inputs can refine how an activity is interpreted in Astar Fi. Depending on the activity, this may include a Label, original cost information, or Source Split.

These inputs affect Astar Fi analytics only. They cannot change onchain history or move assets.

### Money Position

Money Position includes supported money-like assets and stable-value positions, including wallet-held stablecoins and supported stablecoin Earn positions.

Interest-bearing position tokens are valued using supported exchange rates, share prices, total-assets data, or other available protocol information.

Growth in supported stable-value Earn positions is generally recorded as Reward & Interest under Money In. It is not included in Investment PnL.

### Investment Position and Cost Basis

Investment Position includes supported non-stable investment assets.

Cost Basis can come from a recognized purchase or swap, supported transaction history, or user-provided cost information for an external transfer.

When a supported investment asset enters from an external or untracked source, Astar Fi uses its supported market price at the transaction time as the default Cost Basis. If you provide the original cost per token, Astar Fi recalculates the position’s average cost, Unrealized PnL, and ROI.

Changing Cost Basis affects analytics from the relevant activity onward. It does not change the number of tokens held or the original onchain transaction.

### Investment asset transfers out

When a supported investment asset leaves the tracked portfolio, Astar Fi uses its supported market price at the transaction time to calculate the transfer value and resulting Investment PnL.

You may classify an eligible outgoing investment transfer as Money Out instead. This changes its economic treatment in Astar Fi analytics but does not change the asset movement recorded onchain.

### Transaction treatment

* External stablecoin transfers are generally treated as Money In or Money Out.
* A stablecoin transfer in can be classified as proceeds from an investment sold elsewhere. The original cost is treated as Cost Basis Change, while the difference between that cost and the proceeds is recorded as Investment PnL.
* Recognized purchases, sales, and swaps update positions, Cost Basis, and Investment PnL without creating external Money Flow.
* A recognized bridge between the bound wallet’s Ethereum and Base positions is treated as an internal location change.
* If a bridge involves another wallet, an unsupported network, or cannot be fully matched, the visible activity may be treated as a transfer in or transfer out and marked for review.
* Supplying to or withdrawing from a supported Earn product generally changes where an asset is held. It does not create external Money Flow.
* Eligible incoming transfers can be classified or split between more than one source.

### Pricing methodology

Astar Fi uses price sources appropriate to each supported asset or product.

Prices may come from liquid-market data, protocol exchange rates, issuer NAVs, or other supported reference sources.

If a sufficiently reliable price is unavailable, Astar Fi may show the asset balance without including it in Total Net Worth. The asset may also be excluded from value-based analytics.

Displayed values are estimates and may differ from prices available for actual execution.

### APY methodology

Current APY and 30D Average APY use available protocol and product data.

APY may include base yield and incentives when that information is available and can be separated reliably. Weighted APY uses the value of each supported Earn position as its weight.

APY can change with utilization, incentives, market demand, product fees, asset prices, and protocol rules. It is not a guaranteed realized return.

### Risk Tier and Astar Fi Rating

Risk Tier is a broad product classification used for comparison. Prime, Balanced, and Aggressive describe the general risk profile assigned by Astar Fi.

The Astar Fi Rating is a separate internal reference score based on selected risk dimensions and available product data.

Risk Tiers and Ratings may change as liquidity, product structure, disclosures, market conditions, or Astar Fi methodology change. Neither is a guarantee of safety or future performance.

### Refreshes, gaps, and differences

Astar Fi data may update at a different time from a wallet, protocol interface, block explorer, exchange, or another portfolio tracker.

Differences can result from supported coverage, indexing time, price sources, spam filtering, position interpretation, Cost Basis methodology, transaction classification, rounding, and data availability.

A delay or difference does not always indicate an error. Where values differ, compare the underlying wallet activity, supported contracts, pricing time, and calculation method.
