Lumera Hub

Lumera Protocol is a next-generation blockchain built for the age of decentralized AI, autonomous agents, and permanent data storage. Formerly known as Pastel Network, Lumera isn't just another Layer 1 — it's a purpose-built, high-performance foundation for the future of Web3 services.

At its core, Lumera combines scalable infrastructure with programmable economic incentives, making it possible for developers, validators, and everyday users to participate in a self-sustaining ecosystem that powers AI-driven applications, censorship-resistant storage, and secure cross-chain interoperability.

---

Getting Started

Prerequisites

• Node.js 24+
• pnpm 9+
• For desktop: Rust toolchain
• For mobile: Xcode (macOS) or Android Studio

Quick Start (Make)

The fastest way to run the web app is through the Makefile. Each network target installs dependencies, creates apps/web/.env.local from the template when it is missing, and pins the complete network profile — no manual env editing needed:

make devnet    # run the dev server against Lumera devnet
make testnet   # run the dev server against Lumera testnet
make mainnet   # run the dev server against Lumera mainnet

All targets (replace <net> with devnet, testnet, or mainnet):

Target	What it does
make <net>	Install, configure, and run the development server
make <net>-build	Create a production build configured for that network
make <net>-check	Run tests, type checking, and a production build
make <net>-preview	Build and serve a production bundle
make setup	Install dependencies and create .env.local when missing
make test	Run web unit tests
make typecheck	Run web TypeScript checks
make help	List available commands (also the default target)

The dev and preview servers listen on port 3000; override it with PORT:

make testnet PORT=3001

Installation

pnpm install

Development

Select a network

The Make targets above set the network profile for you. When running the app directly with pnpm instead, copy the web environment template and select one of the local network profiles:

cp apps/web/.env.example apps/web/.env.local

NEXT_PUBLIC_NETWORK_PROFILE=testnet

Supported profiles are devnet, testnet, and mainnet. Their chain IDs and endpoints are defined together in apps/web/src/contants/network.ts. Individual NEXT_PUBLIC_CHAIN_NAME, NEXT_PUBLIC_CHAIN_ID, NEXT_PUBLIC_RPC_ENDPOINT, NEXT_PUBLIC_REST_AI_URL, NEXT_PUBLIC_EVM_RPC_ENDPOINT, NEXT_PUBLIC_EVM_WS_ENDPOINT, NEXT_PUBLIC_EVM_CHAIN_ID, and NEXT_PUBLIC_SNAPI_URL values can still override the selected profile.

Wallet support is profile-dependent:

• mainnet uses Interchain Kit with the injected Keplr wallet.
• EVM-enabled devnet and testnet profiles support Keplr plus an injected EIP-1193 MetaMask wallet for native LUME balances and transfers.
• MetaMask does not provide a Cosmos signer. Cosmos staking and governance actions therefore remain unavailable while MetaMask is active.

WalletConnect, Leap, and Cosmostation are not configured. The scaffold document under docs/ contains historical examples for those integrations and is not a current setup guide.

Run Dev Servers with Watcher

Run all apps in development mode:

pnpm dev

Run individual apps:

# Web (Next.js)
pnpm --filter web dev

# Desktop (Tauri)
pnpm --filter desktop tauri dev

# Mobile (Expo)
pnpm --filter mobile start

Build for Deployment

Build all apps:

pnpm build

Build individual apps:

# Web (Next.js)
pnpm --filter web build

# Desktop (Tauri with static export)
pnpm run build:desktop

# Mobile (Expo EAS)
cd apps/mobile
npx eas build --platform ios  # or android

Run Built Versions Locally

After building:

# Web
pnpm --filter web start

# Desktop
# The built app is in apps/desktop/src-tauri/target/release/
# Run the executable directly

# Mobile
# For iOS simulator: npx expo run:ios
# For Android emulator: npx expo run:android
# For web preview: npx expo start --web

Deployment

• Web to Vercel (recommended): cd apps/web && npx vercel --prod This builds and deploys the Next.js app directly to Vercel. Vercel handles the server-side rendering, routing, and hosting—no manual steps required. Ensure you're logged in to Vercel CLI (npx vercel login) and have linked the project.

• Web to Other Cloud Hosts (e.g., VPS with nginx): If deploying to a custom cloud host that expects static files (not full Next.js server features), build a static export first:

  cd apps/web
  NEXT_OUTPUT=export pnpm build  # Creates static files in ./out/

  Copy the ./out/ directory to your remote host (e.g., via SCP, FTP, or cloud storage sync). On the remote host, configure nginx (or your web server) to serve the static files: Point the server root to the ./out/ directory.

  server {
      listen 80;
      server_name hub.lumera.io;
      root /var/www/hub;
      index index.html;
      location / {
          try_files $uri $uri/ /index.html;
      }
  }
  

  Restart nginx: sudo systemctl restart nginx. Note: This is a static subset—server actions and dynamic features won't work. For full Next.js features, use a host that supports Node.js (like Vercel, Netlify, or Railway).

• Desktop: The pnpm run build:desktop produces distributable binaries

• Mobile: Use EAS builds for app stores

Scripts

• pnpm lint: Lint all code
• pnpm format: Format code with Prettier

Official Website

• 👉 https://lumera.io/
• 👉 https://x.com/lumera
• 👉 https://discord.com/invite/lumeraprotocol
• 👉 https://github.com/LumeraProtocol/
• 👉 https://www.reddit.com/r/LumeraProtocol/?rdt=58979
• 👉 https://www.youtube.com/@lumeraprotocol