RWA · VERIFIABLE DATA · WEB3 · AI
The engineering partner that builds your whole project.
Gordian Labs runs it from your idea to a system in production: architecture, code, project management, the security review that signs it off. Roughly twenty engineers behind three named seniors.
ASSET TOKENIZATIONVERIFIABLE DATASMART CONTRACTSPROTOCOL ENGINEERINGAI SYSTEMSTECHNICAL DUE DILIGENCE
GORDIAN LABS | gordianlabs.ioSCALE: 1:1 | UNIT: MM | DWG: GL-WEB-001
01 · What we do
We work where mistakes get expensive.
Everything below is work we have already done.
Asset tokenization.
Real-world asset platforms for institutions: permissioned transfer control to ERC-3643, HSM custody, KYC and the token lifecycle.³
Practice lead · Nicolae Oprisan
Smart contracts.
Secure development, pre-audit reviews, remediation, full-stack dApps.⁷
Practice leads · Dominik Muhs and Nicolae Oprisan
AI systems.
Production LLM systems, retrieval, agents with wallets, verifiable inference.⁸
Practice lead · Bastien Billey
Technical due diligence.
The question that decides the deal: does the code back what the deck says? A written answer, every risk ranked and priced. For investors and acquirers.
Practice leads · Nicolae Oprisan and Dominik Muhs
Both halves of a real-world asset.
Minting the token is the easy half. A claim about the physical world that nobody can check is a rumour in a nice wrapper, so we build the claim's proof as well as its token. We pin data to its source, along the whole path:
- The sensor, with the reading captured at source and signed there.
- A zero-knowledge proof that ties the reading to the device it came from.
- The chain, where the proof settles.
- The token an institutional investor holds.
We have built both: the tokenization platform, and the IoT data acquisition platform under it.³
02 · Leadership
Meet the leadership →
03 · How we engage
Discover. Commit. Ship.
Discover. We talk, read your documentation and ask our questions. Then you get a proposal: the architecture, an estimate in hours, the price capped at that estimate, and the risks we see. We go back and forth until it is right.
Commit. We commit to one approach, scoped and capped. Nobody pays us to hedge across three.
Ship. You see working software every week, and that is the status report.
Capped, then billed by milestone.
We estimate the maximum hours a build takes. That estimate is the ceiling on what you pay.
- The cap holds. Anything past it is ours to absorb.
- Milestones invoice the hours actually spent, so a build that lands early costs less.
- Due diligence runs the same three steps, and what ships is the report. Discover sets the scope, your focus points and a fixed price. The report says whether this team can ship what it promised, and what it costs to get from the code as it stands to what you were expecting.
- Pre-audit reviews carry one fixed price. You own the code and want to know whether it will pass an audit. We read it the way an auditor will and tell you what to fix first.
What can change a price after Commit: the playbook →
04 · Sign-off
Named seniors on every engagement, an engineering team behind them.
Roughly twenty engineers, in-house and through a delivery partner, with web3 and AI production experience, and a project manager assigned to the engagement who owns the schedule and runs the weekly demo. Nothing ships without the same sign-off, regardless of who types:
- Architecture set by the practice lead who owns the engagement.
Every pull request ranked for security impact, and reviewed by the practice lead whose domain it touches.
- The rank decides the reviewer. A deadline does not change the rank.
- Weekly demos, working software, honest attribution in every report.
Ranked by blast radius.
Not every change carries the same risk, so not every change gets the same reviewer. The rank is set when the request is opened rather than argued about at merge time. The Named senior is assigned per project and named in the proposal, so you know before the work starts whose signature you are getting.
| Rank | What it covers | Reviewed by |
|---|---|---|
| 1 | Smart contracts, and anything else that can move value | Nick and Dominik, both, before merge |
| 2 | Infrastructure configuration: networking, identity, secrets, deployment | Nick, or the Named senior on the project |
| 3 | Databases: schema, migrations, access paths | Named senior, or Nick where the data is personal or financial |
| 4 | Backend services | Named senior |
| 5 | Front-end services | Named senior |
What each rank has to satisfy before it merges: the playbook →
05 · Case studies
Project Genesis 2.0
One of two BIS prototypes: the data side, from metered device to digital green bond.
Genesis 2.0 was a green bond with smart-contract carbon instruments attached. Two consortia built two prototypes, and Allinfra built the data side of one of them.
| Field | Detail |
|---|---|
| Year | 2022 |
| Run by | The BIS Innovation Hub Hong Kong Centre, the HKMA and the UN Climate Change Global Innovation Hub |
| Consortium | Goldman Sachs, Digital Asset and Allinfra |
| Data side | Registered devices through to a verification API, built by Allinfra. Nick led Allinfra's engineering. |
| Tokenization | Goldman Sachs' platform, built on Digital Asset's Daml and Canton |
| Published | The BIS report, 24 October 2022. Nick is in it by name.¹¹¹ |
Read the case study →
06 · What we can show a procurement team
Gordian Labs S.R.L., registered in Romania (CUI 54942279, LEI 8945002A2C0FACER9472), an EU company contracting under Romanian and European Union law.
- Inside the EU: A Romanian company, so an EU company. The GDPR applies to us directly rather than by undertaking, and a client inside the Union has no international transfer to arrange and no adequacy decision to rely on. Where DORA or NIS2 reaches your side of the contract, we answer to the same body of law you do.
- Secure development: A documented secure development process, held to the CSSLP certification (isc2.org/certifications/csslp), covering local machine and credential management, development environments, and pre-audit review of application services. Our leadership has operated it on production systems.
- Review and sign-off: Every pull request is ranked for security impact and routed to the practice lead who owns that domain, on the five-rank scale published in the playbook. Rank 1, anything that can move value, requires two named reviewers before merge.
- Service classification: Due diligence, pre-audit reviews and builds conclude at handover. Only a retainer or a hosted component constitutes an ongoing service, and each proposal states which applies, since that classification determines the entry in your register of information.
- Available on request: A completed security questionnaire, and an architecture walkthrough conducted by the engineers who wrote the code.
- Independent inspection: Our public repositories are on GitHub, so engineering standards can be assessed from source before an NDA or an introductory call. Access to smart contract repositories we have authored is available on request.
- Key custody: We hold no client key material at any point. Custody is HSM, MPC or client-held, agreed per engagement and recorded in the proposal.
07 · First call
Start with a call.
On the call we work out the scope together, sign an NDA if you need one, and go through the risks we see. Then we start on the architecture and the budget.