Verbwire.

A finished sentence, signed off by its authors

Visit verbwire.com today and you won't find a pricing page. You'll find a note. The founders explain, calmly, that the company served its purpose and they've moved on. It is a rare thing on the internet - a startup that closed the door, turned off the lights, and wrote a tidy paragraph explaining why instead of just letting the domain expire.

For a few years, though, Verbwire was the on-ramp. It turned the entire smart-contract stack into a single REST API. Tens of thousands of developers used it. Millions of API calls ran through it. Hundreds of hackathons ran on it. And then the world it was built for changed, and so did the people who built it.

To understand why that note reads less like a failure and more like a closing argument, you have to go back to the problem - the one that, for a while, was genuinely miserable.

Building on a blockchain used to be a punishment

In 2021 and 2022, "just deploy a smart contract" was a sentence that hid a week of suffering. You learned Solidity. You wired up Hardhat. You wrestled with gas estimation, RPC nodes, IPFS pinning, wallet libraries, and a toolchain that broke if you looked at it wrong. A developer who was fluent in Python or Java suddenly had to become a blockchain specialist to mint a single token.

The promise of Web3 was openness. The reality was a velvet rope and a bouncer who only spoke Solidity.

That gap - between the millions of developers who could build and the few who knew the arcane stack - was the whole opportunity. Close it, and you don't onboard a few engineers. You onboard a generation.

Two traders who decided the abstraction was the product

Verbwire was founded in 2022 by Bankole Omodunbi and Justin Bojarski - and they did not arrive from a hackathon. They arrived from Wall Street. Omodunbi spent roughly eight years at Credit Suisse, an MD in equities quant trading who ran principal trading products before leaving in 2021. People who build pricing systems for a living tend to have strong opinions about complexity: namely, that other people shouldn't have to see it.

Their bet was contrarian and a little stubborn: that the right product wasn't a better blockchain, a faster chain, or a flashier token. It was the boring part - a clean API that swallowed the entire stack so nobody else had to taste it. In a market obsessed with speculation, they chose plumbing.

One key. Sixty-plus endpoints. The whole stack, hidden.

Here is the elegant part. A developer never touched Solidity. They sent an HTTP request, and Verbwire handled deployment, gas, storage, and the chain-specific weirdness underneath. Write in any language - Python, Java, JavaScript, C++ - and the blockchain answered like any ordinary API.

It was, in the kindest sense, Stripe for the blockchain: the magic was in everything you didn't have to see.

The numbers that did the arguing

Mission statements are cheap. Usage isn't. Verbwire's case rested less on what it claimed and more on how many people quietly shipped on top of it.

It also showed up where builders actually gather. A spot at the Cross Chain Coalition Web3 Demo Day. Workshops on YouTube. An SDK so the API could be called without even thinking about the API. The proof wasn't a billboard. It was a million quiet calls a developer never had to debug.

Onboard the next million, then get out of the way

The goal was never to make Verbwire indispensable forever. It was to make Web3 accessible - to help the next million-plus developers walk through a door that used to be locked. That framing matters, because it explains the ending. A company built to lower a barrier has a strange relationship with its own success: if the barrier falls for other reasons, the company has, in a sense, won.

So when the founders wrote that AI can now write, deploy and audit smart contracts directly, they weren't filing an obituary. They were noting that the moat they dug - human-friendly abstraction - had been filled in by the rising tide of better tools. The complexity gap they monetized got smaller. Which was always the point.

The abstraction outlived the company

Verbwire's real legacy isn't a product you can still buy. It's an expectation. Once developers learned that talking to a blockchain could feel like calling any other API, there was no going back to a week of Hardhat configs. That expectation - that hard things should be one request away - is now the default. Whether the next layer is a Verbwire-style API or an AI that writes the contract for you, the lesson is the same: the friction was never sacred.

The founders took that lesson with them, into frontier AI, quantum computing and autonomous machines - bigger stacks, hiding bigger messes. Different domain, identical instinct.

Back to that note on the homepage

So there's no pricing page. There's a paragraph. Read it again now and it lands differently - not as a company giving up, but as a company that finished its sentence. It set out to make the blockchain feel like an API, and for a few crowded years, it did exactly that, for more developers than most louder startups ever reached.

Most failed startups leave a 404. Verbwire left a thesis: powerful technology shouldn't require a PhD to use. The note on the homepage isn't an ending. It's a receipt.

Demos, in the founders' own words