Skip to content

Update SIP-15: Interface for Dynamic Traits Enforcement #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryanio merged 3 commits into from
Dec 1, 2025
Merged

Update SIP-15: Interface for Dynamic Traits Enforcement #30

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a1b9550
Update SIP-15: Interface for Dynamic Traits Enforcement
ryanio Dec 1, 2025
a2add2e
Revise substandard descriptions and decoding schemes
ryanio Dec 1, 2025
89992f5
Fix author formatting in sip-15.md
ryanio Dec 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 9 additions & 12 deletions SIPS/sip-15.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
sip: 15
title: Interface for Dynamic Traits Enforcement
description: A Seaport interface for specifying and enforcing values of ERC-7496 Dynamic Traits.
author: Ryan Ghods (@ryanio), James Wenzel (emo.eth)
author: Ryan Ghods (ryanio), James Wenzel (emo.eth), Benjamin C. LeFevre (BCLeFevre)
discussions-to: https://github.com/ProjectOpenSea/SIPs/discussions/19
status: Draft
type: Standards
Expand Down Expand Up @@ -51,20 +51,15 @@ If the implementing contract is a contract offerer, it MUST provide `previewOrde

The `context` argument MUST be populated based on the "substandards" specified by the zone or contract offerer; these substandards will be encoded in accordance with SIP-6 versioning with the assumption that all necessary data is to be treated as "variable" data arrays.

The `context` MUST start with a byte identifying the substandard ID below. The byte SHOULD be 1-indexed, but for gas efficiency reasons, 00 MAY also be used as an alias to reference substandard ID 1.

todo MUST be compact
The `context` MUST start with a byte identifying the substandard ID below. For gas efficiency, substandard IDs SHOULD be kept compact (for example, starting at 0) and re‑used consistently across integrations.

Initial substandards include:

| substandard ID | description | decoding scheme |
| -------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| 0 | first consideration item, comparison "equal to", single trait key, zero trait value | `(bytes32 traitKey)` TODO think about this should be in the zone hash, when no extra data is provided |
| 1 | token address and id from first offer item | `(uint8 comparisonEnum, bytes32 traitValue, bytes32 traitKey)` |
| 2 | token address and id from the first consideration item | `(uint8 comparisonEnum, bytes32 traitValue, bytes32 traitKey)` |
| 3 | single token id, single trait key and value(single) | `(uint8 comparisonEnum, address token, uint256 tokenId, bytes32 traitValue, bytes32 traitKey)` |
| 4 | multiple token ids, single trait key and value(multiple) | `(uint8 comparisonEnum, address token, uint256 tokenId, bytes32 traitValue, bytes32 traitKey)[]` |
| 5 | single token id, multiple traitKeys and values | `` |
| substandard ID | description | decoding scheme |
| -------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| 0 | single token, multiple traits | `(address token, uint256 tokenId, (bytes32 traitKey, bytes32 traitValue, uint8 comparisonEnum)[])` |
| 1 | multiple tokens, single trait each | `(address token, uint256 tokenId, bytes32 traitKey, bytes32 traitValue, uint8 comparisonEnum)[]` |
| 2 | multiple tokens, multiple traits each | `((address token, uint256 tokenId, (bytes32 traitKey, bytes32 traitValue, uint8 comparisonEnum)[])[])` |

| comparison enum | behavior |
| --------------- | ------------------------ |
Expand All @@ -75,6 +70,8 @@ Initial substandards include:
| 4 | greater than |
| 5 | greater than or equal to |

For substandard 0, the context explicitly binds a single NFT subject via `(address token, uint256 tokenId)` and then encodes one or more `(bytes32 traitKey, bytes32 traitValue, uint8 comparisonEnum)` tuples for that subject. Substandard 1 encodes multiple `(token, tokenId, traitKey, traitValue, comparisonEnum)` tuples for validating a single trait on each of multiple tokens. Substandard 2 combines both approaches, allowing multiple tokens each with multiple traits.

Additional substandards MAY be specified in subsequent SIPs that inherit this SIP.

## Rationale
Expand Down
Loading