Learn · Certification · StoreFree for developers

Technical: bytes and encryption

The uploader encrypts the selected Private file before uploading its bytes to IPFS; Public upload instead sends unencrypted bytes.

VetKeys needs wallet sign-in, browser encryption support, and an authenticated identity; otherwise Private upload requires the passphrase before it can proceed.

IPFS holds the uploaded bytes, and the person's DocNFT mint records the file separately from that upload.

The phone can capture photo, audio, or video offline, and the builder shows later upload and mint results separately when the connection returns.

Technical: bytes and encryption

Four questions. Each answer is a sentence from this lesson.

Sign up on Learn before this certificate can be emailed.

Start the course
  1. What happens on the private byte path?

    What happens on the private byte path?
  2. Which credentials permit the encryption path?

    Which credentials permit the encryption path?
  3. How does the token relate to the bytes?

    How does the token relate to the bytes?
  4. How can the builder support a disconnected phone?

    How can the builder support a disconnected phone?