Skip to content
East Wolf
Industries — Web3 & Digital Assets

Web3 and
digital assets.

Crypto, NFT and gaming systems. The wallet flow, the custody boundary, the state that sits on a chain and the much larger part that does not, and the mechanics that move an asset from one owner to another.

A deployed contract has no hotfix — which is where the engineering goes
§ 01What we build here01 / 03

What the work
actually is.

Grouped by what the work is, not by which chain it lands on. A chain is a deployment target. Most of the system around it is ordinary software that has to be exactly right about ownership.

01

Wallets and sessions

Connect flows, signature requests, session handling, and the path back for someone who has changed device. The signing is the small part. The work is everything the product must still do correctly while the wallet is absent.
02

Custody boundaries

Self-custody, delegated custody, and the seam between them. The design question does not change: who can move this, on whose authorisation, and what the system does when the key is gone.
03

Minting and provenance

Issuance, metadata, media storage, and a record that has to still resolve years after the launch it was built for. A link that rots takes the provenance with it.
04

Marketplace mechanics

Listings, offers, escrow, transfer and settlement. The order flow around an asset and the guarantees underneath it — not a view on what the asset is worth.
05

On-chain and off-chain state

Indexers, event listeners, reorg handling and read models. A chain gives you an append-only log; a product needs it queryable, consistent and quick. That gap is a system, and it has to be built.
06

Game and asset economies

Inventories, ownership transfer and progression that stays consistent whether the player arrived with a wallet or an ordinary account. Two identity models, one state to keep honest.
§ 02How it is engineered02 / 03

A bad deploy
is permanent.

An immutable ledger removes the safety net most software quietly relies on. There is no discreet hotfix on a live contract, and no rollback of a transfer that has already settled. Everything a normal build would catch in production has to be caught before it.

01

Verification carries the weight

Review, property tests, and a rehearsal against a fork of real state before anything is deployed. A normal release leans on monitoring and a fast patch. This one leans on being right the first time, so the effort moves earlier.
02

Upgrade paths are architecture

Proxies, migrations, pause switches and admin authority are settled before launch, because they cannot be added to something already live. Choosing not to have them is also a decision, and we make it out loud rather than by default.
03

The chain is the settlement layer

Ownership and transfer belong on-chain. Search, catalogue, media, notifications and the rest stay in ordinary services, where a mistake can be fixed on a Tuesday. Putting more on-chain than the guarantee requires is the common and expensive error.
04

Failure is public

Every call, every revert and every balance is readable by anyone, indefinitely. Key handling, observability and incident response are designed on the assumption that an audience is already watching.
Note

Where a jurisdiction, a platform or a counterparty imposes a rule, we build the system to enforce it and to evidence that it was enforced. We are the engineers on that. We are not your counsel, and we will say so before you need us to.

§ 03Start here03 / 03

Start before
you deploy.

Twenty years of delivery and 100+ projects delivered. The team is small and senior, with a network of 50+ engineers around it, and it works from Bucharest.

The case write-ups for this sector are still being prepared. There is a real body of work behind the page, and rather than paraphrase it into claims we cannot yet show you, we would rather take you through it directly. Ask, and we will bring the specifics to the call.

Tell us what you are building
Bucharest, Romania  /  hello@east-wolf.com
Back to Home