Why are some cryptocurrencies created on existing blockchains instead of building new ones?

Some cryptocurrencies are created on existing blockchains because building a completely new blockchain requires significantly more technology, security, infrastructure, and community support than creating a token on an established network.

A project that wants to create a digital asset does not always need its own blockchain. If its main purpose can be achieved using an existing network, building on that network can be faster, cheaper, and less risky.

This distinction is important because not every cryptocurrency operates as an independent blockchain. Some are native assets of their own networks, while others are tokens that operate using the infrastructure of another blockchain.

Building a New Blockchain Is a Major Undertaking

Creating a new blockchain involves much more than writing software.

A project needs to determine how transactions are validated, how participants reach agreement, how the network handles attacks, how users interact with it, and how upgrades are managed.

It may also need to develop:

• Network infrastructure
• Wallet support
• Block explorers
• Developer tools
• Security systems
• Validators or miners
• Governance mechanisms
• Documentation
• User applications

An established blockchain may already provide many of these components.

Instead of building the entire foundation, a project can focus its resources on the product or application it wants to create.

Existing Blockchains Already Have Security Infrastructure

Security is one of the biggest reasons projects use established networks.

A blockchain’s security depends partly on the participants who maintain and validate the network.

A new blockchain starts with a much smaller ecosystem. Depending on its design, it may have fewer validators, less economic activity, fewer developers, and less experience defending against attacks.

An established blockchain may already have years of testing, upgrades, security research, and real-world usage behind it.

This does not make an established network automatically safe. Blockchain systems can still contain vulnerabilities, and applications built on them can be attacked.

However, starting with a mature network can remove some of the risks associated with creating a new network from scratch.

It Can Be Much Faster to Launch

Developing a new blockchain can take substantial time.

A project using an existing blockchain can often concentrate on creating its token, application, smart contracts, or other features.

This can allow a team to move from an idea to a working product more quickly.

Speed can matter when a project is trying to test whether people actually want what it is building.

Development Costs Can Be Lower

Building and maintaining a blockchain requires technical expertise and infrastructure.

There may be costs associated with development, testing, security audits, network maintenance, developer tools, and ecosystem support.

Creating a token on an existing blockchain can reduce some of those requirements.

The project still needs developers and security measures, but it does not necessarily need to operate an entirely separate blockchain network.

Existing Blockchains Already Have Users

Network effects are another major advantage.

An established blockchain may already have millions of users, wallets, developers, applications, exchanges, and other infrastructure.

A new project can potentially benefit from this existing ecosystem.

For example, if a token is created on a blockchain that is already supported by popular wallets, users may not need to learn an entirely new system just to interact with the token.

Existing Wallets Can Make Access Easier

Wallet infrastructure is important to cryptocurrency adoption.

If an existing blockchain is already supported by widely used wallets, a new token may be easier for users to store and interact with.

Building an entirely new blockchain may require additional wallet integrations and technical support.

That can create another barrier between the project and potential users.

Smart Contract Platforms Make Token Creation Possible

Many blockchains support smart contracts.

A smart contract is software deployed on a blockchain that can automatically execute predefined rules.

These platforms allow developers to create tokens without creating a new blockchain.

For example, a developer can create a token with specific rules for supply, transfers, or other functions while relying on the underlying blockchain to process and record transactions.

This is one reason token-based projects have become relatively common.

The Project May Not Need Its Own Consensus System

A blockchain needs a mechanism for deciding which transactions are valid and how the network reaches agreement.

Developing and maintaining this system is a major technical responsibility.

If a project uses an existing blockchain, it can rely on that blockchain’s consensus mechanism instead.

This allows the project team to focus on its own application rather than building a separate system for validating the underlying network.

Developers Can Focus on the Actual Product

Imagine someone wants to create a cryptocurrency-based application for a particular industry.

If the application can operate on an existing blockchain, the team may spend its resources improving the application instead of maintaining a separate blockchain.

This can be an important difference.

The blockchain is infrastructure.

The project itself may be trying to solve a completely different problem.

Interoperability Can Be Valuable

Building on an established blockchain can make it easier to interact with other applications that already operate on that network.

For example, a token may be able to interact with compatible decentralized applications, wallets, and other smart contracts.

This can create an ecosystem around the asset rather than leaving it isolated on a new network.

Liquidity Can Be Easier to Access

Existing blockchain ecosystems may already contain established trading infrastructure and markets.

A new token can potentially connect to this infrastructure more easily than an asset operating on an entirely new blockchain.

However, being created on a popular blockchain does not guarantee that a token will have strong liquidity or meaningful demand.

Those still depend on the project and the market.

Developers Can Use Existing Tools

Established blockchains often have programming libraries, testing environments, documentation, developer frameworks, monitoring tools, and other resources.

This can reduce the amount of infrastructure developers need to create themselves.

It can also make it easier to find people who already understand the technology.

Developers Can Benefit From Existing Communities

A large developer community can be extremely valuable.

Developers can find tutorials, technical discussions, open-source code, security research, and troubleshooting information related to the underlying blockchain.

A new blockchain has to build much of that community from the beginning.

