BSISend your brief

Blockchain development

Blockchain work that assumes the code will be attacked.

A deployed contract can be hard or impossible to change, and it may hold real value. Security decisions therefore come first, not last.

block 1prev hashstateblock 2prev hashstateblock 3prev hashstate
  1. Brief
  2. Scope
  3. Build
  4. Test
  5. Launch
  6. Handover

Where this fits

You need contracts written

Tokens, vesting, staking, marketplaces or custom logic, with a specification written before the code.

You need a product around them

The web app, wallet connection, indexing and backend that make a contract usable by ordinary people.

You are adding blockchain to a product

An existing business needs on-chain records, tokenized assets or payments connected to its current systems.

What we build

Smart contracts
Contract logic with a written specification, automated tests and documented assumptions.
Token systems
Fungible and non-fungible tokens, vesting and distribution, built to your legal adviser's requirements.
dApp front ends
Web apps with wallet connection and transaction screens that tell people what they are signing.
Indexing and backends
Services that read chain data into fast queries, reports and notifications for your product.
Asset tokenization platforms
The issuance, investor and admin software around tokenized assets, working with your counsel and custodian.
Audit preparation
Clean specifications, tests and fixes that help an outside auditor spend time on real risk.

What blockchain development involves

Blockchain development covers the contracts that run on a network and the ordinary software around them. The contract is often a small part of the code but carries most of the risk, because mistakes can be public, permanent and directly tied to money.

Most of a usable product is conventional engineering: a web app, wallet connection, a service that reads chain data, an admin console and monitoring. We plan both parts together.

Choosing a network

The network is a business decision as much as a technical one. These are the questions we work through in scoping.

Who needs to verify the records?
The public, or only known participants. That points toward a public network or a permissioned one.
What will a transaction cost?
Fees that are fine for a large transfer can make small, frequent actions impractical.
Where are your users and assets already?
Wallets, liquidity and exchanges can matter more than technical differences.
How much does it need to integrate?
Custody providers, oracles and auditors do not all support every network.

What an audit does and does not do

An independent audit is a time-limited expert review. It reduces risk, but it does not prove that code is safe. Auditors also work better from a clear specification and a good test suite, so preparation affects what you get for the fee.

After launch, risk moves to operations: who holds the admin keys, how upgrades are approved, and what happens if something looks wrong. Those plans belong in the scope alongside the code.

How we reduce the risk

  1. 01

    Decide on upgrades first

    Immutable contracts, proxies or a modular design. We make the choice early and write down who can change what.

  2. 02

    Protect the admin keys

    Multi-signature control and time delays for privileged actions, rather than one person holding one key.

  3. 03

    Test against real conditions

    Unit tests, testnet deployment and tests against a fork of the live network before anything goes to mainnet.

  4. 04

    Bring in an outside auditor

    We do not call a review of our own code independent. Contracts holding real value should go to a separate audit firm before launch.

Common questions

Do we actually need a blockchain?

Often not. If one party is trusted to run the records, a normal database is cheaper and faster. We will say so during scoping if that is the case.

Do you audit smart contracts?

We review and test our own work, then prepare it for an independent auditor. You should have an outside firm's report for anything holding meaningful value.

Who holds the keys after launch?

You do. Key ownership and any multi-signature setup are agreed in the scope and handed over at launch.

Can you advise on token law or regulation?

No. We are developers, not lawyers or investment advisers. Legal and regulatory questions stay with your own counsel, and we build to their requirements.

What does it cost?

It depends on the contracts, the product around them and the audit plan. You get a written estimate at the end of scoping. Any outside audit fee is separate.

Can a smart contract be changed after deployment?

Only if it was designed for that. Upgradeable designs allow changes but add a privileged control that must itself be protected, so it is a trade-off to settle early.

Can you connect blockchain to our existing systems?

Usually. A backend service can read chain data into your database and submit transactions from your application, with keys held in proper key management.

Tell us what you want to build.

A few lines are enough. We reply in writing with questions.

Send your brief
Blockchain & Smart Contract Development | BSI