Issues

Spec issue: `date` and `nftName` tables show forms no implementation produces

sourcifyeth/erc7730-spec-tests#12 · opened

on Oct 8, 2026

Spec issue: minimal contract examples use `number`/`bytes32` formats and `recipients[0]` paths

sourcifyeth/erc7730-spec-tests#11 · opened

on Oct 8, 2026

Spec issue: embedded-calldata examples use `required` and `excluded` keys that no schema defines

sourcifyeth/erc7730-spec-tests#10 · opened

on Oct 8, 2026

Spec issue: `calldata` table lists `chainIdPath`/`chainId`, `calldataParameters` schema has neither

sourcifyeth/erc7730-spec-tests#9 · opened

on Oct 8, 2026

Spec issue: `metadata.maps` is in the text but not in the 2.0.0 and 2.1.0 schemas

sourcifyeth/erc7730-spec-tests#8 · opened

on Oct 8, 2026

Decide what `label` carries for a field with no label (proposal: empty string)

sourcifyeth/erc7730-spec-tests#7 · opened

on Oct 8, 2026

Decide how the suite handles `visible: optional` fields (proposal: `optional/` folder only)

sourcifyeth/erc7730-spec-tests#6 · opened

on Oct 8, 2026

Decide where the rendered `separator` text goes in the output shape

sourcifyeth/erc7730-spec-tests#5 · opened

on Oct 8, 2026

Decide what `enum` shows when the value is not in the enum

sourcifyeth/erc7730-spec-tests#4 · opened

on Oct 8, 2026

Decide whether `raw` on bytes carries the `0x` prefix

sourcifyeth/erc7730-spec-tests#3 · opened

on Oct 8, 2026

Decide the output form of `nftName`: spec two-line example vs registry `<collection name> #<id>`

sourcifyeth/erc7730-spec-tests#2 · opened

on Oct 8, 2026

Decide the output form of `date`: spec `2024-02-29T08:27:12` vs registry `2026-03-19 12:11:19Z`

sourcifyeth/erc7730-spec-tests#1 · opened

on Oct 8, 2026

Navigation Menu

Repository navigation

Issues

Spec issue: `date` and `nftName` tables show forms no implementation produces

Spec issue: minimal contract examples use `number`/`bytes32` formats and `recipients[0]` paths

Spec issue: embedded-calldata examples use `required` and `excluded` keys that no schema defines

Spec issue: `calldata` table lists `chainIdPath`/`chainId`, `calldataParameters` schema has neither

Spec issue: `metadata.maps` is in the text but not in the 2.0.0 and 2.1.0 schemas

Decide what `label` carries for a field with no label (proposal: empty string)

Decide how the suite handles `visible: optional` fields (proposal: `optional/` folder only)

Decide where the rendered `separator` text goes in the output shape

Decide what `enum` shows when the value is not in the enum

Decide whether `raw` on bytes carries the `0x` prefix

Decide the output form of `nftName`: spec two-line example vs registry `<collection name> #<id>`

Decide the output form of `date`: spec `2024-02-29T08:27:12` vs registry `2026-03-19 12:11:19Z`