# Agent instructions

You are advising on UX and product design for **ERC-5521: Referable NFT**.
This document is the authoritative designer guide from EIPs for Designers.

- Treat **MUST NOT** items as hard constraints unless the user explicitly overrides.
- Use the **Vocabulary** section for UI copy; do not use avoided terms.
- Cite the canonical source URL when giving recommendations.
- Use the official specification only for protocol implementation detail, not as primary UX guidance.

---

# ERC-5521: Referable NFT

Source: https://www.eipsfordesigners.com/standards/ERC-5521
Agent brief: https://www.eipsfordesigners.com/standards/ERC-5521/agent.md
Machine-readable JSON: https://www.eipsfordesigners.com/api/standards/ERC-5521
Last reviewed: 2026-05-25
Last updated: 2026-05-25

| Field | Value |
| --- | --- |
| Status | Final |
| Chain | both |
| Category | NFT Capabilities |
| Journey stages | Asset Discovery & Display, Asset Management |
| Detailed guide | Yes |
| Official specification | https://eips.ethereum.org/EIPS/erc-5521 |
| Discussion search | https://ethereum-magicians.org/search?q=ERC-5521 |

## UX Impact

NFTs can reference other NFTs — creating a directed graph of relationships (remixes, derivatives, citations). Design implications: show 'References' and 'Referenced By' lists, visualize reference graph/network, indicate derivative relationships, display creation timestamps for ordering. Design decisions: graph visualization complexity, how deep to show reference chains, handling cross-contract references, attribution/citation display format.

## Summary

NFTs can reference other NFTs — creating a directed graph of relationships (remixes, derivatives, citations).

## For Designers

- You can show References and Referenced by lists on every derivative NFT detail page.
- Your graph view can limit depth to 2 hops with View full graph for explorers.
- You can link cross-contract references to correct collection with verification badge.

## Applicability

### When to Use

- Remix and derivative culture is core to product.
- On-chain citation between tokens matters.
- Attribution disputes need transparent lineage.

### When to Avoid

- Flat unrelated collectibles.
- Graph would have single node always.
- Indexer cannot resolve cross-contract refs.

## Problems It Solves

### Remix attribution disputes

Impact: high

Old way: He-said she-said off-chain

New way: On-chain reference list on token

### Discovering derivative works

Impact: medium

Old way: Manual search

New way: Referenced by index on originals

### Cross-collection lineage invisible

Impact: medium

Old way: Refs only in metadata text

New way: Resolvable cross-contract reference links

## MUST NOT (Anti-Patterns)

- **Unbounded graph depth render** (critical)
  - Why: Browser hang
  - Instead: Depth limit with expand control

- **Full graph as only view** (high)
  - Why: Casual users bounce
  - Instead: Lists first; graph optional

- **Broken refs shown as active links** (medium)
  - Why: 404 confusion
  - Instead: Reference unavailable state

## Design Decisions

### Graph or lists default?

Recommendation: Lists default; graph optional expand.

Rationale: Graph overwhelms casual collectors.

### Max graph depth?

Recommendation: 2 hops default; slider to 4 max.

Rationale: Citation chains explode combinatorially.

### Citation format?

Recommendation: Remixed from [thumb] [name] with date.

Rationale: Academic citation too cold for art.

## States to Design

### Has references only

Trigger: Derivative of others.

User need: See sources.

Design response: References list prominent.

### Referenced by many

Trigger: Popular original.

User need: Discover derivatives.

Design response: Referenced by with count and preview thumbs.

### Graph expanded

Trigger: User opens full graph.

User need: Explore without overwhelm.

Design response: Pan/zoom with depth filter.

### Broken reference

Trigger: Burned or invalid ref.

User need: Not broken UI.

Design response: Reference unavailable gray node.

### No references

Trigger: Original work.

User need: Still see if referenced by others.

Design response: Original badge; Referenced by if any.

## Vocabulary

- Use "Remixed from" instead of "Reference array entry": Creative attribution language.

- Use "Derivatives" instead of "Referenced-by subgraph": Collector-friendly term.

- Use "View lineage" instead of "Open citation graph": Discovery action language.

## UX Patterns

### Reference Lineage Lists

References and Referenced by on detail.

Components: ReferenceList, ThumbRow, DateLabel

User flow:

- Open NFT
- See references
- Tap source
- Navigate to parent

Mockup registry key: `concept/nft-gallery` (React UI on the live standard page).

### Remix Graph Explorer

Optional 2-hop visual graph.

Components: GraphCanvas, DepthControl, NodeCard

User flow:

- Tap View graph
- See 2-hop
- Expand depth
- Tap node to open

Mockup registry key: `concept/reactions` (React UI on the live standard page).

## What to Prototype First

### Reference lists on detail

Default view for lineage without graph complexity.

Covers: Has references, Referenced by others, None

- References list with thumbs
- Referenced by list
- Tap to navigate

### Lineage graph preview

Visual learners see remix tree.

Covers: 2-hop graph, Deep graph

- Mini graph
- Expand to full screen
- Depth limit label

### Cross-contract reference link

References span collections.

Covers: Same chain ref, Broken ref

- Collection name
- Verify resolved
- Broken link message

### Remix creation flow

Minter selects parent references at create.

Covers: Pick references, Confirm lineage

- Reference picker
- Preview lineage
- Mint with refs

## Mental Model

### Reference

This token points to sources it derives from.

### Referenced by

Other tokens point here — downstream derivatives.

### Directed graph

Edges one-way — remix points to original, not always reverse indexed automatically.

### Cross-contract

Reference may be different collection address — link must resolve both.

### Timestamp ordering

Creation time orders citation chronology.

## Seen in the Wild

- Sound.xyz: Musical remix lineage and attribution patterns. (https://www.sound.xyz/)

- Zora: Creator remix culture on-chain. (https://zora.co/)

- Foundation: Artist attribution on secondary works. (https://foundation.app/)

## On Monad

### Graph indexing

Ethereum: Cross-contract graph slow to build

Monad: Fast indexing enables snappier lineage loads

Design implication: Prefetch references on detail hover on Monad.

### Remix mints

Ethereum: Reference-heavy mints gas costly

Monad: Lower cost encourages on-chain citation at mint

Design implication: Reference picker in mint flow on Monad.

## Related Standards

- ERC-5489: Outbound links complement reference graph — https://www.eipsfordesigners.com/standards/ERC-5489/agent.md

- ERC-721: Referable extension — https://www.eipsfordesigners.com/standards/ERC-721/agent.md

## Technical Notes

ERC-5521 graph UI needs depth limits; resolve cross-contract refs before showing links.

## Official specification (reference only)

https://eips.ethereum.org/EIPS/erc-5521