What's next: ARC, one real application at a time

The new ArcBlock website is live, running entirely on ARC. The pages, content and interactions you see here are already part of ARC doing real work.

So, what comes next?

We wanted to share what we are preparing. ARC's full release will unfold through a series of steps. The website gives everyone a working place to start. From here, we plan to migrate existing services and introduce products built on ARC from the beginning, putting the system to work in different kinds of real use.

What follows is our current direction. Some of this work will overlap, and the pace will depend on product and migration readiness. We will announce usable releases and ways to participate as they become ready.

Bringing the services people already use

One of the next major migrations is ArcBlock.community. Our community site is built with Discuss Kit and currently runs on Blocklet Server. We plan to move it to ARC.

A community brings a different test from a company website. People keep creating, discussing and updating its content. Moving it means supporting an active service with real users and years of accumulated material. It will give us a much fuller demonstration of how ARC handles dynamic, user-generated content.

That work matters beyond our own community. Many people have built with Discuss Kit, and we want the experience of migrating our site to help them upgrade too. Their existing content and familiar ways of using the software deserve careful attention.

Another priority is upgrading DID Space to ArcSpace. DID Space has been running on Blocklet Server. We plan to move it to the ARC-based ArcSpace.

The change is more than a name. The mechanisms behind data spaces are now part of ARC's core, rather than something supplied only as an add-on. Our goal is a smooth transition that lets existing users continue working with their data. We will explain the upgrade process when it is ready; we want to work through the migration before asking people to take it on.

Aside brings ARC into everyday use

Aside is a complete product we are preparing to introduce next. It is built entirely on ARC and spans mobile, desktop and web. For everyday users, it should first be an application worth using. For people interested in ARC, it will also be a working example they can examine.

There is a deliberate choice behind its development. Although we are building Aside ourselves, we treat it internally as an independent third-party application. We want to use ARC from an application developer's position, encounter the difficulties, and bring what we learn back into the platform. A showcase is only so useful if the platform team is the only group that knows how to run it.

We therefore plan to release teaching material alongside the application, showing how to develop and deploy something similar. Builders should be able to see how a complete cross-platform product fits together and find a practical place to begin.

After Aside, we plan to introduce several more applications developed with the same independent, third-party perspective. Each will address a different need and put ARC to work in another setting. We intend to share more of that work as it happens and build in public with other builders.

A fresh start for ArcSphere and the wallet

ArcSphere 2.0 is being prepared as a relaunch. Its direction expands from an AI web browser into an AI agent application browser, with a broader focus on applications and their interactions. It is intended to provide a user-facing entry point for working with ARC applications.

That is why we see it as a new kind of product, rather than a few additions to the previous browser. Alongside the underlying runtime, ARC needs a frontend that people want to open and find easy to use. That experience is the focus of ArcSphere's next chapter.

DID Wallet will be upgraded and renamed ArcWallet. We want its role in managing a user's digital identity, certificates and assets to become clearer. Cryptocurrency asset management will remain, along with ArcBridge and other capabilities connected to ArcBlock Chain.

The aim is a lighter product with better passkey support, improving security and everyday usability together. We will introduce the specific features and workflows as the product becomes ready.

Moving forward with existing builders

New applications are part of the story. So is the work people have already done.

We plan to invite existing builders to work with us on upgrading their Blocklets to ARC, with practical help and guidance. The Blocklet name continues, but its implementation model has changed substantially. Applications have different features and dependencies, so their upgrade paths will need individual attention.

We want to turn that experience into material other builders can use. The places where an upgrade needs a better explanation, a missing tool or a platform change will help determine what we improve next. Building new products in public and upgrading existing ones can contribute to the same effort.

Communication needs to keep pace too. Alongside releases, we need clearer introductions, teaching material people can follow, and ongoing conversations with the community. It should be possible to understand what an update means for you without piecing the story together from scattered announcements.

A chance to meet in October

We have two trips in preparation for October.

We plan to attend ASE 2026 in Munich, October 12–16, and give a keynote at its Harness4GenUI workshop. The discussion will focus on AFS, the Agentic File System, and the work around its interfaces: what foundations should remain stable as AI keeps generating and changing software?

We are also planning small research discussions and academic exchanges with our research partners at CSIRO's Data61, and hope to arrange university visits and informal meetups in Munich and nearby cities. Those arrangements are still being coordinated; we will share details when they are settled.

We then plan to attend Cloudflare Connect in San Francisco, October 19–21, as conference attendees.

Cloudflare is a major infrastructure focus for ARC today. We see a close architectural fit with how ARC runs, and we are investing further in that path. We also intend to maintain our longstanding relationships with AWS and Google Cloud.

During the conference, we plan to hold a small ArcBlock builder meetup in the Bay Area. It would be a chance to talk about applications in progress, older Blocklet upgrades, and problems people are running into. We will announce the time, place and participation details separately.

A release made of real beginnings

If the updates arrive one after another, that is the rhythm we have in mind. The website is running. Community and data-space migrations come next, with new applications moving into everyday use. Each step gives ARC more practical experience and gives people another way to take part.

For now, explore the new site and take a look at ARC and the Blocklet story. We will keep sharing what comes next here. Sometimes that will be a migration, sometimes a new application, and sometimes a tutorial that makes it easier to get started.

ARC's release will take shape through that work.