raunit
6.3K posts

raunit
@raunit
i build on solana prev: @sendaifun

WEST BENGAL CURRENT TRENDS - BJP : 191 TMC : 97 CONG : 1 LEFT : 2



We're excited to announce The Pod. 3 hours of technical programming featuring the deepest dives, happening alongside Accelerate. p-token, post-quantum, RPC 2.0, Quasar, agentic infra, security, and more. If you're a dev working on Solana's hardest problems, this is for you. Powered by @Rockaway_X

building a backtesting infrastructure, starting with Phoenix as a proof of concept. If it works, I’ll scale it to other protocols I was about to post “someone should build this,” then I remembered this tweet: x.com/GuiBibeau/stat… The idea is clear it just needs some iterations.I’ll use Claude, since I’ve hit the Codex limits. For those unfamiliar, here’s what backtesting means: If a trader wants to take a trade at time t+2, I can simulate or evaluate that trade using data from time t. In other words, it’s based on real-time data, but relative to when you’re placing the trade, it’s treated as historical even if it’s just a few slots behind. Simply put: “historical” means anything that has already happened on-chain and is recorded in the network.





the value prop of getTransactionsForAddress (gTFA) is NOT the historical data – you can get that from RocksDB snapshots already gTFA is an index it's purpose is reduce dev time, reduce on-call work, and get your product to market faster let's say you want wallet token history for a specific month with raw data, you need to: 1. resolve the time range to epochs 2. fetch the 1B+ txs for those epochs 3. deserialize every tx 3. track ATA ownership 4. filter out unmatched txs (99%+) 5. parse & aggregate remaining transactions that ends up being too slow for a single query – so you have to build a data pipeline, storage layer, and API gTFA does this with a single query in under 50ms!










