Introducing BasilicEVM

Note: Since this post, BasilicEVM has grown into a broader and more flexible EVM development starter. I still recommend the 0x API and Codex.io integrations for production applications, but the template no longer includes them by default. For the current features and integrations, see the BasilicEVM GitHub repository.

The starter you pick for an EVM app sets a lot of defaults: types, wallets, UI, and how you talk to the chain. BasilicEVM is the stack I use to put that baseline in place for DeFi, NFTs, or a plain dApp, so I don't assemble the same pieces from scratch on every project.

BasilicEVM

What the starter includes

Gasless swaps through 0x

BasilicEVM supports gasless swaps with the 0x API v2 and the Tx Relay API, which removes gas fees from the user's side of a DEX trade. Gas is one of the most common reasons a swap fails or a user drops off, and relaying it changes a few things for the trader:

  • Fewer failed trades, because the user no longer needs a native-token balance to cover gas.
  • Protection from MEV extraction on the relayed transaction.
  • A shorter trading flow without a separate gas-top-up step.

For a dApp team, that means fewer support threads about failed transactions. The implementation follows the same approach as Matcha Auto, so it builds on a relay path that already runs in production.

Market data from Codex

BasilicEVM integrates Codex.io, the blockchain data API behind products like TradingView, Matcha.xyz, and Sudoswap. Codex covers what a trading interface usually needs:

  • Real-time pricing, volume, liquidity, and wallet data across networks including Ethereum, Solana, and Arbitrum.
  • Token and NFT coverage broad enough that you don't need a custom indexer to start.
  • Real-time and historical chart data.

With that data behind an API, you can build market views and wallet activity screens without running your own indexing infrastructure, and spend that time on the product instead of on data pipelines.

The application stack

The rest of the starter is the stack I reach for on EVM products:

  • Turborepo and Bun keep a multi-package codebase fast to install and build.
  • Biome and Next.js 14 handle linting, formatting, server-side rendering, and SEO.
  • Tailwind CSS and shadcn/ui supply utility styles and accessible components.
  • viem and wagmi give type-safe chain calls and React hooks.
  • RainbowKit handles wallet connection with a customizable UI.

Clear conventions plus AI-assisted tools like Cursor and v0.dev let a team move quickly on this base without losing code quality.

How to contribute

BasilicEVM is early and deliberately minimal. If you're adding features, improving documentation, or experimenting with the template, open an issue or a pull request in the repository linked above.

Related writing