Smart contract development in Solidity and Rust
We write the rules in plain language first, then build them in Solidity or Rust, test them hard and prepare the code for an independent audit. The terms in the code stay readable by a person, as the Digital Code of Kazakhstan requires.
Built end to end, the code is yoursContracts we write
Built around your task, not a template.
How the work goes
From rules on paper to mainnet.
- Rules in plain words
Every rule, role and edge case is written down before code, including a dispute procedure where a person decides.
- Code and tests
Solidity or Rust, with unit, fuzz and invariant tests in Foundry or Hardhat.
- Testnet and audit
You try the contract on testnet, then an independent audit firm reviews it.
- Launch and handover
Deployed from a Safe multisig, source code verified, documentation handed to you.
Smart contracts under Kazakhstan law
The Digital Code and the Law on Digital Assets as in force on 15 November 2026.
- Terms can be written as code
All or some terms of a smart contract may be expressed as program code if the code clearly defines the parties’ rights and obligations and the terms can be reproduced in a form a person can read (Digital Code, Art. 67(2)).[1]
- A person settles disputes
A smart contract must provide a dispute procedure in which the final decision is made by a person (Art. 67(3)). We write that procedure into the spec and the admin roles.[1]
- A developer is not a provider
The law lists digital asset service providers: operators of digital financial asset platforms, trading platforms and exchange services, and licensed AIFC participants (Art. 1(5-3)). Software developers are not on the list.[2]
- Issuance and circulation are regulated
Unsecured digital assets may be issued and circulated in Kazakhstan only in the six cases of Art. 12-1(1), including a National Bank licence, the AIFC and the National Bank’s special regime. That depends on the client’s status, not on the code.[2]
Before mainnet
What we check with you before release.
- Spec agreedRules, roles and the dispute procedure approved by you before the first line of code.
- Tests passUnit, fuzz and invariant tests cover every rule.
- Keys in a multisigAdmin rights sit with a Safe multisig, not with one developer.
- Upgrade decisionA proxy leaves room for fixes, an immutable contract gives more certainty. The choice is written down.
- Audit passedThe independent auditor’s findings are fixed and the report is yours.
- Lawyer reviewedYour lawyer has confirmed whether the product needs a status under the Law on Digital Assets.
A ready-made template or your own contract
A template from the internet versus a contract built to your spec.
| A ready-made template or your own contract | Ready-made template | Your own contract |
|---|---|---|
| Rules | Whatever the template allows | Built to your spec |
| Tests | Unknown | Unit, fuzz and invariant |
| Admin keys | Often one wallet | A multisig you control |
| Audit | Not prepared for one | Code and docs for the auditor |
Around your contracts
The app, the chain and the law.
Checked on 15 November 2026
- Digital Code of the Republic of Kazakhstan No. 255-VIII of 9 January 2026
- Law of the Republic of Kazakhstan No. 193-VII of 6 February 2023 "On Digital Assets in the Republic of Kazakhstan"
This is not legal advice. Laws change: before launch, check the current version on adilet.zan.kz and talk to a lawyer or accountant.
Short and to the point.
Do you audit the contracts too?
No. Before mainnet an independent audit firm reviews the code. We prepare the tests and docs for them and fix what they find. Reviewing your own code is not an audit.
Can the contract be upgraded after launch?
We decide that with you before any code. A proxy keeps the door open for fixes, an immutable contract gives users more certainty. Either way, admin rights sit in a multisig.
Which chains do you build for?
Ethereum and compatible chains (Polygon, BNB Chain, Arbitrum, Base) in Solidity, Solana in Rust. We choose with you by users, fees and tooling.
What does a smart contract cost?
We name the price after the brief, once the rules, roles and chains are clear, and fix it in the contract. The audit firm quotes for the audit separately.
Do you need a licence to build it?
Writing the code needs none, as we read the Law on Digital Assets: a software developer is not a digital asset service provider. You may need a status if the contract issues or circulates digital assets. Your lawyer decides, and we build to their requirements.
Who owns the code?
You do: the repository, documentation and admin rights go to the client. We give a 6-month warranty on the work.
What should the contract do?
Describe the rules and we reply quickly with the scope and the next step.