VDNX
ESLet’s talk

Web3·4 min read

Before building a Web3 project: do you need blockchain?

The first Web3 decision is the problem you need to solve. Define the benefit and separate what belongs on-chain from what does not.

Describe the problem without naming the technology

Start Web3 project planning with a sentence describing what someone needs to do. That might mean verifying a credential, transferring a digital asset or checking rules shared by several organisations. If the proposal only makes sense after mentioning a token, its purpose needs more work. The benefit should be open to discussion before choosing a network or developing a contract.

Write down who participates, what they share and what is difficult about the current system. Then describe a conventional alternative. This comparison is not about rejecting blockchain in advance. It identifies the specific property that would justify the added complexity. If one organisation already controls the data and decisions, explain what the user would gain from the change.

Separate the shared rule from the interface

Ethereum describes smart contracts as programs that execute rules on the network. For your product, distinguish that logic from the website presenting it. An interface can explain an operation, but important restrictions need to be enforced by the system carrying it out. Hiding a button does not, by itself, determine who has permission.

Sketch three parts: what the person sees, the rule they need to verify and the services connecting the two. Decide what should remain verifiable if the interface becomes unavailable. This outline helps establish whether the proposal needs a new contract, an integration with an existing one or simply a website explaining a service related to Web3.

Decide which data needs to be on-chain

Create a data inventory before designing screens. For each item, identify who creates it, who needs to see it, whether it can change and what would happen if it were wrong. Keeping some data away from a public chain should be an explicit scope decision, particularly when a project handles information about people or a business.

Contracts do not directly know facts about the outside world. Ethereum's documentation explains that oracles connect external information to them and introduce dependencies on availability and accuracy. If your product relies on a credential or a physical delivery, identify who confirms that fact and how disagreement is resolved. Recording a statement does not, by itself, establish that it is true.

Make control over the rules explicit

Prepare a simple permissions table: who can create, update, pause or remove each part of the system. Add what should happen if an administrative account is lost or compromised. These questions affect the product and its everyday operation. They should not be hidden at the end of a technical specification.

OpenZeppelin documents ownership and role-based controls for separating permissions. The choice should match real responsibilities. If someone can alter a rule, explain that in the user experience. If an operation cannot be changed, design its confirmation with that limit in mind. Trust also depends on people understanding who retains control.

Design for waiting, costs and errors

A prototype that only shows success leaves much of the work undefined. Draw the states for connection, review, signing, submission, waiting, confirmation and failure. Explain when the interface requests a signature and when it submits a transaction. Provide a clear way forward if someone rejects the request or uses a different network.

Ethereum uses gas to measure execution work, and fees depend on network conditions and the operation involved. Decide who bears that cost and how it is communicated before an action. Avoid basing viability on a fixed estimate without its assumptions. Operating costs also include providers, support, monitoring and maintenance of the interface.

Give the pilot a question it can answer

A first version can focus on one action and a clearly defined group of participants. State what you need to learn: whether people understand a permission, whether they can complete the journey or whether shared information solves a coordination problem. A pilot needs a way to evaluate its usefulness, beyond a list of finished screens.

Use a test environment and synthetic data to validate the flow before handling real assets or information. Record the failure cases you simulated and the limits of the review. Checking a journey is not equivalent to auditing a contract. Specialist review and any applicable legal requirements need their own scope and accountable owners.

Bring five decisions to the first conversation

A useful Web3 plan leaves room to reduce scope, change architecture or conclude that a conventional solution is a better fit. What matters is explaining that decision through the user's problem and the conditions under which the system will operate.

If you are preparing a project, gather these answers before requesting a proposal. They make it possible to discuss design and development around a recognisable scope, without turning a technical possibility into a promise of results.

  • What the user needs to do and why the current system is insufficient.
  • Which shared rule or data justifies using blockchain.
  • Which information stays off-chain and who is accountable for it.
  • Who controls permissions, changes and incident response.
  • What the pilot must demonstrate before the project expands.

Sources and documentation

Content created with AI assistance. Check the sources, date and scope of each guide.

What should your Web3 project do?

Tell us about its purpose, users and what still needs defining. We can help you assess the technical scope.

Let’s talk about your idea