Services

Web3

Smart contracts, dApps and wallets, built with security in mind.

A product built with the checks in place
What we do

Contracts, apps, and wallets.

We design and build contracts, apps and wallets. Security is part of the design, and a release waits until the checks are in place.

Three kinds

What the work actually is.

Rules being written down

Smart contracts

The rules, written so they do the one job and no other.

A person using an app

dApps

The app a person uses. The contract is not the product by itself.

Someone moving money in an app

Wallets

How a person holds and moves what the product needs them to hold.

Security

The checks come before the release.

A release waits until the checks are in place. We would rather ship later than ship a contract we have not reviewed.

Designing what a contract can do

In the design

What the contract is allowed to do is decided before it is written.

A review before release

Reviewed

The checks are part of the project, not a favour at the end.

A release after the checks

Then it ships

When the checks are done, the app and the contract go out together.

What this is not

We will not invent a token to fill a page.

If the product does not need a contract, we will say so and build the thing it does need.

No token for its own sake

A token is a product decision, not a decoration.

No chain picked first

The job comes first. The chain follows from the job.

A plain product is fine

Many of the things people ask for are an app, a site, or a platform.

How a project runs

Design, checks, then release.

Discover

The job, and whether a contract is actually required.

Design

The rules, the app, and what a person is trusted to do.

Build

The contract and the app, together.

Launch

Only after the checks. Not before.

Support

We stay. A contract that is live still needs an owner.

If it is not Web3

The other four are here.

Tell us the job.

If it needs a contract, an app, or a wallet, say so. If you are not sure, say that too.