raunit

6.3K posts

raunit banner
raunit

raunit

@raunit

i build on solana prev: @sendaifun

nyc(one day) Katılım Eylül 2024
756 Takip Edilen1.8K Takipçiler
Sabitlenmiş Tweet
raunit
raunit@raunit·
idk why , but I know I will do f'king great in 2026.
English
6
1
33
10.8K
Bruda
Bruda@BrudaSol·
Day 1 Trading onchain Starting with $1000 capital. (extreme risk edition)
English
2
0
2
277
raunit
raunit@raunit·
@jacobvcreech - Subsidize vote fees temporarily through foundation/client incentives, especially for small validators
English
0
0
0
180
Jacob Creech
Jacob Creech@jacobvcreech·
Make slots times as short as possible asap. Hear me out. Pros: - Better for Market Makers - Best in class UX for any app - Continue to be better than any chain including centralized ones - Faster response times Cons: - Harder to index - Temporarily more vote fees until alpenglow Worth the tradeoff?
English
20
10
88
7.5K
raunit
raunit@raunit·
DevSecOpsBiz.
Dansk
0
0
0
143
raunit
raunit@raunit·
Use Bun.
English
0
0
2
160
manu
manu@boomheadvt·
balloons on the timeline. another year in the game. 25🥂 grateful for the people i’ve met and everything that came with it ♥️
manu tweet media
English
10
0
29
636
raunit
raunit@raunit·
Don’t overthink just write them down.
English
0
0
4
177
raunit
raunit@raunit·
Caveman is too good.
English
0
0
1
110
raunit
raunit@raunit·
Update: I was able to backtest it it’s possible, but only to a limited extent. I can test a few strategies, but it won’t scale. I have another idea to build on this, so I’ll try to create a POC over the weekend and will share an update Let’s see how it goes.
raunit@raunit

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.

English
0
0
1
338
Exponent
Exponent@ExponentFinance·
Today we’re announcing our $5 million seed round, led by @Multicoin This funding directly supports Exponent’s next phase: becoming the premier platform for onchain portfolio construction
Exponent tweet media
English
105
55
570
77.5K
Farhaj Mayan
Farhaj Mayan@farhaj·
I built an AI friend called Locky. It has one goal, to help you actually build the thing you keep putting off. You can @textlocky directly on iMessage. Here's what it can do today:
English
42
19
137
16.9K
raunit
raunit@raunit·
@thsottiaux please ship /remote control I want to check my Codex session from my phone, even while I’m in the shower 🥲
English
0
0
0
113
raunit
raunit@raunit·
Tip: Dont use plan mode Instead create a file named spec.md and write down all your ideas, the intended flow, and other relevant details add a final note at the end Also, we dont call it vibe coding anymore its agentic coding
raunit tweet media
English
2
0
1
229
raunit retweetledi
Het Dagli
Het Dagli@daglihet·
When someone sends you USDC, your wallet address never appears in the transaction's account keys. The transfer goes to your ATA. Stream every transaction through a Yellowstone gRPC interface on your wallet pubkey, and you miss it entirely. The user typically doesn't know all of the wallet's ATAs upfront, which is the real problem. gTFA solves it in one call. It resolves which token accounts belong to a wallet, returns transactions whose balances actually changed, and filters out noise where the ATA was touched, but nothing moved. Comparing it to a streaming pipeline and you're processing every transaction on the chain, resolving ATA ownership, diffing token balances, dropping no-ops, and building your own index. Alpha: Stay tuned for another huge release from Helius on this front today, can't wait for our competitors to refute it by writing a blog.
nick | helius.dev@nick_pennie

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!

English
4
1
48
4.6K
raunit
raunit@raunit·
@0xanmol @shek_dev You can share the keys with me I promise they’ll be safe with me I care a lot about you 🫶
English
0
0
0
25
Anmol
Anmol@0xanmol·
@shek_dev I swapped all my inr for usd on august 25th 2025 Best decision ever
English
1
0
3
196