RedDuck Logo

Cases

BlogMemoContact Us

TEAM_

Who actually does the work: the engineering split by function and by stack, and how a team is put together for a protocol
Get a Free Consultation

By function

Smart contract
Frontend
Backend
QA
DevOps
Design

Teams are scoped per protocol rather than assigned from a bench, so the mix above is the pool, not a fixed project shape.

By stack

10EVM / Solidity
10Solana / Rust
5Zero-Knowledge
15TypeScript

These counts overlap — engineers here work across more than one stack, so the figures are not additive.

How a team comes together

01

Analysis before staffing

We challenge the assumptions first and say so if the product should not be built. Only then does the shape of the team follow from the protocol.

02

Owners, not seat-fillers

Engineers own architecture end to end rather than working a ticket queue, so the same people who design the system are the ones who ship it.

03

Security in the loop from day one

Threat modelling starts at design; invariant and fuzz testing run alongside development rather than after it.

04

Handover, then warranty

Mainnet release comes with full authority handover, followed by 20 to 100 business days of free fixes scaled to project size.

Who to talk to

Scoping starts with a conversation about whether the thing should be built at all. Mark Virchenko takes those calls directly.

Mark Virchenko

Mark VirchenkoChief Executive OfficerLinkedIn

_FREQUENTLY ASKED QUESTIONS

Pixel-art question mark cube
smart contract, frontend, backend, qa, devops, design — all in-house, no subcontracting of core protocol work. Team size is scoped per project rather than quoted as a headcount.
Yes — 10 engineers work in Rust on Solana, alongside 10 on EVM and Solidity. Engineers here work across more than one stack, so those counts overlap rather than add up.
EVM chains and Solana carry most of the work, with 5 engineers on zero-knowledge systems. If a protocol needs something outside that, we say so at the analysis stage rather than after signing.
A team scoped to the protocol, not assigned from a bench. The engineers who design the architecture are the ones who ship it, and they stay through audit preparation and handover.
Remote, mostly across Europe, so the working day overlaps the European one in full and the US morning. The company is registered in Kyiv, Ukraine and Larnaca, Cyprus, but nobody is asked to work from either address.
Only Mark Virchenko, Chief Executive Officer. The rest of the team is described in aggregate — headcount by function and by stack — rather than as a gallery.