# 2076 Including Data Manually into VC Documents
Github Issues\
[https://github.com/hashgraph/guardian/issues/2076\
](https://github.com/hashgraph/guardian/issues/2076)1. Additional Data (Evidence Attachments)
The Additional Data feature extends the requestVcDocument block (and its addon variant) with an optional evidence attachments step. When enabled, the request wizard inserts an extra step between form submission and (optional) relayer account configuration, allowing users to attach text comments and/or files as evidence entries. The attached evidence is uploaded to IPFS, embedded into the Verifiable Credential as W3C-compliant evidence entries, and preserved through reassignment operations.
\
1.1. Configuration
1.1.1. Block Properties
Enable additional data – When checked, the request wizard shows an additional step for attaching evidence (text comments and/or files) before final submission. Optional. Defaults to false.
This property is available on both requestVcDocumentBlock and requestVcDocumentBlockAddon block configuration screens.
1.1.2. How It Works
When the Enable additional data option is turned on, the standard request wizard flow changes as follows:
Without Additional Data (default):
Fill Form → Submit
With Additional Data enabled:
Fill Form → 2. Add Evidence Attachments → Submit
With Additional Data + Relayer Account:
Fill Form → 2. Add Evidence Attachments → 3. Configure Relayer Account → Submit
\
1.2. Evidence Attachments Step
The evidence attachments step provides the following UI elements:
\
1.2.1. Text Comment
A text area where users can optionally enter a comment (up to 600 characters). This comment is stored as an evidence entry with dataType: "message".
1.2.2. File Attachments
Users can attach files by:
Clicking the Attach button to open a file picker (multiple file selection supported).
Dragging and dropping files onto the attachment area.
Each file is uploaded to IPFS in the background. While uploading, a loading indicator is displayed. Once uploaded, the IPFS CID is stored as an evidence entry with dataType: "file" and data: "ipfs\://\".
Files can be removed by clicking the close icon next to each file name.
Note: The submit/next button is disabled while any file upload is in progress.
1.2.3. Dialog Mode
The same evidence attachments step is also available when the request form is opened in dialog mode (popup). The behavior and UI are identical to the inline (page) mode.
1.3. Evidence in Verifiable Credentials
When additional data is provided, the evidence entries are embedded directly into the Verifiable Credential before signing:
Each evidence entry is added as a JSON-LD evidence object with type: \["Evidence"].
The EvidenceAttachments system schema context is included in the VC's @context array.
Evidence is preserved when a VC is re-signed through the Reassigning block.
Evidence Entry Structure
{
"type": \["Evidence"],
"dataType": "message",
"data": "User-entered text comment"
}
{
"type": \["Evidence"],
"dataType": "file",
"data": "ipfs\://QmExampleCID..."
}
1.4. Viewing Evidence
When viewing a document that contains structured evidence entries, the document viewer displays them in a user-friendly format:
Text comments are shown with a text icon and the message content.
File attachments are shown with a file icon and a clickable IPFS link.
If the evidence data does not match the structured format (e.g., legacy evidence), it falls back to displaying the raw JSON.
\
1.5. System Schema
A new system schema EvidenceAttachments has been added to support this feature. It defines the structure for evidence entries:
Field Type Required Description
dataType string Yes Type of evidence: "message" or "file"
data string Yes Content: text message or IPFS URI (ipfs\://...)
This schema is automatically registered during system initialization and included in policy imports/exports.
1.6. Sample Policy
A sample policy "iRec Policy 4 (Additional Data)" is included in the Methodology Library demonstrating the feature in action.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://guardian.hedera.com/docs/develop/guardian/standard-registry/guardian-3.6-features-and-enhancements/2076-including-data-manually-into-vc-documents.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.