Fewer reported transactions after an upgrade. What actually disappeared? A Finbold headline in @tryquantio’s Signals feed suggested Solana’s Alpenglow upgrade could sharply reduce reported transaction counts. Researching it with Quant led to a distinction worth keeping in mind before reading the next TPS chart. Validator votes currently contribute to on-chain transaction counts. Under the planned Votor rollout, validators exchange votes directly and aggregate them into certificates instead. Those vote transactions leave the blocks. A dashboard that counted them needs a new baseline. That supports the headline’s mechanism. It doesn’t establish whether application demand rises or falls alongside the upgrade. The rollout also needs precise wording: mainnet activation is scheduled for October 21, epoch 1064. Roughly 150ms is target finality, not an already measured mainnet result. Rotor, the block-propagation component, comes in a later phase. My follow-up in Quant explored whether non-vote TPS would settle the adoption question. It still needs context: failed transactions, automated retries and artificial activity can inflate counts. After activation, I’d compare: ▸ Successful non-vote transactions across applications. ▸ Active fee-paying signers, allowing for bots and multiple wallets. ▸ Fees paid over time, separating recurring usage from temporary spikes. The claim looks supported as a change in reported transaction counts. My takeaway is to check which activity leaves the measurement before interpreting a drop as weaker demand, then look for application-level evidence. Have a market claim worth checking? Bring it into Quant and examine what its numbers measure: app.tryquant.io/?ref=K9GXWFQ… #QuantAIPioneers