# Agent instructions

You are advising on UX and product design for **EIP-7634: Limited Transfer Count 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.

---

# EIP-7634: Limited Transfer Count NFT

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

| Field | Value |
| --- | --- |
| Status | Draft |
| Chain | both |
| Category | NFT Capabilities |
| Journey stages | Asset Management |
| Detailed guide | Yes |
| Official specification | https://eips.ethereum.org/EIPS/eip-7634 |
| Discussion search | https://ethereum-magicians.org/search?q=EIP-7634 |

## UX Impact

NFTs have maximum transfer count — after N transfers, token becomes non-transferable or burns. Design implications: show 'Transfers Remaining: 3/5' counter prominently, warn before final transfer, indicate transfer-exhausted tokens, display transfer history count. Design decisions: whether to show transfer limit upfront during purchase, how alarming the 'last transfer' warning should be, treatment of exhausted tokens (greyed vs hidden vs special badge).

## Summary

NFTs have maximum transfer count — after N transfers, token becomes non-transferable or burns.

## For Designers

- You can show Transfers remaining: 2 of 5 on listing and detail before purchase.
- Your send confirmation can warn This is the last transfer when one remains.
- You can badge Transfer exhausted on tokens that can never move again.

## Applicability

### When to Use

- Collectibles intentionally scarce in secondary circulation.
- Artist policy limits flips.
- Draft EIP deployed with transfer cap.

### When to Avoid

- Standard freely tradable NFTs.
- Cap not enforced on-chain.
- Users expect infinite liquidity.

## Problems It Solves

### Buyers unaware of remaining liquidity

Impact: high

Old way: Discover cannot resell after buy

New way: Transfers remaining on listing

### Accidental final transfer

Impact: high

Old way: Send then token locks unexpectedly

New way: Last transfer warning modal

### Unlimited flipping undermines artist intent

Impact: medium

Old way: No transfer limits

New way: On-chain cap enforces scarcity of movement

## MUST NOT (Anti-Patterns)

- **Hiding transfer cap until send fails** (critical)
  - Why: Surprise lock destroys trust
  - Instead: Counter visible at purchase and send

- **Last transfer without extra confirm** (critical)
  - Why: Irreversible user error
  - Instead: Acknowledgment modal for final transfer

- **Same UI for exhausted and soulbound** (medium)
  - Why: Different implications confused
  - Instead: Transfer exhausted vs Non-transferable labels

## Design Decisions

### How alarming is last transfer?

Recommendation: Require checkbox acknowledgment in modal.

Rationale: Accidental final transfer is irreversible regret.

### Show counter on thumbnail?

Recommendation: Yes when ≤2 remain; always on detail.

Rationale: Scarcity affects price — surface early.

### Exhausted visual treatment?

Recommendation: Distinct badge, not hidden — collectors may still display.

Rationale: Proof of permanent collection piece.

## States to Design

### Full transfer budget

Trigger: New mint, all transfers available.

User need: Know policy exists.

Design response: Up to N transfers badge on detail.

### Low remaining

Trigger: 1-2 transfers left.

User need: Factor into sell/buy decision.

Design response: Amber counter on card and listing.

### Last transfer confirmation

Trigger: User sends with 1 left.

User need: Explicit consent.

Design response: Modal with irreversible warning.

### Transfer exhausted

Trigger: Zero remaining.

User need: Know permanent hold.

Design response: Exhausted badge; Send hidden.

### Burned on exhaust

Trigger: Token burned after final transfer.

User need: Extreme warning before last send.

Design response: This transfer will destroy token copy.

## Vocabulary

- Use "2 transfers left" instead of "Transfer count decrement remaining": Game-life metaphor.

- Use "Final transfer" instead of "Last allowed transfer before lock": Short warning label.

- Use "Cannot move again" instead of "Transfer budget exhausted": Plain permanence language.

## UX Patterns

### Transfer Budget Counter

Remaining transfers on card and detail.

Components: TransferCounter, WarningChip, PolicyTooltip

User flow:

- View NFT
- See 2 of 5
- Decide to buy
- Counter updates on transfer

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

### Last Transfer Gate

Confirmation when one transfer remains.

Components: LastTransferModal, AckCheckbox, ConfirmSend

User flow:

- User sends
- One left detected
- Modal warns
- User acknowledges
- Transfer proceeds

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

## What to Prototype First

### Listing with transfer counter

Secondary buyers price scarcity of remaining transfers.

Covers: 5 of 5, 1 remaining, Exhausted

- Counter chip
- Tooltip explaining cap
- Price context

### Last transfer warning

Final move needs explicit consent.

Covers: Last transfer confirm

- Scary warning modal
- After this cannot transfer
- Confirm checkbox

### Exhausted token view

Permanent hold state needs distinct treatment.

Covers: Transfer exhausted

- Exhausted badge
- Transfer history count
- No Send button

### Primary mint disclosure

First buyers accept transfer policy.

Covers: Policy at mint

- Max transfers stated
- Acknowledge checkbox

## Mental Model

### Transfer budget

Finite number of allowed moves — like lives in a game.

### Decrement on transfer

Each successful send reduces remaining count.

### Exhausted state

Zero remaining — token locked or burned per rules.

### Primary vs secondary

Mint may start count at max; secondary sees what's left.

### Burn on exhaust

Some implementations destroy token — must disclose upfront.

## Seen in the Wild

- Art Blocks: Artist policy on secondary markets informs transfer limit UX. (https://www.artblocks.io/)

- Foundation: Creator royalties and transfer policy display patterns. (https://foundation.app/)

- Zora: Creator-centric metadata for collection rules. (https://zora.co/)

## On Monad

### Transfer counting

Ethereum: Counter update waits for confirmations

Monad: Instant counter refresh after send

Design implication: Update UI immediately post-transfer on Monad.

### Scarce transfer drops

Ethereum: High gas discourages flips

Monad: Low fees — counter more likely to deplete

Design implication: Emphasize counter prominently on Monad marketplaces.

## Related Standards

- ERC-6454: Transfer restriction detection — https://www.eipsfordesigners.com/standards/ERC-6454/agent.md

- ERC-721: NFT with transfer cap extension — https://www.eipsfordesigners.com/standards/ERC-721/agent.md

## Technical Notes

EIP-7634 is draft; treat last transfer as irreversible consent moment.

## Official specification (reference only)

https://eips.ethereum.org/EIPS/eip-7634