Bitcoin Palace is a proposal to construct a landmark tower in Las Vegas using an open execution protocol.
The protocol defines how commitments are held in escrow and released only at verified milestones. Progress is reported on a fixed weekly cadence with evidence attached.
This document specifies: constraints, threat model, milestones, proof standard, and disclosure tiers.
We publish proof. Proof compounds.
Bitcoin reached global scale as a standard of property.
Skylines operate differently. They are capital-intensive, regulated, negotiated, and slow to change.
This protocol defines how a durable coordinate is built: proof → milestones → escrow releases → delivery.
This protocol is defined by constraints. Constraints reduce ambiguity and protect execution.
Constraints create clarity. Clarity creates repeatability.
Any open build system attracts predictable failure modes.
This protocol does not remove risk. It makes risk legible, attributable, and auditable.
Legible risk is manageable risk.
Open Build is an execution control system.
It has three primitives:
Escrow releases follow verified proof. Proof is documented evidence signed by accountable roles.
Milestones start before concrete. The objective is to make progress binary and externally verifiable.
Each milestone publishes: status, proof bundle summary, signature set, next blocking dependency.
Milestones turn ambition into timestamps.
Proof of Build is the evidence standard for milestone verification.
A PoB bundle may include:
— signed agreements, official filings, and receipts
— plans, schedules, and cost assumptions
— procurement lists, bids, and selection memos
— inspection notes and certificates (when applicable)
— dated progress media (when applicable)
— meeting minutes and sign-off records
Each PoB bundle is signed by:
— the responsible role (e.g., owner's rep / AoR / advisor)
— the verifier role (council / third-party auditor where required)
Hash policy: for each milestone, a hash of the PoB bundle is published. Public artifacts may be redacted. Verified/NDA tiers may access full documentation.
PoB is a process. Proof compounds.
Transparency without structure breaks negotiations. Opacity without proof breaks trust.
Disclosure is deliberate. Proof is publishable. Terms are protected.
Participation is role-based, not narrative-based.
Verified contributions become part of the registry. Unverified submissions do not.
The execution council is the accountable verification and delivery layer.
Its purpose:
— maintain milestone definitions
— verify PoB bundles
— publish the weekly scoreboard cadence
— enforce disclosure tiers and redaction rules
— manage conflicts of interest and revocation
Council membership is role-based and evidence-driven.
Council composition is published and updated at each phase transition.
Each phase advances when its proofs exist.
For verified access requests and disclosure tier onboarding: