---
# System prepended metadata

title: Options regarding sharing a ProofMode-enhanced media

---

# Options regarding sharing a ProofMode-enhanced media

In this situation:
    - I have captured a photograph through Custom Signal Build
    - ProofMode proofs were generated (location, device ID, etc.)
    - I have selected the contact(s) with whom I want to share this rich media.

**What, precisely, should go to the Contact(s)?**

Candidates to be included are:  
    - Some text as part of the message (the *Message*),
    - The photograph itself (the *Photo*),
    - The ZIP file of ProofMode proofs (the *Proofs ZIP*),
    - The link to the MobileCoin ledger notarizing the capture (the *MobileCoin registration link*).

Something to keep in mind: The person-to-person workflow includes the idea that as the receiver of such a bundle, we will have *some visual feedback* about its qualities (think green check marks or locks), or show some of the proofs. 
To this effect, having the ZIP file in a single, isolated message might (?) make it easier to de-serialise and pull data out of?

**1. Send, in one go, all assets?**  
    Well-formatted string containing Message + Registration link
    Plus two attachments: the Photo + a ZIP file

**2. Send (Message + Photo) together, then ZIP, then Registration**  
    Feels quite natural to have Message and Photo together,
    But might be costly to have further steps "taking over" your Signal,
    engineering-wise, changes-wise, and UX-wise.

**3. ???**  
    what did i miss

