BauProto × Nightfall Vault · Target picture

Paymentfollowsperformance.Confidential.Provable.

BauProto makes every piece of construction work provable. Nightfall Vault is designed to trigger the payment for it automatically, settle it confidentially and keep it verifiable for every authorised party. Anchored in a public blockchain.

BauProto beta running with the first site-supervision office from Salzburg since October 2026
The situation

Constructionmovesbillionsontrust,paperanddisputes.

Between work delivered and invoice paid lie weeks, change orders, retentions and arguments about what is actually finished. Every party keeps its own version of the truth.

Late payment is the norm

Subcontractors pre-finance projects. Liquidity crunches come from slow approvals, not from bad work.

Disputes over progress

What has been accepted, what is defective, what is a change order? Without a shared chain of evidence, lawyers decide.

Collateral ties up capital

Bonds, retentions and guarantees cost money because nobody can measure the risk.

Confidentiality versus transparency

Cost calculations and payment flows are trade secrets. Public blockchains expose them, closed systems prove nothing.

Architecture

Threelayers.Eachdoesexactlyonething.

BauProto owns the workflow and the chain of evidence. Nightfall Vault runs confidential settlement between institutions. A public blockchain provides the immutable time anchor. No layer has to trust another blindly.

  1. BauProto

    Workflow and evidence

    Implemented
    • Site diary
    • Plans, defects, evidence photos
    • BIM / IFC
    • Acceptance with qualified signature
    • Merkle evidence chain
    • XRechnung / ZUGFeRD
    • Tender to award

    Trust through eIDAS signatures and Merkle proofs

  2. Nightfall Vault

    Confidential settlement

    Planned
    • Permissioned BFT network
    • Seven independent validators
    • Escrow milestones
    • Tokenised bank deposits
    • Pedersen commitments
    • Selective disclosure

    Trust through Consensus of 5 out of 7

  3. Nightfallcoin

    Public time anchor

    Planned
    • Proof-of-work blockchain
    • Checkpoint anchoring of vault states
    • Operated independently of the vault

    Trust through Computing work of an open network

Flow in the target picture

Fromawardtopayment,withoutasinglephonecall.

This is how a project runs when BauProto, Nightfall Vault, an escrow bank and the public anchor work together. Nothing is entered twice, every step stays provable.

  1. BauProto · Tender and award

    The client awards the project

    Tender, bids and award run in BauProto. The award automatically creates the contract with bill of quantities and a payment plan made of milestones.

    Award → contract + BoQ + milestone plan

  2. Escrow bank → Nightfall Vault

    The bank funds the escrow

    The client's bank places the budget in an escrow account and issues tokenised deposits for it in the vault, backed 1:1 and issued only by the bank. BauProto never holds money.

    MINT_ASSET EUR-escrow → escrow:Project-4711 · signer=EscrowBank

  3. BauProto · Execution

    The site documents itself

    Site diary, time-stamped photos, defects on the plan, BIM progress. Every entry becomes part of the Merkle evidence chain. Later changes cannot go unnoticed.

    Entry → hash → Merkle root

  4. BauProto · Acceptance

    Acceptance with qualified signature

    Site supervision and client accept the milestone, signed with ID Austria or a-trust under eIDAS and ÖNORM B 2110. This signature is the technical trigger for everything that follows.

    { milestone: "Shell L2", merkleRoot: 0x9f3a…c71e, qes: [Supervision, Client] }

  5. Nightfall Vault · Consensus

    Seven validators check the same rules

    Are the signatures valid and authorised? Does the milestone match the contract? Is there enough escrow? With five of seven approvals the release is final.

    verify(qes) ∧ match(BoQ) ∧ escrow ≥ amount → 5/7

  6. Nightfall Vault · Payout

    Payment flows as a cascade

    The milestone is released to the general contractor and, as the contract says, straight on to the subcontractors involved. Amounts stay hidden in commitments.

    escrow → GC → Electrical, Facade · amounts hidden

  7. Risk and capital

    Verified work becomes capital

    A subcontractor proves its payment and schedule reliability to its bank through selective disclosure, without revealing calculations. Insurers price warranty risk on real data.

    Proof: on time · defect-free · paid

  8. Public anchor

    The state is anchored publicly

    Periodically the vault writes its state root as a checkpoint into the Nightfallcoin blockchain. Experts and courts can then prove that this state existed at that point in time.

    checkpoint(stateRoot) → block

Nightfall Vault · Consensus

Nosingleoperatorcanmovemoney.

Seven organisationally independent institutions are meant to run one validator each, with equal voting weight. A block is final only when more than two thirds agree: five of seven. Up to two compromised validators cannot break security.

Votes · 0 / 7

Possible operators in the target picture

  • Escrow bank
  • Insurer
  • BauProto
  • Chamber of civil engineers
  • Client association
  • Audit and notary office
  • Independent data centre

In every round two validators misbehave. Their votes are discarded and the release still goes through.

Finality in one to three seconds. Validators check validity but hold no participant keys and cannot create value.

Planned

Properties

Privacy by design

Amounts live in cryptographic commitments, not in plain text.

Verifiable integrity

Every validator checks that no value is created out of nothing.

Selective disclosure

Release proofs selectively without exposing the whole history.

Institutional integration

Roles, four-eyes principle, HSM or MPC, interfaces for treasury systems.

Confidentiality

Everyoneseesexactlywhattheyneedtosee.

Public blockchains show everything. Classic databases prove nothing. Nightfall Vault separates validity from visibility: validators check that everything adds up without knowing the amounts.

What the general contractor sees

Example
Milestone
Shell L2
Amount
€ 412.800,00
Recipient
Elektro Huber GmbH

What the vault ledger stores

C = v·G + r·H

0x7c1e9a04d3b2f8e1…

  • Range proof
  • Signature
  • Nullifier
Validator checksCGC 0x3a90c4…=CElectrical 0x41b2e7…+CFacade 0x1f08d3…Input = sum of outputs, without knowing any amount

Who sees what

—AmountRecipientProof of workValidity
General contractor
Subcontractor
Validators
Bank, insurer
Court, expert
  • sees it
  • own items only
  • only via released proof
  • does not see it

Cryptographic building blocks

Pedersen commitments

Amounts are hidden but can still be added up, so every validator can check that inputs and outputs match.

Range proofs and nullifiers

No negative amounts, no hidden inflation, no spending the same release twice.

Payment proofs

The recipient proves a single payment to an auditor, bank or court. The rest of the history stays private.

Public anchor

Immutabletime,securedbycomputingwork.

In this setup the public proof-of-work blockchain Nightfallcoin provides what no single institution can: a neutral time anchor that nobody can turn back.

Planned
  • Block · Proof of Work
  • Vault root

Checkpoint anchoring

Vault state roots are anchored periodically. An anchor proves that a state existed, but does not replace the validators' checks.

Separate security

The blockchain stays unchanged and independent. If the vault fails, it keeps running, and vice versa.

No token of our own

BauProto issues no token. Here the blockchain serves solely as a time anchor for proofs.

Not investment advice and not an offer of crypto-assets. Anchoring is a later, separately specified extension.

Evidence & security

Court-proof,notjuststored.

Documentation is only worth as much as its immutability. Every action is bound into a continuous hash chain — retroactive changes to the history become detectable.

Merkle-secured audit trail

Block 1
9f3a…c21e
Block 2
4b7d…08fa
Block 3
e21c…9d43
Block 4
7a90…f1b6
Sealed
c5e8…2a7d
Action

An entry, defect, decision or acceptance is created

Hash

The content is summarised cryptographically

Chaining

The hash is linked to its predecessor

Checkpoint

The chain is sealed periodically

Qualified signatures

Signatures under European signature law, via Austrian trust service providers and the national digital identity.

Tenant isolation in the database

Separation between organisations is not only checked in the application but anchored in the database itself.

Instruction chain

Who gave which instruction and when stays traceable with timestamp and author — even years later.

Recoverability

Deleted items remain recoverable at first; permanent deletion is a deliberate, logged operation.

eIDAS
ID Austria
a-trust
ÖNORM B 2110
GDPR
Local AI

Noconstructionplanleavesthebuilding.

The AI runs on the company's own hardware. Estimates, plans, variations and correspondence stay in-house — that is not a setting, it is the architecture.

COMPANY SERVERProject dataLocal modelVector indexno outbound pathExternal cloud

Model on your own hardware

Language model and embedding model run locally. There is no path by which project content goes to a cloud provider.

Semantic project search

Projects, tasks, decisions, meetings and plan pins are indexed as vectors. Search works by meaning, not by string.

Assistant inside the workflow

An overlay on a keystroke, with conversation history and project context — instead of a separate chat window.

Vendor-neutral by design

Access runs through a neutral abstraction rather than a hard-wired provider. The model is interchangeable.

spec
Embedding dimension
768
Vector search
pgvector / HNSW
Data egress
none
Perspectives

Onetruth.Sixpointsofview.

Every participant works on the same data foundation, but nobody gets someone else's interface. The role determines navigation, permissions and cockpit.

Site supervision

Cockpit

An overarching view of quality, schedule, defects and acceptances — the coordinating role with the widest access.

  • Defect #214Facade L2, parapet crack
  • Acceptance shell L2QES supervision + client
  • Payment request 04€ 412,800.00
  • Electrical cost estimateno access
  • Plan revision CSection A–A, index C
  • Tender ventilationDeadline 28 Nov, 4 bids
  • visible
  • restricted
  • no access

The same six records — visible, restricted or locked depending on the role.

Platform modules

Whatisintheproducttoday.

Not statements of intent, but built modules with a data model, an interface and test coverage. The maturity level is shown on every module.

Site diary & documentationDaily entries, decisions, meetings and tasks on one shared data foundation. File names follow an enforced naming standard.Implemented
Plans, pins & defectsPlans as image or PDF, defects as located pins with photo evidence and markup. Via QR code and deep link the pin takes the tradesperson straight to the spot.Implemented
BIM & IFCIFC models in the 3D viewer. A defect pin can be linked to a specific building component; the viewer zooms to it on request.Implemented
Acceptance & signaturesAcceptances are signed with qualified signatures. The signature is the technical trigger for invoicing and escrow release.Implemented
Bill of quantities & invoicingLine items, progress and payment applications are connected. Quantities are checked against the bill of quantities.Implemented
E-invoicingXRechnung as well as ZUGFeRD and Factur-X in the EN 16931 profile, including reverse charge as the standard case in construction.Implemented
TenderingPublish a tender, receive bids across organisations, compare them and award the contract — which produces the assignment.Implemented
Marketplace & matchingSubcontractor profiles with trades, regions and certificates. Matching with reasoning, and reviews from completed jobs.Implemented
Escrow & payment releaseAgreements, milestones and state machine are built; the signed acceptance automatically sets the milestone to ready for release. Goes live only with a licensed partner.Pilot-ready
Local AI & copilotAssistant on a keyboard shortcut, semantic project search and document understanding — entirely on your own hardware.Implemented
Perspective cockpitOne data foundation, one focused view per role. Navigation and permissions follow the role, not the other way round.Implemented
Project healthDaily snapshots per project, trend history and an exportable report.Implemented
Network effect

Everyprojectmakesthesystemmorevaluable.

The client brings the general contractor, the contractor brings its subcontractors, they bring their suppliers. Every verified piece of work improves the data for risk, insurance and financing, and every round turns the wheel faster.

Round 1Work

Guiding principles

Thesiteproves.Thevaultpays.Theblockchainremembers.

BauProto owns the relationship with the construction project. Licensed banks and insurers provide the regulated infrastructure underneath. Partners are interchangeable building blocks under a stable workflow and data layer.

What we never do

No custody of client funds

Escrow is run exclusively by licensed banks.

No asset without an issuer

No value is created without verifiable authorisation by the registered issuer.

No master keys

Nobody gets keys that decrypt private data or move other people's value.

No speculation

BauProto issues no token and changes no money supply.

No claimed confidentiality

Confidentiality is promised only where it is implemented cryptographically and audited.

No operation without review

Independent security reviews before any productive use.

Trust boundaries

BauProto

Tenant isolation, row-level security, qualified signatures.

Vault validators

A compromised validator gains no access to other parties' wallets.

Issuer and bank

Responsible for the economic backing of every issued asset.

Public anchor

Its own proof-of-work consensus. A failed connector does not affect the blockchain.

The way there

Provefirst.Thenopenup.Thenscale.

Each stage builds the trust the next one needs and has a verifiable acceptance criterion. The order is not negotiable.

  1. Data ownership

    • BauProto in operation
    • Design partners on site
    • Penetration test and restore drill
    • E-invoicing (XRechnung)

    GateOperated and used

    Milestone: Beta with the first site-supervision office from Salzburg since October 2026

  2. Escrow pilot

    • Legal opinion on payment law
    • Partner bank runs escrow account
    • Signed event log
    • Vault: specification, state machine, BFT testnet

    GateRegulatory model decided

  3. Confidential and connected

    • Vault: confidential transfers
    • Independent cryptography audit
    • Further validators
    • Checkpoint anchoring

    GateExternal audit without critical findings

  4. Capital and risk

    • Factoring on verified work
    • Warranty insurance
    • Tokenised bank deposits in the vault

    GateReal transaction volume

Honest maturity

This page shows the target picture. BauProto Construction OS is implemented; the Financial OS with escrow milestones is pilot-ready but only switched on with a licensed partner. Nightfall Vault is planned: specification and prototype follow, confidential transfers only after an independent audit. Checkpoint anchoring is a later, separately specified extension.

The construction industry does not have a software problem. It has an infrastructure problem.

Husref Huremović

Founder

Salzburg, Austria

Background

Developed out of construction practice.

BauProto is not being designed at the drawing board of a software house, but out of daily work on the construction site. The demands on documentation, proof and settlement are not theoretical problems there — they determine whether a project works economically.

Contact

Request a conversation

BauProto is in development. For construction companies, site supervision offices, investors and potential partners, this is the right moment for a conversation.

Send an email
Email
husref.huremovic@bauproto.app
Location
Salzburg, Austria
Response time
Usually within 48 hours

Who this is for

  • Construction companies and site supervision offices interested in a pilot
  • Investors focused on infrastructure and vertical SaaS
  • Licensed financial and insurance institutions as potential partners
BauProto

Payment follows performance. Confidential. Provable.

Contact

Pilot-ready modules are technically implemented but not yet operating as a regulated service. Nightfall Vault and checkpoint anchoring describe a planned target picture. Not investment advice, not an offer of crypto-assets, no promise of regulated services.

© 2026 BauProto. All rights reserved.

ImprintPrivacy