Burhan: every maintenance pound backed by mathematical proof
How Ouda Developments uses blockchain technology to document maintenance deposits and expenses, so every owner can verify them personally without having to trust anyone. The money stays in an Egyptian bank, in Egyptian pounds.
★The idea in one minute
Owners pay a large maintenance deposit, then have no independent way to see where it went. “Burhan” means proof in Arabic, and it is the name of the system that changes this: every pound entering or leaving the maintenance account becomes a sealed digital entry that cannot be edited, deleted or back-dated without being exposed immediately.
Money stays in the bank
The deposit is held by a licensed Egyptian bank in Egyptian pounds. No crypto, no owner wallets.
Fingerprint on the network
Once a day, one fingerprint of the whole ledger is sealed on a public blockchain that Ouda does not control.
Owners verify for themselves
With one tap, the owner’s phone recomputes the fingerprint and compares it with the sealed one: “Match” or “No match”.
Expense or depositinvoice, amount, category, approvals
FingerprintSHA-256 of the entry
Chaineach entry carries the previous one
Merkle treethe day’s entries in one root
Public daily seal32 bytes on a public network
Owner checkfrom the phone, no middleman
1The problem: trusting the maintenance deposit
The maintenance deposit is a percentage of the unit price that every owner pays, and it is managed for many years after handover. Today the only source of trust is the word of whoever manages it.
To show the scale, here is a hypothetical example with simple numbers (not the figures of any actual project):
| Item (hypothetical example) | Value |
|---|---|
| Unit price | EGP 1,000,000 |
| Maintenance deposit | 8% = EGP 80,000 per unit |
| Number of units | 100 units |
| Total deposit | EGP 8,000,000 |
| Operation and maintenance | Bravo Facility Management |
Can’t see
The books stay inside the company; at best an annual summary arrives.
Can’t verify
Even when shown the ledger, the owner can’t tell whether it is last month’s ledger or an edited one.
Audits are a snapshot
An auditor sees what is presented on audit day, not what happened all year.
2The trust model: money in the bank, proof on the network
The system separates where the money is from where the evidence is. The money never moves on the blockchain, and the evidence never stays in the company’s hands alone.
| Party | What it holds | Role |
|---|---|---|
| Licensed Egyptian bank | The deposit in EGP, a separate account per project | The bank statement is the final reference for the balance |
| Ouda ledger | Every movement with its documents and approvals | Records each event as it happens |
| Public network | One fingerprint per day (32 bytes) | A dated witness Ouda does not control |
| Owners and auditors | The verification tool | Compare the ledger with the seal and the bank statement |
3The entry: the system’s building block
Every financial movement is recorded as a single “entry” with fixed fields. There are four entry types: deposit, investment return, maintenance expense and correction.
| Field | Content | Example |
|---|---|---|
| Sequence number n | Increases by one per entry, no gaps | 000412 |
| Project | Project code | CANARY |
| Type | Deposit / return / expense / correction | Expense |
| Amount | In piasters (whole number) | 4,850,000 piasters = EGP 48,500 |
| Category | Code from a fixed chart of categories | Elevators |
| Supplier | Code from the supplier register | V-017 |
| Document fingerprint | H(invoice PDF) | 9f2c… |
| Bank reference | Transaction number on the statement | TRX-88213 |
| Approvals | Digital signatures (section 7) | 2 of 3 |
| Previous fingerprint | h(n−1) | 41ab… |
4The digital fingerprint (hash)
A mathematical function that turns any text or file, whatever its size, into a fixed-length 256-bit number. We use SHA-256, the same function Bitcoin is built on, and a published standard (FIPS 180-4).
A real example computed with SHA-256. The two entries differ by one piaster, and the fingerprints are completely different:
→ 197c1e08750ff974875cd1aeb55633553b69bf630945b4a21fb1e4fda65aa0f4
→ 8e50545f6a87d83ef3e34eccea48b930f8f3cf747c310d544dc244378c478123
Deterministic
The same input always gives the same output.
Highly sensitive
Changing a single piaster changes almost the whole fingerprint.
One-way
The entry can’t be recovered from its fingerprint, and no other entry can be forged with the same one.
5The chain of entries: nothing deleted, nothing slipped in
Each entry carries the fingerprint of the one before it, so the entries link together like the links of a chain.
h=7c21…h=41ab…h=197c…h=e05d…| Tampering attempt | Result |
|---|---|
| Editing an old entry | Exposed its fingerprint and every later one change |
| Deleting an entry | Exposed a gap in the sequence numbers and a broken chain |
| Inserting a back-dated entry | Exposed there is no slot for it without recomputing everything after |
6Merkle tree and the daily seal on a public network
At the end of each day, the fingerprints of that day’s entries are combined in a “Merkle tree”, a method invented by Ralph Merkle and used by Bitcoin itself.
Why a tree and not a list? Because an owner can prove their entry is inside the day with a very short “path”, without downloading the other entries:
| Entries | Fingerprints in the path | Proof size |
|---|---|---|
| 1,000 | 10 | 320 bytes |
| 10,000 | 14 | 448 bytes |
| 1,000,000 | 20 | 640 bytes |
7Approvals: no expense on one person’s signature
Every expense needs approvals from more than one party, and each approval is a digital signature with its owner’s private key (Ed25519, RFC 8032).
| Expense amount | Approvals | Signers |
|---|---|---|
| Below a small threshold (to be set) | 2 of 3 | Bravo operations manager, Ouda finance, owners’ representative |
| Above the small threshold | 3 of 3 | All three |
| Annual or exceptional contracts | 3 of 3 + prior notice | All three |
8Balance equations and bank reconciliation
The ledger computes the balance at any moment from the entries alone, then it is compared with the bank statement every month.
Illustrative example: in the hypothetical example (100 units, total deposit EGP 8 million), assuming an annual return r for illustration only:
| Assumed return r | Annual return | Per unit per month |
|---|---|---|
| 10% | EGP 800,000 | about EGP 667 |
| 15% | EGP 1,200,000 | EGP 1,000 |
9How an owner verifies
Owners don’t need to understand the equations; they work for them in the background. From the community app or the owners’ portal:
Open the expenseamount, category, supplier, invoice, approvals
Tap “Verify”the phone computes the fingerprint itself
Rebuild the rootfrom the Merkle path (10 to 20 fingerprints)
Read the sealdirectly from the public network
“Match”or “No match”
10Privacy
No personal data ever reaches the public network. What is published there is one irreversible fingerprint per day.
Pseudonyms
Owners appear as codes, not names or unit numbers. Each owner sees their own deposits; everyone sees expenses.
Salted fingerprints
Sensitive data is sealed together with a secret random number (salt), so it can’t be guessed.
Invoices stay with us
The file stays on Ouda’s servers and is shown to owners; only its fingerprint enters the chain.
11Security math and the system’s limits
To change an entry while the sealed fingerprint stays valid, a forger must find a different entry with the very same fingerprint.
What the system protects against, and what it doesn’t. Overpromising about technology destroys the very trust we want to build, so here are the limits plainly:
| Risk | Does the system stop it? | How |
|---|---|---|
| Editing an amount after recording | Fully prevented | The sealed fingerprint no longer matches |
| Deleting an expense or deposit | Fully prevented | Gap in the sequence and a broken chain |
| Back-dated entry | Fully prevented | The daily seal on the public network |
| Expense approved by one person | Prevented | Minimum signature threshold |
| Gap between ledger and bank | Exposed monthly | Published reconciliation rule |
| Inflated invoice from the start | Exposed to owners | Visible invoice, external auditor, price comparison |
| Collusion of all signers | Not prevented | An owners’ representative among signers reduces the risk |
12Cost
The network cost is negligible, because we write only one transaction per project per day, however many entries there are.
The real cost is in software, operations and audit, to be set with the technology partner. Network fees are paid by an external technology partner that invoices Ouda in Egyptian pounds, so neither Ouda nor the owners hold any cryptocurrency. This structure is subject to counsel’s approval.
13Governance and legal compliance
The system will not go live before a written legal opinion from an Egyptian law firm specialised in banking and fintech.
- Does recording fingerprints only on a public network fall outside crypto-asset trading under Central Bank Law No. 194 of 2020?
- Is paying network fees through a technology partner invoicing in EGP sound?
- What wording is allowed in announcements, and may the network be named?
- Alignment with Personal Data Protection Law No. 151 of 2020.
- Is prior approval from any regulator required?
- Clauses needed in the buyer contract and the owners’ association bylaws.
| Party | Role |
|---|---|
| Ouda Developments | System owner, funds it, member of the approvals |
| Bravo Facility Management | Operator: records expenses and signs them |
| Owners’ association / representative | Independent signer, approves the annual budget |
| Egyptian bank | Holds the funds; its statement is the final reference |
| External auditor | Annual audit; its report is sealed in the ledger |
| Technology partner (to be selected) | Builds the system and pays network fees |
14Implementation plan
The system is at the design stage today and will not record real money before the second gate: a written legal opinion and an independent security review.
① Design — now
- Whitepaper 1.0
- Chart of categories
- Approval thresholds
② Prototype
- Test data only
- Open verification tool
- Trial with Bravo
③ First operation
- First project handed over
- Real money
- Owners’ app
④ Rollout
- All group projects
- Annual external audit
- Public report to owners
?Owners’ FAQ
Will my money be turned into cryptocurrency?
No. The deposit stays in an Egyptian bank in Egyptian pounds; the public network only receives a digital fingerprint.
Do I need a wallet or to understand blockchain?
No. Verification is one tap in the owners’ app.
Will my name or unit number be visible online?
No. No personal data leaves the ledger, and owners appear as pseudonymous codes.
If an entry is wrong, is it deleted?
No. A new correction entry is added that everyone can see, and the original entry stays.
Is the system live now?
It is at the design stage and will not record real money before the legal opinion and the independent security review.
What is visible is hard to cheat
Burhan doesn’t make fraud impossible, but it makes it visible, permanent and exposed. A developer’s responsibility doesn’t end at key handover, and this system makes it measurable.
References
- S. Nakamoto, “Bitcoin: A Peer-to-Peer Electronic Cash System”, 2008.
- S. Haber, W. S. Stornetta, “How to Time-Stamp a Digital Document”, Journal of Cryptology, 1991.
- R. C. Merkle, “A Digital Signature Based on a Conventional Encryption Function”, CRYPTO 1987.
- NIST, FIPS 180-4: Secure Hash Standard (SHA-256), 2015.
- IETF, RFC 8032: Edwards-Curve Digital Signature Algorithm (Ed25519), 2017.
- IETF, RFC 6962: Certificate Transparency, 2013.