There Is a Trade-Off

Using an existing blockchain is not automatically the best choice.

A project may eventually discover that the underlying network does not provide everything it needs.

For example, it might require:

• Different transaction rules
• Greater control over upgrades
• Specialized performance characteristics
• Custom governance
• Specific privacy features
• Different fee structures
• Specialized infrastructure

In such cases, creating a dedicated blockchain may make more sense.

Control Is One of the Biggest Differences

When a project creates a token on another blockchain, it depends on that network.

The underlying blockchain controls important aspects of the environment.

If the network changes its technology, fees, rules, or capabilities, applications and tokens operating on it may be affected.

A project with its own blockchain has considerably more control over its underlying infrastructure.

That control comes with additional responsibility.

Transaction Fees Can Matter

Using an existing blockchain means users generally have to interact with that network’s transaction system.

Depending on the network, fees may change with demand.

A project might therefore choose a particular blockchain because its transaction costs and performance are suitable for its intended use.

However, fees are only one part of the decision.

Security, reliability, ecosystem support, scalability, and developer experience can also matter.

Scalability Can Influence the Decision

Some projects require a high volume of transactions.

If an existing blockchain cannot meet the project’s performance requirements, the team may look for another network or consider building its own.

In some cases, projects use specialized networks or scaling systems connected to established blockchains instead of creating a completely independent blockchain.

This can provide a middle ground between using an existing network and building everything from scratch.

Different Projects Have Different Needs

A simple digital token may have little reason to operate its own blockchain.

A project that needs to define an entirely new type of network economy may have stronger reasons to build one.

For example, a blockchain designed specifically for a particular application may require technical features that general-purpose networks do not provide efficiently.

The right architecture depends on the problem being solved.

Tokens and Coins Are Not Exactly the Same

The terminology can be confusing.

People often use “cryptocurrency,” “coin,” and “token” interchangeably, but there is a useful distinction.

A coin is generally the native asset of its own blockchain.

A token is generally an asset created on top of an existing blockchain.

For example, a network may have its own native cryptocurrency while also supporting thousands of independently created tokens.

This is why a project can create a cryptocurrency-like asset without creating an entirely new blockchain.

Existing Networks Can Reduce Technical Complexity

Creating an application on top of an existing network allows a project to separate its responsibilities.

The blockchain handles things such as transaction validation and distributed record-keeping.

The project can focus on its own user experience, business model, application, or community.

This division of responsibilities can make development more practical.

But Projects Still Need to Understand the Underlying Blockchain

Using an established network does not eliminate technical risks.

Smart contracts can contain vulnerabilities.

Poorly designed tokens can create unexpected behavior.

Applications can have security weaknesses.

Users can also lose funds through scams, phishing, or mistakes.

Therefore, relying on an established blockchain should not be interpreted as a guarantee of safety.

It simply means the project is building on infrastructure that already exists.

Building a New Blockchain Can Make Sense for Some Projects

There are legitimate reasons to create a new blockchain.

A project might need complete control over:

Consensus → Governance → Fees → Block production → Network rules → Upgrades

If those elements are central to the project’s purpose, using another blockchain may be too restrictive.

A new blockchain can provide greater customization.

The challenge is that the project must now attract validators, developers, users, applications, and economic activity.

The Network Effect Creates a Difficult Challenge

A new blockchain needs users to make it valuable.

Users often want applications and liquidity.

Developers want users.

Applications want users and developers.

Validators want economic incentives.

This creates a difficult bootstrapping problem.

An established blockchain already has much of this ecosystem, which can make it attractive to new projects.

The Decision Is Really About Trade-Offs

Choosing between an existing blockchain and a new one involves balancing several factors.

Consideration	Existing Blockchain	New Blockchain
Development speed	Usually faster	Usually slower
Infrastructure	Already available	Must be developed
Network security	Inherited from network	Must establish
Control	More limited	Much greater
Ecosystem	Existing	Must build
Development cost	Often lower	Often higher
Customization	Limited by network	Highly customizable
Maintenance	Less infrastructure responsibility	Significant responsibility

Neither option is automatically superior.

The right choice depends on what the project actually needs.

The Bigger Lesson

Some cryptocurrencies are created on existing blockchains because not every project needs to build an entire blockchain to solve its problem.

Using an established network can provide access to existing security infrastructure, users, wallets, developers, applications, and transaction systems. It can also reduce development time and allow a team to concentrate on the product it is actually trying to build.

Creating a new blockchain makes more sense when a project needs significant control over network rules, consensus, governance, performance, fees, or other underlying features.

The choice therefore comes down to a fundamental technology decision:

Do we need to build the entire infrastructure, or can we safely and effectively build what we need on infrastructure that already exists?

For many projects, using an existing blockchain is the more practical answer. For others, creating a new network may be justified by the level of control and specialization they require.

Understanding that distinction makes it much easier to understand why the cryptocurrency ecosystem contains both independent blockchain networks and thousands of tokens built on top of them.

Would you prefer to build a cryptocurrency on an established blockchain or create an entirely new blockchain, and what would influence your decision?