GitMyABI

We kept hitting the same “bug” over and over:

Frontend breaks → hours debugging → turns out… outdated ABI.

Not a hard problem.

Just a stupid, recurring one.

So, it seems that everyone has a workaround:

• copy ABI into frontend

• publish to npm

• CI scripts

• “just remember to update it”

Let’s be honest here: none of these scale.

Frontend has CI/CD.

Backends have CI/CD.

But the interface between them is still handled like it’s 2015.

So we started building GitMyABI.

The Idea is simple:

Stop treating ABIs like files.

Treat them like versioned build artifacts.

Push → build → versioned ABI → consume.

No copying. No guessing. No “did you update it?” No Ghost bugs.

And what’s interesting is this becomes even more critical with AI.

If AI agents are going to interact with smart contracts, they need deterministic, versioned interfaces — not random JSON files floating around repos.

Curious if others think this is actually a problem

or if everyone’s just… used to the pain?