Contracts
Every collection on Highlight is backed by a smart contract deployed on-chain. You don’t choose the implementation — the platform picks one based on your collection type and token standard.
Contract implementations
Section titled “Contract implementations”| Implementation | Standard | Used for | Reusable |
|---|---|---|---|
EditionsDFS1155Implementation | ERC-1155 | All edition types (Open, Limited, 1of1) | Yes |
SingleEditionDFSImplementation | ERC-721 | Open Edition only | No |
MultipleEditionsDFSImplementation | ERC-721 | Limited Edition, 1of1 | Yes |
SeriesImplementation | ERC-721 | Collectors Choice series | No |
RandomSeriesImplementation | ERC-721 | Standard series | No |
GenerativeSeriesImplementation | ERC-721 | All generative (Open and Limited) | No |
“Reusable” means the same deployed contract can back multiple collections. Non-reusable contracts get one per collection.
All deployments use ObservabilityV2 for on-chain event emission.
Multi-chain
Section titled “Multi-chain”Contracts are deployed per-chain. A collection belongs to exactly one chain. Use client.config.chains() to discover supported chains.
Deploy lifecycle
Section titled “Deploy lifecycle”| Collection status | Contract status |
|---|---|
Draft | Not deployed |
InProgress | Deploy transaction submitted, awaiting confirmation |
Live | Deployed, mints are possible |
The multi-step deploy workflow (Validate → UploadMetadata → [UploadCode] → GenerateTransaction → AwaitTransaction → RecordTransaction) is explained in deploy workflow.
Related
Section titled “Related”- Collections — types overview
- Deploy workflow — the full state machine
- Support matrix — contract selection rules
- SDK: contracts — contract record queries