Technology

Trust by design

Every record receives a unique digital fingerprint. Once recorded, authenticity can be independently verified without relying on any single organisation.

Trust architecture

Designed for verification — not speculation

Plain-language controls institutional reviewers care about. No crypto jargon required.

Off-chain storage, on-chain proof

Files and commercial detail stay in encrypted storage with role-gated access. The ledger stores only digests, enums, and timestamps — enough to verify integrity without publishing sensitive narratives.

Law-first, chain-second

Legal milestones and assignment steps complete in the portal first. Smart contracts record evidence hashes and gate transitions — they do not replace counsel or override facility documentation.

Independent verification

Auditors and investors download self-contained packs with documents, chain metadata, and a verifier script. No portal login required to reproduce integrity checks.

Segregated duties

Registrar, attestor, and compliance roles are separated. Governance timelocks delay privileged changes. Continuous smart contract tests guard production behaviour.

Independent verification

What auditors see on a public explorer

Institutional reviewers can open the transaction, confirm the document digest, and reconcile it to portal records — without logging in.

Illustrative example Sepolia testnet (sample)

Facility snapshot recorded on chain

Shows how an institutional reviewer would see a document anchor — doc type, digest, block time, and a link to the public explorer for independent verification.

Event
Document registered
Doc type
terms.facility_snapshot
Digest
0x9f3a8c21…d0f4a2
Block
8412903 · 2026-06-14 11:32 UTC
Contract
DocumentRegistry 0x742d…bEb0
Transaction
0x4a7f9e2b…0d9e8f

View on Sepolia Etherscan

Production modules

Built in code — mapped to live services

Production services and smart contracts mapped to the lending lifecycle — for technical diligence and investor review.

Origination & intake

From application to anchored submission snapshot

Borrowers submit through guided intake. AI extracts deal data for human review. Submission snapshots anchor under controlled doc types before credit work begins.

  • Application submission snapshots and declaration consent flows
  • Indicative terms and heads of terms PDF generation from live deal data
  • DocuSign and PandaDoc e-signature orchestration on the same deal record
application.submission.snapshot
terms.indicative_terms → PDF
e-sign: completed

Diligence workbench

Collateral truth with human confirmation gates

Land Registry OC1 parsing, Companies House charges, and valuation evidence flow into structured lanes. AI proposes field values — credit teams confirm before anchoring.

  • Title duplicate scan across active deals before funding
  • Security diligence JSON snapshots dual-anchored with per-file hashes
  • Drawdown readiness rollup: CPs, borrower compliance, and collateral lanes
legal.title.land_registry
duplicate scan: clear
bundle.diligence.v1 anchored

Document integrity

Every file versioned, fingerprinted, and attestable

Generated credit papers, drawdown notices, and completion statements follow enforced _vN versioning. Each edition can be registered and independently attested on-chain.

  • 80+ canonical BlockchainDocTypeEnum values from KYC to facility notices
  • Portfolio-wide duplicate byte detection across deals
  • Encrypt-then-pin CID envelopes for institutional privacy posture
DocumentRegistry.register + attest
doc_type: facility.drawdown.notice
version: _v3

Lifecycle & compliance

Governed transitions — not spreadsheet milestones

LoanStateMachine records origination through realisation. ComplianceRegistry gates wallet eligibility before material actions. GovernanceTimelock delays privileged changes.

  • Parallel diligence and legal stage FSM with workflow reconciliation
  • ComplianceRegistry: KYC, AML, risk tier, freeze, and investor category
  • 61+ automated smart contract tests in continuous verification
LoanStateMachine → FinancialClose
ComplianceRegistry: Verified
tests: 61 passing

Credit intelligence

Underwriting models on the same auditable deal record

Development finance metrics, SONIA-linked accrual, and sensitivity stress tests sit alongside documents your auditors can independently verify.

  • LTC, LTGDV, IRR, and cap-driven senior/subordinate facility optimiser
  • Scenario sensitivity with traffic-light risk scoring for committee packs
  • AI document Q&A grounded in uploaded PDFs — proposals, not auto-truth
LTC · LTGDV · SONIA accrual
sensitivity: scored
document Q&A: PDF-grounded

Privacy posture

Institutional-grade — not public PII on a ledger

Personal and commercial detail stays in encrypted off-chain storage with role-gated access. The chain carries digests, enums, and opaque identifiers — enough for independent verification without exposing sensitive narratives.

  • ComplianceRegistry stores KYC/AML posture — not identity documents on-chain
  • Encrypt-then-pin CID envelopes bind encrypted packages to anchors
  • Third-party verification packs for auditors without portal credentials
  • GovernanceTimelock and segregated registrar/attestor duties

See the verification layer in action