A new NearLaunch experiment is showing how NEAR and the Internet Computer Protocol can be used together to simplify the process of deploying websites on chain.
The project uses NEAR Intents to handle payment options and ICP to host the resulting website. According to the project’s developer, users can choose from a range of tokens supported through NEAR Intents when deploying a site, while the website itself is deployed to the Internet Computer.
The approach brings two different parts of the technology together. NEAR Intents is designed to abstract cross-chain transactions by allowing assets to be routed between connected networks, while ICP supports websites and applications that can run directly from canisters on its network. NEAR’s documentation currently lists more than 30 connected chains and more than 100 assets across its Intents infrastructure.
On the ICP side, websites can be deployed to asset canisters and accessed through an icp.net address. ICP’s developer documentation confirms that frontend applications can be hosted directly on the network, with static files served through canisters and accessible through standard web browsers.
NearLaunch is being presented as an early demonstration of what that combination could look like. Rather than requiring users to hold or pay directly with ICP, the application aims to give them a broader selection of payment assets through NEAR Intents while using ICP as the hosting layer.
The project is still under development, and its creator has advised users against trying it at this stage. That means the current implementation should be viewed as an experiment rather than a finished product or production-ready deployment service.
The development is noteworthy in the context of two communities that have often competed for attention around decentralised application infrastructure. The NearLaunch example instead presents a practical case where the two networks can serve different functions within the same workflow.
For users, the potential appeal is straightforward: payment and deployment could be separated, allowing a wider range of assets to be used to access a service while the resulting website runs on ICP. For developers, it points to the possibility of combining specialised infrastructure from different networks rather than treating them as mutually exclusive alternatives.
ICP already supports full frontend deployment directly to its network, including static sites and applications built with frameworks such as React, Vue and Svelte. NEAR Intents, meanwhile, is designed to provide cross-chain asset access through its solver-based infrastructure.
NearLaunch remains an early-stage project, so its reliability, security and eventual user experience will need to be assessed as development continues. For now, its main contribution is as a demonstration of how NEAR and ICP technologies can complement each other in a single user flow, rather than competing for the same role.
CREDITS : @richard_hery
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion