These usually show up when a Web3 idea moves from prototype to something that will hold customer funds.
You need a fungible token, NFTs or a multi-token contract with clear rules for minting, supply and transfers.
A hackathon or testnet contract is about to hold real money, and it was never built for that.
Auditors are scheduled, and the code, docs and tests are not ready for them yet.
You have a report with issues to resolve and need engineers who can fix them without creating new ones.
Payments, escrow, rewards or ownership records need to run on a blockchain alongside your app.
Contracts are live, nobody fully understands them, and you need someone to take over safely.
Roles, states, limits and failure cases written down before code, so tests and auditors have a spec to check.
Contracts for Ethereum and other EVM-compatible chains, built on well-reviewed open-source libraries where possible.
ERC-20 tokens, ERC-721 NFTs and ERC-1155 multi-token contracts with clear minting, supply and access rules.
Proxy-based upgrades where they make sense, immutable contracts where they don't, and a documented upgrade process.
Tests that check every rule, feed random inputs and call sequences, and confirm key properties always hold.
Storage layout, loops and calls reviewed to cut fees on the actions your users perform most.
Internal review, static analysis and docs prepared so independent auditors spend their time on real risks.
Scripted deployments, verified source code, multisig admin roles, on-chain alerts and an incident playbook.
Whatever the contract does, the same basics decide whether it can safely hold value for years.
Roles and permissions listed for every function
Invariants: what must always be true
Known risks and trust assumptions stated
Upgrade and pause rules decided up front
Unit tests for every rule and revert
Fuzz tests with random inputs
Invariant tests over random call sequences
Tests on a fork of the target network
Admin roles held by a multisig, not one key
Time delays on sensitive changes where it fits
Least privilege for every role
Key holders and recovery steps documented
Source code verified on the block explorer
Alerts on unusual transactions and balances
Pause or limit switches where the design allows
An incident playbook your team has rehearsed
You need contracts, an app and a back end built together, with the contracts ready for an independent audit.
You're adding stablecoin payments, tokenized assets or on-chain settlement next to an existing product.
A testnet contract or hackathon build works, and now it needs to be rebuilt for mainnet and real users.
You own the front end or the brand and need engineers for the contract layer behind it.
Fungible, NFT or multi-token contract.
Payments, escrow, rewards or vaults.
Review, tests and docs before auditors start.
Resolve issues and re-test.
Review, document and monitor.
Multisig roles and an incident plan.
We agree on what the contract does, who can do what, which chain it runs on and what must never happen, in writing.
Contract structure, upgrade approach, admin roles and integrations with your app and back end, reviewed with you before coding.
Small, readable contracts with unit, fuzz and invariant tests, run on testnets and on forks of the target network.
Internal review and static analysis, then an independent audit firm of your choice. We fix findings and support the re-check.
Scripted deployment, verified source, admin rights moved to a multisig, alerts and an incident playbook handed to your team.
A defined set of contracts, ready for audit
Fixed price after scoping.
For a clear piece of work: a token, a payment or escrow contract, or the on-chain part of a new product.
Specification agreed up front
Contracts with unit, fuzz and invariant tests
Pre-audit review and documentation
Audit findings fixed and re-tested
Deployment, monitoring and hand-over
Contract, back-end and app engineers
Monthly, per engineer or team.
For products where contracts, the app and the back end keep changing together after launch.
Engineers matched to your stack
Ownership of contracts and integrations
Upgrades planned, tested and reviewed
On-chain monitoring and incident support
Scale up for new features or chains
Smart contracts rarely work alone. They need an app, a back end, wallets and monitoring around them, and we build those parts too. On the KickEX mobile crypto exchange, we worked on the multi-currency wallet, trading and withdrawals.
We worked on KickEX, a mobile crypto exchange app with a multi-currency wallet, trading and withdrawals.
Contracts, back end, web and mobile apps from one team.
Code is reviewed for how it could be attacked, not only for whether it works.
Work can start in about two weeks.
85% of our customers come back with new work.
You review what the contract must do before it's written.
We prepare code for auditors; we don't audit our own work.
We tell you which risks remain and who holds which keys.
Repositories, deployer accounts and admin keys stay with you.
Our engineers in Poland and Cyprus overlap with part of the US working day.
No sales pitch
Tell us what your contracts need to do
Describe your product, the chain you have in mind and where you are today. We'll suggest an approach and come back with a rough estimate.
By subscribing you agree to receive emails from Gilzor. You can unsubscribe at any time. Privacy Policy.
