u/buddies2705

Building a stablecoin analytics dashboard that shows daily USDT volume on Tron — total USD moved, transfer count, and unique active addresses per day.

The naive approach is pulling every raw transfer event and aggregating client-side, but Tron processes an enormous number of USDT transfers daily and paginating through all of them to compute a daily sum is both slow and burns through API quota fast.

I've tried pulling from TronGrid with date filters but it doesn't return pre-aggregated metrics — you get the raw rows.

CoinMetrics covers some of this but it's expensive for just one chain and doesn't give you the address-level breakdowns.

Is there an API that lets you group by date and return sum(transfer_amount), count(transfers), and uniq(senders) server-side in a single call?

Doing a lot of memecoin and wallet research lately and the workflow is broken — I write SQL against my own database copy of Solana trades, export to CSV, paste into Claude, get analysis, repeat. Every iteration loses context.

Tried building a quick MCP server over a Dune query but rate limits killed it within a day. The CoinGecko MCP works fine for price/market data but doesn't have wallet-level trade data, which is what I actually need (per-trader PnL, copy-trade candidates, detecting wallets that are basically pump orchestrators).

What's the cleanest setup for getting wallet-level and pool-level DEX trades into Claude as a queryable tool? Ideally something with Solana + EVM coverage and not too much auth ceremony.

We're building a tool that pings users when interesting new tokens launch on Base — clanker, Virtuals, flaunch and direct Uniswap v3 / Aerodrome deployments. The detection part is the bottleneck. Polling Basescan for new contract creations is slow and noisy. Subscribing to logs over Alchemy WebSockets works for known factory addresses but we keep missing tokens that ship from custom factories, and the WS connection drops every few hours so we lose launches during reconnect. Running our own Base node is on the table but we'd rather not maintain Erigon for what should be a "tell me when a new pair has its first swap" subscription.

What does everyone's new-pair detection stack on Base look like? Especially for tokens that don't go through a known launcher.

Doing diligence before deploying liquidity into v4 and the hook situation is wild.

Every pool can have its own hook contract that modifies swaps, fees, position changes, donations — and as an LP I want to know what the hook does before parking capital.

Right now I'm decoding PoolManager Initialize events, grabbing the hooks address per pool, then manually verifying contracts on Etherscan and reading source one at a time. Across mainnet + Base + Arbitrum + Unichain it's already hundreds of unique hook contracts, and it's only been a few months.

Has anyone built (or found) a clean dataset of v4 hooks by address with their flag bits decoded and a pool/usage count per hook? Pools-grouped-by-hook would also do.

Building a payment flow that needs to credit user accounts the moment a USDT transfer hits one of our deposit addresses on TRON. Currently polling TronGrid every few seconds across a few thousand addresses and it's both slow and we keep getting throttled during busy periods. Tried running a full node — the bandwidth and storage cost was brutal for what is essentially a "tell me when balance changes" problem. WebSocket support on the public endpoints has been inconsistent, drops every few hours.

What does your stack look like for this? Specifically interested in anything that pushes sub-second notifications on TRC-20 transfers without us operating the node ourselves.

I want to follow tokens from the moment they're created on PumpFun, through their bonding-curve trades, the graduation event, and then continue tracking them on PumpSwap once they're an AMM. Right now I have two scripts watching two different program IDs and a janky reconciliation step trying to stitch the same token's history together.

Is there a cleaner way to get this as one continuous trade history for a token regardless of which Pump venue it's on at any given moment?

Is anyone aware of a data source that returns the supply snapshot inline with each trade event? Feels like a basic thing but I can't find it.

Hello everyone,

This is Gaurav from the Bitquery team. We have launched a new Trading MCP.

This MCP includes all trades from the last 30 days across 8 blockchains, including Solana, Ethereum, BNB, Base, Tron, Optimism, Arbitrum, and Polygon.

It has a latency of less than 10 sec.

It allows you to do any type of analysis, such as finding interesting tokens, price volume surge, creating trading models, finding traders, and analyzing them.

It is currently free https://mcp.bitquery.io/

Looking for feedback

