# ERC-5375: Author NFTs Source: https://www.eipsfordesigners.com/standards/ERC-5375 Agent brief: https://www.eipsfordesigners.com/standards/ERC-5375/agent.md Machine-readable JSON: https://www.eipsfordesigners.com/api/standards/ERC-5375 Last reviewed: 2026-04-05 Last updated: 2026-04-05 | Field | Value | | --- | --- | | Status | Final | | Chain | both | | Category | Security & Trust | | Journey stages | Authentication & Identity | | Detailed guide | Yes | | Official specification | https://eips.ethereum.org/EIPS/eip-5375 | | Discussion search | https://ethereum-magicians.org/search?q=ERC-5375 | ## UX Impact NFT metadata includes verified author consent signatures — proves creator agreed to be credited, prevents fake attributions. Design implications: show 'Verified Author' badge with proof link, display multiple co-authors, indicate consent verification status. Design decisions: how to handle unverified vs verified authors — warning indicators, whether to allow display of unverified claims. ## Summary ERC-5375 provides a standard way to cryptographically prove who created an NFT. The creator signs the token metadata or creation transaction, and this signature is stored with the NFT. Anyone can verify that the claimed author actually approved this specific NFT, preventing fake collections and impersonation. ## For Designers - You can design UI that delivers cryptographic signature proves specific address created this NFT. - You can design UI that delivers verify signature against known artist address. - You can design UI that delivers multiple author signatures prove each collaborator approved. ## Applicability ### When to Use - Your product addresses: no way to verify if NFT is from the claimed creator. - Your product addresses: fake collections impersonate famous artists. - The flow should deliver: cryptographic signature proves specific address created this NFT. - You are designing a verified creator badge experience with visible states and recovery paths. ### When to Avoid - Require cryptographic signature from actual creator. - Clear verified vs unverified indicators on every NFT. - Always show "Verify Authorship" option, even if unverified. - Wrong-address or approval mistakes are not recoverable in your product context. ## Problems It Solves ### No way to verify if NFT is from the claimed creator Impact: critical Old way: Trust collection name, check social media, hope it's real New way: Cryptographic signature proves specific address created this NFT ### Fake collections impersonate famous artists Impact: critical Old way: Scammers create "Official Beeple" collection, buyers fooled New way: Verify signature against known artist address, fakes exposed ### Collaborations have no provable attribution Impact: high Old way: Metadata says "by Alice and Bob" but no proof New way: Multiple author signatures prove each collaborator approved ### Creator identity can't be verified post-purchase Impact: high Old way: Original listing is gone, can't prove authenticity New way: Signature is on-chain forever, always verifiable ## Anti-Patterns ### Treating deployer address as creator Severity: critical Anyone can deploy a contract claiming to be someone Instead: Require cryptographic signature from actual creator ### Not showing verification status prominently Severity: critical Users assume all NFTs are verified, get scammed Instead: Clear verified vs unverified indicators on every NFT ### Hiding that verification is available Severity: high Users don't know they can check authorship Instead: Always show "Verify Authorship" option, even if unverified ### Complex signature verification UI Severity: high Only technical users can verify, others still at risk Instead: Simple verified/unverified badge with optional deep dive ### Not warning about missing signatures Severity: medium Users don't know unverified = higher risk Instead: Show warning: "This NFT has no authorship proof" ## UI Components ### AuthorVerificationBadge Shows author verification status States: verified, unverified, checking, invalid Props: signature, expectedAuthor, onVerify ### SignatureProofPanel Detailed signature verification display States: collapsed, expanded, verifying Props: signedData, signature, recoveredAddress ### CollaboratorList Lists multiple verified authors States: loading, loaded, partial-verified Props: authors, roles, signatures ### FakeCollectionWarning Alert for unverified/suspicious collections States: warning, danger, suspicious Props: claimedCreator, actualDeployer, hasSignature ## On Monad ### Verification Speed Ethereum: Signature verification queries take 1-3 seconds Monad: Instant verification responses Design implication: Can verify every NFT in a gallery view, not just on click ### Batch Verification Ethereum: Verifying collection of 100 NFTs is slow/expensive Monad: Batch verify entire collections quickly Design implication: "Verify all NFTs in collection" feature practical ### Multi-Author Ethereum: Many signatures = many slow checks Monad: Multi-author verification still instant Design implication: Complex collaborations verified as fast as single author ### Storage Ethereum: Storing signatures on-chain is expensive Monad: Lower costs make on-chain signatures more practical Design implication: More NFTs can have author signatures stored on-chain ## Key Takeaways - ERC-5375 = cryptographic proof of NFT authorship - Creator signature stored with NFT, verifiable forever - Show verified/unverified status prominently - Warn users when author signature is missing - On Monad: instant verification enables batch checking ## UX Patterns ### Verified Creator Badge Show proof of authorship on NFT displays User flow: - User views NFT page - See "Created by" section - Verified checkmark indicates signature exists - Click to see signature proof - Signature verified against creator address - Trust the attribution is genuine Mockup registry key: `concept/nft-gallery` (React UI on the live standard page). ### Signature Verification Panel Deep dive into authorship proof User flow: - User wants to verify authorship - Open verification panel - See exact data that was signed - See signature and recovered address - Confirm address matches claimed creator - Option to verify independently Mockup registry key: `concept/verify-safety` (React UI on the live standard page). ### Multi-Author Attribution Show multiple collaborator signatures User flow: - User views collaborative NFT - See list of all collaborators - Each shows their role in creation - Each has verified signature - Click to see individual proofs - Trust all listed creators participated Mockup registry key: `concept/nft-gallery` (React UI on the live standard page). ### Collection Verification Verify entire collection is from claimed creator User flow: - User encounters suspicious collection - Check verification status - See warning: no author signature - Deployer address doesn't match - Link to genuine collection for comparison - Avoid potential scam Mockup registry key: `concept/verify-safety` (React UI on the live standard page). ## Technical Notes ERC-5375 stores an author signature in NFT metadata or on-chain. The signature is over a hash of the token URI (or specific metadata fields). Verification recovers the signer address and compares to the claimed author. Multiple signatures support collaborations. The standard is compatible with EIP-712 typed data signing for readable author signing flows.