The problem Trifecta | DataFi SDK solves
User involvement:
- User keeps custody of the Diffie-Hellman private key
- Edge device SDK hashes a ghost key used for data encryption/decryption
- Diffie-Hellman public key is published in the protocol's smart contract
- Permissionless blockchain used as the key exchange medium between parties, achieving end-to-end privacy even through public permissionless channels
Trifecta edge device SDK:
- Generates ECDH private key
- Fetches ECDH public key from the on-chain Trifecta KeyLedger
- Derives the ECDH secret
- Performs HMAC KDF on the secret
- Uses the hash to carry out AES encryption on the data
- Stores the data on IPFS
- Stores the IPFS hash and wallet address metadata on the Trifecta AccessLedger & Trifecta DataLedger
Infrastructure:
- Trifecta edge device SDK for dApp developers to build on top of
- Trifecta smart contract, which the SDK communicates with
- Edge device SDK
- Edge device cryptography layer
- EVM smart contract
Challenges I ran into