Development
Crypto development
Smart contracts, tokens and wallet connection in the interface. Tests for foreign calls and gas, a testnet release first, history in an ordinary database.
- Reply to your brief
- within 24 hours
- First call
- 30 minutes, no commitment
- First working version
- in 4–5 weeks
Process
What happens, and when
The work is split into stages, and each one has a named result. You see it yourself rather than reading about it in a report.
Days 1–5
The on-chain boundary
The first decision is the boundary: what genuinely has to live on-chain, and what is cheaper and safer on an ordinary server. Every on-chain action costs a fee and stays there for good, so the contract gets only what it exists for — ownership, the rules of settlement, proof. The network is chosen here as well, along with who pays the fees: the user or the product.
You get — The chosen network and what lives on-chain
Weeks 2–3
The contract described
We describe the contract’s state and its functions before the first line of code: who is allowed to call what, and what happens to money on every call. The decision that matters most is upgradeable or not. An immutable contract is more honest and easier to verify; an upgradeable one forgives a mistake, but it hands the owner a power the user deserves to know about in advance.
You get — Functions, call rights and the upgrade decision
From week 3
Tests and the testnet
The contract is written together with its tests, and that is not hygiene: once it is deployed there is nothing left to patch, so tests are the only way to learn the behaviour while it can still change. It goes onto a test network with a wallet and the interface attached, and we count the fee for every action — that fee is part of the product’s price, not a technical detail.
You get — The contract on a testnet with fees counted
Before mainnet
Mainnet rehearsal
We run the scenarios against a fork of the live network: an empty balance, a rejected signature, gas above the estimate, a call from the wrong address. On audits, plainly: an external audit is not part of this work and costs separately. If the contract will hold other people’s money, plan it early and leave time for the changes it asks for.
You get — Failure scenarios checked against a network fork
After deployment
Work around the contract
A published contract is not edited: any change means a new address and moving across everyone already using it. So the work afterwards happens around the contract — the interface, watching its events, answering what the chain shows. The source is verified on the explorer, so the code can be checked against the address without taking our word for it.
You get — Verified source and event monitoring
What the work covers
The smart contract
the state it keeps and the functions over it, who is allowed to call each one, money in and money out, events that make every action visible
Token and issuance
a coin or NFT contract to the network’s standard, the rules for minting and burning, metadata, distribution to a list of addresses
Wallet in the interface
connecting a wallet, signing and sending a transaction, switching networks, waiting for confirmation and handling a rejection
Contract tests
a call from someone else’s address, a repeated send, insufficient funds, a rollback on failure, gas spent per function
Deploying to the network
a deploy script, the test network first and the live one after, the code prepared for an external audit and the changes it asks for, addresses wired into the app
Operation history
reading the contract’s events, the history kept in an ordinary database, the status shown in the interface without a call to the chain
What we need from you
- The rules of settlement written out in words — who gets what, and on what condition
- The network, if it is already chosen, and the decision on who pays the fees — the product or the user
- An answer on whose money ends up in the contract and how much — it sets how far the checks go and whether an external audit comes before deployment
What people usually ask
Contact
Send a description of the task
A reply with the scope, the timeline and a budget estimate comes within 24 hours.
The first call is 30 minutes, with no commitment on your side.
01
You describe the task
Five questions in the form, or a plain email — whichever suits you.
02
We answer within a day
With the scope, the timeline and a budget estimate, based on what you told us.
03
We talk for 30 minutes
To clear up whatever is unclear. It commits you to nothing.