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.
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
- PhD in Artificial Intelligence
- Lecturer, Igor Sikorsky Kyiv Polytechnic Institute
- Alumnus, Igor Sikorsky Kyiv Polytechnic Institute
Areas of expertise
- Artificial Intelligence - LLM integration, RAG, agents, ML platforms
- Blockchain protocols - DeFi, NFT, smart contracts, dApps
- FinTech platforms - payments, compliance, RegTech
- Custom software development - web, mobile, enterprise
- DevOps and cloud architecture
- Engineering leadership - strategy, technical due diligence
Career timeline
-
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.
-
Lecturer, Igor Sikorsky Kyiv Polytechnic Institute
Teaching engineering at Ukraine's leading technical university.
Ideas from practice
Articles by Dmytro Nasyrov
MCP Server Development
A spec-current guide to MCP server development after the 2026-07-28 revision, covering the stateless protocol change, the modern-vs-legacy split, server primitives, transports, authorization and the named security failure modes, plus what a server actually costs to build and maintain.
MiCA Review 2026: What MiCA v2 May Change
The European Commission's MiCA review consultation, launched 20 May 2026 under Articles 140 and 142, with responses due 30 September 2026. What the questionnaire actually asks across stablecoins, CASP prudential and reporting rules, DeFi, staking, lending and perpetual futures, what it stays silent on and what each area would change in the systems we build.
AI Act Technical Documentation
Annex IV of the EU AI Act translated point by point into engineering deliverables, plus the logging and retention duties in Article 12, Article 19 and Article 26 and the unconfirmed SME simplified-documentation route.
Crypto AML Rule Tuning
Crypto AML rule tuning covering the ATL/BTL threshold-testing lifecycle, a hedged sub-1 percent SAR-conversion retirement signal, the back-test gate before a threshold ships and what MiCA vs the incoming AMLR actually require of CASP transaction monitoring.
CASP Wind Down Plan
A CASP wind down plan is required by MiCA Article 74 and defined by almost nothing else in the act: no paragraph numbering, no recital, no technical standard, no filing duty and no deadline. What MiCA does supply is two conflicting destinations for client assets, a transfer to a successor provider under Article 64(8) and a return to the client under Article 75(6), and it never says which one runs. This article walks the wind-down in execution order, from the duties that have to be standing before any exit decision through trigger, freeze, client instruction, execution, sub-custody unwind and register closeout, and it is honest about the three different timing formulas MiCA writes for cessation, none of which is a number.
Crypto Transaction Monitoring: Integration Architecture Guide
Crypto transaction monitoring for EU CASPs covering KYT versus KYC, webhook and polling integration patterns, reorg-safe verdict caching, whale-wallet pagination limits, account abstraction edge cases and the EU regulatory requirements that make it mandatory.
Last updated: