Custom smart contract development in Corsica
Smart contract development means turning rules agreed between several parties into a program that runs by itself on a blockchain. We are a development studio based in Bastia. We design readable, documented contracts, test them and then deploy them, after first checking with you that a blockchain really is the right tool for your project.
What is a smart contract?
A smart contract is a program stored on a blockchain. It applies rules set in advance automatically, along the lines of 'if this condition is met, that action happens'. Once deployed, its code can be read by anyone. Nobody can change it in secret, not even its author.
Most business smart contracts are written in Solidity. The language is designed for the EVM, the Ethereum Virtual Machine, in other words the execution engine shared by Ethereum and plenty of compatible networks, which leaves you a lot of freedom over which network to use.
The word 'contract' can mislead. A smart contract is not a contract in the legal sense, it mechanically applies technical rules. The agreement between the parties still has to be set down in writing.
When does a smart contract make sense?
A smart contract adds something when several of these conditions are met. Otherwise, a conventional application will be simpler, and cheaper.
- 01
Several parties, no trusted intermediary
Partners need to share rules and information without any one of them controlling the system alone.
- 02
Stable, precise rules
The conditions can be written down clearly in advance. They do not change every month.
- 03
A need for public verification
Customers, partners or authorities must be able to check for themselves what was recorded, and on what date.
- 04
A record that has to last
The proof must stay available for a long time, without depending on the company that created it.
Smart contract examples by sector
- 01
Farming and food supply chains
Recording each stage of a batch, from harvest through to packaging. Only authorised participants have write access.
- 02
Training and qualifications
Issuing attestations that can be verified, with the option of revoking one issued in error.
- 03
Local authorities
Publishing the digital fingerprint of official documents to prove their date and integrity.
- 04
Logistics and partnerships
Confirming steps shared between several companies, a delivery or a receipt for instance, with a common history.
- 05
Startups
Building the blockchain layer of a digital product, integrated with a web or mobile app.
Working with a blockchain developer, step by step
We work from Haute-Corse with clients on the island and elsewhere. You deal with the same person from the first conversation to launch.
- 01
Understand
Together we describe the participants and the rules. The edge cases too, and what should happen when something goes wrong. Then we write a plain-English specification.
- 02
Design
Choice of network, of what goes on-chain, of the admin roles. And one decision to take early. Should the contract be upgradeable, or not?
- 03
Build and test
Writing the code in Solidity, with automated tests that cover normal use as well as errors, not forgetting attempts at misuse.
- 04
Validate
Deployment to a test network, where nothing has real value, so you can try the whole flow. After that, a code audit.
- 05
Deploy
Smart contract deployment to the main network and publication of the verified source code. We hand over access along with the documentation.
Deliverables and support after deployment
- 01
Source code
Commented, version-controlled, delivered with its automated tests. It belongs to you.
- 02
Documentation
The contract rules in plain English, its architecture and its roles. Plus how to carry out admin operations.
- 03
Deployment scripts
To repeat the deployment exactly, on a test network or on another compatible network.
- 04
Integration
The contract is connected to your website or app. Your users never have to handle a technical tool.
- 05
Ongoing support
Once it is live, we can monitor the contract's activity and help with admin operations. Future changes are prepared with you.
What to check before deploying a smart contract
- 01
Immutability
A deployed contract cannot be patched like a website. Whether to build in an upgrade mechanism is a design decision, with its own benefits and risks.
- 02
Admin keys
Private keys are the secret codes that authorise sensitive operations. They have to be kept with the greatest care, ideally by you and under the control of several people.
- 03
Network fees
Every operation on a public blockchain has a cost, and it varies. Optimised code and a sound architecture bring it down.
- 04
Dependencies
Libraries, oracles (services that bring outside data onto the blockchain), other contracts being called. Each one is a weak point to assess.
- 05
Legal framework
If the project involves tokens, it may fall under the EU's MiCA regulation. Legal advice is then essential before you start.
What determines the cost of smart contract development
Every project receives a clear quote after an initial conversation. The budget depends mainly on these points.
- 01
Complexity of the rules
How many cases to cover, how many roles, how many interactions between contracts.
- 02
Choice of network
Public or private. The testing and optimisation requirements are not the same.
- 03
Upgradeability
An upgradeable contract needs extra architecture and extra testing.
- 04
Integration
User interface, connection to your software, admin tools.
- 05
Depth of audit
An internal review or an in-depth audit, depending on what is at stake.
Technologies and methods
- Solidity
- EVM
- Automated testing
- Test networks
- Source code verification
- TypeScript
Frequently asked questions
Which blockchain should we choose?
It depends on who needs to read and write the data, on the volume of operations, on how long the proof must last. We compare the public and private options with you. Then we recommend the simplest one that meets the need.
Can a smart contract be changed after deployment?
The deployed code, no. You can, however, build in an upgrade mechanism from the design stage, or deploy a new version and move usage over to it. Each option affects trust and security, and we explain how before you decide.
Who holds the contract's keys?
You do. We help you set up safe storage for the admin keys, for example with approval by several people, and we document the procedures.
How much does it cost to use a smart contract day to day?
On a public network, every operation incurs fees that vary. They depend on the network and on how complex the operation is, but also on how busy things are at the time. We estimate them during design, and we optimise the code to keep them down.
Should a contract you have built be audited?
For a high-stakes contract, yes, it is a good idea. We always test and review our own code, but an extra pair of outside eyes remains good practice, and we are happy to make that work easy.