Unity Network
  • Unity Network
    • Introduction
    • Unity Network FL Architecture
    • Data Security
    • Case Study
      • Flashback Overview
      • Registration
      • Integration
      • Model Training
      • Objectives and Outcomes
  • Unity Network SDK
    • Key Features
    • Registration
    • Node Setup
    • SDK Integration
      • Wallet Module
      • Node Module
  • Permissions Management
    • User Permissions
  • Model Training
    • Organization registration
    • Model Training Requests
    • Secure Training and Updates
      • Model Training
        • Model Loading and Initialization
        • Data Loading
        • Training
      • Secure Transmission of Encrypted Updates
        • ECDH Key Exchange for Secure Encryption Key Generation
        • Encrypt and Transmit Model Updates
        • Secure Aggregation and Decryption at Central Server
        • Distribute Updated Model and Continue Training
      • Sharing Model Updates with the Model Owner and Verifying Authenticity of Training
        • Construct the Merkle Tree and Commit to the Merkle Root
        • Log Hashes of Accessed Dataset Chunks During Training
        • Transmission of Model Updates, Merkle Proofs, and Hash Log to the Model Owner
        • Verification by the Model Owner
  • Training rewards
    • Incentivization Process
Powered by GitBook
On this page
  1. Model Training
  2. Secure Training and Updates
  3. Sharing Model Updates with the Model Owner and Verifying Authenticity of Training

Log Hashes of Accessed Dataset Chunks During Training

  1. Log Hashes During Data Access:

    • During training, every time the model accesses a dataset chunk, the node logs the hash of that chunk.

    • This logging is done in real-time and saved as a secure log on chain that the model owner can review after training.

  2. Randomized Hash Sampling:

    • To reduce overhead, the model owner may specify randomized intervals for hash logging (e.g., every Nth data access). This still provides integrity verification without requiring constant logging.

  3. Secure Storage of the Hash Log:

    • The hash log is stored on chain, preventing tampering. After training, this log will be shared with the model owner for verification.

PreviousConstruct the Merkle Tree and Commit to the Merkle RootNextTransmission of Model Updates, Merkle Proofs, and Hash Log to the Model Owner

Last updated 5 months ago