We're a five-person team — a lead and four engineers — with years spent shipping Starknet infrastructure: appchain sequencers, STARK proving pipelines, TEE-based settlement systems. Not a generalist shop picking up cryptography on your project's dime.
Every engagement starts with engineers who've already shipped in this exact stack. You get production-grade code, reviewed trust assumptions, and a team that ships on the timeline a fundraising round or mainnet deadline actually demands.
See how we workWorking with a specialized team isn't about hiring extra hands — it's about removing the translation layer between what you need and what gets built.
Engineers are matched to your stack from day one — Cairo, Rust, STARK proving, TEE attestation — so the first two weeks are spent shipping, not explaining what a Merkle proof is.
Code ships with test coverage, audited-style review practices, and documentation a future auditor or new hire can actually follow.
Scale from one embedded engineer to a full team, month to month, without long-term contracts or scopes that stop making sense mid-research.
Every engagement — a proving pipeline, a TEE-based settlement system, a cross-chain verifier — follows the same four-stage process.
We map the protocol, threat model, and integration points with your team, so the architecture is validated before it's expensive to change.
We design the system — circuits, contracts, or verification flows — and validate the riskiest assumptions first with a working proof-of-concept.
Engineers build in short, reviewable cycles with your team looped in continuously — no month-long silence before a surprise delivery.
Code ships with documentation and test coverage your team can maintain independently, with optional support for audits, upgrades, or scaling.
Four domains, one engineering standard.
Appchain sequencers, settlement orchestration, and cross-chain messaging for teams running dedicated Starknet-based rollups.
STARK proving and recursive verification, plus SP1/Groth16-based proving paths, sized to real constraints around prover time and onchain verification cost.
AMD SEV-SNP attestation-based architectures for teams that need a hardware-backed trust anchor instead of a trusted operator.
Proof verification across chains and data-availability integrations for rollups that settle or publish outside their home chain.
Engineers arrive already fluent in the primitives — STARK proofs, TEE attestation, slot-ownership verification — so discussions move at the pace your team expects.
Every deliverable is written assuming it will eventually face an external audit, a research reviewer, or a skeptical technical co-founder.
The same engineers who scope the architecture ship the code and support it post-launch — context never gets lost in a handoff.
Practical experience across STARK proof generation, splitting, and onchain verification, applied to real constraints around prover time and verification cost.
Hardware-attested execution environments used as a trust anchor for off-chain computation that still needs to settle onchain.
Verifying proofs across chains and integrating data-availability layers for rollups that settle or publish beyond their home chain.
Sequencer and settlement-contract development for dedicated Starknet-based appchains, written with production operation in mind.
Working with a specialized partner still means a few things are on you to get right.
All code, circuits, and documentation produced under an engagement are owned by the client on delivery — Visoft retains no rights to project-specific work.
Fixed-scope estimates are only as accurate as the discovery phase; skipping it to save time typically costs more time later.
Confidentiality agreements are signed before any technical discovery call, since most clients work on unannounced protocols or unpublished research.
Yes. We commonly work as the technical execution arm for non-technical founders, though we recommend at least one technical stakeholder on the client side to own long-term maintenance decisions.
The client does, fully, on delivery. Visoft does not retain licensing rights, equity stakes, or reuse rights over project-specific code or circuits.
Yes — embedded engagements are designed to plug into your existing team and workflow rather than operate as a separate silo.
An NDA is signed before any technical discovery call. Research-stage clients can request that scoping discussions happen without any public-facing artifacts being created.
Flexible and fixed-scope engagements both include a defined re-scoping checkpoint, so a pivot doesn't require canceling and restarting.