Blockchain & Web3 Development Company in Amsterdam

The MiCA question comes first on any Amsterdam Web3 build, because a licensed activity and an internal pilot are entirely different cost structures. Engagements break into a scoped consortium proof-of-concept on Hyperledger Besu or Fabric with three to five participating nodes, one or two production business workflows, a basic explorer dashboard, and the documented governance pack over ten to fourteen weeks, a production smart-contract system on Polygon PoS, Polygon zkEVM, or Arbitrum One with formal verification on financial contracts, OpenZeppelin-based role and permission control, Tenderly and Defender monitoring, and a documented incident-response runbook, or a regulated MiCA-aligned tokenisation platform or crypto-asset service provider build, including the DNB and AFM classification work, integrated custody with a licensed counterparty, and the Wwft AML transaction-monitoring overlay. Amsterdam rates sit just below London and Zurich on the same scope but above Berlin and Madrid because of the Adyen, ING, and DNB engineering bar. Every engagement is fixed-fee in EUR with milestone draws rather than open time-and-materials.

Almost certainly, depending on the activity. Under MiCA, in force from 30 December 2024, crypto-asset service providers (CASPs) require authorisation from the relevant national competent authority before offering custody, exchange, trading platform operation, portfolio management, advice, or transfer services. In the Netherlands, DNB and the AFM share supervision with a clear split: DNB handles prudential and AML supervision under the Wwft, the AFM handles conduct and market-integrity supervision under the Wft (Wet op het financieel toezicht). The existing Wwft crypto-service-provider registration regime has been transitioning into the MiCA CASP licence through 2025 and 2026. We start every Amsterdam tokenisation or CASP engagement with a written regulatory classification memo that maps your intended activity to the relevant MiCA Title and the Wft category, and we engineer the platform against the technical and organisational requirements DNB and the AFM publish. We are not lawyers — your law firm signs off on the classification — but we have engineered against the resulting requirements at production scale across multiple EU jurisdictions.

Yes, and it is the conversation most Amsterdam payments-adjacent blockchain projects actually need. The European Central Bank's TARGET Instant Payment Settlement (TIPS) service and the EBA Clearing RT1 rail both speak ISO 20022 pacs.008 and pacs.002 messages, and Adyen plus Mollie engineering treat any DLT settlement layer as a parallel rail that must reconcile cleanly with SEPA Instant rather than replace it. We engineer the integration as a two-leg pattern: an on-chain settlement event triggers an ISO 20022 message into the SEPA Instant rail through the licensed PSP, with idempotency keys and reconciliation hooks that survive the ten-second SEPA Instant timeout. Atomic settlement across both legs uses a hashed timelock or an escrow-and-release pattern depending on the trust model. The DNB Payments Department reviewed comparable patterns at peer banks during the eurozone wholesale-CBDC exploratory work, and our reference implementations are designed to that bar.

MiCA applied fully to crypto-asset service providers from 30 December 2024, with grandfathering provisions running into 2026 for firms already authorised under national regimes. For an Amsterdam issuer or CASP, our engineering work covers the white-paper notification workflow under MiCA Title II (for asset-referenced and e-money tokens, Titles III and IV apply respectively), the technical and organisational arrangements under Title V (custody segregation, client-asset reconciliation, complaints handling, conflicts-of-interest registers, operational resilience under DORA), the prudential reporting feeds into DNB, and the AML hooks under the EU Transfer of Funds Regulation. DNB is the competent authority for prudential and AML matters in the Netherlands, the AFM is the competent authority for conduct and market integrity, and both publish detailed Q and A guidance we engineer to. Your law firm and DNB plus the AFM negotiate the licence itself; we deliver the platform that meets the technical requirements.

The Autoriteit Persoonsgegevens (AP) is among the more active EU data-protection authorities and has fined companies meaningfully in recent years for compliance gaps. Article 17 of the GDPR (right to erasure) and the AP's published interpretation of immutability mean that direct on-chain personal data creates a compliance trap with no clean exit. Our standard pattern is structural: personal data sits off-chain in an EU-resident PostgreSQL or equivalent (encrypted at rest with AWS KMS, GCP Cloud KMS, or Azure Key Vault, access-controlled with documented roles, retention-managed under a documented schedule), and only a salted hash, commitment, or zero-knowledge proof is written to the chain. When an Article 17 erasure request lands, the off-chain record is deleted and the on-chain hash becomes a cryptographically meaningless string, satisfying both the immutability of the ledger and the erasure obligation. This pattern has been reviewed favourably by AP-side investigators in pilot reviews we have been pulled into for Dutch clients.

Yes, when the contract value justifies the cost. Formal verification with Certora Prover or Halmos on a non-trivial DeFi or tokenisation contract typically adds three to six weeks and EUR 35,000 to EUR 90,000 to a build, plus the engineering time required to write the formal specification (which is often the slower part of the work). We recommend formal verification on every contract that custodies more than EUR 5M in assets, every contract that DNB or the AFM will review under MiCA Article 26, and every contract where an upgrade path is not available so a post-deployment bug cannot be patched without a migration. For lighter-weight builds — internal Adyen or ING tooling pilots, supplier provenance contracts with no direct financial value — we substitute Foundry fuzz testing, Echidna property-based testing, and Slither plus Mythril static analysis, which catch the most common bug classes at a fraction of the cost. The architecture decision record documents which approach we picked and why.

Our New York office covers the European morning through early afternoon on a five to six hour overlap with Amsterdam CET, which is enough for synchronous standups with Dutch product, compliance, and engineering leads at ING, ABN AMRO, Adyen, or Booking.com. Our Chandigarh hub covers the Amsterdam evening on a three and a half to five hour overlap, which handles overnight build runs, regression testing, and asynchronous Slack handoffs. We run a follow-the-sun model where the New York office takes the morning architecture and design conversations, hands clean specifications to Chandigarh at the end of the European working day, and reviews the resulting work first thing the next morning. The DNB and AFM filings happen during Dutch business hours with our engineering leads available in person at the client's Amsterdam office for the supervisory meetings.

Besu is EVM-compatible, runs Solidity smart contracts, and uses IBFT 2.0 or QBFT consensus for permissioned deployments. Fabric is non-EVM, runs chaincode in Go, Node.js, or Java, and uses a Raft-based ordering service with channel-level privacy. For an Amsterdam banking consortium where ING, ABN AMRO, Rabobank, and Adyen tier participants want the broader Solidity tooling ecosystem (Foundry, Hardhat, OpenZeppelin, Tenderly) and easier auditor recruitment from the wider EU Solidity talent pool, Besu typically wins. For a consortium with strict per-pair confidentiality requirements between competing counterparties — common in trade finance where exporters and importers in adjacent industries cannot see each other's terms — Fabric's channels remain the cleanest architecture. We write the trade-off into the architecture decision record during the four-week design phase so the steering committee can re-open the call later if the consortium membership or the regulatory frame shifts.