ERC-1155-C referencia de la función de colección
Todas las funciones legibles y escribibles de la colección actual ERC-1155-C, con permisos y ajustes permanentes explicados.
En esta página
¿Qué contrato describe esto?
Esta referencia cubre CreatorEditionCollection , 0.4.0-erc1155-beta.1 . Los contratos más antiguos mantienen su comportamiento original. La configuración de fábrica de Aurora cambia las implementaciones futuras; no actualiza las colecciones que ya existen. Utilice la dirección de su colección, incluyendo Leer como proxy o Escribir como proxy cuando el explorador ofrezca esas pestañas. No envíe acciones de recopilación a su dirección de implementación.
Las funciones de solo lectura inspeccionan el estado sin enviar una transacción. Las funciones escribibles requieren una transacción de billetera y gas. Las funciones de pago también aceptan el pago en moneda nativa requerido. Todos los precios y cantidades en el ABI son enteros en la unidad monetaria más pequeña; en Ethereum y Base, esa unidad es wei.
Expanda una función para ver sus argumentos, valores de retorno y explicación. Se incluyen todas las funciones públicas/externas en el ABI compilado, con métodos heredados y funciones sobrecargadas. Una función que aparece en un explorador no significa que su billetera esté autorizada para llamarlo. BLOQUEADO significa que el selector mostrado no se puede usar después de la inicialización.
Acciones unidireccionales y configuraciones escritas una vez
- La implementación corrige la implementación, la vinculación inicial del validador, la autoridad de tarifas, la identidad de la galería, el nombre, el símbolo y el límite de vida útil del acuñar. Estos contratos no son actualizables. El validador de transferencia activo puede ser reemplazado, inhabilitado o restaurado por el propietario utilizando updateTransferValidator.
- El registro de lanzamiento corrige la raíz del inventario, el tamaño del inventario y la referencia del marcador de posición. Para un lanzamiento respaldado por ilustraciones, el propietario publica el catálogo de ilustraciones comprometido mientras el lanzamiento se pausa y antes de su primer acuñar. Las entradas se agregan en orden y se comprueban contra ese compromiso congelado; las entradas existentes no se pueden sobrescribir. El catálogo completo debe ser publicado antes de pausar. Las identidades de token existentes no se pueden recordar como ilustraciones diferentes.
- setAutoEnableTrading es editable solo antes de que se active el primer acuñar y antes de la negociación. enableTrading y la primera habilitación automática no se pueden deshacer.
- endDrop cierra permanentemente una liberación. closeMinting detiene permanentemente toda la colección acuñación . Al volver a establecer una bandera de pausa en false no se deshace ninguno de los cierres.
- renounceOwnership elimina permanentemente todos los permisos de propietario. Primer cierre acuñación, permitir el comercio, retirar todos los ingresos y terminar o cancelar la revelación. Revise los metadatos finales y la configuración regalía antes de enviar. La propiedad no se puede recuperar; un propietario previamente nombrado no puede aceptar después.
- Renuncia impide futuros metadatos autorizados por el propietario y cambios en regalía, pero no puede hacer que un host HTTPS sea inmutable o congelar las políticas de validación externa. NFTs todavía puede comerciar sujeto a esas políticas. La futura administración del validador que requiera que el propietario de la colección no esté disponible.
Readable functions
DEFAULT_TRANSFER_VALIDATORRead only · constant
Upstream library default validator address. Use getTransferValidator for this collection’s actual validator.
- Función y argumentos
DEFAULT_TRANSFER_VALIDATOR()- Devoluciones / pago
- address
MAX_BATCH_SIZERead only · constant
Maximum copies or unique NFTs in one mint transaction: 20.
- Función y argumentos
MAX_BATCH_SIZE()- Devoluciones / pago
- uint256
MAX_ROYALTY_BPSRead only · constant
Maximum royalty setting: 1,000 basis points, or 10%.
- Función y argumentos
MAX_ROYALTY_BPS()- Devoluciones / pago
- uint96
allowlistLeafRead only · proof helper
Calculates the whitelist proof leaf for a wallet, allocation and individual price, bound to this chain, collection, release and phase.
- Función y argumentos
allowlistLeaf(bytes32 dropId, bytes32 phaseId, address wallet, uint256 allowance, uint256 unitPrice)- Devoluciones / pago
- bytes32
autoApproveTransfersFromValidatorRead only · locked setting
Reports whether the validator has automatic operator approval. It is disabled and cannot be enabled after initialization in these builds.
- Función y argumentos
autoApproveTransfersFromValidator()- Devoluciones / pago
- bool
autoEnableTradingRead only · pre-mint choice
Reports whether the first mint automatically enables transfers. It can be changed only before any mint and before trading is enabled.
- Función y argumentos
autoEnableTrading()- Devoluciones / pago
- bool
balanceOfRead only · holder balance
ERC-721: number of NFTs held by a wallet. ERC-1155: number of copies of a specified token ID held by an account.
- Función y argumentos
balanceOf(address account, uint256 id)- Devoluciones / pago
- uint256
balanceOfBatchRead only · holder balances
Returns ERC-1155 balances for matching account and token-ID arrays. The arrays must have equal length.
- Función y argumentos
balanceOfBatch(address[] accounts, uint256[] ids)- Devoluciones / pago
- uint256[]
collectionRead only · identity
Returns this collection’s address. Native minting runs at the collection address itself.
- Función y argumentos
collection()- Devoluciones / pago
- address
concurrentPublicMintRead only · capability for new collections
Returns true for the current mint design: each payer has an independent authorization sequence, so another wallet minting does not invalidate their approval. Real supply, phase, price and expiry checks still apply. Older deployed builds retain their original approval behavior.
- Función y argumentos
concurrentPublicMint()- Devoluciones / pago
- bool
contractURIRead only · reference
Returns collection-level metadata, such as its profile. This is separate from individual token metadata.
- Función y argumentos
contractURI()- Devoluciones / pago
- string
dropEndedRead only · permanent release flag
Reports whether a release has been permanently ended.
- Función y argumentos
dropEnded(bytes32)- Devoluciones / pago
- bool
editableMetadataRead only · capability, not current permission
Identifies a contract with metadata-update functions. It stays true even after ownership is renounced, when nobody can authorize owner-only updates.
- Función y argumentos
editableMetadata()- Devoluciones / pago
- bool
factoryRead only · immutable
Returns the factory bound into this implementation at deployment. It cannot be replaced.
- Función y argumentos
factory()- Devoluciones / pago
- address
galleryIdRead only · written ONCE
Aurora folder identity used to create this collection. It is fixed when initialized.
- Función y argumentos
galleryId()- Devoluciones / pago
- bytes32
getDropRead only · release state
Returns the release configuration, minted count, version and existence flag. A zero cap means uncapped at that level; collection limits still apply.
- Función y argumentos
getDrop(bytes32 dropId)- Devoluciones / pago
- (bytes32 inventoryRoot, uint256 inventorySize, string placeholderURI, uint256 supplyCap, uint256 walletCap, bool paused) config, uint256 minted, uint256 version, bool exists
getPhaseRead only · phase state
Returns phase timing, price, caps, allowlist root, pause flag, minted count, version and existence flag.
- Función y argumentos
getPhase(bytes32 dropId, bytes32 phaseId)- Devoluciones / pago
- (uint64 startsAt, uint64 endsAt, uint256 unitPrice, uint256 supplyCap, uint256 walletCap, bytes32 allowlistRoot, bool paused) config, uint256 minted, uint256 version, bool exists
getTransferValidationFunctionRead only · integration helper
Returns the validator function selector and whether the validation call is read-only. ERC-1155 validation includes transfer amount.
- Función y argumentos
getTransferValidationFunction()- Devoluciones / pago
- bytes4 functionSignature, bool isViewFunction
getTransferValidatorRead only · current validator or zero
Returns the active transfer validator. The zero address means validator checks are disabled. The owner can change this using updateTransferValidator.
- Función y argumentos
getTransferValidator()- Devoluciones / pago
- address validator
isApprovedForAllRead only · operator approval
Reports whether an operator is approved to transfer the holder’s tokens. Approval does not give collection administrator permissions.
- Función y argumentos
isApprovedForAll(address owner, address operator)- Devoluciones / pago
- bool isApproved
metadataBaseURIRead only · metadata reference
Returns the most recently published metadata directory. Covered tokens append their decimal token ID and .json.
- Función y argumentos
metadataBaseURI()- Devoluciones / pago
- string
metadataRevisionRead only · increasing revision
Counts published complete metadata snapshots. Expected revision protects against accidentally overwriting a newer snapshot.
- Función y argumentos
metadataRevision()- Devoluciones / pago
- uint256
metadataSupplyRead only · snapshot marker
Lifetime minted quantity covered when the last metadata snapshot was published. ERC-1155 counts copies, not token types.
- Función y argumentos
metadataSupply()- Devoluciones / pago
- uint256
mintCatalogRead only · immutable catalog address
Returns the immutable artwork catalog bound to this factory or collection implementation. Registered collections use it to store and verify committed inventory before opening a mint, then read artwork during successful mint transactions. The collection owner publishes entries through the catalog’s appendMintCatalog function; this getter does not publish or modify artwork.
- Función y argumentos
mintCatalog()- Devoluciones / pago
- address
mintCatalogSizeRead only · catalog publication progress
Returns the number of artwork entries uploaded to this release’s immutable catalog. A release backed by artwork cannot open until this equals its committed inventory size. This is publication progress, not the number already minted.
- Función y argumentos
mintCatalogSize(bytes32 dropId)- Devoluciones / pago
- uint256
mintFeeAuthorityRead only · immutable
Returns the immutable factory that validates public-mint fee authorizations. It does not have owner or withdrawal powers.
- Función y argumentos
mintFeeAuthority()- Devoluciones / pago
- address
mintNonceRead only · payer-specific replay protection
Returns the next authorization sequence for a paying wallet across this collection. A successful public mint increments only that payer’s sequence, consuming their previous approvals; another wallet’s mint does not change it. Failed transactions roll back the increment. This value is used in the legacy-named expectedMinted request field in current builds.
- Función y argumentos
mintNonce(address)- Devoluciones / pago
- uint256
mintSupplyCapRead only · written ONCE, cannot raise or remove
Lifetime collection mint ceiling. Zero means uncapped. It includes manual and public mints; ERC-1155 counts all copies.
- Función y argumentos
mintSupplyCap()- Devoluciones / pago
- uint256
mintedByWalletRead only · cumulative count
Total quantity minted by a paying wallet within a release. Sending the NFTs to a different recipient does not move this payer’s allowance.
- Función y argumentos
mintedByWallet(bytes32, address)- Devoluciones / pago
- uint256
mintingClosedRead only · ONE-WAY flag
Whether collection minting has been permanently closed.
- Función y argumentos
mintingClosed()- Devoluciones / pago
- bool
mintingPausedRead only · reversible until closed
Whether collection-level minting is paused. This is separate from the native sale pause and per-release/phase pauses.
- Función y argumentos
mintingPaused()- Devoluciones / pago
- bool
nameRead only · written ONCE
Collection name set at deployment. No later name setter is provided.
- Función y argumentos
name()- Devoluciones / pago
- string
nativePublicMintRead only · capability
Returns true for integrated public minting. It does not by itself identify a particular version or payout capability.
- Función y argumentos
nativePublicMint()- Devoluciones / pago
- bool
ownerRead only · authority
Wallet or contract with collection administrator rights. Zero address means ownership was renounced and owner-only functions cannot be used.
- Función y argumentos
owner()- Devoluciones / pago
- address
pausedRead only · reversible sale flag
Native sale pause flag. It blocks public minting and the owner mintBatch path; it does not stop already-enabled transfers or withdrawals.
- Función y argumentos
paused()- Devoluciones / pago
- bool
payoutRecipientRead only · release payment mode
Payment destination for a release. Zero means retain artwork proceeds; any configured nonzero address receives direct payouts. Different releases can have different destinations.
- Función y argumentos
payoutRecipient(bytes32)- Devoluciones / pago
- address
pendingOwnerRead only · ownership handover
Nominated next collection owner. Control changes only after this address accepts. Renunciation clears any pending nomination.
- Función y argumentos
pendingOwner()- Devoluciones / pago
- address
pendingRevealRead only · reveal plan
Current reveal commitment, release ID, base/max supply, expected metadata revision, due time and existence flag. There can be one pending reveal across the collection.
- Función y argumentos
pendingReveal()- Devoluciones / pago
- bytes32 dropId, bytes32 commitment, uint256 baseSupply, uint256 maxSupply, uint256 expectedRevision, uint64 revealAt, bool exists
phaseMintedByWalletRead only · cumulative count
Cumulative quantity paid for by one wallet in one release phase. Counts remain when the phase settings change.
- Función y argumentos
phaseMintedByWallet(bytes32, bytes32, address)- Devoluciones / pago
- uint256
placeholderArtworkIdRead only · deterministic identity
Returns the stable ERC-1155 artwork ID for placeholder mints in a release. All copies in that placeholder release share the same token ID.
- Función y argumentos
placeholderArtworkId(bytes32 dropId)- Devoluciones / pago
- bytes32
proceedsRead only · accounted balance
Creator revenue retained for withdrawal across releases. Excludes direct payouts and platform fees. Forced or unrelated native-currency deposits are not necessarily withdrawable proceeds.
- Función y argumentos
proceeds()- Devoluciones / pago
- uint256
quoteRead only · current-state estimate
Validates a proposed mint against current phase, version, supply, payer nonce and wallet rules and returns artwork unit and total prices. Another payer minting does not change this payer’s nonce. Does not include the platform fee or gas, reserve inventory, validate fee authorization, or guarantee a receiving contract accepts payment.
- Función y argumentos
quote((bytes32 dropId, bytes32 phaseId, uint256 dropVersion, uint256 phaseVersion, uint256 quantity, uint256 expectedMinted, uint256 maxUnitPrice, address recipient, uint256 allowance, uint256 allowlistPrice) request, address payer, bytes32[] allowlistProof)- Devoluciones / pago
- uint256 unitPrice, uint256 totalPrice
revealCommitmentRead only · reveal helper
Computes the hash binding a metadata directory, secret salt, release, supply bounds, revision and due time to this chain and collection.
- Función y argumentos
revealCommitment(bytes32 dropId, string baseURI, bytes32 salt, uint256 baseSupply, uint256 maxSupply, uint256 expectedRevision, uint64 revealAt)- Devoluciones / pago
- bytes32
royaltyBpsRead only · royalty setting
Secondary-sale royalty setting in basis points: 500 means 5%. This is unrelated to primary mint price.
- Función y argumentos
royaltyBps()- Devoluciones / pago
- uint96
royaltyInfoRead only · ERC-2981
Returns the royalty receiver and calculated amount for a token and sale price. It is royalty information, not proof that every marketplace enforces payment.
- Función y argumentos
royaltyInfo(uint256 tokenId, uint256 salePrice)- Devoluciones / pago
- address, uint256
royaltyReceiverRead only · separate from mint proceeds
Receiving wallet for secondary-sale royalties. It does not gain ownership or withdrawal permission.
- Función y argumentos
royaltyReceiver()- Devoluciones / pago
- address
supportsInterfaceRead only · integration helper
Reports support for a given interface identifier. This does not attest to audit status or marketplace compatibility.
- Función y argumentos
supportsInterface(bytes4 interfaceId)- Devoluciones / pago
- bool
symbolRead only · written ONCE
Collection ticker set during deployment. No later symbol setter is provided.
- Función y argumentos
symbol()- Devoluciones / pago
- string
tokenIdForArtworkRead only · artwork identity
Maps an artwork ID to its minted token ID, or zero if none. ERC-721 IDs are sequential; ERC-1155 uses uint256(artworkId).
- Función y argumentos
tokenIdForArtwork(bytes32)- Devoluciones / pago
- uint256
tokenStandardRead only · constant
Returns ERC1155 for edition contracts.
- Función y argumentos
tokenStandard()- Devoluciones / pago
- string
tokenURIRead only · token metadata
Returns resolved metadata for a minted token. ERC-721 requires the token to exist; the ERC-1155 alias follows uri and returns empty for an unknown token.
- Función y argumentos
tokenURI(uint256 tokenId)- Devoluciones / pago
- string
totalSupplyRead only · cumulative supply
Lifetime minted quantity: unique NFTs for ERC-721, total copies across all editions for ERC-1155. Transfers do not reduce it.
- Función y argumentos
totalSupply()- Devoluciones / pago
- uint256
totalSupplyOfRead only · edition supply
Lifetime copies minted for one ERC-1155 token ID. This is not a wallet balance.
- Función y argumentos
totalSupplyOf(uint256)- Devoluciones / pago
- uint256
totalTokenTypesRead only · edition count
Number of distinct minted ERC-1155 artwork/token IDs, independent of how many copies exist.
- Función y argumentos
totalTokenTypes()- Devoluciones / pago
- uint256
tradingEnabledRead only · ONE-WAY flag
Whether transfers have been permanently enabled. Validator restrictions still apply when true.
- Función y argumentos
tradingEnabled()- Devoluciones / pago
- bool
uriRead only · token metadata
ERC-1155 metadata reference for a token ID, empty if unknown. Snapshot updates affect every copy of a covered edition. Filenames use decimal IDs, not the standard {id} substitution pattern.
- Función y argumentos
uri(uint256 tokenId)- Devoluciones / pago
- string
validatorRead only · immutable initial binding
Initial validator bound into the factory/implementation at deployment for provenance. It does not change when a collection replaces or disables its active validator. Read getTransferValidator on the collection for the active setting.
- Función y argumentos
validator()- Devoluciones / pago
- address
Writable functions
acceptOwnershipPending owner · completes two-step transfer
The nominated pending owner accepts collection control. A pending reveal prevents the handover.
- Función y argumentos
acceptOwnership()- Devoluciones / pago
- No return value
cancelRevealOwner · cancels the current commitment
Removes the pending reveal commitment. Does not publish artwork or automatically resume paused minting. The owner can prepare a new reveal or metadata update.
- Función y argumentos
cancelReveal()- Devoluciones / pago
- No return value
closeMintingOwner · ONE WAY, cannot reopen
Permanently stops both owner and public minting across the collection. Existing tokens can still trade if trading is enabled; metadata and withdrawal controls remain available until ownership is renounced.
- Función y argumentos
closeMinting()- Devoluciones / pago
- No return value
configureDropOwner · inventory written ONCE per release; caps and pause repeatable
Creates or updates a release. Its inventory root, inventory size and placeholder reference cannot change once registered. A release backed by artwork must have its full verified catalog uploaded before it is unpaused. Supply caps cannot fall below already minted amounts. Changes increment the release version and invalidate old quotes.
- Función y argumentos
configureDrop(bytes32 dropId, (bytes32 inventoryRoot, uint256 inventorySize, string placeholderURI, uint256 supplyCap, uint256 walletCap, bool paused) config)- Devoluciones / pago
- No return value
configurePayoutOwner · repeatable while release is paused and not ended
Sets a release’s receiving wallet. Zero address means retain proceeds for withdrawal; a nonzero address receives each artwork payment. Requires an existing paused release that has not been ended. The collection itself cannot be its payout recipient. Changes invalidate old quotes; earlier proceeds stay withdrawable.
- Función y argumentos
configurePayout(bytes32 dropId, address recipient)- Devoluciones / pago
- No return value
configurePhaseOwner · repeatable until release is permanently ended
Creates or edits timing, artwork price, supply/wallet limits, allowlist root and pause state within an open release. End must be zero or after start. Already minted counts remain; changes invalidate old quotes.
- Función y argumentos
configurePhase(bytes32 dropId, bytes32 phaseId, (uint64 startsAt, uint64 endsAt, uint256 unitPrice, uint256 supplyCap, uint256 walletCap, bytes32 allowlistRoot, bool paused) config)- Devoluciones / pago
- No return value
enableTradingOwner · ONE WAY, cannot disable trading
Permanently enables transfers, including when minting is paused or closed. Validator policies still apply. Repeated calls after enabling revert.
- Función y argumentos
enableTrading()- Devoluciones / pago
- No return value
endDropOwner · ONE WAY for this release
Permanently ends one release and invalidates its mint quotes. It does not close other releases, cancel its pending reveal or withdraw funds.
- Función y argumentos
endDrop(bytes32 dropId)- Devoluciones / pago
- No return value
executeRevealAnyone with committed data after due time · consumes the commitment ONCE
Publishes the exact committed metadata directory and salt after the reveal time. Supply must match the commitment’s bounds and revision. Clears the pending reveal and leaves public minting paused. This function alone does not end the release: Aurora’s reveal flow adds an owner-approved endDrop call. Force reveal uses separate owner transactions; this function cannot bypass the due time.
- Función y argumentos
executeReveal(string baseURI, bytes32 salt)- Devoluciones / pago
- No return value
initializeFactory only · ONCE during deployment
The factory sets owner, collection identity, name, symbol, royalty settings, lifetime supply cap and initial trading policy while creating the clone. It cannot initialize the same clone again.
- Función y argumentos
initialize(address creator, bytes32 galleryId_, string name_, string symbol_, address royaltyReceiver_, uint96 royaltyBps_, uint256 supplyCap_)- Devoluciones / pago
- No return value
initializeERC1155Factory initialization only · ONCE
Inherited ERC-1155 initialization hook, already called during clone creation. Further calls revert; it is not a metadata-update tool.
- Función y argumentos
initializeERC1155(string uri_)- Devoluciones / pago
- No return value
mintBLOCKED · compatibility selector
Legacy unsigned public-mint selector. It always reverts in these fee-authorized builds, including for free mints. Use mintWithFee.
- Función y argumentos
mint((bytes32 dropId, bytes32 phaseId, uint256 dropVersion, uint256 phaseVersion, uint256 quantity, uint256 expectedMinted, uint256 maxUnitPrice, address recipient, uint256 allowance, uint256 allowlistPrice) request, bytes32[] allowlistProof, (bytes32 artworkId, string tokenURI, bytes32[] proof)[] inventory)- Devoluciones / pago
- No return value · PAYABLE
mintBatchOwner · repeatable while minting is available
Owner mints selected artwork directly, without public-phase pricing or platform mint-fee authorization. ERC-721 artwork IDs must be unique; ERC-1155 includes copy amounts and can reuse an existing edition. Collection supply limits, pause/closure and receiver checks still apply; a pending reveal blocks this path.
- Función y argumentos
mintBatch(bytes32[] artworkIds, string[] tokenURIs, uint256[] amounts, address recipient)- Devoluciones / pago
- No return value
mintWithFeeEligible payer with valid authorization · payable
Public mint with a whitelist proof when required, exact artwork price plus signed platform fee, quantity/wallet limits and current versions. Current builds use the payer’s mintNonce and assign artwork from the next committed catalog entries when the transaction succeeds; the inventory argument must be empty. A valid authorization is required even for zero fees. Creator payment follows configurePayout. Any failure rolls back the mint and payments; network gas can still be charged.
- Función y argumentos
mintWithFee((bytes32 dropId, bytes32 phaseId, uint256 dropVersion, uint256 phaseVersion, uint256 quantity, uint256 expectedMinted, uint256 maxUnitPrice, address recipient, uint256 allowance, uint256 allowlistPrice) request, bytes32[] allowlistProof, (bytes32 artworkId, string tokenURI, bytes32[] proof)[] inventory, uint256 fee, bytes authorization)- Devoluciones / pago
- No return value · PAYABLE
renounceOwnershipOwner · IRREVERSIBLE, final action only
Permanently sets owner and pendingOwner to zero. Requires mintingClosed=true, tradingEnabled=true, proceeds=0 and no pending reveal. Removes metadata, royalty, payout, pause and other owner administration permanently. External validator rules still apply and may change; nobody can recover ownership through this contract.
- Función y argumentos
renounceOwnership()- Devoluciones / pago
- No return value
safeBatchTransferFromHolder or approved operator · batch transfer
Transfers several ERC-1155 IDs and amounts with matching arrays. Applies holder/operator authorization, trading and validator rules and contract receiver checks.
- Función y argumentos
safeBatchTransferFrom(address from, address to, uint256[] ids, uint256[] amounts, bytes data)- Devoluciones / pago
- No return value
safeTransferFromHolder or approved operator · each transfer changes ownership/balance
Transfers a token, or ERC-1155 copies, from its holder to a recipient. Requires holder/operator authorization, enabled trading and validator approval. A contract recipient must accept the NFT callback. The ERC-721 overload with bytes passes optional receiver data.
- Función y argumentos
safeTransferFrom(address from, address to, uint256 id, uint256 amount, bytes data)- Devoluciones / pago
- No return value
scheduleRevealOwner · one pending commitment; cancel before replacing
Stores a commitment and future due time for one existing release, matching current supply/revision and valid upper supply bounds. Pending reveal restricts other mint paths and ownership changes. Does not schedule an automatic transaction.
- Función y argumentos
scheduleReveal(bytes32 dropId, bytes32 commitment, uint256 baseSupply, uint256 maxSupply, uint256 expectedRevision, uint64 revealAt)- Devoluciones / pago
- No return value
setApprovalForAllToken holder · repeatable approval/revocation
Grants or revokes an operator’s ability to transfer all of the caller’s collection tokens. It cannot transfer collection administrator ownership.
- Función y argumentos
setApprovalForAll(address operator, bool approved)- Devoluciones / pago
- No return value
setAutoEnableTradingOwner · editable BEFORE first mint/trading only
Chooses whether the first successful mint enables transfers automatically. Only available before any mint and before trading is enabled. False allows manual enabling later.
- Función y argumentos
setAutoEnableTrading(bool enabled)- Devoluciones / pago
- No return value
setAutomaticApprovalOfTransfersFromValidatorBLOCKED after initialization
Inherited upstream setter. Disabled after factory initialization; the collection owner cannot use it to grant automatic validator approval.
- Función y argumentos
setAutomaticApprovalOfTransfersFromValidator(bool autoApprove)- Devoluciones / pago
- No return value
setContractURIOwner · repeatable until ownership is renounced
Changes the collection-level metadata reference. Accepts URI schemes without a protocol allowlist, subject to syntax and length checks. Does not change individual token metadata.
- Función y argumentos
setContractURI(string newURI)- Devoluciones / pago
- No return value
setDefaultRoyaltyOwner · repeatable until ownership is renounced
Changes the secondary-sale receiver and royalty rate, from 0 to 1,000 basis points. Receiver must be nonzero. Does not change the mint proceeds wallet.
- Función y argumentos
setDefaultRoyalty(address receiver, uint96 basisPoints)- Devoluciones / pago
- No return value
setMetadataBaseURIOwner · repeatable until ownership is renounced
Publishes a complete directory for existing tokens using exact current lifetime supply and metadata revision. Requires a nonempty collection and no pending reveal. Directory must end in / and use decimal token-ID .json filenames. Scheme is unrestricted; existing marketplace support is not guaranteed.
- Función y argumentos
setMetadataBaseURI(string newURI, uint256 expectedSupply, uint256 expectedRevision)- Devoluciones / pago
- No return value
setMintingPausedOwner · reversible BEFORE permanent closure
Pauses or resumes collection minting. Once closeMinting has been called, this action cannot reopen it. It does not lock trading.
- Función y argumentos
setMintingPaused(bool value)- Devoluciones / pago
- No return value
setPausedOwner · reversible; cannot override permanent closure
Pauses or resumes native sale minting and the guarded owner mint path. Separate collection, release and phase gates can still stop minting. Reveals leave this flag true.
- Función y argumentos
setPaused(bool value)- Devoluciones / pago
- No return value
setTransferValidatorFactory initialization / internal guarded call only · direct calls BLOCKED
Inherited setter visible in the ABI. Direct calls after initialization are BLOCKED, including owner calls. Use the guarded updateTransferValidator function to replace, disable or restore the active validator.
- Función y argumentos
setTransferValidator(address transferValidator_)- Devoluciones / pago
- No return value
transferOwnershipOwner · two-step, repeatable until renounced
Nominates the next collection owner; that address must acceptOwnership. Zero cancels the nomination without renouncing. Pending reveal blocks the change.
- Función y argumentos
transferOwnership(address newOwner)- Devoluciones / pago
- No return value
updateTransferValidatorOwner · reversible and repeatable until renounced
Replaces the active validator with a compatible deployed contract, or disables it with 0x0000000000000000000000000000000000000000. The owner can restore it later. Disabling stops validator-based royalty enforcement and other validator restrictions, but preserves royaltyInfo, holder approvals, the trading lock and mint fees. Nonzero addresses need deployed code and cannot be this collection. Code presence does not prove safety or compatibility; token-type registration is attempted and policies may need separate setup. Emits TransferValidatorUpdated. Reentrant changes are blocked and automatic validator approval stays disabled. Unavailable after ownership is renounced.
- Función y argumentos
updateTransferValidator(address nextValidator)- Devoluciones / pago
- No return value
withdrawOwner · repeatable while proceeds remain
Sends a positive amount no greater than proceeds to a nonzero chosen recipient. Only the owner authorizes it; the recipient can differ from Aurora’s saved wallet. Available during or after minting. Failed payments revert; reentrant withdrawals are blocked.
- Función y argumentos
withdraw(address recipient, uint256 amount)- Devoluciones / pago
- No return value
acuñar entradas y referencias de metadatos
Una tupla es un grupo de campos con nombre que se muestran juntos en la firma de función. DropConfig contiene inventoryRoot , inventorySize , placeholderURI , supplyCap , walletCap y se detuvo. PhaseConfig contiene startsAt , endsAt , unitPrice, supplyCap , walletCap , allowlistRoot y se detuvo. Los tiempos son Unix segundos; un final de fase de 0 significa que no hay final programado. Un límite de suministro o billetera de 0 significa ilimitado en ese nivel de límite, mientras que una asignación de lista blanca de 0 permite no mints.
MintRequest une dropId , phaseId , dropVersion , phaseVersion , cantidad, expectedMinted , maxUnitPrice , destinatario, asignación y allowlistPrice . En estas compilaciones actuales, expectedMinted conserva su nombre ABI anterior, pero significa mintNonce (pagador), no el recuento total de acuñado de la versión. Una aprobación es consumida por el público exitoso de ese pagador acuñar. Las billeteras separadas pueden contener aprobaciones válidas al mismo tiempo; otra billetera acuñación por sí sola no invalida la suya. Expiración, cambio de configuración, límites de cartera, sincronización de fase y liquidación real aún pueden evitar un acuñar .
Las ilustraciones se asignan cuando la transacción tiene éxito, utilizando las siguientes entradas de catálogo comprometidas. Las aprobaciones no reservan obras de arte o suministros particulares, y los coleccionistas no pueden elegir un índice de catálogo diferente. El argumento de inventario en mintWithFee debe estar vacío en estas compilaciones. InventoryItem (artworkId, tokenURI y su prueba Merkle) se utiliza en su lugar cuando el propietario publica entradas de catálogo en el contrato mintCatalog separado de la fábrica. Aurora prepara esas transacciones de publicación en lotes limitados mientras que el lanzamiento se pausa y no tiene mints. Requieren la firma del propietario y la red gas; la publicación se reanuda a partir de mintCatalogSize después de una interrupción. Las versiones solo de marcador de posición no requieren un catálogo de ilustraciones.
El catálogo es de datos públicos en la cadena, y la asignación sigue su orden comprometido; no es una fuente de aleatoriedad. Las URL de las ilustraciones finales publicadas en un catálogo se pueden inspeccionar antes de acuñación incluso cuando los tokens muestran un marcador de posición. Una revelación retrasada debe mantener las referencias finales de las obras de arte fuera del catálogo publicado hasta que se revelen. La configuración de revelación compatible con Aurora maneja esto por separado de las ilustraciones de revelación instantánea.
Las referencias de metadatos aceptan cualquier esquema URI sintácticamente válido en lugar de una lista de permisos de protocolo. Las referencias están limitadas a 256 bytes; directorios de instantáneas a 220 bytes y una barra diagonal, sin consulta ni fragmento. Los archivos de directorio utilizan identificadores decimales seguidos por .json. Se rechazan referencias vacías, espacios en blanco, caracteres de control y barras invertidas. Los contratos almacenan referencias pero no obtienen, ejecutan ni garantizan el contenido. Aurora todavía aplica sus propias reglas de visualización y extracción seguras.