TriaChain Solutions / Rust and Go

Rust and Go, for the parts that cannot be wrong.

The team's experience includes core protocol work on Polkadot at Parity Technologies and the Forest Filecoin node at ChainSafe. That background brings a healthy paranoia about state, concurrency and money to systems where mistakes get expensive.

// what we take on

Four kinds of systems work

[01] backends

Backends that hold state

Balances, settlement, reconciliation, ledgers. Systems where a rounding error becomes a legal problem and where the audit trail matters as much as the feature.

[02] protocol

Protocol and node engineering

Chains, clients, consensus-level code and peer-to-peer networking. The deep end, backed by hands-on work on production protocols.

[03] performance

Services that got too slow or too expensive

A hot path rewritten in Rust or Go, a service that stops falling over at peak, or a cloud bill that drops because the same work now fits on a fraction of the machines.

[04] team

Rust and Go alongside your team

You may not need a separate project. We can review pull requests, pair with your developers and take responsibility for a service alongside them.

// how it works here

Four things worth knowing

  • Rust where it earns its keep. Rust is worth it when correctness and performance both matter. When they do not, Go ships sooner and reads better to whoever maintains it next. We tell you which one your problem is.
  • Smart contracts go to outside auditors. If we write a contract that will hold real money, it goes to a specialist audit firm before it does. Anyone who tells you their own code needs no third-party audit is selling you confidence.
  • Concurrency is the job, not the surprise. Most of the bugs that cost real money live in the space between two things happening at once. That is the part of this work we enjoy, which is an odd thing to admit in public.
  • The infrastructure is yours. Repositories, nodes, cloud accounts and keys in your name. We hold nothing you would have to ask us for later.
// questions

What clients ask first

Can you work as part of our team?

Yes. Bring us in for a project, or have us review pull requests, pair with your developers and own a service. Same people either way.

Rust or Go for our project?

Go for most backends: faster to write, easier to hand over. Rust when you need control over memory and timing, when the same work has to fit on fewer machines, or when correctness has legal consequences.

Do you work on blockchain protocols?

Yes, at the level of chains, nodes and clients rather than only the application layer. Substrate, Polkadot and Filecoin from the inside, EVM chains from the backend and integration side.

Do you write smart contracts?

Yes, and we will tell you when a contract is the wrong tool for what you described. Whatever we write goes to an outside audit firm before it holds real money.

Can you rewrite an existing service in Rust or Go?

Often, and often we will advise against rewriting all of it. The usual answer is to move the two or three hot paths and leave the rest alone.

What size of team can you field?

Three of us, plus engineers we have worked with for years when a project genuinely needs more. If it needs more than that, we will say so rather than stretch.

// contact

Tell us about the system

Write in plain words: what it has to do, what it is doing wrong today, and what the failure costs you. One of the three of us answers, usually the same day.

info@triachain.com