Back to home
Web3

Web3 & blockchain

Smart contracts, dApps and on-chain integrations — only when it genuinely makes sense.

Overview

I don't push Web3 on projects that don't need it. But when it fits — token-gated access, on-chain provenance, decentralized identity, payments outside traditional rails — I build the contracts, the front-end and the audit trail. Solidity, Ethers and Hardhat are tools I use daily.

What you get

Smart contracts

Solidity contracts written, tested, audited, deployed to mainnet or L2.

dApp front-end

Wallet connect, transaction UX, gas-aware flows — built with Next.js + wagmi.

Off-chain plumbing

Indexers, webhooks, subgraphs — the boring half of every Web3 product.

Security & gas review

Internal audit, gas profiling, deployment checklists. Optional external audit.

How I work
  1. Week 1 — ArchitectureChain, contracts, data flows. We decide what goes on-chain and what doesn't.
  2. Weeks 2-3 — ContractsImplementation, unit tests, testnet deploy.
  3. Weeks 4-5 — dAppFront-end, wallet flows, end-to-end testing.
  4. Week 6 — MainnetAudit pass, deploy, monitoring.
Tech stack
SolidityEthers.jsHardhatFoundrywagmiNext.jsThe Graph
Timeline
4 to 10 weeks depending on contract complexity
Pricing
From €8k — varies a lot based on audit needs.
Frequently asked
Do I really need Web3?

Probably not. I'll tell you straight if a regular database serves you better. When Web3 wins, it's usually because of trustless ownership or jurisdiction-neutral payments.

Which chains do you work on?

Mostly Ethereum, Base, Optimism, Arbitrum and Polygon. Solana on request for specific use cases.

What about audits?

I do an internal audit and use static analyzers. For mainnet money-handling contracts, an external audit is non-negotiable — I'll connect you with firms I trust.

Ready to start?

Tell me about your project in a few lines — I get back within 24h.