Smart Contracts

Smart Contract Development

Contracts that hold real money. Architecture, implementation, third-party audit, mainnet, and the maintenance nobody quotes for.

Cancel any week. Last week refunded if we didn't blow you away. No hours tracked.

// 01

What We Do

Contract work is mostly decisions, not Solidity. We make those decisions explicit before anything ships to an address that cannot be changed.

Contract Architecture

The decisions that get expensive to reverse once you have deployed.

  • Storage layout and access control
  • What belongs on-chain and what does not
  • Upgrade path chosen before launch, not after
  • Failure modes and pause conditions

Solidity and Rust Implementation

EVM L1 and L2 in Solidity, Solana and NEAR in Rust.

  • ERC-20, ERC-721, ERC-1155 and custom standards
  • Protocol logic with real accounting
  • Gas-aware implementation, measured rather than guessed
  • Backend and indexer integration

Testing and Invariants

Foundry and Hardhat suites that model an adversary, not a happy path.

  • Invariant and fuzz testing
  • Fork tests against live mainnet state
  • Adversarial cases: MEV, reentrancy, oracle failure
  • Coverage gates enforced in CI

Upgradeability Decisions

Proxy, immutable, or migration. Each one costs you something different.

  • Transparent and UUPS proxy trade-offs
  • Immutable contracts with a planned migration path
  • Storage-collision safety across upgrades
  • Timelock and governance over upgrade keys

Third-Party Audit Coordination

We do not audit our own code. We prepare it, brief the auditor, and fix what comes back.

  • Audit-ready specs and documentation
  • Auditor selection and scoping
  • Remediation and re-review
  • Published report, as on LivLive

Deployment and Monitoring

Mainnet is where the work starts, not where it stops.

  • Deterministic, reproducible deploys
  • Signing keys in AWS KMS, never on a laptop
  • Event monitoring and alerting
  • Ongoing maintenance under retainer
// 02

How we approach contract work

We start from audited, battle-tested patterns and write custom code only where the use case genuinely is custom. Before we quote, we will tell you which parts of your idea do not need a contract at all. Gas is measured against our own engagement history rather than estimated: see where gas costs actually went across our Web3 mandates. For the wider picture, start at Web3 and blockchain development.

// 03

When a smart contract is the wrong answer

A contract earns its cost when value moves between parties who do not trust each other, or when the record has to be publicly verifiable. It does not earn its cost when a database already solves the problem, when the only argument for it is that investors want a token, or when the logic will need to change every quarter. Immutability is a feature until it is your product roadmap. We turn down contract work that fails that test, because the cheapest contract is the one you did not need.

Have a contract to build, or one you inherited?

Send us the spec, or the repo. You get an architecture read and a real number, not a discovery call.

// proof

Proof, not promises

These are selected projects, not our full portfolio. We have shipped 75+ products since 2018.

What clients say

Google

THE agency to go for blockchain development. Super experienced and highly professional team. Love to work with them.

Richard Leitgeb
Original
LinkedIn

For technical questions on blockchain and NFT, I always come back to Kevin. He has familiarized himself very well in this area, and the expertise he brings is certainly essential for projects like these. I can only recommend everyone get in touch with Kevin on these topics.

Fritz Fahringer Klarheit vor KI
Trustpilot

Experts in smart contract development.

CJ
Original

Independently rated 4.5/5 on Trustpilot Read the reviews

FAQs

Honest answers about smart-contract delivery

End any week, with one message. No notice period, no exit interview, no fine print. We invoice weekly, so the most you’re ever committed to is the current week.
It’s in your contract: tell us, and we refund that week. No questions, no invoices to dispute, no calls to escalate. The only rule: refunds apply to the most recent week.
Because hours are the wrong metric. If we’re optimizing for hours billed, we’re not optimizing for your outcome. The deal is simpler: every week, we earn the next one. If we don’t, you don’t pay. We’re free to spend zero hours or sixty. What matters is whether you’re blown away.
We work with operators, not lottery winners. If a request would require breaking physics, the law, or a third party’s systems, we say so, and if we can’t align, we walk. The guarantee is mutual: you can fire us any week; we can also fire ourselves.
A focused ERC-20 or NFT deployment with custom logic and a thin dApp lands around €15-35k including mainnet rollout. A protocol with custodial logic, integrations, and a third-party audit runs €60-150k+ depending on audit scope. Production-grade wallets, bridges, or new L1/L2 infrastructure start around €100k and 3-6 months. We put audit, gas-optimization passes, and post-launch monitoring inside the proposal, so the number you sign is the number you pay.
Both, and we default to the safer one. We start from OpenZeppelin and other production-proven implementations whenever they fit, and write custom smart contracts when the use case is genuinely novel. Greenfield is sometimes necessary. Starting from code that has already survived mainnet is almost always cheaper and safer.
No, and you should be wary of anyone who offers to. We coordinate an independent third-party audit and fix the findings, but we do not mark our own homework. On LivLive the Resonance Security report is published. We budget the audit into the plan from day one rather than treating it as an optional extra at the end.
EVM: Ethereum L1, Optimism, Arbitrum, Base, Polygon, and zkSync. Non-EVM: Solana, NEAR, and Internet Computer. We are chain-agnostic on purpose. We will tell you when moving to another chain is right and when it is tribalism that will cost you users.
Yes, that is a large share of the work. We inherited a prototype on LightBridge and progressively replaced the weak architectural decisions while it stayed live. We start with a read of the deployed bytecode, the test suite, and the upgrade keys, then tell you honestly whether hardening or redeploying is cheaper.
// Get to know us

Get to know us

Long-term relationships over quick wins.