Skip to content Skip to footer

Dmitry Meshkov: Calling for Verifiable Research in DeCC

Dmitry Meshkov, Founder and CEO of Quex, is an active member of the Decentralised Confidential Computing ecosystem. Speaking from the perspective of a deep technologist, he values practical progress over posturing. And when it comes to research in Web3, Meshkov doesn’t mince words.

“You don’t care who’s posted the research, you care if the tech works and is verified. That’s what matters,” he says.

His comments follow the release of Messari’s first DeCC report and in advance of a followup. While the inaugural report laid some groundwork, Meshkov, like others, believes it needs more depth and analysis.

“The first report was helpful in mapping the landscape,” he notes. “However, for real progress, we need research that dives into which technologies are best suited for specific applications, not just what they are, but when and why they should be used.”

At Quex, Meshkov is focused on building secure, verifiable compute infrastructure. That means technical rigour comes first. In his view, independent research only becomes valuable when it is specific, detailed, and actionable.

“Having someone like Messari independently verify claims around TEE implementations or security postures adds a layer of trust you can’t get from marketing materials alone,” he says. “Otherwise, it’s just noise.”

Trust, as it turns out, is central to Meshkov’s philosophy. He sees verified research not just as validation but as a foundation for collaboration. At Quex, that collaboration already exists. The team has partnered with Secret Network to jointly test their TEE applications, ensuring interoperability and security aren’t just assumptions but documented outcomes.

“It doesn’t matter where the company is based, or who’s shouting the loudest. If your proof is verifiable and your infrastructure is secure, then you’re worth listening to.”

For future Messari reports, Meshkov would like to see comparative analysis of different compute architectures across use cases, the standardisation of reporting frameworks, and even joint testbeds for DCC members.

He’s also direct about what’s missing.

“We need research that shows not just who is in the ecosystem, but how they are using technology responsibly and how they are not. Highlight those who claim to use secure environments but don’t implement verification. That matters.”

If Messari does convene a DeCC working group, Meshkov believes it should focus on actionable outcomes: standardising verification methods, building shared security frameworks, and issuing reference architectures that go beyond white papers.

In an industry often crowded with hype and vague claims, Meshkov’s ask is simple: show your work. And let the facts speak louder than the logos.