mirror of https://github.com/luxfi/bridge.git synced 2026-09-24 00:26:46 +00:00

Files

T

zeekay ee958f516f phase2-r2: scrub bridge3 / @luxbridge/app / lux-bridge references

Sweep through configs, docs, and ignore files after the structural
collapse in the previous commit. Updates fall into three buckets:

1) Restore the Dockerfile for app/bridge/
   - app/bridge/Dockerfile: new file, Vite SPA → ghcr.io/hanzoai/spa,
     same shape as the pre-collapse legacy Dockerfile, build context
     is repo root so @luxfi/bridge (workspace:*) resolves.
   - cmd/bridge/Dockerfile: switch UI-build stage to the workspace
     build context so the new app/bridge (which depends on the
     sibling pkg/bridge package) actually installs.
   - Makefile build-ui target: drop the per-app build context for
     the same reason — context must be repo root.

2) Update workspace docs to the new layout
   - README.md: rename @luxbridge/app row → @luxbridge/lux-tenant,
     port 3000 → 3001 (the slim tenant's vite config uses 3001).
   - docs/LLM.md: drop the bridge3 row, rename app/bridge row to
     @luxbridge/lux-tenant, update dev port.
   - docs/{BRIDGE-STATUS,LOCAL-SETUP,CI-CD-DOCKER-IMAGES}.md:
     `docker build … ./app/bridge` → `… -f app/bridge/Dockerfile .`
     so docs reflect the workspace-rooted build context.
   - .github/workflows/publish.yml: drop @luxbridge/app and
     @luxbridge/app-v3 from the private-packages comment.

3) Delete AI-slop status reports + test harness
   - CI_STATUS_REPORT.md, DEPLOYMENT_STATUS.md, WORKFLOW_AUDIT.md,
     WORKFLOWS_SUMMARY.md — stale and referenced bridge3.
   - test-bridge-ui.js — top-level Puppeteer/Playwright probe of the
     deleted legacy UI; not a workspace test.
   - .dockerignore: drop the test-bridge-ui.js entry now that the
     file no longer exists.

Out of scope (untouched): pkg/bridge/src/{Bridge,config,types,mount}
and pkg/bridge/src/app/ — Phase 3 R2 is working there. The
`@luxbridge/app` mentions in those files are historical comments
explaining the prior workspace cycle, not live references.

2026-05-21 15:15:37 -07:00

3.7 KiB

Raw Blame History

Lux Bridge

Bridge monorepo for Lux Network — a decentralized cross-chain bridge using Multi-Party Computation (MPC) for secure asset transfers.

Embed the bridge SDK

To embed bridge.lux.network in another app, install @luxfi/bridge:

pnpm add @luxfi/bridge react react-dom

import { mountBridge } from '@luxfi/bridge'

mountBridge({
  config: {
    apiHost: 'https://api.bridge.lux.network',
    env: 'mainnet',
    brand: { name: 'Lux Bridge', primaryColor: '#0066ff' },
  },
})

@luxfi/bridge is the only package consumers import. All @luxbridge/* packages are internal workspace deps and are never published.

Package scopes

Scope	Visibility	Role
`@luxfi/bridge`	public (npm)	Canonical SDK — embed bridge UI into a host app.
`@luxfi/core`	public (npm)	Shared types (Asset, Network, Contract, ...).
`@luxfi/threshold`	public (npm)	T-Chain MPC threshold-signature SDK.
`@luxfi/utila`	public (npm)	Utila protobuf client.
`@luxbridge/lux-tenant`	private (workspace)	Slim Vite SPA for bridge.lux.network — consumes `@luxfi/bridge`.
`@luxbridge/settings`	private (workspace)	Network + asset registry.
`@luxbridge/explorer`	private (workspace)	On-chain explorer UI.
`@luxbridge/server`	private (workspace)	Bridge API daemon.
`@luxbridge/ui-automation`	private (workspace)	Selenium UI test harness.

One canonical SDK name. One mount function. One config shape.

Prerequisites

Node.js v20+
pnpm v9.15.0+
Go 1.22+ (for MPC tools)
Docker (for infrastructure services)

Quick Start

1. Install Dependencies

# Install pnpm if needed
npm install -g pnpm

# Install project dependencies
pnpm install

# Install MPC tools via Go
make install-mpc

2. Start Infrastructure

# Start infrastructure services (Lux ID, KMS, databases, etc.)
make up

This starts:

Lux ID (Casdoor) - Port 8000 - Unified authentication
KMS (Vault) - Port 8200 - Key management
NATS - Port 4223 - Messaging
Consul - Port 8501 - Service discovery
PostgreSQL - Port 5433 - Bridge database
Lux ID DB - Port 5434 - Auth database

3. Start MPC Network

# Start 3-node MPC network
make start-mpc-nodes

This runs MPC nodes on:

Node 0: HTTP 6000, gRPC 9090
Node 1: HTTP 6001, gRPC 9091
Node 2: HTTP 6002, gRPC 9092

4. Start Application Services

In separate terminals:

# Terminal 1: Bridge API Server
cd app/server && pnpm dev

# Terminal 2: Bridge UI
cd app/bridge && pnpm dev

5. Access Services

Architecture

Bridge UI → Bridge Server → MPC Nodes → Blockchain Networks
                               ↓
                    KMS + Lux ID + Consul

Key Features

MPC Security: 2-of-3 threshold signatures
Multi-Chain: Support for EVM and non-EVM chains
Unified Auth: Lux ID (Casdoor) integration
Key Management: Secure key storage in KMS
Service Discovery: Consul for dynamic configuration

Development

# Run tests
pnpm test

# Check MPC status
lux-mpc-cli status --url http://localhost:6000

# View logs
tail -f logs/mpc-node-0.log

# Stop services
make stop-mpc-nodes  # Stop MPC
make down           # Stop infrastructure

Documentation

Tips

Since "pnpm" is a finger twister, many people alias it to "pn". For example, with bash, put alias pn='pnpm' in .bashrc.

3.7 KiB Raw Blame History