IdentHash cryptographically binds sender and receiver identity to every on-chain transaction β without exposing personal data. Zero PII on-chain. Fully decentralized.
Current Travel Rule solutions share raw PII between VASPs via centralized servers β creating privacy risks, single points of failure, and regulatory liability.
Raw personal data transmitted between VASPs β breach risk, GDPR liability, no immutable audit trail. One leak exposes millions of users.
If the Travel Rule middleware goes down, compliant transfers stop entirely. No on-chain fallback. No business continuity.
RWA and STO transfers lack cryptographic proof that legal ownership actually changed hands on-chain. Regulatory risk is enormous.
IdentHash resolves Travel Rule compliance and RWA ownership proof simultaneously β on Polygon Mainnet, zero PII exposure, zero infrastructure overhead.
Sender & receiver identity hashed as PII_commitment β personal data never leaves the client device. Privacy preserved by design.
IdentHash permanently recorded on Polygon Mainnet. Tamper-proof. Immutable. Verifiable by regulators at any time.
VASPs call POST /api/record with a single API request. Zero infrastructure overhead. Integrate in minutes, not months.
Blockchain transaction hash = immutable compliance evidence. Acceptable to regulators globally. Pay-as-you-go pricing.
The diagrams above illustrate the core patented IdentHash logic in simplified form. Field mapping, validation rules, and API contracts can be customized for any exchange’s specific compliance workflow — contact us to discuss a tailored integration.
2027 marks simultaneous enforcement across three major jurisdictions. IdentHash is built for this exact moment.
Travel Rule mandatory for all Swiss VASPs. Sender and receiver identity must be cryptographically verifiable on-chain.
Legal basis: Anti-Money Laundering Ordinance of FINMA (GwV-FINMA), Art. 65 — requirements for the transmission of information on the originator and beneficiary in connection with virtual asset transfers.
What it requires: Swiss VASPs must collect and transmit originator and beneficiary information for virtual asset transfers, and verify the identity of the parties involved.
How IdentHash helps: Originator/beneficiary identity is bound to each transfer via an on-chain commitment hash, giving exchanges a verifiable, tamper-evident record to support FINMA compliance and audit requests. The structure shown above is the core patented logic — field mapping and validation can be adapted to a Swiss exchange’s specific workflow.
RWA tokenization and STO ownership transfer require on-chain identity binding under Korean financial regulation.
Legal basis: Amended Act on Electronic Registration of Stocks, Bonds, etc., together with related Capital Markets Act and Real-Name Financial Transactions Act requirements.
What it requires: Ownership transfer of tokenized real-world assets and security token offerings must maintain verifiable identity binding between wallet, security ID, and the underlying holder.
How IdentHash helps: The IdentHash structure binds wallet, securities ID, and a PII commitment hash in a single on-chain record — without ever exposing raw personal data. Field definitions can be customized to match a given exchange’s identity verification process.
EU-wide Travel Rule enforcement across all crypto-asset service providers. No exemptions for DeFi-adjacent services.
Legal basis: EU Anti-Money Laundering Regulation (AMLR), applying Travel Rule obligations consistently across all member states to crypto-asset service providers.
What it requires: CASPs must collect, verify, and transmit originator and beneficiary information for crypto-asset transfers, with no exemption for DeFi-adjacent services.
How IdentHash helps: A single on-chain record per transfer gives CASPs a uniform compliance artifact usable across any EU member state. Integration can be tailored to each provider’s existing compliance stack.
140+ countries implementing FATF Recommendation 16. Exchanges without Travel Rule compliance face delisting and sanctions risk.
Legal basis: FATF Recommendation 16, extended to virtual assets and VASPs — the source of the "Travel Rule" name.
What it requires: VASPs must collect and share required originator/beneficiary data with counterparty VASPs and make it available to authorities upon request.
How IdentHash helps: A FATF-aligned, blockchain-anchored record gives any exchange a baseline, internationally recognizable compliance artifact — with implementation details adaptable per jurisdiction and exchange.
IdentHash is protected by a pending Korean patent portfolio and an applied TTA Korean standard β establishing prior art across the full RWA and Travel Rule lifecycle.
46 claims covering the IdentHash generation device, PII_commitment binding, S_bundle / R_bundle multi-layer architecture. PCT filing in progress.
PATENT PENDING Β· PCT FILINGReal-time and periodic on-chain disclosure of RWA asset status. Covers BlackRock BUIDL-type periodic disclosure systems globally.
PATENT PENDING Β· PCT FILEDIdentHash submitted as a TTA (Telecommunications Technology Association) Korean standard proposal. Currently under review.
STANDARD APPLIEDIdentHash TRP v2.2 deployed and operational. AML Compliant. Real transactions recorded on-chain today. Not a prototype.
β LIVE Β· MAINNETIdentHash provides the API infrastructure for RWA issuers and institutional counterparties to execute, record, and verify contracts on-chain β replacing centralized document platforms with blockchain-native proof.
Real estate, bonds, commodities, and tokenized assets. Both parties sign digitally β IdentHash hashes the contract and records it on Polygon Mainnet instantly.
Fund managers, banks, and family offices subscribe to RWA token offerings via a legally binding on-chain contract β no intermediary required.
When RWA tokens change hands, the transfer agreement is hashed with both parties' identity proofs and permanently recorded β fulfilling Travel Rule and ownership proof simultaneously.
Issuer-to-exchange listing agreements, custody arrangements, and regulatory disclosures β all executed through a single API call and stored immutably on-chain.
/api/contract with party identities + contract dataUnlike DocuSign β your contract lives on the blockchain. No central server. No single point of failure. No third-party trust required.
Try Contract Now β Request API AccessTry the live IdentHash TRP v2.2 demo β real Polygon Mainnet transactions, real PII_commitment hashes, real compliance records.
Anyone can now verify a contract's identity, contract, and document hashes directly against Polygon Mainnet β straight from the browser, with zero trust in our servers.
Verify a Contract Now βRequest an API Key or partnership discussion.
Zero upfront cost. Pay-as-you-go. Integration in minutes.