Metadata & Labels
Metadata makes a Private Multisig easier to recognize and manage. It does not grant access or change on-chain authority.
Vault metadata
Section titled “Vault metadata”A vault may include:
- A name
- A short description
- An image
Keep names and descriptions concise. Do not place secrets, recovery phrases, private keys, or sensitive member information in metadata.
Member labels
Section titled “Member labels”Member labels are private, human-readable names shown to authorized vault members when locally available.
FounderTreasury managerOperations signerLabels help members understand roles, but they are convenience metadata only.
Metadata and permissions
Section titled “Metadata and permissions”| Item | Purpose | Grants authority? |
|---|---|---|
| Vault name or description | Identifies the vault | No |
| Member label | Describes a member’s role | No |
| Vault membership | Identifies an authorized participant | Yes |
| Approval threshold | Sets how many approvals are required | Yes |
Access and signing authority come from the vault’s membership and authorization records. Changing a label never adds a member, removes a member, or changes the approval threshold.
Privacy
Section titled “Privacy”Treat all metadata as potentially sensitive. Only add information that other authorized vault members need, and verify the current app behavior before assuming any field is private.