Contracts
client.contract is read-only — it lists and gets existing contract records. The deployment workflow lives on client.collection — see deploy workflow.
const res = await client.contract.list({ limit: 20, cursor: "optional-next-cursor",});Cursor-paginated. Scoped to the authenticated account.
const res = await client.contract.get({ contractId });Deployment
Section titled “Deployment”Deploy operations live on client.collection:
await client.collection.deploy({ highlightId });const status = await client.collection.deployStatus({ highlightId });await client.collection.deployConfirm({ highlightId, txHash: "0x..." });See the deploy workflow guide for the full state machine and polling pattern.
Contract implementations
Section titled “Contract implementations”The platform derives the contract implementation from the collection type + token standard:
| Collection type | ERC721 | ERC1155 |
|---|---|---|
OpenEdition | SingleEditionDFSImplementation | EditionsDFS1155Implementation |
LimitedEdition / OneOfOne | MultipleEditionsDFSImplementation | EditionsDFS1155Implementation |
Series (Collectors Choice) | SeriesImplementation | — |
Series (Standard) | RandomSeriesImplementation | — |
GenerativeSeries | GenerativeSeriesImplementation | — |
See support matrix for reusability and the full combination set.