RX 1420.405 MHz · --:--:--FR / EN
CH.03 · 93.3 MHz

Custom smart contract development in Corsica

Smart contract development means turning rules agreed between several parties into a program that runs automatically on a blockchain. As a development studio based in Bastia, we design, test and deploy readable, documented contracts, after first checking with you that a blockchain really is the right tool for your project.

01 — WHAT IT IS

What is a smart contract?

A smart contract is a program stored on a blockchain that automatically applies rules set in advance: if a given condition is met, a given action takes place. Once deployed, its code can be read by anyone and nobody can change it in secret, not even its author.

Most business smart contracts are written in Solidity, a language designed for the EVM, the Ethereum Virtual Machine: the execution engine shared by Ethereum and many compatible networks. This leaves you plenty of freedom over which network to use.

The word contract can be misleading: a smart contract is not a contract in the legal sense. It mechanically applies technical rules; the agreement between the parties still needs to be set down in writing.

02 — WHEN YOU NEED IT

When does a smart contract make sense?

A smart contract adds value 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 and 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 when.

  • 04

    A record that has to last

    The proof must remain available for a long time, independently of the company that created it.

03 — USE CASES

Smart contract examples by sector

  • 01

    Farming and food supply chains

    Recording each stage of a batch, from harvest to packaging, with write access reserved for authorised participants.

  • 02

    Training and certification

    Issuing verifiable certificates, 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, such as a delivery or receipt, with a common history.

  • 05

    Startups

    Building the blockchain layer of a digital product, integrated with a web or mobile app.

04 — HOW IT WORKS

Working with a blockchain developer: the project stages

We work from Haute-Corse with clients in Corsica and beyond, with a single point of contact from the first conversation to launch.

  • 01

    Understand

    Together we describe the participants, the rules, the edge cases and what should happen if something goes wrong, then write a plain-English specification.

  • 02

    Design

    Choice of network, of what goes on-chain, of the admin roles and of whether the contract should be upgradeable.

  • 03

    Build and test

    Writing the code in Solidity, with automated tests covering normal use, errors and attempts at misuse.

  • 04

    Validate

    Deployment to a test network, where nothing has real value, so you can try the whole flow, followed by a code audit.

  • 05

    Deploy

    Smart contract deployment to the main network, publication of the verified source code, and handover of access and documentation.

05 — DELIVERABLES

Deliverables and support after deployment

  • 01

    Source code

    Commented, version-controlled and delivered with its automated tests. It belongs to you.

  • 02

    Documentation

    The contract rules in plain English, its architecture, its roles and how to carry out admin operations.

  • 03

    Deployment scripts

    To reproduce the deployment exactly, on a test network or another compatible network.

  • 04

    Integration

    Connecting the contract to your website or app, so that your users never have to handle technical tools.

  • 05

    Ongoing support

    Once live, we can monitor the contract's activity, help with admin operations and prepare future changes.

06 — WHAT TO CHECK

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, the secret codes that authorise sensitive operations, must 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 variable cost; optimised code and a sound architecture keep it down.

  • 04

    Dependencies

    Libraries, oracles (services that bring outside data onto the blockchain) and other contracts called: each one is a potential weak point to assess.

  • 05

    Legal framework

    If the project involves tokens, it may fall under the EU's MiCA regulation: legal advice is essential before you start.

07 — COST

What determines the cost of smart contract development

Every project receives a clear quote after an initial conversation. The budget depends mainly on the following.

  • 01

    Complexity of the rules

    The number of cases to cover, roles and interactions between contracts.

  • 02

    Choice of network

    Public or private, each with different testing and optimisation requirements.

  • 03

    Upgradeability

    An upgradeable contract needs extra architecture and 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.

08 — TOOLS

Technologies and methods

  • Solidity
  • EVM
  • Automated testing
  • Test networks
  • Source code verification
  • TypeScript
09 — FAQ

Frequently asked questions

Which blockchain should we choose?

It depends on who needs to read and write the data, the volume of operations and how long the proof must last. We compare the options with you, public or private, and recommend the simplest one that meets the need.

Can a smart contract be changed after deployment?

The deployed code does not change. 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 has implications for trust and security, which we explain 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 with the network, the complexity of the operation and how busy the network is at the time. We estimate them during design and optimise the code to keep them down.

Should a contract you have built be audited?

We test and review our code systematically. For a high-stakes contract, an additional audit by an outside reviewer remains good practice, and we make that process easy.

IN THE SAME AREA — BLOCKCHAIN