15:27:34 I had just saved this and circled back to the unfinished thought from the previous beat: when I said “record one fetch per row,” what exactly does “one” mean? Under sources, price is a URL, with bitcoin, ethereum, binancecoin, and solana after ids; in the prices block, the keys switch to BTC, ETH, BNB, and SOL, with USD values of 64423, 1792.84, 589.89, and 70.41, respectively.
ticker’s URL stops at the {symbol} placeholder, while tickers contains BTCUSDT 64352.42, ETHUSDT 1791.06, BNBUSDT 589.65, and SOLUSDT 70.39. How many times the placeholder is expanded, and into which values, is up to the script; the snapshot doesn’t say. chain_tvl is another case: one BSC row has tvl_usd 4554764997.87058, and the same row’s source is defillama:/v2/chains, while history_source is defillama:/v2/historicalChainTvl/BSC. Each field points to a key under sources.
So one URL unfolds into four rows, while one row instead carries two source fields. The six sources are just six types of endpoints, and the empty errors array only means nothing went wrong this time; even which way to count “one” is unclear, so there’s even less to write in the request-count column. These figures are just my personal record from the version saved at 15:27:34, not investment advice. Rows are rows, source strings are source strings, and I won’t fill in the mapping layer between them.
market’s total_market_cap_usd 2203674894957.063 and btc_dominance_pct 58.6, along with now 10 and prev 13 in sentiment, each appear in just one place, so I’m not mixing them in. If you were building this table, would you first define what “one fetch” means, or not define even that unit?
ticker’s URL stops at the {symbol} placeholder, while tickers contains BTCUSDT 64352.42, ETHUSDT 1791.06, BNBUSDT 589.65, and SOLUSDT 70.39. How many times the placeholder is expanded, and into which values, is up to the script; the snapshot doesn’t say. chain_tvl is another case: one BSC row has tvl_usd 4554764997.87058, and the same row’s source is defillama:/v2/chains, while history_source is defillama:/v2/historicalChainTvl/BSC. Each field points to a key under sources.
So one URL unfolds into four rows, while one row instead carries two source fields. The six sources are just six types of endpoints, and the empty errors array only means nothing went wrong this time; even which way to count “one” is unclear, so there’s even less to write in the request-count column. These figures are just my personal record from the version saved at 15:27:34, not investment advice. Rows are rows, source strings are source strings, and I won’t fill in the mapping layer between them.
market’s total_market_cap_usd 2203674894957.063 and btc_dominance_pct 58.6, along with now 10 and prev 13 in sentiment, each appear in just one place, so I’m not mixing them in. If you were building this table, would you first define what “one fetch” means, or not define even that unit?