Trust
The evidence, before the pitch
A compliance officer visits this page before your CEO gets a second call. So it leads with verifiable identity, the custody arrangement, and exactly how compliance is enforced — not with narrative.
Who is the legal counterparty?
The operating entity is UnyKorn LLC, a Wyoming limited liability company, alongside the co-owned UNYKORN 7777 INC. Full registration identifiers — GLEIF LEI, D-U-N-S, ISO MIC, and EIN — with independent verification links are published on the legal entities page. Publishing these kills most of the “are you real” friction before it starts.
How is custody handled?
Non-custodially. Qualified custody is delegated to BitGo Bank & Trust N.A., an OCC-chartered trust company, under segregated multi-signature vaults with an m-of-n signer policy. The tenant holds their own backup key, so Unykorn software is never a sole custodian. Detail: custody architecture.
How is compliance enforced?
As a gate before value moves, in exactly one place. Every value movement passes a single AML / KYC / FATF Travel-Rule check before it executes: OFAC and sanctions screening, KYC/KYB verification-state checks, IVMS101 originator/beneficiary data exchange above the regulatory threshold, and rules-based transaction monitoring. On-chain, eligibility is enforced at the token boundary via ERC-3643. This is an engineering control layer; licensed compliance review is maintained alongside it.
What standards are implemented?
| Domain | Standard / Control |
|---|---|
| Security-token identity | ERC-3643 (T-REX), ONCHAINID |
| Sanctions / AML | OFAC screening, FATF Travel Rule (IVMS101) |
| Qualified custody | OCC-chartered trust delegation, m-of-n multi-sig |
| Oracle attestation | EIP-712 signed attestations, m-of-n aggregation |
| Federal counterparty | SAM.gov UEI / CAGE validation, exclusion screening |
Subprocessors and audit status
The current subprocessor list, security-audit status per contract, and compliance-program documentation are maintained on the security page. Attestation reports (e.g. SOC 2) are published there as they are completed. Where an item is in progress it is labeled as such rather than implied complete.