Erc721 Erc1155 Eip712 Permit Security
ERC-5192 Minimal Soulbound NFTs: Non-Transferable KYC Badges, Wrapper Traps & Revocation
ERC-5192 standardizes minimal Soulbound NFTs via locked(tokenId) and Locked/Unlocked events, powering on-chain KYC/KYB gating—provided auditors block smart-wallet ownership transfers.

Permissioned liquidity pools (Uniswap v4 KYC hooks, Aave Arc, tokenized T-bill vaults) and regulated RWA venues under ESMA, Dubai VARA, and MAS frequently issue non-transferable on-chain compliance credentials without leaking raw PII onto public blockchains. Rather than reinventing incompatible token interfaces, the ERC-5192 Minimal Soulbound NFT Standard extends standard ERC-721 with a tiny 1-function, 2-event locking interface (IERC5192, EIP-165 ID 0xb45a3c0e) so wallets and indexers like the Seaport marketplace protocol immediately know never to allow listing or transferring locked tokens!
Anchored in our EIP-712, Permit2 & proxy security master guide, naive Soulbound ("SBT") deployments suffer from a glaring Smart-Account / Wrapper Ownership Sale Bypass unless paired with continuous signer-state or ERC-3643 identity-registry verification!
ERC-5192 Specification & OpenZeppelin v5 _update Hook Implementation#
ERC-5192 adds exactly three elements on top of ERC721:
function locked(uint256 tokenId) external view returns (bool)(reverts iftokenIdcorresponds to zero owner / nonexistent token!).event Locked(uint256 tokenId)(emitted upon Soulbound minting or administrative freeze) andevent Unlocked(uint256 tokenId).- Inside OpenZeppelin v5's unified
_update(address to, uint256 tokenId, address auth)hook, any movement wherefrom != address(0) && to != address(0)(i.e., neither minting nor issuer revocation/burn!) reverts withErrTokenLocked(tokenId)whenever_locked[tokenId] == true!
The Fatal Soulbound Wrapper Trap: Selling the Safe or ERC-6551 Account!#
Watch how sanctioned actors bypass naive Soulbound KYC badges across DeFi and NFT venues in our marketplaces directory (from RWA launchpads to gated drops like Admit One and Art Blocks X Bright Moments):
- Verified KYC user Mallory deploys a 1-of-1 Safe smart-contract wallet (
or an ERC-6551 Token-Bound Account owned by an unlocked wrapper NFT!) and completes KYC so the issuer mintsKYC_SBT #402toaddress(Safe). KYC_SBT #402can never leaveaddress(Safe)(ERC-5192 reverts transferFrom!).- Instead of transferring
KYC_SBT #402, Mallory callsSafe.swapOwner(Mallory, Buyer)(or sells the parent NFT of the ERC-6551 account on Seaport)!address(Safe)never changed, yet a completely un-KYC'd Buyer now controlsaddress(Safe)and trades freely in the "KYC-gated" pool!
Mandatory Institutional Mitigations:
- EOA-Only or Monitored Safe Guard Minting: Either restrict SBT recipients to verified keys/custodians, or attach an immutable Safe
Guard/ ERC-3643ONCHAINIDclaim topic check that invalidates the credential the instantSafe.getOwnersor EIP-7702codehashchanges! - Rolling Time-to-Live (
expirationTimestamp): Storeuint64 validUntilpertokenIdrequiring periodic zero-cost off-chain refresh attestations (e.g., 90–180 days).
On-Chain Identity & Credential Architecture Comparison#
| Credential Standard | Token / Storage Layer | Marketplace UI Auto-Detection | Wrapper / Safe Sale Defense | Best Institutional Use Case |
|---|---|---|---|---|
| ERC-5192 Soulbound NFT | ERC-721 + locked(id) (0xb45a3c0e) | 100% Native (OpenSea/Blur hide List) | Requires extcodesize / Safe owner hash check | Accredited-investor & Reputation badges |
| EAS (Ethereum Attestation Service) | Singleton registry (Attestation struct) | Non-NFT (Custom indexer required) | Binds recipient + revocable expirationTime | High-volume off-chain/on-chain KYC claims |
| ERC-3643 (`T-REX`) | Security Token + IdentityRegistry | Built into token transfer hook | Verifies ONCHAINID cryptographic claim sigs | Regulated tokenized funds & bonds |
| ERC-5484 Consensual SBT | ERC-721 + BurnAuth enum | Partial EIP-165 support | Defines IssuerOnly vs Both burn rights | University degrees, credit-default flags |
Safe-Owner-Bound Soulbound Validity Invariant#
To close the smart-account wrapper loophole mathematically, institutional ERC-5192 contracts record a cryptographic Controller Fingerprint (H_ctrl) at mint time and verify it inside isValidCredential(address holder):
- At Mint Time t_0 for verified account A:
- Hctrl(t0) = (A.code.length == 0)
- ? keccak256(abi.encode("EOA", bytes32(0)))
- : keccak256(abi.encode(A.codehash, ISafe(A).getOwners, ISafe(A).getThreshold))
- Runtime Pool Hook Check at Swap Time t:
- Valid(A, t) = (ownerOf(id) == A)
- && (locked(id) == true)
- && (block.timestamp < expiry[id])
- && (Hctrlcurrent(A) == Hctrlrecorded[id])
- Worked Wrapper-Bypass Foiled Test:
- Sanctioned actor buys Safe 0x99..BB via swapOwner(VerifiedAlice -> Actor):
- Hctrlcurrent(0x99..BB) != Hctrlrecorded[id] -> Valid(0x99..BB, t) evaluates FALSE instantly (0-second auto-freeze)!
Inspecting ERC-6551 Token-Bound Accounts Next#
The exact opposite of a non-transferable ERC-5192 badge is an ERC-6551 Token-Bound Account (TBA)—where transferring one parent NFT atomically transfers an entire smart-contract wallet full of tokens and child NFTs! Examine TBA frontrunning traps next in ERC-6551 Token-Bound Account inventory frontrunning and ERC-2981 vs transfer validators inside our EIP-712, Permit2 & Proxy Security hub.
Frequently asked questions
How can someone sell a Soulbound NFT if transferFrom always reverts?
If the issuer allows minting the Soulbound token to a smart-contract wallet (such as a Gnosis Safe or ERC-6551 Token-Bound Account), the recipient can transfer ownership of the wallet itself without ever calling transferFrom on the SBT.
Does putting KYC Soulbound NFTs on Ethereum violate EU GDPR privacy laws?
Publishing names, passport hashes, or raw PII on an immutable blockchain violates GDPR; compliant ERC-5192 badges publish only an opaque revocable boolean/tier flag and expiry timestamp with zero PII.
Should an ERC-5192 contract also revert on approve and setApprovalForAll?
Yes. Reverting inside approve and setApprovalForAll for permanently locked collections saves users wasted gas and prevents stale approvals if a token were ever conditionally unlocked.
How does an issuer revoke an ERC-5192 KYC badge if a wallet is sanctioned?
In OpenZeppelin v5 ERC721._update, the lock guard checks (from != address(0) && to != address(0)), allowing an authorized REVOKER_ROLE to call _burn(tokenId) (where to == address(0)) in a single block.
Publication record
- Published
- November 13, 2026
- Updated
- November 14, 2026
- Author
- Dr. Devon Kurosawa, PhD
- Review
- Review not recorded
- Automated fact check
- Passed in the stored pipeline record
- Source URLs
- 3 recorded
AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.
Academic & Institutional Attribution
Cite This Research & Embed Live Data Card
Standard academic & institutional research paper citation format.
Dr. Devon Kurosawa, PhD. (2026, November 14). ERC-5192 Minimal Soulbound NFTs: Non-Transferable KYC Badges, Wrapper Traps & Revocation. NFTVenue Ledger. https://nftvenueledger.com/protocols/erc-5192-soulbound-attestation-locking-compliance-badgesRegulatory Directory Cross-Reference
Referenced Institutions & Regulatory Registries
Top Regulated Institutions in This Coverage Slice
Related Erc721 Erc1155 Eip712 Permit Security & Institutional Briefings
Explore Erc721 Erc1155 Eip712 Permit Security Hub (20) →Erc721 Erc1155 Eip712 Permit Security
EIP-712 Typed Signatures, Permit2 Allowances, NFT Royalties & Proxy Timelocks: 2026 Security GuideErc721 Erc1155 Eip712 Permit Security
ERC-6551 Token-Bound Accounts (TBAs): State Nonce Frontrunning & Circular Ownership LocksErc721 Erc1155 Eip712 Permit Security
ERC-721 safeTransferFrom & onERC721Received Reentrancy: Max-Supply Bypass & Escrow DrainsErc721 Erc1155 Eip712 Permit Security
Blind-Signing Deprecation (eth_sign), Pre-Sign Transaction Simulation & EIP-7730 Clear SigningErc721 Erc1155 Eip712 Permit Security
ERC-1155 Batch Transfer Security: Mandatory Receiver Hooks, Array Mismatches & Gas-Bomb DoSErc721 Erc1155 Eip712 Permit Security
CREATE2 Metamorphic Contracts, Cancun EIP-6780 SELFDESTRUCT & Bytecode Provenance AuditsErc721 Erc1155 Eip712 Permit Security
EIP-7201 Namespaced Storage Layouts: Eliminating __gap Fragility in Upgradeable ProxiesErc721 Erc1155 Eip712 Permit Security
EIP-712 Domain Separator Engineering: Dynamic chainId Caching & Cross-Fork Replay DefenseCross Chain Bridge Validator Exploits
Foundry Stateful Invariant Fuzzing, Handler Ghost Variables & Halmos Symbolic Bytecode ProvingCross Chain Bridge Validator Exploits
Cross-Contract Flash-Swap Oracle Manipulation: Spot-Reserve Valuation & Thin-Pool Collateral DrainsCross Chain Bridge Validator Exploits
Solidity Fixed-Point Precision Audits: WAD/RAY Scaling, mulDiv Overflow & Rounding ExploitsCross Chain Bridge Validator Exploits
Cross-Chain Message Replay, Chain Reorgs & Finality Depth Engineering (safe vs finalized)
NFTVenue Ledger Data, Benchmarks & Contributor Records
CC BY 4.0 Open Data
Open Institutional Datasets (CSV / JSON) →
Download desk-compiled quantitative series & schemas.
2026 Reference Matrix
2026 Institutional Benchmarks & Thresholds →
Statutory capital, clearing, margin & rate conventions.
Editorial Records
Authors & Review Records →
View named contributors where those records are available.
Complete Index
Master Research & Dossier Archive →
Browse all published briefings by topic pillar & date.