We plan to add token transfer data next from multiple chains.

Feel free to ask any questions.

We have launched a new MCP https://mcp.bitquery.io/

It has last 30 days of all trades done on chains - Solana, Ethereum, Tron, BNB Chain, Optimism, Arbitrum, Base.

It has a latency of less than 10 seconds, and you can do any type of analysis, such as finding interesting tokens to trade.. profitable traders to copy, etc.

It's free to use, we looking for feedback

I manage reporting for a small crypto fund. Our Solana wallet has hundreds of token movements per month — but a huge chunk aren't simple buys and sells. They're LP deposits into Meteora, yield farming rewards from Marinade, airdrop claims, token migrations. Each of these creates transfer events but they mean very different things for cost basis.

What I need as a starting point is just a clean per-token summary: total tokens received, total tokens sent, net change, across a specific reporting period. From there I can classify each flow. But even getting that first step — a per-currency inflow/outflow summary for one wallet over one quarter — is surprisingly hard without running my own indexer.

How are crypto fund accountants handling this on Solana?

I want a simple check before aping into any SPL token: who holds what percentage, how many unique receivers have ever gotten this token, and what the top 10 concentration looks like. CoinGecko shows "holders" but the number is usually wrong for newer tokens, and it doesn't show distribution curves.

What I really want is something like "for token X, show me total received per wallet, sorted by balance, with a count of unique holders." Basically an aggregated view of all transfer history for one mint address. But computing this myself from raw transfer events for tokens with millions of transfers is painfully slow.

What are you using for quick token distribution checks on Solana?

Tron handles the most USDT volume of any chain but the tooling is years behind Ethereum.

I'm building a merchant payment system that needs to detect incoming TRC-20 USDT payments to hundreds of deposit addresses within a few seconds of confirmation.

TronGrid's event polling works but the rate limits mean I'm either paying a fortune or missing payments during busy periods.

What's everyone using as the backbone for Tron payment detection in production?

Especially interested in how you handle the reliability side — can't afford to miss a customer deposit.

Working on a research project that needs the full trade history for graduated Pump.fun tokens. Buys/sells on the bonding curve, creator wallet activity, graduation timing, then post-migration AMM trades on PumpSwap.

Live data is solved — WebSocket subscriptions, Geyser, take your pick. The historical side is what's wrecking the budget.

What I've tried:

- Solana RPC — rate limits made it useless past a few hours of data

- Archive node providers — quotes started at $500/mo, hard to justify before I even know if the dataset is useful

- Dune on Solana — slow at this scale, and decoded data on the Pumpfun program was patchy when I last looked

- Parsing logs from my own node — works for a small window, doesn't scale

What I actually want is a parquet or CSV dump per month, hosted somewhere I can pay per GB or per query rather than a flat retainer.

For folks doing serious on-chain research on Solana — what does your historical-data layer actually look like? Self-hosted? Vendor? Some hybrid?

Spent the last few weekends trying to backtest a copy-trading strategy on Solana. The idea: find wallets with high win rates over the past 30 days, copy their trades with ~2s execution delay.

Problem: every "smart money" leaderboard I look at (Cielo, Nansen, the various Solana-specific ones) shows wallets with 60–80% win rates that look amazing on paper. When I actually replay them with realistic execution lag and fees, the alpha mostly disappears.

A few things I've figured out so far:

• A lot of these "winners" got most of their PnL from buying tokens during pre-launch or in the first few blocks. By the time you can copy them with any realistic latency, you're buying at 3–5x their entry.
• The shorter the analysis window (8h, 24h), the more contamination from this pre-window position-taking. 14–30 day windows are way cleaner, but most tools default to 24h.
• Memecoin wallets are the worst — anyone trading low-liquidity stuff has zero tolerance for execution delay. Your 1.5s lag kills you before the trade is even confirmed.

The only category that actually held up under realistic conditions was wallets trading higher-liquidity stuff (LSTs, tokenized equities, blue chips on Solana). Lower headline returns, but the alpha survives being copied.

Curious if anyone has different experience. Do you actually run copy-trading in production, and if so, what data window are you using to qualify wallets? Or have you given up on this whole approach?

