Security & Trust Center

Don't take our word for it. Check the proof.

Every document sealed on TradeProto is fingerprinted and recorded on a public blockchain. Drop in a sealed file and see, in seconds, whether it matches the record exactly.

  • 01Your file never leaves your deviceThe fingerprint (SHA-256) is computed in your browser. Only that 64-character code is sent.
  • 02One changed byte, a different fingerprintIf anyone has altered the document, even by a comma, it will not match.
  • 03Checkable without usEvery match links to the public on-chain record on Etherscan.
Dragon Seal verifierapi.tradeproto.ai
OR PASTE A FINGERPRINT
Nothing is uploaded or stored. The check is a read-only lookup by fingerprint.
    Status board

    Every layer, and where it stands today.

    We show what is live, what is on testnet, what is being built, and what is not in place yet. If a layer isn't live, we say so.

    Live In productionTestnet Running on a test networkIn development Being builtPending Action scheduledNot yet Not in place

    How proofs work

    From document to public record, in four steps.

    The record proves a document existed in an exact form at a point in time, and hasn't changed since. It doesn't reveal what the document says.

    01

    Fingerprint

    The document is reduced to a SHA-256 fingerprint. The same file always gives the same code; any change gives a different one.

    sha256(file) → 3f9a…c21e
    02

    Chain and sign

    Each event is linked to the one before it and signed, so nothing can be removed or reordered without breaking the chain.

    chain = sha256(prev ‖ leaf)
    03

    Anchor daily

    A single Merkle root covering the day's events is written to Ethereum. One transaction proves thousands of records.

    AuditRoot.anchor(root)
    04

    Verify anytime

    Anyone can recompute the fingerprint and check it against the on-chain record, with or without TradeProto.

    GET /api/verify/:sha
    What it proves

    Integrity and time

    The document is exactly the one that was sealed, and it existed when the record was written.

    What it doesn't prove

    That the contents are true

    A seal shows a document hasn't changed. Whether its contents are correct is confirmed by the qualified party who issued or inspected it.

    What stays private

    The document itself

    Only fingerprints go on-chain. Personal data and document contents are never published.

    Contract registry

    Every deployed contract, with its address and who controls it.

    ContractNetworkPurposeAddressAdmin

    Verify any address on Etherscan before relying on it. TradeProto will never ask you to send funds to a contract address.

    Keys & custody

    No single key controls the system. No one at TradeProto holds your asset.

    Administration requires two of three signers

    Contract administration sits behind a multi-signature Safe. Any change needs two independent signers, each on their own device.

    Signer 1
    Signer 2
    Signer 3
    →
    2 of 3 to act
    • No master key. The platform has no key that can decrypt client documents or sign on a client's behalf.
    • Operational keys are limited. On the anchor contract, the operational key can only record fingerprints. Ownership of every mainnet contract sits with the Safe, so no operational key can change it.

    Assets and cash stay with regulated institutions

    • Cash stays in bank accounts, pledged under control agreements where needed.
    • Securities and metals stay with custodians and vaults, who attest to holdings.
    • Goods are held under bills of lading and warehouse receipts, verified with the issuer.

    What TradeProto never does

    • Hold client funds or take custody of client assets
    • Accept PDFs or screenshots as proof of funds; confirmation is bank-to-bank only
    • Ask you to sign a transaction or pay a fee to receive funds
    • Take instructions from anyone who can't prove written authority to act for the principal
    Compliance posture

    Who can participate, and how they are checked.

    In place

    • KYC/KYB before any step. Identity, sanctions and beneficial-ownership checks on every counterparty.
    • Identity on-chain, data off-chain. A verified status is recorded as an on-chain claim; personal data is not published.
    • Permissioned tokens. ERC-3643 checks the holder's claim on every transfer.
    • Tamper-evident audit trail. Compliance events are chained, signed and anchored.

    Not yet in place

    • Independent smart-contract audit. Planned before any instrument is offered.
    • SOC 2 report. Readiness work in progress; no report issued.
    • Offerings. No instrument is currently offered. Any offering will be made under Rule 506(c) of Regulation D, only to accredited investors whose status has been verified, after counsel review.
    • Jurisdictions beyond the United States. Added only after local counsel review.
    Incident response

    If something goes wrong, here is what happens.

    Detect

    Chain integrity is re-verified end to end; any broken link or signature mismatch raises an alert.

    Contain

    Affected flows are paused. A pause cannot move or seize assets; it only stops new actions.

    Notify

    Affected counterparties are told what happened, what is affected and what to do.

    Publish

    A written post-incident report, with the on-chain evidence, is posted here.

    Response targets will be published with the first audited release.

    Report an issue

    Found a vulnerability? Tell us first.

    Email the details and steps to reproduce. We acknowledge reports promptly, keep you informed, and credit researchers who report responsibly. Please don't access data that isn't yours or disrupt service while testing.

    Security contact
    hello@tradeproto.ai

    Use subject line "Security report". A bug bounty programme will be announced with the first audit.