Blockchain & Web3 Development Company in Copenhagen

MiCA is the boundary a Copenhagen blockchain budget either stays inside or crosses: a scoped consortium proof-of-concept on Hyperledger Fabric or Besu 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 Finanstilsynet classification work, integrated custody with a licensed counterparty, and the AML transaction-monitoring overlay. Copenhagen rates sit close to Stockholm and Oslo on the same scope, slightly above Berlin and Madrid because of the Maersk and Novo Nordisk engineering bar, and below London or Zurich. 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 require authorisation from the relevant national competent authority before offering custody, exchange, trading platform operation, portfolio management, advice, or transfer services. In Denmark, Finanstilsynet (the Danish Financial Supervisory Authority) is the competent authority and handles authorisation under the Danish Financial Business Act (lov om finansiel virksomhed) as amended to integrate MiCA. The existing Danish virtual-asset-service-provider registration regime has been transitioning into the MiCA CASP licence through 2025 and 2026. We start every Copenhagen tokenisation or CASP engagement with a written regulatory classification memo that maps your intended activity to the relevant MiCA Title and the Danish Financial Business Act category, and we engineer the platform against the technical and organisational requirements Finanstilsynet publishes. 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. The EU Falsified Medicines Directive (FMD) requires serialised packaging with a unique identifier (product code, serial number, batch number, expiry date) and a tamper-evident anti-counterfeiting device on every prescription medicine pack in the EU, with verification through the European Medicines Verification Organisation (EMVO) hub and the national medicines verification systems. Our pharma DLT work plugs into the GS1 EPCIS event data model (commissioning, packing, shipping, dispensing events) and writes provenance hashes to the chain while keeping the actual serial-number data inside the FMD-compliant national verification system. This pattern survives the Danish Medicines Agency and the European Medicines Agency review, satisfies the FMD on first principles, and gives Novo Nordisk, Lundbeck, or Genmab procurement the audit evidence pack they need. The EU Digital Product Passport coming through the Ecodesign for Sustainable Products Regulation (ESPR) is the next adjacent regulatory frame, and our architecture is designed to absorb it without a rewrite.

TradeLens — the Maersk and IBM joint venture on Hyperledger Fabric for shipping provenance — wound down in 2022 because the consortium economics did not justify the DLT premium over a centralised platform with cryptographic audit, not because the technology failed. The lesson Copenhagen procurement teams took from that experience is that DLT must solve a coordination problem across organisations that genuinely do not trust each other, and the consortium governance has to give every participant a credible exit and a credible reason to stay. We open every Copenhagen shipping or supply-chain consortium engagement with that conversation explicitly. When the answer is that a centralised platform with signed audit logs would meet the actual business requirement at a fraction of the cost, we say so and we ship that instead. When DLT is genuinely the right answer (multi-port, multi-customs-authority, multi-OEM workflows with no neutral coordinator), we build it with the membership and exit terms that the TradeLens post-mortem made plain are essential.

Datatilsynet (the Danish Data Protection Authority) enforces the GDPR in Denmark and has been actively pursuing compliance gaps in the financial services and tech sectors. Article 17 of the GDPR (right to erasure) and Datatilsynet'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 Datatilsynet investigators in pilot reviews we have been pulled into for Danish clients.

Yes. The EU Renewable Energy Directive III (REDIII) and the Association of Issuing Bodies (AIB) European Energy Certificate System (EECS) framework underpin the existing Guarantees of Origin scheme for renewable electricity. Several pilots across the EEA, including ones adjacent to Orsted's offshore wind portfolio, have explored DLT-based tokenisation of GO certificates to enable hourly granularity, cross-border transfer with cryptographic audit, and 24/7 renewable matching for corporate buyers. Our work in this space designs the on-chain GO representation as a salted hash of the AIB-issued certificate identifier rather than putting the certificate metadata on-chain, integrates with the national issuing body (Energinet for Denmark) for the off-chain authoritative record, and writes the transfer events to the chain for the cryptographic audit log. The result is a system that the Danish Energy Agency and the buyer's external auditor both accept, with no exposure to MiCA classification because the GO certificate is a regulatory instrument rather than a financial instrument under MiFID II.

Our New York office covers the European morning through early afternoon on a six hour overlap with Copenhagen CET, which is enough for synchronous standups with Danish product, compliance, and engineering leads at Maersk, Novo Nordisk, Orsted, Lundbeck, or DSV. Our Chandigarh hub covers the Copenhagen evening on a three and a half to four and a half 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. Finanstilsynet filings and Datatilsynet correspondence happen during Danish business hours with our engineering leads available in person at the client's Copenhagen 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 a Copenhagen shipping or pharma consortium where Maersk, MSC, CMA CGM, port-authority, or pharma-distributor peers want strict per-pair confidentiality between competing counterparties — common where exporter and importer terms cannot leak — Fabric's channels remain the cleanest architecture, and the local TradeLens-era familiarity reduces the steering-committee friction. For a consortium where the 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. We write the trade-off into the architecture decision record during the four-week design phase.