Building a tax/PnL tool for DeFi traders. Need every swap a wallet has done across Uniswap v2/v3, Sushi, Balancer, Curve, and a handful of L2 DEXs over the last 18 months.

What I've tried:

1. The Graph hosted subgraphs — fine for one chain at a time, dies when you try to query a year of data with pagination. Half the subgraphs I need got deprecated when the hosted service sunset.
2. Self-hosted archive node — Geth full sync is fine, but archive mode is 18 TB and growing. We're a 3-person team. This is not a thing we want to babysit.
3. Alchemy/Infura — rate limits make 18-month backfills take literal days, and the bill scales linearly per user. Not great.
4. Dune — great for analysis, terrible as a backend. Query API is rate limited and not really meant for app-tier reads.

So what's everyone actually doing? Are people just eating the archive node cost? Paying $3–5k/month to one of the paid providers? I feel like I'm missing an obvious option.

Context: ~600 users in beta. Our infra cost per user is currently embarrassing. Need to fix this before we open paid signups.

Hey, looking for a sanity check from anyone who's been through this.

We started building our own Solana indexer back in January for a small DEX analytics dashboard. Validator + Geyser plugin writing to Postgres. Seemed manageable on paper.

Three months later: still falling behind by 200–400 slots during peak hours. Restart the plugin and it takes 6–8 hours to backfill before we're real-time again. AWS bill went from ~$400 to ~$2,100 because we kept scaling the box up trying to outrun the firehose.

Things I've tried:

• Switched from Yellowstone to a custom Geyser fork
• Filtering events at the plugin level (helped, but we still lose state we actually need)
• Splitting writes into a Kafka topic + downstream consumers
• Throwing a beefier machine at it (i3en.6xlarge → i3en.12xlarge, marginal improvement)

Honestly at this point I'm wondering if running our own infra is the right call at all. My CTO is convinced we'll save money long-term, but I'm not seeing the math anymore.

For anyone running a production Solana indexer:

• How long did it take you to get stable?
• Are you actually saving money vs paying a data provider?
• Is there a setup that doesn't fall over every 10 days?

Considering throwing it all away and just paying someone. Talk me into or out of it.

For a research project I need fairly standard tabular data: transactions, transfers, DEX trades, balance updates for Ethereum and Solana, ideally with consistent column naming across chains and going back at least 2–3 years.

The team's existing approach involves running an Ethereum archive node and a custom Solana Geyser plugin, and frankly I don't want to spend my next quarter on infra I don't understand well.

Is there a sane way to just get Parquet files dropped into a GCS bucket so I can LOAD DATA into BigQuery and start working? I'd rather pay for the data than spend three months building the pipeline. What are people in this situation actually doing in 2026?

For an ML feature engineering project I need every Uniswap, Curve, PancakeSwap, and Raydium trade from 2021 onwards loaded into Snowflake.

RPC backfill on a self-hosted Ethereum archive node is going to take weeks at this volume, the existing subgraphs are missing fields we need, and Dune is great for ad-hoc but I can't COPY INTO from a query result.

Has anyone done bulk historical loading of DEX trades into a warehouse cleanly?

Specifically curious about file format (Parquet vs JSONL), how people partition by block range, and whether anyone has found a vendor that just delivers this as columnar dumps to S3 instead of forcing us to build the extraction layer ourselves.

We need a real-time pipeline: every DEX trade across major EVM chains and Solana lands in ClickHouse within seconds for live dashboards. I've seen teams do this with Kafka → ClickHouse Kafka engine, but I'm wondering if there are managed crypto-specific data feeds that already deliver in protobuf/Avro and integrate cleanly.

What's the architecture people are actually running in production? Specifically interested in how you handle backfill and gap recovery.

For a project I'm backtesting an LP strategy on Polygon and I need historical reserves for a specific pool every minute over the last 90 days. Pulling this from RPC means archive node queries which is expensive. Subgraphs are sometimes incomplete for older pools.

How are people getting historical pool state at this granularity? Especially across L2s.