Blockchain Lab Ops
TrustOps
TrustOps is a case file for business verification: profile, ownership notes, a human decision, and a status a partner is allowed to see. The documents stay in a private store. They are not written to a public chain.
Not sold as kyb blockchain platform.
Synthetic businesses. Evidence stays hidden. No real customer records.
Who it is for
Fintechs, B2B marketplaces, and lenders that repeat the same evidence chase for every partner.
The workflow, before and in the demo
Before
- Documents arrive by email and sit with one analyst.
- Ownership is unclear, and two reviewers reach two decisions.
- A partner asks for the same pack again.
- Nothing records when the check should be repeated.
In the demo
- A business profile and an ownership note.
- Evidence described, not uploaded. The demo has no real documents.
- A review queue and a decision: approve, reject, or ask again.
- A status a verifier can see, without the hidden file.
Modules
- Organisation profile
- Ownership note
- Evidence described and redacted
- Case queue and human review
- Decision log
- Status a relying party can check
- Reverification reminder
- Role permissions
What would integrate later
- A private evidence store the buyer controls. This page does not provide one.
- Source checks, if any, are chosen later. A connector is not a certificate.
- A partner should receive a status, not a copy of the passport scan.
Controls, and the limit on them
- The verified-business demo hides evidence from the verifier. There is no document upload.
- Public-chain storage of identity or KYB files is refused.
- A completed demo case is not an AML or KYC certificate.
Commercial shape
If a pilot is later agreed, the shape is a case-workflow fee. No price on this page is a quotation.
Fit scan
Exploring whether the workflow is real
An onboarding map and a clear no: documents do not go on a public chain.
Illustrative range if a team is later free: 1–2 weeks. Not a delivery promise.
Working demo
Needs something colleagues can click
The verified-business demo: synthetic onboarding, review, and a verifier who cannot see the file.
The synthetic demo is already on this site. A private walkthrough is not scheduled here. Not a delivery promise.
Pilot scope
Ready to discuss a limited pilot, with counsel
A written case model and role matrix. Not a regulated onboarding programme.
Illustrative range only after counsel and a provider are chosen: 6–12 weeks. Not a delivery promise.
Integration design
A provider or system of record is already chosen
Where a source check would be called, and what it is forbidden to return.
Illustrative range for a later pilot: 3–6 months. Not a delivery promise.
Managed design
A pilot exists and someone must keep it current
Rule changes and reverification after a pilot exists. Not a compliance retainer.
Monthly, only after a pilot exists. Not a delivery promise.
A pattern, not a customer
Pattern, not a client: a platform onboards businesses and sends the same evidence pack to every partner. No company is named because none is claimed.
Questions worth answering first
- Where do the documents sit today, and who can open them?
- What decision must a partner be able to repeat without the file?
- What would be unacceptable to write on a public chain?
- When does a check expire?
Adjacent lines
What this line will not do
- Not regulated custody. Blockchain Lab does not hold client assets.
- Not payment execution. A rail, when one is used, is operated by a provider the buyer and its counsel select.
- Not legal advice.
- Not financial promotion and not an offer.
- Not an AML or KYC certificate. A demo case file is not a compliance opinion.
- Not a statement of returns. Return: Not shown.
- Not a production security clearance. No audit is claimed.
- Not a new chain by default.
- Demos use synthetic data. No real funds, wallets, private keys, or customer records.
- Business documents do not go on a public chain.
Illustrative commercial design. Not legal advice, not an offer, and not a delivery promise.