Flippy
469 posts

Sabitlenmiş Tweet


Since the onchain rapists are now deving their own tokens, I found it interesting to have a tool to warn me when they are about to unload their shit on my face.
They are usually using the same bundles so from one chart to another you can reuse their wallets.
I also made a tool to look for bundled wallets in charts but I'm keeping this one for me for now hihi
This tool tells you when bundled wallets are consolidating back to the dev before the dump happens. you input the token, add the wallets you're watching. it tracks each one live via helius webhooks - the second a wallet transfers back to the dev it flips status. >50% consolidated and you get a dump imminent alert.
here's what it actually does:
-auto-detects the dev wallet from mint metadata
-tracks each wallet status live: not in / holding / transferred to dev
-fires a dump imminent alert when >50% have consolidated
-live progress bars + color-coded wallet grid so you see the picture at a glance
-sub-second latency from on-chain tx to your screen
persistent wallet pool, survives restarts
the information was always on-chain. this just makes it fast enough to act on.
English
Flippy retweetledi

@VibeCoderOfek yeah thats the real issue, thats why the handoff doc isnt just a summary. But you're right that it can still leak, the validation step before each session is the safety net and Im still ironing that part out tbf
English

@Flippymingo 30k token per session cap works until handoff summaries lose edge case details enforce a validation step that re injects critical schema before every new session or quality drops by hour six
English

so i built CASM to fix context rot - Claude Agent Session Manager
the article explains the problem in detail but the short version :
you don't actually have 200k tokens to work with
auto-compaction kicks in way before that
and it's lossy - it silently drops implementation details
Claude starts hallucinating interfaces that don't exist
marking tasks as done that were never implemented
the fix is structural, not a prompt trick
CASM breaks your project into 6-12 isolated sessions each one gets :
→ a condensed architecture overview (~5k tokens)
→ only the files it actually needs (~20k tokens)
→ a handoff summary from the previous session (~3k tokens)
total input per session : ~30k tokens
context never degrades
output quality on session 8 = output quality on session 1
the session that starts clean always wins full breakdown of the context rot problem 👇
Flippy@Flippymingo
English

@ashen_one solid template, one thing i'd add is that context files section can actually work against you in long sessions. the more you inject, the faster you hit context rot. Made a full breakdown here if you're interested x.com/Flippymingo/st…
Flippy@Flippymingo
English

built an accurate PNL calendar for solana traders
every terminal has one : axiom, bloom, padre and so on
they look clean, feels legit
but none of them show your REAL PNL
platform fees are either buried, wrong, or just missing
so you think you're up, you're actually down
(that's my case most of the time, im a fucking dumbass)
so i built my own
features :
→ daily PNL calendar view
→ multi-wallet support
→ breakdown by terminal
→ real fee calculation per platform
stack :
→ next.js 14 + typescript
→ prisma + supabase for the db
→ helius api to pull on-chain tx data
axiom, padre, gmgn etc all return fee data
differently in their instruction logs
wrote custom parsers for each terminal
normalized everything into one schema
now i finally know how broke i actually am
English

I just minted a @theloonies_nft, one of the most hyped nft collection on Aptos.
Lets ditch limits together.
#theloonies #aptos
preview.theloonies.xyz/preview/0xa6df…
English

@nayms @coinbase This collaboration breaks new ground for traditional insurers by providing them with the tools they need to transact on blockchain.
What this collaboration will bring:
-As part of the collaboration, Nayms will provide the infrastructure to enable insurers to transact directly on
English










