Stewardship
Custody, treasury policy, governance, reporting, and long-term Bitcoin care.
HoldBanking House Control Room
Know who we can serve, how, and what must be true.
This is the meeting surface for Lunar Rails: identify the client, locate the jurisdiction, match the service, choose the route, and leave with the exact next unlock.
A banking house of Bitcoin is a trusted relationship layer for serious principals who need to hold, move, trade, finance, and understand Bitcoin capital without pretending every client, market, or service is the same.
ClientWho are they and what pressure are they under?
ServiceWhat do they need us to do?
RouteWhich entity, partner, or provider can deliver it?
UnlockWhat missing proof turns maybe into yes?
5Client groups to route
4Jurisdiction answers
8Reputation and trust gaps
Operating map
The house only makes sense when these four maps connect.
Every call should move one of these maps forward. If it does not, it is probably just interesting noise.
Trust and reputation
What makes the promise believable.
Trust is not a slogan. It is proof, process, counterparties, and repeated good judgment.
Build roadmap
The unlocks that change what we can say.
These are the wires to keep connecting so the map becomes operational instead of aspirational.
House and pillars
The banking house built for Bitcoin.
This is the conceptual map underneath the control room: four rooms of service, sitting on the foundation that makes the promise credible.
4Rooms: hold, move, trade, know
8Foundation pillars
1Relationship layer
Movement
Lightning, payment routing, fiat access, transfers, API rails, and settlement paths.
MoveExecution
OTC, conversion, liquidity aggregation, swaps, and best-execution workflow.
TradeIntelligence
Atlas, reporting, risk, client memory, market maps, and decision support.
KnowFoundation pillars
Licenses
Compliance
Security
Trust
Partners
Flux
Atlas
Customer Success
Service envelope
What the house can offer.
Filter by readiness. The honest map matters more than the prettiest promise: current, partner-enabled, planned, and license-gated capabilities should never be blurred together.
Serviceability map
Can we serve this customer?
Use one simple rule: we need the right country, the right service, and the right delivery route before anyone gets a yes.
What is missing
The work needed to turn blocked or maybe markets into a real yes.
Service tiles
Fast read by service. These wrap cleanly instead of hiding columns.
Client segment atlas
Who needs the house, and why.
The buyer is not buying a generic platform. Each segment has a different stress pattern: fiat obligations, custody risk, governance, liquidity pressure, and proof of trust.
Client operating system
How we contact, maintain, and serve clients.
This is the work loop behind the Banking House: turn a relationship into mapped context, a clear route, first value, ongoing trust, and reusable intelligence.
Segment playbook
How the lifecycle changes by client type.
Pick a segment to see the best first contact, first value, maintenance motion, and reputation proof.
Customer success loop
What must stay visible after the first call.
The relationship layer only works if every client has status, owner, next action, risk, and proof of value.
Operating model
Departments that hold up the house.
The artifact becomes more useful as owners get attached. For now, this is the operating model: each room needs product, compliance, operations, ecosystem, and customer success translation.