0xeabz 🦇🔊

[0xeabz 🦇🔊 @0xeabz]

I'm open to new opportunities 🛠️

Engineer focused on EVM/SVM infra & blockchain data.

Rust · Golang · TypeScript · Solidity · React/Next.js

Building with AI-agentic coding pipelines.

Full-time or contract, remote.
Work: https://t.co/B9TUW02pvN

DMs open, RTs appreciated 🙏

Some things I've been building 👇

[0xeabz 🦇🔊 @0xeabz]

@resend Just applied through the CLI. So far, the best experience I've had submitting a CV.

[0xeabz 🦇🔊 @0xeabz]

3) Tirith

Once you start running several coding agents in parallel, you hit a new problem fast: they don't know about each other. One refactors a file while another edits it, and work gets silently overwritten. You end up spending more time untangling conflicts than you saved by parallelizing.

Tirith is an MCP coordination server that gives agents shared awareness: what's being worked on, by whom, and what's off-limits right now. Agents coordinate instead of colliding.

https://t.co/MnMLUZCMS2

[0xeabz 🦇🔊 @0xeabz]

I'm open to new opportunities 🛠️

Engineer focused on EVM/SVM infra & blockchain data.

Rust · Golang · TypeScript · Solidity · React/Next.js

Building with AI-agentic coding pipelines.

Full-time or contract, remote.
Work: https://t.co/B9TUW02pvN

DMs open, RTs appreciated 🙏

Some things I've been building 👇

[0xeabz 🦇🔊 @0xeabz]

2) op-p2p-indexer

OP Stack L2s are multiplying fast, and almost everyone indexing them goes through RPC providers. That means rate limits, growing bills, and a single point of failure sitting between you and data that is, in theory, public.

But the data is already out there, being gossiped between nodes on the p2p network. So I'm building an indexer that listens there directly, with no middleman. Raw data first, then an analytics layer on top.

https://t.co/OCy8FffDK5

[0xeabz 🦇🔊 @0xeabz]

Almost ready for open/public testing.

Currently checking benchmarks and preparing the first MVP.

More info 👇🏻

https://t.co/EgCKoHnAwh

[0xeabz 🦇🔊 @0xeabz]

I'm building a 4th option:

A self-hosted indexer that reads blocks straight from the chain's p2p network. It works like a light node: it joins the gossip layer, decodes blocks as they propagate, and streams them into ClickHouse.

No API keys. No rate limits. No archive node.

[0xeabz 🦇🔊 @0xeabz]

Current status: in active development 🛠️

Supporting Optimism and Unichain for now, working toward an MVP.

Follow along to see the results.

[0xeabz 🦇🔊 @0xeabz]

I'm building a 4th option:

A self-hosted indexer that reads blocks straight from the chain's p2p network. It works like a light node: it joins the gossip layer, decodes blocks as they propagate, and streams them into ClickHouse.

No API keys. No rate limits. No archive node.

[0xeabz 🦇🔊 @0xeabz]

Starting with OP Stack L2s. Raw data first, analytics next.

Fully open source, built in public:
https://t.co/iAs9pHpXk9

[0xeabz 🦇🔊 @0xeabz]

Every blockchain app needs data: full history plus live blocks, as fast as possible.

Your options today:

Managed indexers (The Graph, Dune, Goldsky, Alchemy, QuickNode, Covalent…): reliable, but expensive
RPC endpoints: rate-limited, free or paid
Your own node: heavy hardware, constant babysitting 🧵

[0xeabz 🦇🔊 @0xeabz]

Just started a new hobby project: indexing @Optimism Stack chains directly from the p2p network.

It's not production-ready yet, but it will be soon. The indexer will also contribute valid data back to the p2p layer.

https://t.co/iAs9pHqv9H

[0xeabz 🦇🔊 @0xeabz]

Just started vibe coding with Unreal Engine 5.8.

So far, it's been a really hard environment to work with, especially since I have no clue about game dev.
Any suggestions?

[0xeabz 🦇🔊 @0xeabz]

Open for part-time freelance dev work (~20 hrs/wk):

• Rust data and infra for EVM chains.
• Frontends for web3 protocols
• AI agent tooling (MCP Servers)

DMs open

https://t.co/bu3xS5gzEk

[0xeabz 🦇🔊 @0xeabz]

@Kantorcodes Sure! Let’s give it a try, I am still benchmarking current performance, it’s really on experimental phase.

[0xeabz 🦇🔊 @0xeabz]

Been vibecoding for the last month, and one of my main issues has been running multiple agents on different tasks with no coordination between them.

So I built this tool to coordinate AI agents through MCP. So far it's working well: https://t.co/GdiY0D89oU

[0xeabz 🦇🔊 @0xeabz]

@Kantorcodes No. Tirith is a coordinator, not a security layer: runtime state and committed state share one write path, and any agent can do any of it. Identity is self-declared by design. The swarm lead only routes escalations.

[0xeabz 🦇🔊 @0xeabz]

@mitansh_j07 Yes! And right now they are coordinating themselves to build their coordinator. It’s truly amazing.

[0xeabz 🦇🔊 @0xeabz]

@gakonst @tempo Just applied. Would love to join Tempo.