Nedbank
Bank-grade blockchain intelligence, deployed on-premise
LedgerCore deployed inside the bank’s own environment to support analytics, compliance monitoring and due diligence under institutional control.
Named engagement. Client detail on this page is limited to what Sixpence publishes about the relationship.
- Client
- Nedbank
- Sector
- Banking
- Capability
- On-premise blockchain intelligence
- Platform
- LedgerCore
- Updated
The mandate
Give a bank the ability to analyse digital-asset activity relevant to its own customers and counterparties, inside its own environment, under its own controls.
The situation
A bank looking at digital-asset exposure faces a problem that hosted analytics tools do not solve. The questions it needs to ask are about its own customers, which means the query itself is sensitive. Sending a customer identifier or a counterparty address to a third-party platform is a disclosure, and it is often the disclosure a bank is least able to make.
There is a second problem that matters more over time. Analysis used in a compliance decision or a due diligence conclusion needs to be reproducible later. A hosted platform whose datasets and heuristics change outside the bank’s control cannot support that, because the answer given last quarter may not be the answer the platform gives today, and the bank has no record of why.
What was built
- 01
On-premise deployment
The analytics capability deployed inside the bank’s environment, so queries about customers and counterparties never leave the institutional boundary.
- 02
Compliance monitoring
Screening and monitoring against the bank’s own risk appetite and control framework rather than a vendor default, with results landing in the systems the compliance function already uses.
- 03
Due diligence workflow
Counterparty assessment producing a documented, reproducible conclusion with the confidence of each attribution recorded alongside it.
- 04
Reproducible analysis
Pinned data snapshots and recorded query parameters, so a conclusion reached months ago can be reconstructed exactly.
How it was approached
Deployment happened in the bank’s estate from the beginning rather than being built elsewhere and migrated. That is a deliberate discipline: sandbox environments have permissive networking, borrowed credentials and no change control, so every governance assumption validated there is validated against something that does not resemble the destination.
The integration work that produced the most value was unglamorous. Resolving on-chain activity against the bank’s existing counterparty records is an identity problem, and identity is where analytical ambition usually meets its limit. Getting that join right, with confidence recorded rather than implied, is what let the output be used in decisions rather than admired in reviews.
Outcome
- Digital-asset analysis performed without customer or counterparty identifiers leaving the bank’s environment.
- Compliance monitoring aligned to the institution’s own framework rather than to a vendor default.
- Due diligence conclusions that can be reproduced and explained after the fact.
- Analytical capability operating under the bank’s existing access, change and audit controls.
Capability transferred
- Bank staff operating the capability without vendor involvement in routine work.
- Runbooks held and executed by the bank’s own engineering function.
- Attribution and confidence methodology documented for the compliance and risk functions.
Methods
- On-premise deployment
- Address clustering and attribution
- Counterparty identity resolution
- Pinned snapshots for reproducibility