--- title: "Smart Contract Development" canonical: https://wavect.io/services/smart-contract-development/ language: en description: "Smart contract development from architecture to mainnet. Solidity and Rust, Foundry invariant tests, third-party audit coordination, deployment and monitoring." image: "https://wavect.io/img/general/bak/open_graph_preview.jpg" --- Smart Contracts # Smart Contract Development Contracts that hold real money. Architecture, implementation, third-party audit, mainnet, and the maintenance nobody quotes for. - $2M+ Raised through LivLive, the RWA product whose contracts we built [See the case study](/case-studies/livlive/) - Audited Resonance Security audit published against the LivLive contracts [See the case study](/case-studies/livlive/) - $1M+ Secured by the LightBridge contracts on mainnet [See the case study](/case-studies/lightbridge/) // 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](/blog/web3-mandates-gas-cost-l1-l2-hindsight/). For the wider picture, start at [Web3 and blockchain development](/services/blockchain/). // 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. // proof ## Proof, not promises ### [LivLive](/case-studies/livlive/) - **Status:** Live - **Outcome:** +1,000 - Concurrent Users - **Summary:** AR-RWA platform: $2M+ raised through the product, 1,000+ concurrent users, six weeks flat. - **Stack:** Solidity, Typescript, React ### [LightBridge](/case-studies/lightbridge/) - **Status:** Live - **Outcome:** 6 chains - Network support - **Summary:** Engineered Boba's official LightBridge with their team: 6-chain near-instant transfers, $1M+ secured in production. - **Stack:** Typescript, Python, GraphQL ### [ZybraMoney](/case-studies/zybra-money/) - **Status:** Live - **Outcome:** Weekly - Release Gates Held - **Summary:** QA governance through a high-change rebuild, release safety held weekly, hundreds of defects closed. - **Stack:** Node.js, Typescript, PostgreSQL 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. Read more → Richard Leitgeb Original 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." data-quote-original=" **Bei Fragen zu Blockchain und NFT greife ich bei technischen Fragestellungen gerne immer wieder auf Kevin zurück.** Er hat sich hier sehr gut eingearbeitet und die Expertise, die er mitbringt, ist für derartige Projekte mit Sicherheit unerlässlich. Kann deshalb nur jedem empfehlen, sich zu diesen Themen mit Kevin in Verbindung zu setzen." data-original-lang=de> 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. Read more → Fritz Fahringer Klarheit vor KI Translated · tap for original Trustpilot **Experts in smart contract development.** Read more → CJ Original Independently rated 4.5/5 on Trustpilot [Read the reviews](https://www.trustpilot.com/review/wavect.io) [![Clutch Top Smart Contract Development Company in Austria 2026 award for Wavect](/img/awards/clutch-top-smart-contract-development-company-austria-2026_hu_52411afb91c9353b.webp) Verified on Clutch · 2026 Top Smart Contract Development Company in Austria View our Clutch profile](https://clutch.co/profile/wavect-gmbh) [![Clutch Top Blockchain Company in Austria 2026 award for Wavect](/img/awards/clutch-top-blockchain-company-austria-2026_hu_f3bd0de76b443d6d.webp) Verified on Clutch · 2026 Top Blockchain Company in Austria View our Clutch profile](https://clutch.co/profile/wavect-gmbh) ## FAQs Honest answers about smart-contract delivery ### How does the weekly cancellation actually work? 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. ### What if I'm not blown away by the work? 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. ### Why don't you track hours? Because hours are the wrong metric. If we optimize for hours billed, we do not optimize for your outcome. The deal is simpler: every week has a defined result, and we earn the next week by delivering it. You pay for progress against that result, not for a timesheet. ### What does 'expectations detached from reality' mean? 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. ### What does smart-contract development cost? 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. ### Do you write contracts from scratch or fork existing ones? 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](/glossary/smart-contract/) 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. ### Do you audit the contracts you write? 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](/case-studies/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. ### Which chains do you actually ship on? 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. ### Can you take over contracts somebody else wrote? Yes, that is a large share of the work. We inherited a prototype on [LightBridge](/case-studies/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. // More in ## More in Web3 & Blockchain ### [Web3 & Blockchain](/services/blockchain/) The hub: dApps, payments, scaling and the chains we ship on. Routes to the capability you actually need. ### [Account Abstraction](/services/account-abstraction-development/) ERC-4337 smart accounts, paymasters, session keys and recovery. Three production SDKs behind us. ### [Web3 Wallets](/services/web3-wallet-development/) Smart, embedded and invisible wallets, plus MetaMask Snaps. Non-custodial by default. ### [Cross-Chain Bridges](/services/cross-chain-bridge-development/) We built a six-chain production bridge, which is mostly why we will tell you when not to build one. ### [Zero-Knowledge](/services/zero-knowledge/) Privacy by cryptographic proof, not policy: ZK identity, private transactions, and ZK rollups. // Get to know us ## Get to know us Long-term relationships over quick wins. [![Blogs](/img/services/gtku_blogs_hu_d7e3f659443e93f9.webp) Read our Blog](/blog/overview/) [![No BS Around Tech Podcast](/img/services/gtku_podcast_hu_aac94ba51d8a6f9f.webp) No BS Around Tech Podcast](/#trust-podcast) [![Image Gallery](/img/services/gtknu_gallery_hu_451025d2d15b7558.webp) Get some Impressions](/#image-gallery) ## Structured Data ```json { "@context": "https://schema.org", "@graph": [ { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ], "employee": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "founder": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "legalRepresentative": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "name": "Wavect GmbH", "subjectOf": { "@id": "https://wavect.io/verified-claims.json#dataset", "@type": "Dataset", "creator": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "description": "A machine-readable registry of quantitative and qualitative claims published by Wavect, with review dates, localized page appearances and public third-party citations where available.", "inLanguage": "en", "isAccessibleForFree": true, "license": "https://creativecommons.org/licenses/by/4.0/", "name": "Wavect verified publication claims", "url": "https://wavect.io/verified-claims.json" }, "url": "https://wavect.io/" }, { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "sameAs": [ "https://www.wikidata.org/wiki/Q139796365", "https://www.linkedin.com/in/wsdt", "https://github.com/wsdt" ], "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "sameAs": [ "https://www.wikidata.org/wiki/Q139796367", "https://www.linkedin.com/in/jocr77/", "https://github.com/jo-chris" ], "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/#website", "@type": "WebSite", "inLanguage": [ "en", "de", "es", "zh" ], "name": "Wavect", "potentialAction": { "@type": "SearchAction", "query-input": "required name=search_term_string", "target": { "@type": "EntryPoint", "urlTemplate": "https://wavect.io/search/?q={search_term_string}" } }, "publisher": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "url": "https://wavect.io/" }, { "@id": "https://wavect.io/verified-claims.json#lightbridge-value-secured", "@type": "Claim", "appearance": { "@id": "https://wavect.io/services/smart-contract-development/#webpage", "@type": "WebPage", "inLanguage": "en", "url": "https://wavect.io/services/smart-contract-development/" }, "author": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "dateModified": "2026-08-04", "identifier": "lightbridge-value-secured", "inLanguage": "en", "text": "$1M+ moves through LightBridge, secured in production on mainnet." }, { "@id": "https://wavect.io/verified-claims.json#livlive-raised-through-product", "@type": "Claim", "appearance": { "@id": "https://wavect.io/services/smart-contract-development/#webpage", "@type": "WebPage", "inLanguage": "en", "url": "https://wavect.io/services/smart-contract-development/" }, "author": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "dateModified": "2026-08-04", "identifier": "livlive-raised-through-product", "inLanguage": "en", "text": "$2M+ was raised through LivLive, the AR-RWA product Wavect built." }, { "@id": "https://wavect.io/verified-claims.json#livlive-third-party-audit", "@type": "Claim", "appearance": { "@id": "https://wavect.io/services/smart-contract-development/#webpage", "@type": "WebPage", "inLanguage": "en", "url": "https://wavect.io/services/smart-contract-development/" }, "author": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "citation": { "@type": "WebPage", "url": "https://github.com/ResonanceCybersecurity/audits/blob/main/Solidity%20Smart%20Contract%20Audits/Audit_Report_LIV-NFT_FINAL_22.pdf" }, "dateModified": "2026-08-04", "identifier": "livlive-third-party-audit", "inLanguage": "en", "text": "The LivLive contracts carry a published third-party security audit by Resonance Security." }, { "@id": "https://wavect.io/verified-claims.json#web3-mandates-gas-breakdown", "@type": "Claim", "appearance": { "@id": "https://wavect.io/services/smart-contract-development/#webpage", "@type": "WebPage", "inLanguage": "en", "url": "https://wavect.io/services/smart-contract-development/" }, "author": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "dateModified": "2026-08-04", "identifier": "web3-mandates-gas-breakdown", "inLanguage": "en", "text": "Across 21+ Web3 mandates Wavect has shipped, roughly 60-75% of cumulative gas cost went to write transactions on user-facing flows. Aggregate ranges from engagement history, not exact per-project audits." } ] } ``` ```json { "@context": "https://schema.org", "@graph": [ { "@id": "https://wavect.io/services/smart-contract-development/#service", "@type": "Service", "areaServed": [ { "@type": "Country", "name": "Austria" }, { "@type": "Place", "name": "Worldwide" } ], "category": "Web3 & Blockchain", "description": "Smart contract development from architecture to mainnet. Solidity and Rust, Foundry invariant tests, third-party audit coordination, deployment and monitoring.", "name": "Smart Contract Development", "provider": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "serviceType": "Smart Contract Development", "url": "https://wavect.io/services/smart-contract-development/" }, { "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "item": "https://wavect.io/", "name": "Home", "position": 1 }, { "@type": "ListItem", "item": "https://wavect.io/services/overview/", "name": "Services", "position": 2 }, { "@type": "ListItem", "item": "https://wavect.io/services/blockchain/", "name": "Web3 & Blockchain", "position": 3 }, { "@type": "ListItem", "item": "https://wavect.io/services/smart-contract-development/", "name": "Smart Contract Development", "position": 4 } ] }, { "@id": "https://wavect.io/services/smart-contract-development/#webpage", "@type": "WebPage", "description": "Smart contract development from architecture to mainnet. Solidity and Rust, Foundry invariant tests, third-party audit coordination, deployment and monitoring.", "inLanguage": "en", "isPartOf": { "@id": "https://wavect.io/#website", "@type": "WebSite" }, "mainEntity": { "@id": "https://wavect.io/services/smart-contract-development/#service" }, "name": "Smart Contract Development", "url": "https://wavect.io/services/smart-contract-development/" } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "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." }, "name": "How does the weekly cancellation actually work?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "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." }, "name": "What if I'm not blown away by the work?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Because hours are the wrong metric. If we optimize for hours billed, we do not optimize for your outcome. The deal is simpler: every week has a defined result, and we earn the next week by delivering it. You pay for progress against that result, not for a timesheet." }, "name": "Why don't you track hours?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "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." }, "name": "What does 'expectations detached from reality' mean?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "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." }, "name": "What does smart-contract development cost?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "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." }, "name": "Do you write contracts from scratch or fork existing ones?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "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." }, "name": "Do you audit the contracts you write?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "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." }, "name": "Which chains do you actually ship on?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "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." }, "name": "Can you take over contracts somebody else wrote?" } ], "speakable": { "@type": "SpeakableSpecification", "cssSelector": [ ".faq-question", ".faq-answer" ] } } ```