Data Storage

​

Encryption architecture

​

Data categories

• Private Instance Data: Customer records, internal documents, compliance files - encrypted with your instance key, stored in Trusset infrastructure, inaccessible to Trusset.
• Public Data: Token metadata, pricing information, public documents - encrypted but marked for controlled sharing via REST endpoints when needed.
• On-Chain Data: Smart contract state, transaction history, public blockchain records - stored on blockchain, publicly readable by design.

​

Manage encryption keys

​

On-chain data strategy

• Your instance’s own ERC-3643 register: the investor country, which the register stores by design as its ISO 3166-1 numeric code, and a residency claim hash on the investor’s ONCHAINID, the keccak256 hash of the three-letter country code, which anyone can match by hashing each code. Both are written under your signature.
• The Trusset ID Register, used by an instance without a register of its own: the wallet’s investor type (its MiFID classification as a number from 0 to 3), a hash of the verification, the wallet of the verifier that wrote it, the verification time and the expiry times, and whether the record is active or frozen. It also keeps every claim written for the wallet (KYC, AML, accreditation, residency, citizenship, tax residency, sanctions check or PEP check): the claim type, a hash of its data, the wallet that issued it, when it was issued, when it expires and whether it is active. Anyone can list them with getClaims. A claim entered as a short value, such as a country code or a yes or no answer, is hashed without a salt, so it can be matched by hashing each possible value. See Investor Profiles.

• Zero-Knowledge Proofs: Users prove identity attributes (age, accreditation, citizenship) without revealing underlying data.
• IPFS Storage: Documents, metadata, and public files store on IPFS with content addressing. Only document hashes record on-chain, linking to off-chain content.
• Minimal On-Chain State: Smart contracts only store essential information - token balances, ownership records, configuration parameters. Everything else lives off-chain.

​

Public data endpoints (coming soon)

// POST https://api.trusset.org/instance/data/configure

await fetch('https://api.trusset.org/instance/data/configure', {
  method: 'POST',
  body: JSON.stringify({
    publicCategories: [
      'token_metadata',      // Allow external reads of token info
      'pricing_data',        // Share price feeds with partners
      'compliance_reports'   // Enable auditor access
    ],
    accessControls: {
      token_metadata: ['public'],           // No authentication required
      pricing_data: ['api_key'],           // Require API key
      compliance_reports: ['approved_auditors'] // Whitelist specific addresses
    }
  })
});