WEBVTT 00:00:01.300 --> 00:00:05.269 Let's follow one pair through the app without assuming every screen should 00:00:05.269 --> 00:00:09.238 look the same. Use BTC-USD in our example account, or another clearly 00:00:09.238 --> 00:00:13.207 identified pair in an existing Paper position. Keep the full pair in 00:00:13.207 --> 00:00:17.175 your notes. We will compare what the market list, Portfolio, and Transactions 00:00:17.175 --> 00:00:21.144 each tell us, including the possibility that one view has no matching 00:00:21.144 --> 00:00:21.475 item. 00:00:21.975 --> 00:00:25.487 Start in Coin Universe. Find the pair and note the source label, 00:00:25.487 --> 00:00:28.999 current ranking, and any filter. The row tells you about a market 00:00:28.999 --> 00:00:32.511 in the shared list. It does not establish that you own it. 00:00:32.511 --> 00:00:36.023 If you clear the search and the row moves, that is a 00:00:36.023 --> 00:00:38.950 change in presentation, not evidence of a purchase or sale. 00:00:39.450 --> 00:00:43.100 Now look for the same pair in Portfolio. A matching position tells 00:00:43.100 --> 00:00:46.750 you that the displayed account has a holding recorded there. No matching 00:00:46.750 --> 00:00:50.400 position can be a perfectly sensible result when you have only researched 00:00:50.400 --> 00:00:54.050 the asset. Do not buy it to force the two lists to 00:00:54.050 --> 00:00:57.700 match. Also check the mode, filters, and any display setting that hides 00:00:57.700 --> 00:00:59.525 small holdings before explaining an absence. 00:01:00.025 --> 00:01:04.063 You may see more than one position associated with the same pair. 00:01:04.063 --> 00:01:08.100 Different strategies or sources can have separate positions, so matching a symbol 00:01:08.100 --> 00:01:12.138 alone is not always enough to identify the exact holding you meant. 00:01:12.138 --> 00:01:16.176 Read the available strategy or source labels and quantities. Two rows with 00:01:16.176 --> 00:01:20.214 the same coin name should not automatically be treated as an accidental 00:01:20.214 --> 00:01:20.550 duplicate. 00:01:21.050 --> 00:01:24.965 Open Transactions through the app's navigation and check its current account context 00:01:24.965 --> 00:01:28.879 and available filters. Look for the same pair in the relevant period. 00:01:28.879 --> 00:01:32.794 A transaction describes an event, while Portfolio describes a current holding. An 00:01:32.794 --> 00:01:36.708 older purchase and sale can remain part of the history even when 00:01:36.708 --> 00:01:40.623 no position is currently open. Those views can differ without either one 00:01:40.623 --> 00:01:41.275 being wrong. 00:01:41.775 --> 00:01:46.001 Compare like with like. Check the pair, quote asset, side, quantity, price, 00:01:46.001 --> 00:01:50.227 and time that the record actually provides. If one view says BTC-USDC 00:01:50.227 --> 00:01:54.453 and another says BTC-USD, you have not yet matched the same market. 00:01:54.453 --> 00:01:58.678 If one is Paper and the other is Live, you are comparing 00:01:58.678 --> 00:02:02.200 different account consequences. Correct those mismatches before investigating the arithmetic. 00:02:02.700 --> 00:02:06.629 Keep the record's scope in mind too. Recent app transactions on mobile 00:02:06.629 --> 00:02:10.557 identifies TraderLobby executions only and may display a delay notice. It is 00:02:10.557 --> 00:02:14.486 not a claim to include every action ever taken at an exchange. 00:02:14.486 --> 00:02:18.414 A current market price, an earlier execution price, and a position's average 00:02:18.414 --> 00:02:22.343 entry can all be different values for good reasons. Name their meanings 00:02:22.343 --> 00:02:23.325 before expecting equality. 00:02:23.825 --> 00:02:27.649 Finish with a three-part note: the pair is visible in market research; 00:02:27.649 --> 00:02:31.473 the relevant holding is present, absent, or still unclear; and the relevant 00:02:31.473 --> 00:02:35.296 transaction is present, absent within this view, or still unclear. Add any 00:02:35.296 --> 00:02:39.120 filter or timing limitation. This is how you follow evidence across screens 00:02:39.120 --> 00:02:42.944 without turning a missing row into a story the app has not 00:02:42.944 --> 00:02:43.900 actually told you.