Platform — Ledger
Every movement,recorded
At the centre of the platform is one ledger: append-only, hash-linked and under dual control. It is designed to be the record of what actually happened — one nobody can edit, and anyone entitled to can verify.
01 — One ledger
One ledger. Every movement.
Accounts, payments, FX and controls in a single programmable system — visible to the cent, auditable to the event. This is the workspace being built on top of it.
DZD Operating · •• 4021
4 208 116,09
+1.8% · ARTS · ATCI
EUR Trade
€1 912 004,55
DZD Payroll
402 318,27
Latest activityLive
- Atlas Agro SPAATCI · Settled+4 850 000,00
- Hodna ManufacturingARTS · Settled−21 200 000,00
- Rheinwerk GmbHSWIFT · Pending−€250 000,00
- Sahel LogisticsBook · Settled+934 011,45
DZD → EUR
147.2040
Mid · locked 28s
Approvals1
Payroll · 18 422 040,00
Treasury /Overview
DZD Operating
•• 4021
4 208 116,09
ARTS · ATCI
EUR Trade
•• 8817
€1 912 004,55
SWIFT
DZD Payroll
•• 2203
402 318,27
ATCI
Latest activity
Live · streaming
| Counterparty | Ref | Rail | Amount | Status |
|---|---|---|---|---|
| Atlas Agro SPA | INV-20841 | ATCI | +4 850 000,00 | Settled |
| Hodna Manufacturing | PO-1174 | ARTS | −21 200 000,00 | Settled |
| Rheinwerk GmbH | FX-EUR-0392 | SWIFT | −€250 000,00 | Pending |
| Sahel Logistics | INV-20802 | Book | +934 011,45 | Settled |
| Pixely Payroll | RUN-2026-08 | ATCI | −18 422 040,00 | Needs approval |
| Casbah Data Co. | INV-20777 | ARTS | +2 790 460,60 | Settled |
FX — DZD → EUR
MID
147.2040
Approvals
1 openPayroll run 2026-08 · 18 422 040,00
Policy: payouts > 5M DZD
Event stream
evt_8fk2q1 ledger.credit.posted dzd_op +4 850 000,00
evt_8fk2q0 payment.settled arts confirmed
evt_8fk2pz fx.quote.locked eurdzd 147.2040
evt_8fk2py policy.approval.required payroll 2-of-3
evt_8fk2px payment.initiated swift 250 000,00
02 — How it is built
A record nobody can edit.
Three properties carry the weight, and the rest follow from them.
Append-only
Entries are added, never changed. A correction is a new entry that reverses the old one, so the mistake and its repair both stay on the record.
Hash-linked
Each entry carries the fingerprint of the one before it. Alter any entry and every link after it breaks — tampering is not hidden, it is evident.
Dual control
Movements above your policy's threshold wait for more than one approver. No single person moves money alone, and the approvals are written to the ledger too.
Every event announced
Each posting is published as an event — credit posted, approval required, payment settled — for the platform's services and for your own systems.
Attestations on the record
Identity results are written as signed attestations: who was proved, when, and by which checks — evidence a later decision can rely on.
Audit-ready by construction
Reporting reads from the ledger itself, not from a copy assembled afterwards. The audit trail is the record, not a summary of it.
03 — The life of an entry
Proposed, approved, written, proved.
How a movement is designed to become a line in the ledger — and why it can be trusted once it is there.
- 01
Propose
A payment, a payroll run or a transfer between accounts is proposed — by a person, a rule or an API call.
- 02
Approve
Policy decides who must agree. Above the threshold, a second hand is required before anything is written.
- 03
Post
The entry is appended and linked to the one before it. From here it can be reversed by a new entry, never edited.
- 04
Prove
Anyone entitled to can walk the chain and confirm it is whole — the auditor, the regulator, or your own finance team.
04 — Get in touch
Put iton the record
Talk to us about the ledger, the controls on it and how your own systems would read from it.