taera
15 posts

taera
@tradertaera
dumbass that gets lucky sometimes | degen | indie dev | crypto since 2015
Katılım Aralık 2012
25 Takip Edilen15 Takipçiler

6/
Why this is almost certainly his wallet
Several independent pieces of evidence point to the same conclusion:
His own older tweet shared the wallet address. The wallet is tied to the coin associated with him.
The deployer wallet matches the previously shared address. A linked funding wallet has a traceable transaction history. The wallet is associated with the username va3ko. His public profile details, including his email address and role, are consistent with these findings.
English

I tracked down @Va3Ko's (a @pumpfun contributor) wallet
"2DFthmMUVotXSGLY9X9QYCKvVCrnxECReeA4aKtKb77Z"
and here is how I found his personal Solana wallet through publicly available information.
This was not random guessing but the result of carefully examining his profile, old posts, and on-chain data. Here is exactly how I did it, step by step, and why the evidence checks out.
A thread:
English
taera retweetledi
taera retweetledi

Introducing /visual-plan - a skill to generate rich, visual plans for Claude Code and Codex.
Plan mode in Claude Code is incredible.
But I always find my eyes glazing over when it gives me this huge markdown essay in my terminal.
I found I can make much better visual plans with reusable components.
So I made a skill called `/visual-plan`.
It generates plans as MDX with visual, interactive components. Diagrams, interactive API specs, schema design changes, annotated code, and even pan and zoomable wireframes.
So for any UI work, you can look at a wireframe first, comment on it, iterate, and then have the agent work.
I’ve found this to be a much more intuitive interface for reasoning about what the agent is doing.
It’s somewhat inspired by that popular post about how HTML is better than Markdown.
But HTML can be slow and verbose to write. And it doesn’t look good checked into a repo.
This has really made me feel like humans and engineering are entering a new abstraction phase, where we reason about things at the plan level.
As long as the plan is good, agents are getting more and more reliable at executing on it.
Almost to the degree that we trust the C compiler to compile to assembly reliably.
Plans are the new intermediate representation.
I also made a skill for the reverse of this, called `/visual-recap`.
After the agent works, it gives you a recap of everything it did.
Same idea: wireframes, interactive API specs and diffs, schemas, annotated code, etc.
So now when you’re reviewing what the agent did for you, or looking at a pull request of somebody else’s code, you can see a visual recap instead of just reading a wall of text.
It’s all free and open source. You can find it on my GitHub.
Will link to it in the reply because we all know how dumb these algorithms are with links.
English
taera retweetledi
taera retweetledi
taera retweetledi
taera retweetledi











