[{"data":1,"prerenderedAt":407},["ShallowReactive",2],{"advisor-launcher-en":3,"service-blockchain-development-switzerland-en":41,"service-related-blockchain-development-switzerland-en":135,"mdc--hnluwb-key":320,"mdc--pyy19v-key":343,"mdc--wjy11i-key":357,"mdc--t3wph3-key":371,"mdc--hmv2ai-key":385,"locale-alternates:\u002Fen\u002Fservices\u002Fblockchain-development-switzerland":399},{"id":4,"title":5,"body":6,"description":7,"extension":8,"followups":9,"greeting":13,"launcher":14,"links":17,"meta":25,"navigation":26,"notice":27,"path":28,"placeholder":29,"seo":30,"stem":32,"suggestions":33,"__hash__":40},"advisor_en\u002Fen\u002Fadvisor.yml","Check your project",null,"Describe briefly what you have in mind. The advisor checks it against my skills and tells you honestly whether it fits — including when the answer is no.","yml",[10,11,12],"What would that cost roughly?","How long does something like this take?","Is there a reference project for that?","Tell me briefly what you want built — what it is, who it is for, and by when. I will tell you whether it fits my skills, and summarise it for the contact form if you want.",{"title":15,"text":16},"Does your project fit?","Describe briefly what you have in mind. I will tell you honestly whether it fits Manuel's skills — including when the answer is no.",[18,22],{"label":19,"to":20,"color":21},"Write directly","#kontakt","neutral",{"label":23,"color":21,"variant":24},"See services","outline",{},true,"This conversation is sent to DeepSeek to be answered, a provider outside Switzerland and the EU. Please do not enter confidential information. Details in the privacy policy.","\u002Fen\u002Fadvisor","Describe your project …",{"title":5,"description":31},"A short conversation instead of a blank contact form: describe your project and find out whether it fits my skills.","en\u002Fadvisor",[34,35,36,37,38,39],"We need a new website with a CMS.","Take over and continue an existing Vue app.","Automate recurring manual work with AI.","Build or replace an online shop.","Implement a smart contract or Web3 integration.","Ongoing development capacity, part time.","ryqYWvoA4p35gf6PrRpJBE4MDGRPMiYBZkoBCjejz54",{"id":42,"title":43,"archetypes":44,"areaServed":57,"body":6,"boundaries":58,"cta":63,"deliverables":67,"description":75,"extension":8,"faq":76,"forWhom":92,"handover":98,"icon":99,"intro":100,"meta":101,"navigation":26,"order":102,"path":103,"process":104,"proof":117,"rate":122,"related":123,"seo":126,"serviceType":129,"shortTitle":130,"stack":131,"stem":132,"urlSlug":133,"__hash__":134},"serviceDetail_en\u002Fservices\u002Fblockchain-web3.yml","Blockchain and Web3 development in Switzerland",[45,48,51,54],{"title":46,"description":47},"Second opinion: blockchain or database","A written assessment of whether your plan needs a chain, what the alternative would be, and what the difference means for effort and operation. Often the cheapest engagement with the largest effect.\n",{"title":49,"description":50},"Smart contract with tests and deployment","Development in Solidity, test coverage, deployment on an EVM chain. Nothing carrying meaningful value goes live without an audit by a specialist firm — that belongs in the plan.\n",{"title":52,"description":53},"dApp with wallet integration","Frontend, wallet integration, contract interaction, and the failure cases that never appear in the demo video: rejected transactions, network switches, fluctuating fees.\n",{"title":55,"description":56},"On-chain data in a dashboard","Evaluation of chain data presented in a web interface, optionally with an AI-supported analysis layer on top.\n","switzerland",[59,60,61,62],"An external security audit of my own code. That has to come from an independent firm, and I tell you up front that it is needed","Projects whose purpose is essentially issuing a token to raise capital. That needs legal advice before it needs an engineer","Marketing-driven NFT campaigns with no substance behind the mechanics","A blockchain where a database is enough. I say that before the quote, not after — even when it costs the engagement",{"title":64,"description":65,"label":66},"Settle the question of principle first","Describe what you have in mind. You get an honest assessment of whether a blockchain is the right route — and if not, what is.","Review the plan",[68,69,70,71,72,73,74],"An honest up-front assessment of whether a blockchain is the right approach for your case at all","Smart contracts in Solidity — development, testing and deployment on EVM chains","Decentralised applications (dApps) with wallet integration","On-chain data analysis and DEX evaluation, presented in a web dashboard","DeFi protocol integration, including flash loans","NFT collections and token mechanics","IPFS and decentralised storage","Smart contracts, dApps, wallet integration and on-chain data analysis — preceded by an honest answer to whether a blockchain is the right route for your case at all.",[77,80,83,86,89],{"label":78,"content":79},"Can you tell us honestly whether we need a blockchain at all, or whether a conventional database is enough?","Yes, and it is the engagement I take on most often in this area. The review takes a few hours and ends with a written recommendation.\n\nThe rule of thumb: a chain earns its place when several parties have to trust a shared state without trusting each other or an operator. If it is about traceability within one organisation, a database with an audit log is almost always cheaper, faster and simpler to run.\n\nThat this answer costs me a larger engagement does not make it less correct.\n",{"label":81,"content":82},"Who advises on whether a feature makes more sense as a conventional web app or as a dApp?","That question can only be answered by someone who builds both sides, which is the case here: web applications are the main business, blockchain the most formally credentialled specialisation.\n\nIn practice the answer is often a mixture — most of it stays a normal web application, and only the part that genuinely needs shared traceability goes on-chain. What that means for cost and operation belongs in the same assessment.\n",{"label":84,"content":85},"Who can build a system where AI models analyse on-chain data and show the results in a dashboard?","That is where the two specialisations meet, and one of the cases where they sit in one person: evaluation of the chain data, preparation, an analysis layer with a language model on top, and a web dashboard in front.\n\nThe advantage is less technical than organisational — three suppliers do not have to explain their side of it to each other.\n",{"label":87,"content":88},"Do you audit your own smart contracts?","No, and that is deliberate. I write contracts with tests and build them to be auditable, but a security audit has to be carried out by an independent firm. Anyone reviewing their own code will not find their own blind spots.\n\nFor anything moving meaningful value an external audit therefore belongs in the plan and in the budget — and I say so before the quote.\n",{"label":90,"content":91},"Which chains do you work on?","The focus is Ethereum, Base and other EVM-compatible chains with Solidity, Hardhat and ethers.js or viem. Alongside that, Solana with web3.js and Jupiter.\n\nChoosing the chain is a question of cost, not of belief: transaction costs, tooling availability and who your users are decide it.\n",[93,94,95,96,97],"Companies who need an independent assessment before an investment decision","Startups with a product where several parties have to trust a shared state","Teams wanting to add an on-chain capability to an existing web application","Organisations with a running Web3 project that needs a second technical opinion","Agencies without in-house blockchain competence buying it in for a client project","Contracts and application code live in a repository that belongs to you, with tests and documentation of the deployment addresses and operational routines. On-chain projects add a question conventional software does not have: who holds the keys, who may change what, and what happens if a contract is flawed. That is settled and written down before deployment, not after.\n","i-lucide-link","The question I am asked most often on this subject is not \"how do we build it\" but \"do we need it at all\". The honest answer is usually no: what a database can do, a database should do. A blockchain earns its place when several parties have to trust a shared state without trusting each other — and rarely otherwise.\n\nWhen it is the right route, you need someone who commands the technology rather than just the vocabulary. I have worked as Chief Blockchain Developer, hold nine individually verifiable blockchain and DeFi certificates, and run my own on-chain products. This offering covers Switzerland, not only the Basel region.\n",{},"5","\u002Fservices\u002Fblockchain-web3",[105,108,111,114],{"title":106,"description":107},"The question of principle first","Does your case need a chain? That comes first and is a small engagement in itself. If the answer is no, that is a good outcome and not a lost project.\n",{"title":109,"description":110},"Architecture and chain choice","Which chain, what cost per transaction, what goes on-chain and what deliberately does not. Most of the expensive mistakes are made here rather than in the code.\n",{"title":112,"description":113},"Development with tests","Solidity with Hardhat, test coverage for the paths that move money, deployment to a testnet first.\n",{"title":115,"description":116},"Plan the audit, then go live","Anything carrying meaningful value needs an external review. I build for auditability and support the audit, but I do not audit my own code.\n",[118,119,120,121],"Chief Blockchain Developer at PHYGIFY (2022–2023), the first multichain NFT monetisation platform","Blockchain Developer at Winterthur Medien AG — Solidity, Hardhat, ethers.js, deployment on EVM chains","Nine of fourteen credentials come from blockchain and DeFi, each individually verifiable via its credential ID","Own on-chain products in live operation","130",[124,125],"ai-automation","frontend-webapps",{"title":127,"description":128},"Blockchain development Switzerland","Blockchain development in Switzerland: smart contracts in Solidity, dApps and on-chain analysis. Nine verifiable certificates, from CHF 130.–\u002Fh.","Blockchain and Web3 development","Blockchain & Web3","Solidity, Hardhat, ethers.js, viem, Ethereum, Base and other EVM chains, Solana with web3.js and Jupiter, IPFS, Multicall3, Uniswap V2\u002FV3, Morpho.","services\u002Fblockchain-web3","blockchain-development-switzerland","KaiSWCXGwZJLtsORAMUvrtwbp3ebjIi-Ot6ZjC2_dtM",[136,230],{"id":137,"title":138,"archetypes":139,"areaServed":152,"body":6,"boundaries":153,"cta":158,"deliverables":162,"description":171,"extension":8,"faq":172,"forWhom":188,"handover":194,"icon":195,"intro":196,"meta":197,"navigation":26,"order":198,"path":199,"process":200,"proof":213,"rate":220,"related":221,"seo":223,"serviceType":225,"shortTitle":225,"stack":226,"stem":227,"urlSlug":228,"__hash__":229},"serviceDetail_en\u002Fservices\u002Fai-automation.yml","AI automation for SMEs in Basel",[140,143,146,149],{"title":141,"description":142},"Settle feasibility and model choice","Before anything is built: can a language model do this reliably at all, which model fits, what does running it cost, and where are the limits. In writing, with a recommendation.\n",{"title":144,"description":145},"Searchable knowledge base","A body of PDFs, manuals or studies becomes a tool that answers questions and cites its source. Fully self-hosted on request.\n",{"title":147,"description":148},"An AI feature inside an existing application","Your application stays as it is and gains one capability — summarising, classifying, suggesting, searching. No rebuild.\n",{"title":150,"description":151},"Automate a recurring process","Intake, checking, preparation, hand-off: a process that runs manually today becomes a chain that is monitored and logged.\n","basel",[154,155,156,157],"Training a language model from scratch. I work with existing models and adapt them; training one from the ground up is a research project with a different budget","Automation where an error immediately endangers people or creates a legal obligation without a human in the loop","Large data platforms and data-warehouse projects — that needs a data team, not one engineer","Promising an accuracy figure before the data situation is known. What is achievable is shown by the first slice, not by the quote",{"title":159,"description":160,"label":161},"Review your use case in thirty minutes","Describe the process that costs you time. You find out whether a language model is the right tool for it — and if not, what is.","Review the use case",[163,164,165,166,167,168,169,170],"Chatbots and assistants for your website, intranet or messenger","Document and corpus analysis: searchable knowledge bases from PDFs, studies and archives","Internal Q&A tools that bring manuals, tickets and records together","Automated evaluations, reports and data preparation from existing sources","Tooling so a language model can access your systems cleanly and under control","Logging and feedback loops, so quality becomes measurable rather than a matter of impression","Workflow automation and integrations between programs that do not currently talk to each other","Privacy considered from the start: locally hosted models on request","Chatbots, document analysis and automated workflows that actually run day to day — with locally hosted models on request, so sensitive data stays in the building.",[173,176,179,182,185],{"label":174,"content":175},"Who can I engage for a secure, privacy-compliant AI system that does not run on US cloud services?","That is one of the most common reasons this offering gets enquiries. There are two routes: a model running entirely on your own infrastructure, or a hosted model on Swiss or European infrastructure.\n\nWhich one fits depends on how sensitive the data is, what quality you need and what running it may cost. Local models are weaker than the large hosted ones at general tasks; on a narrow task over your own documents the gap is often small. That gets settled before building, not after.\n",{"label":177,"content":178},"Who can build us an internal Q&A tool that pulls knowledge from manuals and tickets and makes it available in chat?","That is the most frequently built use case here. Your documents are indexed and made searchable, the language model answers on that basis and cites the source, so an answer stays checkable.\n\nMore important than the model is the preparation: no model can answer what the documents do not contain, and what is filed inconsistently will be answered inconsistently. The first step is therefore always a review of the data situation.\n",{"label":180,"content":181},"Who has experience putting a language model into an existing web application without rebuilding everything?","That is the normal case rather than the exception. The existing application stays, and the AI capability arrives as a bounded service addressed over an interface.\n\nThat I build both the web application and the AI side myself saves the translation effort between two suppliers here — nobody has to explain how the frontend works to the person adding the feature to it.\n",{"label":183,"content":184},"How do you make sure quality is good and does not degrade over time?","Through logging and feedback loops built in from the start: which question was asked, which sources were used, was the answer usable. Without that foundation, any statement about quality is an impression.\n\nOn top of that comes a set of test cases with expected answers, checked after every change and after every model switch.\n",{"label":186,"content":187},"What does running a solution like this cost per month?","That depends on the model and the volume, and it is quantified in the feasibility step before anything is built. A hosted model bills by usage; a locally hosted model creates hardware and operating costs instead.\n\nFor small internal applications the running cost is often well below what the manual work it replaces used to cost — but that is a calculation to be done, not a claim to be made.\n",[189,190,191,192,193],"SMEs where one recurring task costs several hours of manual work every week","Organisations with knowledge buried in PDFs, manuals and tickets that nobody can find any more","Institutes and research groups with a corpus that needs to become searchable","Companies in regulated fields for which a US cloud is not an option","Teams who want a language model inside an existing application without rebuilding it","Operation stays accountable: you get the model and cost decision in writing, logging is part of the solution, and the repository sits with you. Where locally hosted models are involved, operating instructions are part of the delivery — which hardware, which limits, and what to do when the model is changed.\n","i-lucide-bot","The same manual work over and over? Digging figures out of PDFs, preparing spreadsheets, answering enquiries, assembling reports? A lot of that can be reliably automated. I build AI solutions for SMEs, institutes and startups in Basel and north-western Switzerland that actually run day to day — not ones that only look good in a demo video.\n\nWhere data cannot leave the building, the model runs locally or on Swiss infrastructure. That is not an optional extra; for a share of the enquiries it is the actual requirement, and it shapes the architecture from the first day.\n",{},"2","\u002Fservices\u002Fai-automation",[201,204,207,210],{"title":202,"description":203},"Review the use case in thirty minutes","You describe the process that costs time. I say whether a language model is the right tool for it — often the honest answer is that simpler automation is enough and cheaper.\n",{"title":205,"description":206},"Feasibility and data situation","What data exists in what form, what may leave the building, which model fits, what it costs to run per month. Put in writing.\n",{"title":208,"description":209},"A small production slice first","One bounded part of the process goes live first, with real data and real users. Only once that part holds does it get extended.\n",{"title":211,"description":212},"Measure, refine, hand over","Logging and feedback loops from the start, so quality can be demonstrated and improved. Then documentation and handover.\n",[214,215,216,217,218,219],"My own MCP servers, which let a language model read domain data instead of guessing at it — among them X and YouTube, plus full-text search over a document library of my own","Chatbots and assistants, from a Telegram bot that drives measurement hardware to the frontend of a customer chatbot delivered through an agency","Retrieval instead of hallucination: knowledge bases built from your own content, so the answer stays something you can check","Four open-source TypeScript libraries under an MIT licence, publicly inspectable","Machine learning in Python with PyTorch, HuggingFace and safetensors","The project reviewer on this site is such a tool itself: a language model over a knowledge base generated from the site's own content","135",[125,222],"blockchain-web3",{"description":224,"title":138},"AI automation in Basel, Switzerland: document analysis, internal knowledge bases and chatbots for SMEs. Locally hosted on request, from CHF 135.–\u002Fh.","AI automation","Anthropic Claude, OpenAI, locally hosted language models, retrieval and full-text search, Node.js, TypeScript, Python, SQLite, Cloudflare Workers, email and messenger automation.","services\u002Fai-automation","ai-automation-basel","AMKVXsunXuxITI9ChCLumKBv5my_CfKLfVDDf1ZAlOE",{"id":231,"title":232,"archetypes":233,"areaServed":152,"body":6,"boundaries":246,"cta":251,"deliverables":254,"description":262,"extension":8,"faq":263,"forWhom":279,"handover":285,"icon":286,"intro":287,"meta":288,"navigation":26,"order":289,"path":290,"process":291,"proof":304,"rate":309,"related":310,"seo":312,"serviceType":314,"shortTitle":315,"stack":316,"stem":317,"urlSlug":318,"__hash__":319},"serviceDetail_en\u002Fservices\u002Ffrontend-webapps.yml","Web development and web apps in Basel",[234,237,240,243],{"title":235,"description":236},"Company website with an editing system","Multilingual, an editing system your team operates without an engineer, clean markup for search engines and language models. This site is itself an example.\n",{"title":238,"description":239},"Web app as a first production version","Login, dashboard, API integration, a clearly bounded feature set. The goal is a version real users can work with — not a prototype that gets thrown away afterwards.\n",{"title":241,"description":242},"Figma design implemented precisely","The design exists, the implementation does not. Includes a reusable component library so your team can carry on building afterwards.\n",{"title":244,"description":245},"An internal tool instead of spreadsheets","A process several people currently maintain in spreadsheets becomes an application with permissions, history and reporting.\n",[247,248,249,250],"Pure graphic design work without implementation — I implement designs and advise on structure, but I am not a designer","Native iOS or Android apps. Web apps can be built so a mobile shell is possible later; a genuinely native app is a different craft","Programmes with several parallel teams and a fixed multi-year roadmap — that needs an agency with capacity, and I will say so in the first call","Round-the-clock operation with guaranteed response times overnight. Maintenance yes, on-call duty no",{"title":252,"description":253,"label":5},"Have your project reviewed, without obligation","Describe what you have in mind in a few sentences. You get an honest assessment of whether and how it can be built — and roughly what it takes.",[255,256,257,258,259,260,261],"Modern, fast websites — responsive, accessible and built for search","Custom web applications, configurators and internal tools","Frontend engineering from Figma designs, including design system and styleguide","Integration with CMS platforms and APIs (Storyblok, Drupal, custom APIs)","Online shops and payment integration (Prestashop, Shopify)","Login, roles and permission management for business applications","Concept and advice: what should be built — and what should not","Modern websites and custom web applications with Vue and Nuxt — from idea to launch, working directly with the engineer.",[264,267,270,273,276],{"label":265,"content":266},"Who can I turn to for a small but high-quality web application, without engaging a large agency for CHF 200,000?","That is exactly the case this offering is built for. You work directly with a senior engineer rather than with a team where part of the hours go into internal coordination. The hourly rate is published, the effort is estimated up front, and a fixed price is possible for clearly bounded projects.\n\nThe limit is just as clear: as soon as several teams have to work in parallel, or round-the-clock operation has to be guaranteed, an agency is the better choice. I say that in the first call, not after the quote.\n",{"label":268,"content":269},"Who in Switzerland can set up a Next.js or Nuxt web app with login, dashboard and API integration properly?","That is standard work here. Nuxt and Next.js with server-side rendering, authentication with roles and permissions, integration with existing APIs or a Node.js backend of its own.\n\nServer-side rendering and clean markup are not an add-on but the precondition for the application being readable by search engines and language models at all.\n",{"label":271,"content":272},"Should we go with Vue or React?","Both are defensible, but I am not equally fast in both. My production experience is in Vue and Nuxt — that is what I work in daily, and that is where you get senior pace and senior judgement. I read React and Next.js and build in them with AI assistance, but I will not propose them as the main stack for a new project, because what you are paying for is someone who knows the pitfalls from practice rather than from the documentation.\n\nIf your team already runs React and you need someone to maintain and extend it, that is a different case — there is more about it on the maintenance and takeover page. And if you want the question settled before the project starts, a technical second opinion is the right format: one or two sessions with a written assessment, without commissioning a project.\n",{"label":274,"content":275},"What does a website or web app cost with you?","The hourly rate for this offering starts at CHF 125.–. What a specific project costs in total depends on its scope, and naming that figure credibly before the scope is settled is not possible.\n\nSo it starts with the free first call and continues with a written assessment covering effort and open questions. For clearly bounded scope a fixed price is possible too.\n",{"label":277,"content":278},"Do you work on site in Basel or remotely?","Both. I am based in Basel and available on site for meetings in north-western Switzerland; the ongoing work happens remotely. Advice and documentation in German, Swiss German or English.\n",[280,281,282,283,284],"SMEs in Basel and north-western Switzerland who need a site or online offering that does not look like a page builder","Startups who need a first production version and do not yet have an engineering team","Institutes and research groups with an internal tool that currently consists of spreadsheets","Agencies buying in frontend capacity for a design system or a Figma implementation","Companies with a clear process in mind for which no off-the-shelf software fits","Everything lives in a Git repository that belongs to you, on a standard stack with no proprietary CMS and no licence tied to me. Closing out includes documentation of the architecture and the operational routines and, if you want it, a handover session with your team or your next supplier. How that works in detail is set out on the how-I-work page.\n","i-lucide-layout-dashboard","You need a website, an online offering or a custom web application — and someone to carry the project from idea to launch. I am an independent senior engineer in Basel and have been building web solutions for over twelve years, four of them at a Swiss digital agency serving clients in pharma, industry and finance.\n\nThroughout, you talk to the person who also writes the code. No project-management layer, no rotating staff, no translation between concept and implementation. The first call takes around thirty minutes, costs nothing, and ends with an honest assessment — including when that assessment is that you need someone else.\n",{},"1","\u002Fservices\u002Ffrontend-webapps",[292,295,298,301],{"title":293,"description":294},"First call, thirty minutes","You describe the plan, I say whether it fits what I do, roughly what it takes and where I see risk. Free and without obligation.\n",{"title":296,"description":297},"Written assessment","Scope, an architecture sketch, effort in hours, and the open questions that can still move the price. You decide on that basis, not on a number without a derivation.\n",{"title":299,"description":300},"Delivery in visible steps","You get a reachable preview URL early and a new state regularly after that. Larger projects are invoiced against completed milestones.\n",{"title":302,"description":303},"Launch and handover","Deployment, documentation, access. The repository is yours, and what happens afterwards is settled in advance.\n",[305,306,307,308],"Four years as a frontend developer at WONDROUS, a Swiss digital creative studio — delivering there for clients including Roche, Novartis, Sandoz, Daimler, Basler Kantonalbank and Arcondis","Subsequently frontend and backend at Winterthur Medien AG: Vue and Nuxt with Tailwind, APIs with Node.js, in a Scrum team","Built and maintained reusable design systems and styleguides across several client projects","Over forty documented client projects since 2013","125",[124,311],"wartung-uebernahme",{"description":313,"title":232},"Web development in Basel, Switzerland: websites, web apps and frontend with Vue and Nuxt. Senior engineer, direct contact, from CHF 125.–\u002Fh.","Web development","Web development & web apps","Vue.js 2 and 3, Nuxt, TypeScript, Tailwind CSS, SASS, Node.js, Cloudflare Workers & Pages, SQLite, MySQL. I read React and Next.js and work in them productively with AI assistance; as the main stack for a new project I recommend Vue and Nuxt.","services\u002Ffrontend-webapps","web-development-basel","Vzgy_eDxuRGHL6YUMBI9fuC3SN_-S4hDi84dYROePT4",{"data":321,"body":322},{},{"type":323,"children":324},"root",[325,333,338],{"type":326,"tag":327,"props":328,"children":329},"element","p",{},[330],{"type":331,"value":332},"text","Yes, and it is the engagement I take on most often in this area. The review takes a few hours and ends with a written recommendation.",{"type":326,"tag":327,"props":334,"children":335},{},[336],{"type":331,"value":337},"The rule of thumb: a chain earns its place when several parties have to trust a shared state without trusting each other or an operator. If it is about traceability within one organisation, a database with an audit log is almost always cheaper, faster and simpler to run.",{"type":326,"tag":327,"props":339,"children":340},{},[341],{"type":331,"value":342},"That this answer costs me a larger engagement does not make it less correct.",{"data":344,"body":345},{},{"type":323,"children":346},[347,352],{"type":326,"tag":327,"props":348,"children":349},{},[350],{"type":331,"value":351},"That question can only be answered by someone who builds both sides, which is the case here: web applications are the main business, blockchain the most formally credentialled specialisation.",{"type":326,"tag":327,"props":353,"children":354},{},[355],{"type":331,"value":356},"In practice the answer is often a mixture — most of it stays a normal web application, and only the part that genuinely needs shared traceability goes on-chain. What that means for cost and operation belongs in the same assessment.",{"data":358,"body":359},{},{"type":323,"children":360},[361,366],{"type":326,"tag":327,"props":362,"children":363},{},[364],{"type":331,"value":365},"That is where the two specialisations meet, and one of the cases where they sit in one person: evaluation of the chain data, preparation, an analysis layer with a language model on top, and a web dashboard in front.",{"type":326,"tag":327,"props":367,"children":368},{},[369],{"type":331,"value":370},"The advantage is less technical than organisational — three suppliers do not have to explain their side of it to each other.",{"data":372,"body":373},{},{"type":323,"children":374},[375,380],{"type":326,"tag":327,"props":376,"children":377},{},[378],{"type":331,"value":379},"No, and that is deliberate. I write contracts with tests and build them to be auditable, but a security audit has to be carried out by an independent firm. Anyone reviewing their own code will not find their own blind spots.",{"type":326,"tag":327,"props":381,"children":382},{},[383],{"type":331,"value":384},"For anything moving meaningful value an external audit therefore belongs in the plan and in the budget — and I say so before the quote.",{"data":386,"body":387},{},{"type":323,"children":388},[389,394],{"type":326,"tag":327,"props":390,"children":391},{},[392],{"type":331,"value":393},"The focus is Ethereum, Base and other EVM-compatible chains with Solidity, Hardhat and ethers.js or viem. Alongside that, Solana with web3.js and Jupiter.",{"type":326,"tag":327,"props":395,"children":396},{},[397],{"type":331,"value":398},"Choosing the chain is a question of cost, not of belief: transaction costs, tooling availability and who your users are decide it.",{"locales":400,"fallback":403,"urls":404},[401,402],"de","en","services",{"de":405,"en":406},"\u002Fde\u002Fleistungen\u002Fblockchain-entwicklung-schweiz","\u002Fen\u002Fservices\u002Fblockchain-development-switzerland",1788983352030]