refactor(rename): branding strings + active-use docs → bitSpire
Final rename commit covering user-facing copy and the docs that
describe current state. The mechanics of the rename are done after
this; the LNbits backend swap (phase 3) is the next concern.
Code branding strings (Lightning invoice descriptions):
apps/machine/src/services/lightning.ts
apps/machine/src/stores/atm.ts
docs/clink-protocol.md (example code blocks)
"Lamassu ATM Payment" → "bitSpire Payment"
"Lamassu ATM - Cash Out" → "bitSpire - Cash Out"
`Lamassu ATM - Buy ${n} sats`→ `bitSpire - Buy ${n} sats`
Top-level docs:
README.md, CLAUDE.md — title + intro + dir-tree references.
deploy/nixos/README.md — title + worktree-path commands.
docs/machine-installation.md — opening line carries the historical
note ("Lamassu Next" → "bitSpire"). The body still uses
`/opt/lamassu/` paths and the `lamassu-kiosk` systemd unit
because the dev branch is moving to NixOS disk-image flash
(phase 4) — this AppImage-sideload doc represents the legacy
deploy path. Leaving the LP/lamassu refs in there as part of
its historical context; a separate doc will describe the
NixOS path.
.claude/skills/nostr-check.md — header only.
DELIBERATELY left as "Lamassu Next" (pedagogical / historical):
- docs/adr/001-hal-architecture.md — frozen ADR; renaming
distorts the historical decision context.
- docs/architecture-comparison.md — deliberately contrasts
"lamassu-server" (prior) with "lamassu-next" (us at the time
of writing).
NOT done in this commit (deferred to LNbits/clean-up phase):
- docker/docker-compose.dev.yml container names
(lamassu-relay, lamassu-bitcoind, etc.) — these belong to the
LP-bearing dev stack that 3c/3d will significantly reshape.
Verified: pnpm typecheck clean (12/12 cached).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
28a35ca479
commit
219e7e1e4d
8 changed files with 23 additions and 23 deletions
|
|
@ -1,10 +1,10 @@
|
|||
# CLAUDE.md
|
||||
|
||||
This file provides guidance to Claude Code when working with the Lamassu Next codebase.
|
||||
This file provides guidance to Claude Code when working with the bitSpire codebase.
|
||||
|
||||
## Project Overview
|
||||
|
||||
**Lamassu Next** is a Nostr-native Lightning ATM system. Key principles:
|
||||
**bitSpire** is a Nostr-native Lightning ATM system. Key principles:
|
||||
|
||||
- **KYC-Free**: No identity collection, no compliance theater
|
||||
- **Lightning-Native**: Security encapsulated in Lightning protocol
|
||||
|
|
@ -14,7 +14,7 @@ This file provides guidance to Claude Code when working with the Lamassu Next co
|
|||
## Architecture
|
||||
|
||||
```
|
||||
lamassu-next/
|
||||
bitSpire/
|
||||
├── apps/
|
||||
│ ├── machine/ # Electron + Vue 3 ATM kiosk application ✅
|
||||
│ ├── dashboard/ # Vue 3 operator dashboard (planned)
|
||||
|
|
@ -166,7 +166,7 @@ cd ~/dev/local/docker/regtest && ./start-regtest
|
|||
source docker-scripts.sh
|
||||
|
||||
# Start lamassu services connected to regtest
|
||||
cd lamassu-next/docker && ./start-with-regtest.sh
|
||||
cd bitSpire/docker && ./start-with-regtest.sh
|
||||
|
||||
# CLI helpers
|
||||
bitcoin-cli-sim -generate 1 # Mine blocks
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue