Skip to content

Founder & engineering leadership

Dmytro Nasyrov

Founder and CTO Pharos Production

Founder of Pharos Production, PhD in Artificial Intelligence and lecturer at Igor Sikorsky Kyiv Polytechnic Institute.

  • Artificial intelligence
  • Software architecture
  • Engineering leadership
Dmytro Nasyrov
Dmytro NasyrovEngineering

About

Dmytro Nasyrov is the founder and CTO of Pharos Production, a software development and AI engineering company since 2013. With 23 years of engineering experience and a PhD in Artificial Intelligence, he leads engineering culture at Pharos and lectures at Igor Sikorsky Kyiv Polytechnic Institute.

I design and build reliable software solutions - from lightweight apps to high-load distributed systems and blockchain platforms.

PhD in Artificial Intelligence, MSc in Computer Science (with honors), MSc in Electronics & Precision Mechanics.

Education and credentials

Career timeline

  1. Founder and CTO, Pharos Production

    Software development and AI engineering. 90+ engineers, 110+ apps for 200+ clients across 28 industries. Aligned with ISO 27001, SOC 2, HIPAA, PCI DSS and GDPR frameworks.

  2. Lecturer, Igor Sikorsky Kyiv Polytechnic Institute

    Teaching engineering at Ukraine's leading technical university.

Ideas from practice

Articles by Dmytro Nasyrov

235 articles
  • A completed national registration application form and a paperclipped attribute checklist lying on a desk beside a brass embossing seal, the registration filing a business completes with a national authority before it may request any attribute from an EUDI Wallet
    14 min read

    EUDI Wallet Relying Party

    Before a single attribute can be requested from an EUDI Wallet, the business behind the integration has to be a registered relying party in the Member State where it is established. This is what that registration involves, what it permanently constrains and what happens when it is refused or withdrawn.

  • Two lawyers in a law library comparing an open regulation volume against a printed question and answer page.
    20 min read

    ESMA Q&A 2552: Crypto-Assets Without an Identifiable Issuer

    On 18 February 2026, nearly nine months after the question was submitted, the European Commission answered ESMA Q&A 2552: crypto-assets without an identifiable issuer sit outside MiCA Title II, so no white paper is required and Article 5(2) does not bind the platforms that list them. The answer that underpins Bitcoin and Ether listings across the EU is an administrative Q&A interpreting a recital, and neither is binding law. We trace what the Q&A actually says, what it leaves standing and what an engineering team builds around a determination that can be challenged years later.

  • Two printed specification documents compared on a desk, one open and pencil-annotated and one closed and bound shut, a smartphone showing a blurred credential card screen resting between them, the format decision that keeps a EUDI Wallet verifier build inside freely licensed specifications instead of the ISO mdoc route
    11 min read

    EUDI Wallet Integration

    The first decision in an EUDI Wallet integration is not which vendor to buy. It is which credential format you accept, because one route keeps the whole build inside specifications the framework itself sets requirements out from and the other puts an ISO standard your team has to obtain separately on the critical path.

  • A rack hardware security module with a tamper seal, three numbered tamper evident pouches holding signing devices and three separate closed laptops on a key ceremony table, crypto custody key management compared.
    14 min read

    MPC vs Multisig vs HSM

    The engineering decision underneath MiCA custody: MPC threshold signatures, HSM tamper-response hardware and on-chain multi-sig compared on single-point-of-failure resistance, auditability, recovery, cost and chain-agnosticism, with a cold/warm/hot tiering pattern and key ceremony, rotation and disaster-recovery design notes.

Last updated:

Work with Dmytro and the Pharos team

Describe your project and we will get back within one business day.

Your contact details
Please enter your name
Please enter a valid email address
Please enter your message

We use your details only to reply to your request. Data Privacy and Legal Notice

We typically reply within 24 hours