Early accessb0-x is in development. Deploys aren’t open yet; the sites gallery and the on-chain gateway are live. Examples are labelled.
b0-xBeta

Deploy

From Vercel or GitHub
to Bitcoin.

Point b0-x at a project you already have. It builds the static output, and you choose whether to publish it on chain. Import and builds are planned; publishing works today.

In development

Import

Two ways in. Later

You sign in with bWalletX, then link the source you already use. b0-x reads the project; it does not take it over. Your Vercel project and GitHub repo stay exactly where they are.

From Vercel

Link your Vercel account with a read-only token, pick a project, and b0-x pulls the build settings it can use: framework, output directory, build command.

From GitHub

Install the b0-x GitHub app on a repo. Pushes to the branch you choose trigger a build. Previews for other branches need off-chain hosting, which isn't built.

From your machine

Or skip both and point b0-x at a built folder. Today that's the publisher, pnpm publish-site <dir>. See the docs.

Your key signs it

Every deploy is tied to your wallet key, so the dashboard, versions and names all belong to you, not to an account we hold.

Build

Build, then upload the output.

b0-x runs your build command in a clean container and keeps only the static output: HTML, CSS, JS, images, fonts. That output is what gets hosted and, if you choose, published.

# illustrative: this command doesn't exist yet
$ npx b0-x deploy
→ Detected: Next.js (static export) · output: out/
→ Running: pnpm build
→ 37 files · 4.2 MB
✓ built. Publish it on chain?

Preview URLs Later

A throwaway URL for each build, never written on chain. Not built: previews need off-chain hosting, and we haven't chosen the storage service.

Serving

Today the b0-x gateway serves published versions at b0-x.com/s/<name>/. Subdomains like <name>.b0-x.com are planned; DNS isn't set up.

Publish

A build can be published on chain as a numbered version. A name points at the version you choose.

Honest scope

What works today, what comes later.

One thing works today. The rest is the order we plan to build in.

  • TodayPublishing a static site on chain with the CLI (pnpm publish-site): each file an inscription, plus an ORDFS directory. The gateway serves it at b0-x.com/s/<name>/. bfriendsx and bvideox are published.
  • FirstStatic sites: plain HTML, Vite, Astro, Next.js static export, docs generators (Docusaurus, VitePress, MkDocs). Build, publish on chain, OpNS names.
  • FirstSign-in and payment with bWalletX (BRC-100), so any BRC-100 wallet works.
  • LaterGitHub push-to-deploy and branch previews; Vercel project import with build-setting detection.
  • LaterOff-chain hosting for previews and heavy media. Not built; no storage service chosen.
  • LaterSubdomains (<name>.b0-x.com) and custom domains.
  • Stays putServers, serverless functions and databases. A Next.js app with API routes keeps those on Vercel (or wherever it runs). b0-x publishes the static half: pages, assets, the front end.
Read the draft docs

Connect bWalletX to join early access. Nothing is stored; this just shows you your key.