Skip to content
NFTVenue Ledger
Directory

Trung tâm Chuyên đề Trụ cột · 20 Báo cáo đã xuất bản

Erc721 Erc1155 Eip712 Permit Security

Erc721 Erc1155 Eip712 Permit Security research topics and source records from NFTVenue Ledger. Institutional smart contract and NFT marketplace security hinges on EIP-712 replay isolation, Permit2 signature bounds, Seaport conduits, ERC-2981 royalties, and UUPS proxy timelocks.

Điểm nhấn Nghiên cứu Định chế — Erc721 Erc1155 Eip712 Permit Security

  • Replacing persistent ERC-20 approve(type(uint256).max) calls with one-time Permit2 SignatureTransfer witnesses reduces post-swap wallet allowance VaR to zero.
  • Seaport isolates ERC-721/1155 transfer permissions inside an immutable Conduit contract while enabling O(1) master counter increments to cancel all open listings.
  • Voluntary ERC-2981 royaltyInfo signaling requires pairing with ERC-721C transfer-validator bytecode hooks when creators mandate on-chain royalty enforcement.
  • Upgradeable proxies must combine _disableInitializers, EIP-7201 namespaced storage structs, and >=48h–7d TimelockController delays to prevent storage collisions and instant rugs.
  • Caching DOMAIN_SEPARATOR as immutable requires checking BOTH block.chainid == _CACHED_CHAIN_ID and address(this) == _CACHED_THIS on every read to prevent fork replays and proxy delegatecall bugs.
  • EIP-712 struct encoding requires 32-byte abi.encode word alignment, pre-hashing dynamic string/bytes/array values, and sorting nested struct definitions alphabetically in TYPEHASH.

Thực thể Đồ thị Tri thức Liên kết (9)

Tất cả Thực thể →

Danh sách Báo cáo Phân tích — Erc721 Erc1155 Eip712 Permit Security (20)

Hồ sơ Định chế & Sàn Môi giới Được Cấp phép

Cơ quan Giám sát Tài chính & Khung Pháp lý

Tất cả Cơ quan Quản lý →

Câu hỏi Thường gặp (FAQ) — Erc721 Erc1155 Eip712 Permit Security

Why can signing an off-chain Permit2 message drain tokens even though it costs zero gas?

Once a user has granted a one-time ERC-20 approval to the canonical Permit2 contract, signing an off-chain EIP-712 PermitSingle or PermitBatch payload authorizes the named spender to pull tokens on-chain immediately.

How does Seaport protect NFT holders if a new marketplace Zone contract has a bug?

Users approve only the immutable, minimal Seaport Conduit contract rather than complex marketplace routers, and Zones can only validate or reject orders—never arbitrarily sweep un-signed user NFTs.

Why is ERC-2981 alone insufficient to stop zero-royalty NFT trading?

ERC-2981 is a pure read-only view function (royaltyInfo) returning a suggested recipient and amount; ERC-721 transferFrom does not call or enforce ERC-2981 unless paired with an on-chain transfer validator.

What is the difference between a Transparent Proxy and a UUPS Proxy?

Transparent proxies put upgrade branching in the proxy fallback (checking msg.sender == admin on every call), whereas EIP-1822 UUPS places upgrade logic inside the implementation contract to save gas on user calls.

Why must cached EIP-712 domain separators check address(this) in addition to block.chainid?

During deployment, immutable _CACHED_THIS captures the implementation bytecode address; when a proxy calls that implementation via DELEGATECALL, address(this) is the proxy address, requiring dynamic recomputation.

Why does EIP-712 prefix every digest with the two bytes 0x1901?

Defined by EIP-191, leading byte 0x19 guarantees the signed payload can never start with a valid RLP-encoded Ethereum transaction byte (preventing tx-replay confusion), while 0x01 designates EIP-712 structured data.

Khám phá Các Chuyên đề Nghiên cứu Liên quan (NFTVenue Ledger)

Erc721 Erc1155 Eip712 Permit Security — Trung tâm Chuyên đề Trụ cột | NFTVenue Ledger | NFTVenue Ledger