The Standard

Identity Information:

• Name: Full name or alias of the identity.
• Description: Brief description of the identity.
• Image: Profile image stored on Arweave.
• Links: Website or social media URLs.
• Tags: Keywords associated with the identity.
• Artist-specific Information:
• Date of birth: Date of birth, date of death (if applicable), and location
• RepresentedBy: Array of gallery/institution identity IDs representing the artist
• Gallery/Institution-specific Information:
• Physical addresses: Location information
• RepresentedArtists: Array of artist identity IDs represented by the gallery/institution

ART Fields:

1. Artist Identity ID: The unique identifier linking to the artist's identity in the Identity Contract.
2. Title: The name of the artwork.
3. Description: A detailed description of the artwork, its context, and significance.
4. Year of Creation: The year the artwork was completed.
5. Medium: Materials used to create the artwork (e.g., "oil on canvas," "bronze sculpture").
6. Dimensions: Size of the artwork, listed as height x width x depth (in cm or inches).
7. Edition: If the artwork is part of an edition, include the edition number and total editions (e.g., "1/10").
8. Series: A label used to group artworks that belong to the same thematic or conceptual body of work. This allows artists to document and organize pieces that are part of a unified vision, making it easier for collectors and institutions to understand the context of each artwork within a larger narrative.
9. Catalogue Inventory: [REMOVED - Catalogue Inventory details should be recorded in the Note field to maintain consistency and clarity.]
10. Image: A high-resolution image or scan of the artwork stored on Arweave.
11. Sales Information: [REMOVED - Sales information will be securely stored on-chain, tracked through verifiable events.]
12. Certification Method: [REMOVED - The certification method is clearly recorded as the ART Stamp, providing a consistent and trusted way to authenticate the physical artwork.]
13. Exhibition History: JSON string containing an array of exhibitions with name, date, and location.
14. Condition Reports: JSON string containing an array of reports with date and description of the artwork's condition.
15. Artist Statement: [REMOVED - Artist statements are best included in the Note field for added context and personal insight.]
16. Bibliography: JSON string containing an array of references with title, author, and page.
17. Keywords or Tags: An array of themes, styles, or movements related to the artwork (e.g., "surrealism," "landscape").
18. Location / Collection: JSON string containing location and collection information where the artwork resides.
19. Status: [REMOVED - Status will be dynamically determined based on predefined rules—for example, automatically reflecting if an artwork is listed for sale on a marketplace or is burned.]
20. Note: A flexible field for additional remarks, context, or annotations related to the artwork. This could include restoration notes, collector insights, special dedications, artist statements, or any other relevant information that does not fit into the predefined fields.
21. Royalties: Percentage of resale royalties set by the artist (in basis points, e.g., 1000 = 10%).

Full Admin Role [TEMPORARY-DEVELOPMENT PHASES ONLY]

The most powerful role in the system with system-wide administrative capabilities.

Powers:

• Identity Contract:
  • Grant and revoke roles to any identity
  • Assign and remove custodians for any identity
  • Authorize contract upgrades
• ArtContract:
  • Set the Identity contract reference
  • Mint NFTs in any contract
  • Update metadata for any NFT
  • Set royalties for any NFT
  • Grant roles to other identities
  • Assign and remove partial editors
  • Transfer NFTs between accounts (even without owner approval)
  • Authorize contract upgrades

How to Assign:

On the Identity contract

function grantRole(bytes32 ArcConstants.FULL_ADMIN_ROLE, uint256 identityId)

Security Note:
This role should be granted with extreme caution as it has nearly unlimited power across the entire system.

---

Identity Owner

The wallet address that created the identity or to whom the identity belongs.

Powers:

• Update all fields of their own identity
• Assign custodians to their identity
• Remove custodians from their identity
• Create Art Contracts (if registered as an Artist)

---

Art Contract Owner (Artist)

The artist who created the Art Contract or to whom ownership was transferred.

Powers:

• Mint NFTs in their own contract
• Update metadata for any NFT in their contract
• Set royalties for any NFT in their contract
• Grant roles to other identities for their contract
• Assign and remove partial editors for NFTs in their contract
• Transfer ownership of their Art Contract to another artist

Ownership Transfer:

Art Contract ownership can be transferred from one artist to another using the transferOwnership function. This allows for:

• Transferring a catalog to another artist
• Account migration
• Estate planning
• Collaboration management

Limitations:

• The new owner must have an Identity of type Artist
• Only the current owner or an identity with FULL_ADMIN_ROLE can transfer ownership

---

Custodian

Identity-Level Custodian

When an identity is assigned as a custodian of another identity through the Identity.assignCustodian() function:

Powers:

• Update all fields of the identity they are custodian for
• Act on behalf of the identity owner across all contracts

How to Assign:

On the Identity contract

function assignCustodian(uint256 identityId, uint256 custodianIdentityId)

Contract-Level Custodian (CUSTODIAN_ROLE)

When granted on a specific ArtContract:

Powers:

• Mint NFTs: Create new NFT tokens in the contract
• Update Metadata: Modify metadata for any NFT in the contract
• Set Royalties: Modify royalty settings for any NFT in the contract
• Grant Roles: Grant roles to other identities for the contract
• Assign Partial Editors: Assign and remove specific editors for individual NFTs

How to Assign:

On the specific ArtContract

function grantRole(bytes32 ArcConstants.CUSTODIAN_ROLE, uint256 identityId)

Limitations:

• Cannot transfer ownership of an identity
• Cannot directly modify the Identity contract (only accessible to FULL_ADMIN_ROLE)
• Cannot make contract-level changes beyond their defined scope

---

Minter

Powers:

• Mint NFTs: Create new NFT tokens in the contract
• Update Metadata: Modify metadata for any NFT in the contract

Limitations:

• Cannot set or modify royalties
• Cannot grant roles to other identities
• Cannot assign partial editors to NFTs
• Cannot transfer ownership of the contract

How to Assign:

On the specific ArtContract

function grantRole(bytes32 ArcConstants.MINTER_ROLE, uint256 identityId)

---

Full Editor

Powers:

• Update Metadata: Modify metadata for any NFT in the contract

Limitations:

• Cannot mint new NFTs
• Cannot set or modify royalties
• Cannot grant roles to other identities
• Cannot assign partial editors to NFTs
• Cannot transfer ownership of the contract

How to Assign:

On the specific ArtContract

function grantRole(bytes32 ArcConstants.FULL_EDITOR_ROLE, uint256 identityId)

---

Partial Editor

Powers:

• Update a Single NFT: Can only update metadata for the specific NFT they're assigned to

Limitations:

• Cannot mint new NFTs
• Cannot set royalties
• Cannot grant roles to other identities

How to Assign:

On the specific ArtContract

function assignPartialEditor(uint256 tokenId, uint256 editorIdentityId)

---

Standard Users (No Special Roles)

Powers:

• Create their own identity through the Identity contract
• View public information about identities and artworks
• Transfer NFTs they own (standard ERC-721 functionality)
• Approve others to transfer their NFTs (standard ERC-721 functionality)
• If an artist, create their own ArtContract

Limitations:

• Cannot mint NFTs on contracts they don't own
• Cannot update metadata on any NFTs they don't own
• Cannot set or modify royalties
• Cannot grant roles to identities
• Cannot assign custodians or partial editors

---

Security Considerations

When assigning roles:

• Only assign trusted entities
• Use the most granular level of access needed for the task
• Consider using partial editors for single-NFT access instead of roles with broader permissions
• Regularly audit role assignments to ensure appropriate access levels