ERC1155-C primary sources
Primary source packet
1) Creator Token Standards repository overview
- URL: https://github.com/limitbreakinc/creator-token-standards
- Supporting raw source: https://raw.githubusercontent.com/limitbreakinc/creator-token-standards/main/README.md
- Why it matters:
- Best project-owned overview of the full standard family.
- Explicitly describes ERC1155-C as an extension of OpenZeppelin ERC-1155 with creator-definable transfer security profiles.
- Shows the adjacent control planes around ERC1155-C: shared validator registry, wrappers, EOA registry, royalty mix-ins, and deployment / configuration flow.
2) Core ERC1155-C contract
- URL: https://raw.githubusercontent.com/limitbreakinc/creator-token-standards/main/src/erc1155c/ERC1155C.sol
- Why it matters:
- Best direct source for the token-side mechanism.
- Shows how batch ERC-1155 transfers are routed through
_validateBeforeTransferand_validateAfterTransferon everyid/amountpair. - Shows auto-approval behavior for the configured transfer validator and the exposed transfer-validation function selector.
3) ERC1155-C wrapper contract
- URL: https://raw.githubusercontent.com/limitbreakinc/creator-token-standards/main/src/erc1155c/extensions/ERC1155CW.sol
- Why it matters:
- Important migration / governance source rather than a mere extension.
- Shows how existing vanilla ERC-1155 collections can be wrapped into ERC1155-C through opt-in staking and optional unstaking constraints.
- Makes it clear that ERC1155-C is not only for brand-new collections; it can also act as an upgrade path.
4) Payment Processor integration guide
- URL: https://raw.githubusercontent.com/limitbreakinc/payment-processor-v2/main/README.md
- Why it matters:
- Strong evidence that ERC1155-C is meant to plug into a broader trading path, not just exist as an isolated token contract.
- States plainly that Payment Processor is built for ERC721-C and ERC1155-C while remaining backward compatible with vanilla ERC-721 / ERC-1155.
- Helps separate token-side validator policy from exchange-side orderflow and fulfillment infrastructure.
5) Limit Break official protocol update
- URL: https://medium.com/limit-break/limit-break-goes-permissionless-for-popular-creator-protocols-cd71fba8174a
- Why it matters:
- Useful official narrative source on why the standards matter operationally.
- Confirms the move toward permissionless deployment of the Creator Token Transfer Validator and the broader protocol stack that ERC1155-C depends on.
- Shows how Limit Break positions creator-token enforcement as an ecosystem-wide deployable protocol rather than a one-collection custom trick.
Why ERC1155-C cleared the bar
- ERC1155-C is not just a copy of ERC721-C with a number changed.
- It preserves the same external validator architecture but applies it to batch-transfer and semi-fungible token semantics, which is a distinct control surface.
- It also introduces an analytically useful migration path through
ERC1155CW, where existing collections can opt into the new policy layer through wrapping.
Suggested comparison set for later passes
- ERC721-C
- CreatorTokenTransferValidator
- Seaport SignedZone
- Operator Filter Registry
- Royalty Registry
- other ERC-1155-native marketplace policy systems if they surface later