Errors and Solutions
mQuarkControl.sol
While calling the functions to the mQuark Control contract. You sometimes recieve error messages depending on the functions and arguments you might use. This page is a reference for you to better understand about why an error message is returning for you.
NotOwner(string code, uint256 tokenId)
The reason a person would get the "NotOwner" error is that they are trying to perform an operation that requires them to be the owner of a specific token, but they are not.
| Type | Code | Solution |
|---|---|---|
revert | NO | To resolve this error the person should ensure that they are the rightful owner of the token before attempting the operation. They can do this by verifying their ownership rights through the appropriate authentication process. If they are not the owner of the token, they should refrain from attempting any owner-specific operations and instead consider alternative actions based on their user role or permissions. |
Unsubscribed(string code, uint256 tokenId, uint256 entityId)
The "Unsubscribed" error is thrown when an attempt is made to perform an operation on a token that has been unsubscribed from the associated entity. This error is raised to prevent unauthorized actions on tokens that are no longer linked to their respective entities.
| Type | Code | Solution |
|---|---|---|
revert | US | If you encounter the "Unsubscribed" error it indicates that the token you are trying to interact with has been unsubscribed from its associated entity. To resolve this issue, you should verify the subscription status of the token before performing any operations on it. |
NotAuthorized(string code)
The "NotAuthorized" error is raised when the caller of a function or operation is not authorized to perform the requested action. This error serves as a security measure to prevent unauthorized access to certain functionalities or sensitive data within the system.
| Type | Code | Solution |
|---|---|---|
revert | NA | If you encounter the "NotAuthorized" error it means that you do not have the necessary permissions or authorization to perform the operation you attempted. |
Verify Authorization: Double-check that you have the correct authorization to perform the desired action. Review the documentation or guidelines provided to determine the necessary permissions or roles required for the operation. Ensure that you meet the criteria specified for the particular functionality.
Request Authorization: If you believe that you should have the authorization but are still encountering the error, reach out to the appropriate authority or administrator responsible for granting permissions. Request the necessary authorization and provide any relevant information or justifications to support your request.
Follow Access Control Procedures: Make sure you adhere to the access control policies and procedures defined within the system. Respect the designated roles and permissions to maintain the security and integrity of the system.
It is important to note that unauthorized access attempts can lead to potential security risks or violations. Therefore, always ensure that you have the proper authorization before attempting any actions within the system.
mQuark Controller.sol
ArrayLengthMismatch(string code)
The "ArrayLengthMismatch" error is raised when the lengths of the input arrays provided to a function or operation do not match. This error is typically used to ensure that arrays being processed together have the same number of elements, as their lengths should be aligned for proper execution of the intended logic.
| Type | Code | Solution |
|---|---|---|
revert | ALM | If you encounter the "ArrayLengthMismatch" error, it means that the lengths of the input arrays you provided are not consistent. To resolve this issue, you can consider the following steps: |
Verify Array Lengths: Double-check the lengths of the input arrays you are passing to the function or operation. Ensure that all arrays involved in the operation have the same number of elements. Review the requirements or specifications of the function to understand the expected array lengths.
Adjust Input Arrays: If the lengths of the input arrays do not match, you need to modify the arrays to align their lengths. Depending on the specific situation, you may need to add or remove elements from one or more arrays to make them consistent. Alternatively, you can adjust the logic of your code to handle arrays of different lengths appropriately.
Validate Input Data: It is essential to validate the input data before performing operations that involve arrays. Implement checks to ensure that the input arrays meet the required length criteria. You can add conditional statements or assertions to verify the lengths of the arrays before executing any critical logic.
By ensuring that the lengths of the input arrays match, you can avoid the "ArrayLengthMismatch" error and ensure the proper execution of your code.
TemplateIdNotExist(string code)
The "TemplateIdNotExist" error is raised when the provided template ID does not exist. This error typically occurs when you attempt to reference or access a template using an ID that is not recognized or does not correspond to any existing template.
| Type | Code | Solution |
|---|---|---|
revert | TINE | If you encounter the "TemplateIdNotExist" error, it means that the template ID you provided does not exist within the system.Verify Template ID: Double-check the template ID you are using and ensure it is correct. Cross-reference the template ID with the available templates or a list of valid IDs to confirm its existence. |
RoyaltyIsTooHigh(string code)
The "RoyaltyIsTooHigh" error is raised when the provided royalty percentage is considered too high. This error typically occurs when you attempt to set a royalty percentage that exceeds the allowed limit or violates the rules and regulations of the system.
Royalty should be between 0 - 3000
| Type | Code | Solution |
|---|---|---|
revert | RTH | Adjust Royalty Percentage: Update the royalty percentage to ensure it falls within the acceptable range. If the provided royalty percentage is too high, consider lowering it to a value that complies with the system's guidelines. Modify the code or configuration responsible for setting the royalty percentage to reflect the adjusted value. |
NotTokenOwner(string code)
The "NotTokenOwner" error is raised when the caller of a function is not the owner of the token. This error typically occurs when the caller tries to perform an operation that requires ownership of a specific token, but they are not the owner.
| Type | Code | Solution |
|---|---|---|
revert | NTO | Verify Ownership: Ensure that the caller is the rightful owner of the token before attempting any operations that require ownership. You can compare the caller's address with the owner's address stored in the token's data or associated smart contract. |
mQuark Entity.sol
InvalidURILength(string code, uint256 uriLength)
The error is raised when the length of the provided URI is 0.
| Type | Code | Solution |
|---|---|---|
revert | IUL | Check the provided collection URIs parameter. |
InvalidTemplate(string code, uint256 templateId)
The "InvalidTemplate" error is raised when the provided template ID is invalid. Template IDs are used to identify and reference specific templates within a system or application. An invalid template ID indicates that the provided value does not correspond to an existing or recognized template.
| Type | Code | Solution |
|---|---|---|
revert | IT | Follow the steps below |
Confirm Template Existence: Validate that the template ID corresponds to an existing template within the system. You can do this by querying the system's template registry or database to verify if the template with the given ID exists.
Recheck Input: Double-check the source of the template ID input and ensure that it is being provided correctly. Mistyped or incorrect template IDs can lead to the "InvalidTemplate" error. If the template ID is entered manually, make sure there are no typographical errors or inconsistencies.
Provide Valid Template ID: If the provided template ID is indeed invalid, you will need to supply a valid and recognized template ID that exists within the system. Obtain the correct template ID from the system's documentation, user interface, or by consulting with the appropriate personnel or administrators.
InvalidCollectionPrice(string code, uint256 mintPrice)
The "InvalidCollectionPrice" error is raised when the provided collection price is invalid. Collection prices are used to determine the cost or value associated with acquiring or minting items from a collection. An invalid collection price indicates that the provided value does not meet the requirements or constraints defined by the system or application.
| Type | Code | Solution |
|---|---|---|
revert | ICP | Collection price can only be zero or equal or higher than the selected template price. If you would like to check the template price please see the `mQuark Controller contract. |
NotCollectionOwner(string code, address collectionAddress)
The "NotCollectionOwner" error is raised when the caller is not the owner of the collection. In a decentralized or distributed system, collections are often associated with ownership, and certain actions or operations may only be performed by the owner of the collection. This error serves as a security measure to prevent unauthorized access or modifications to collections.
| Type | Code | Solution |
|---|---|---|
revert | NCO | Follow the steps below. |
Verify Ownership: Confirm the ownership of the collection by comparing the address of the caller with the actual owner's address. You can use the collection address provided in the error message to identify the specific collection in question.
Check Caller's Address: Verify the address of the caller making the request against the expected owner's address. If they do not match, it indicates that the caller is not the owner of the collection and should not have access to owner-only functionalities.
Provide Valid Owner Address: If the caller is indeed not the owner of the collection but requires access to owner-specific functionalities, they should provide a valid owner address associated with the collection. Only the owner's address can successfully perform operations restricted to collection owners.
NoERC165Support(string code, address collectionAddress)
The "NoERC165Support" error is raised when the collection contract does not support the ERC165 interface. The ERC165 interface is a standard interface in the Ethereum ecosystem that allows smart contracts to declare which interfaces or capabilities they support. It enables other contracts or external entities to query whether a contract supports a specific interface before interacting with it.
| Type | Code | Solution |
|---|---|---|
revert | N165 | Follow the steps below. |
Verify Interface Support: Confirm whether the collection contract implements the ERC165 interface. You can do this by inspecting the contract's source code or documentation, or by using tools such as Etherscan or the Ethereum development environment.
Implement ERC165 Interface: If the collection contract does not currently support the ERC165 interface, you will need to modify the contract's code to include the required interface implementation. The ERC165 interface defines a standard function, supportsInterface, which allows contracts to indicate which interfaces they support.
Update or Replace the Contract: Depending on the specific requirements and constraints of your system, you may need to update the existing collection contract to include ERC165 support. Alternatively, if the contract is not flexible enough to accommodate the ERC165 interface, you may need to consider replacing it with a different collection contract that already supports ERC165. |
NoERC721Support(string code, address collectionAddress)
The "NoERC721Support" error is raised when the collection contract does not support the ERC721 interface. The ERC721 interface is a standard interface in the Ethereum ecosystem for non-fungible tokens (NFTs). It defines the basic functionality and required functions for managing and interacting with NFTs.
| Type | Code | Solution |
|---|---|---|
revert | N721 | Follow the steps below. |
Verify Interface Support: Confirm whether the collection contract implements the ERC721 interface. You can do this by inspecting the contract's source code or documentation, or by using tools such as Etherscan or the Ethereum development environment.
Implement ERC721 Interface: If the collection contract does not currently support the ERC721 interface, you will need to modify the contract's code to include the required interface implementation. The ERC721 interface defines functions such as balanceOf, ownerOf, safeTransferFrom, and more, which are necessary for working with NFTs.
Update or Replace the Contract: Depending on the specific requirements and constraints of your system, you may need to update the existing collection contract to include ERC721 support. Alternatively, if the contract is not flexible enough to accommodate the ERC721 interface, you may need to consider replacing it with a different collection contract that already supports ERC721. |
NotExternal(string code, address collectionAddress)
The "NotExternal" error is raised when the provided collection address is not an external collection. It means the provided address is an mQuark Collection.
| Type | Code | Solution |
|---|---|---|
revert | NE | Validate Collection Address: Double-check the accuracy of the collection address that you provided. Ensure that the address is correct and corresponds to a valid collection contract on the Ethereum network. |
TotalSupplyIsZero(string code)
Provided total supply parameter is zero.
| Type | Code | Solution |
|---|---|---|
revert | TSZ | Be sure that provided `total supply parameter is not zero. |
InvalidCollection(string code, uint64 collectionId)
The "InvalidCollection" error is raised when the provided collection ID is invalid. This means that the collection ID does not correspond to a valid or existing collection.
| Type | Code | Solution |
|---|---|---|
revert | IC | Follow the steps below. |
Verify Collection ID: Double-check the collection ID you provided and ensure its accuracy. Cross-reference it with the available collections to confirm that the ID matches an existing collection. It's possible that there was a typographical error or a misunderstanding of the correct collection ID.
Retrieve Valid Collection IDs: If you are unsure about the valid collection IDs or want to ensure their correctness, consult the documentation or the system that provides the collection IDs. Retrieve a list of valid collection IDs and verify that the ID you provided is included in that list.
InvalidEntity(string code, address entity)
The "InvalidEntity" error is raised when the provided entity address is invalid. This means that the address does not correspond to a valid or existing entity.
| Type | Code | Solution |
|---|---|---|
revert | IE | Follow the steps below. |
Verify Entity Address: Double-check the entity address you provided and ensure its accuracy. Make sure that the address is a valid Ethereum address and follows the correct format. It's possible that there was a typographical error or a misunderstanding of the correct entity address.
Retrieve Valid Entity Addresses: If you are unsure about the valid entity addresses or want to ensure their correctness, consult the documentation or the system that provides the entity addresses. Retrieve a list of valid entity addresses and verify that the address you provided is included in that list.
mQuark NFT.sol
InvalidVariation(string code, uint256 variationId)
The "InvalidVariation" error is raised when attempting to access an invalid variation. This error indicates that the provided variation ID does not correspond to a valid or existing variation.
| Type | Code | Solution |
|---|---|---|
revert | IV | Verify Variation ID: Double-check the variation ID you provided and ensure its accuracy. Make sure that the ID corresponds to a valid variation or simply check the collection and see the available variations. |
CollectionIsSoldOut(string code)
has reached its maximum supply or has been completely sold out. This error indicates that there are no more tokens available for minting within the collection.
| Type | Code | Solution |
|---|---|---|
revert | CSO | Verify Collection Status: Double-check the status of the collection to confirm that it is indeed sold out. Ensure that all tokens within the collection have been minted or sold. Explore Alternative Collections: If the desired collection is sold out, explore other available collections that may offer similar tokens or fulfill your requirements. Look for alternative collections with available tokens for minting. |
WrongMintType(string code, uint8 mintType)
The "WrongMintType" error is raised when attempting to perform a mint operation with an incorrect mint type. There are several available mint functions but only one of them can be used for the collection.
| Type | Code | Solution |
|---|---|---|
revert | WMT | First be sure that you are calling the right mint function. Then check the collection's mint type by simply calling the getCollectionInfo function. |
| Function Name | Mint Type |
|---|---|
mint | 1, 5, 7 or 11. |
mintWithURI | 3 or 9 |
mintWhitelist | 0, 4, 6 or 10. |
mintWithURIWhitelist | 2 or 8 |
InvalidPayment(string code)
The "InvalidPayment" error is raised when the payment provided for a certain operation is either invalid or insufficient. This error indicates that the payment amount does not meet the required criteria for the specific transaction or action being performed.
| Type | Code | Solution |
|---|---|---|
revert | IP | Verify Payment Amount: Double-check the payment amount and ensure that it meets the required criteria for the operation. |
NoPaymentRequired(string code)
The "NoPaymentRequired" error is raised when attempting to perform a minting operation that does not require any payment. This error indicates that the specific minting operation you are trying to execute does not involve any payment or fee.
| Type | Code | Solution |
|---|---|---|
revert | NPR | Proceed without Payment: Since no payment is required for the minting operation, you can proceed with the operation without providing any payment. Make sure to follow the correct steps and include any additional required information or parameters as specified. |
VerificationFailed(string code)
The "VerificationFailed" error is raised when the verification process of a signature fails. This error indicates that the provided signature is invalid or does not match the expected signature.
| Type | Code | Solution |
|---|---|---|
revert | VF | Follow the steps below. |
Check Signature Parameters: Verify that you are passing the correct signature parameters, such as the signed message or data, the signer's address, and the signature itself. Ensure that these parameters are accurate and properly formatted.
Verify Signature Integrity: Double-check the integrity of the signature data. Ensure that the signed message or data has not been altered or tampered with since the signing process. Any modification to the signed data will cause the signature verification to fail.
NotWhitelisted(string code)
The "NotWhitelisted" error is raised when the mint address used for a minting operation is not whitelisted. This error indicates that the specified address does not have the necessary permission or approval to perform the minting operation.
| Type | Code | Solution |
|---|---|---|
revert | NW | Verify Whitelist Status: Check the whitelist or authorization system to determine if the mint address should be whitelisted. Confirm whether the specified address should have the necessary access rights to perform minting operations. Double-check provided merkle proof: If the mint address is whitelisted, ensure that the provided merkle proof is correct and valid. |
NotOwner(string code, uint256 tokenId)
The "NotOwner" error is raised when the caller of a function is not the owner of the specified token. This error indicates that the current user does not have the necessary ownership rights to perform the requested operation on the token.
| Type | Code | Solution |
|---|---|---|
revert | NO | Verify Token Ownership: Check the ownership status of the token in question. Ensure that the caller is the rightful owner of the token and has the necessary ownership rights. |
Unsubscribed(string code, uint256 tokenId, uint256 entityId)
The "Unsubscribed" error is raised when attempting to access the entity slot of a token that is not subscribed to any entity. This error indicates that the token in question does not have an active subscription to an entity, and therefore, accessing its entity slot is not possible.
| Type | Code | Solution |
|---|---|---|
revert | US | Follow the steps below. |
Verify Subscription Status: Check the subscription status of the token by retrieving the associated entity ID or entity information. Ensure that the token has an active subscription to an entity before attempting to access its entity slot.
Subscribe to an Entity: If the token is not currently subscribed to any entity, you need to subscribe it to an entity. Determine the appropriate entity for the token and initiate the subscription process. This may involve calling a specific function or executing a transaction to establish the subscription.
InoperativeSignature(string code)
The "InoperativeSignature" error is raised when the provided signature is not operative. This error indicates that the signature provided for a certain operation is invalid or already used.
| Type | Code | Solution |
|---|---|---|
revert | IOS | Follow the steps below. |
Validate Signature: Verify that the signature provided is in the correct format and matches the expected signature format for the specific operation. Ensure that all required parameters and data are included in the signature generation process.
Check Signature Validity: Perform signature verification using the appropriate cryptographic algorithms and methods. This may involve using public key cryptography, digital signature libraries, or other security mechanisms to validate the signature's authenticity.
Ensure Correct Signature Usage: Confirm that the signature is being used correctly in the context of the operation. Check that the signature is applied to the intended data and that the verification process is correctly implemented according to the specific requirements and protocols.
NotAuthorized(string code)
The "NotAuthorized" error is raised when the caller is not authorized to perform a specific operation. This error indicates that the current user or account does not have the necessary permissions or privileges to execute the requested action.
| Type | Code | Solution |
|---|---|---|
revert | NA | If you encounter the "NotAuthorized" ###, it means that you do not have the necessary permissions or authorization to perform the operation you attempted. |
Verify Authorization: Double-check that you have the correct authorization to perform the desired action. Review the documentation or guidelines provided to determine the necessary permissions or roles required for the operation. Ensure that you meet the criteria specified for the particular functionality.
Request Authorization: If you believe that you should have the authorization but are still encountering the ###, reach out to the appropriate authority or administrator responsible for granting permissions. Request the necessary authorization and provide any relevant information or justifications to support your request.
Follow Access Control Procedures: Make sure you adhere to the access control policies and procedures defined within the system. Respect the designated roles and permissions to maintain the security and integrity of the system.
It is important to note that unauthorized access attempts can lead to potential security risks or violations. Therefore, always ensure that you have the proper authorization before attempting any actions within the system.
InsufficientBalance(string code)
The "InsufficientBalance" error is raised when the caller does not have a sufficient balance to perform a specific operation. This error indicates that the caller's account or wallet lacks the required funds or tokens needed to complete the requested action.
| Type | Code | Solution |
|---|---|---|
revert | IB | Check Account Balance: Verify the caller's account balance to confirm if it meets the minimum balance requirements or has enough funds or tokens for the operation. |
MintLimitReached(string code)
The "MintLimitReached" error is raised when the minting limit has been reached for an account. This error indicates that the maximum number of tokens that can be minted for the account has already been reached, and no more tokens can be minted.
| Type | Code | Solution |
|---|---|---|
revert | MLR | Check Minting Limit: Verify the current minting limit set for the account. This limit determines the maximum number of tokens that can be minted per account. |
mQuark Registry
EntityAddressNotRegistered(string code, address entity)
The "EntityAddressNotRegistered" error is raised when the given address is not registered. This error indicates that the provided address does not exist in the system's registry or database.
| Type | Code | Solution |
|---|---|---|
revert | EANR | Verify Address: Double-check the address you are using and ensure that it is correct. Mistyped or incorrect addresses can result in this error. Register Address: If the address is indeed not registered, you need to register it in the system. |
EntityIdNotRegistered(string code, uint256 entity)
The "EntityIdNotRegistered" error is raised when the given ID is not registered. This error indicates that the provided ID does not exist in the system's registry or database.
| Type | Code | Solution |
|---|---|---|
revert | EINR | Verify ID: Double-check the ID you are using and ensure that it is correct. Mistyped or incorrect IDs can result in this error. Register ID: If the ID is indeed not registered, you need to register it in the system. |
mQuark Subscriber.sol
NotAuthorized(string code, address caller)
The "NotAuthorized" error is raised when the caller is not authorized to perform a specific operation. This error indicates that the current user or account does not have the necessary permissions or privileges to execute the requested action.
| Type | Code | Solution |
|---|---|---|
revert | NA | If you encounter the "NotAuthorized" error, it means that you do not have the necessary permissions or authorization to perform the operation you attempted. |
Verify Authorization: Double-check that you have the correct authorization to perform the desired action. Review the documentation or guidelines provided to determine the necessary permissions or roles required for the operation. Ensure that you meet the criteria specified for the particular functionality.
Request Authorization: If you believe that you should have the authorization but are still encountering the ###, reach out to the appropriate authority or administrator responsible for granting permissions. Request the necessary authorization and provide any relevant information or justifications to support your request.
Follow Access Control Procedures: Make sure you adhere to the access control policies and procedures defined within the system. Respect the designated roles and permissions to maintain the security and integrity of the system.
It is important to note that unauthorized access attempts can lead to potential security risks or violations. Therefore, always ensure that you have the proper authorization before attempting any actions within the system.
NotRegistry(string code, address caller)
The "NotRegistry" error is raised when the caller address is not the expected registry address. This error indicates that the current caller is not the designated registry address required for the operation.
| Type | Code | Solution |
|---|---|---|
revert | NR | Verify Registry Address: Check the expected registry address that should be calling the specific operation. Ensure that the caller's address matches the designated registry address. |
NotEntityOwner(string code, uint256 entityId)
The "NotEntityOwner" error is raised when the caller is not the owner of the entity with the specified ID. This error indicates that the current caller does not have the necessary authorization to perform operations specific to the entity identified by the given ID.
| Type | Code | Solution |
|---|---|---|
revert | NEO | Verify Caller's Ownership: Check the ownership of the entity identified by the provided entity ID. Compare it with the caller's address to determine if they are the rightful owner. |
NotCollectionOwner(string code, address collectionAddress)
The "NotCollectionOwner" error is raised when the caller is not the owner of the collection with the specified address. This error indicates that the current caller does not have the necessary authorization to perform operations specific to the collection identified by the given address.
| Type | Code | Solution |
|---|---|---|
revert | NCO | Verify Caller's Ownership: Check the ownership of the collection identified by the provided collection address. Compare it with the caller's address to determine if they are the rightful owner. |
AlreadySubscribed(string code, uint256 subscriptionId, address InvalidTokenContract, uint256 tokenId)
The "AlreadySubscribed" error is raised when the specified subscription ID is already associated with the given token and token contract. This error indicates that the token is already subscribed to the subscription identified by the provided ID, and attempting to subscribe it again would result in a duplicate subscription.
| Type | Code | Solution |
|---|---|---|
revert | AS | Follow the steps below. |
Verify Subscription Status: Check the current subscription status of the token and token contract. Confirm whether they are already subscribed to the subscription with the provided ID.
Avoid Duplicate Subscriptions: If the token and token contract are already subscribed to the specified subscription, avoid attempting to subscribe them again. You can either skip the subscription operation or provide appropriate error handling to inform the user that the subscription already exists.
Manage Subscriptions: If necessary, implement mechanisms to track and manage subscriptions to prevent duplicate subscriptions. This may involve maintaining a list of subscribed tokens and their associated subscriptions, validating subscription status before subscribing, or implementing appropriate data structures to efficiently manage subscriptions.
Unexist(string code, uint256 entityId)
The "Unexist" error is raised when the entity with the specified ID does not exist. This error indicates that the provided entity ID does not correspond to any existing entity in the system.
| Type | Code | Solution |
|---|---|---|
revert | UE | Follow the steps below. |
Verify Entity ID: Double-check the entity ID you provided and ensure that it is correct. The error may occur if the ID is invalid or if there was a mistake in specifying the correct ID.
Confirm Entity Existence: Check the entity registry or database to verify if the entity with the given ID exists. If it does not exist, you may need to review the entity creation process and ensure that entities are properly registered and assigned unique IDs.
TokenLocked(string code, address contractAddress, uint256 tokenId)
The "TokenLocked" error is raised when the token with the specified ID is locked by the given contract address. This error indicates that the token cannot be subscribed to another entity.
| Type | Code | Solution |
|---|---|---|
revert | TL | Follow the steps below. |
Verify Contract Address and Token ID: Double-check the contract address and token ID you provided to ensure their accuracy. The error may occur if either the contract address or the token ID is incorrect.
Communicate with Contract Owner/Developer: If you are not the owner or developer of the contract, reach out to the appropriate party to discuss the token locking situation. Explain the issue you encountered and inquire about the necessary actions or permissions required to unlock the token. They may provide instructions or assistance in resolving the lock.
Unlock Token: Calling the
unlockTokenfunction of the contract will unlock the token and allow it to be subscribed to another entity.
InvalidPayment(string code, uint256 amount)
The "InvalidPayment" error is raised when the payment amount provided is invalid. This error indicates that the specified payment amount does not meet the required criteria
| Type | Code | Solution |
|---|---|---|
revert | IP | Validate Payment Amount: Review the payment amount you provided and ensure it meets the required criteria. Check if there are any specific rules or constraints regarding the payment amoun |
InvalidTokenContract(string code, address contractAddress)
The "InvalidTokenContract" error is raised when the token contract address provided is invalid. This error indicates that the specified token contract address does not meet the required criteria or does not correspond to a valid token contract.
| Type | Code | Solution |
|---|---|---|
revert | ITC | Verify Token Contract Address: Double-check the token contract address you provided and ensure its accuracy. Make sure that the address corresponds to a valid and deployed token contract on the blockchain network you are interacting with. |
Unsubscribed(string code, uint256 entityId)
The "Unsubscribed" error is raised when attempting to access the entity slot of a token that is not subscribed to any entity. This error indicates that the token in question does not have an active subscription to an entity, and therefore, accessing its entity slot is not possible.
| Type | Code | Solution |
|---|---|---|
revert | US | Follow the steps below. |
Verify Subscription Status: Check the subscription status of the token by retrieving the associated entity ID or entity information. Ensure that the token has an active subscription to an entity before attempting to access its entity slot.
Subscribe to an Entity: If the token is not currently subscribed to any entity, you need to subscribe it to an entity. Determine the appropriate entity for the token and initiate the subscription process. This may involve calling a specific function or executing a transaction to establish the subscription. |
VerificationFailed(string code)
The "VerificationFailed" error is raised when the verification process of a signature fails. This error indicates that the provided signature is invalid or does not match the expected signature.
| Type | Code | Solution |
|---|---|---|
revert | VF | Follow the steps below. |
Check Signature Parameters: Verify that you are passing the correct signature parameters, such as the signed message or data, the signer's address, and the signature itself. Ensure that these parameters are accurate and properly formatted.
Verify Signature Integrity: Double-check the integrity of the signature data. Ensure that the signed message or data has not been altered or tampered with since the signing process. Any modification to the signed data will cause the signature verification to fail.
UnknownCollection(string code)
The "UnknownCollection" error is raised when the collection with the specified ID or address is unknown or does not exist
| Type | Code | Solution |
|---|---|---|
revert | UC | Follow the steps below. |
Validate Collection ID/Address: Double-check the collection ID or address you provided and ensure its accuracy. Make sure that the ID or address corresponds to an existing collection in the system.
Collection Existence: Verify if the collection exists in the system. Check the database or storage where collections are stored and confirm if the collection associated with the provided ID or address is present.
NotFreeCollection(string code)
The "NotFreeCollection" error is raised when attempting to perform unlocking the token from a collection that is not free.
| Type | Code | Solution |
|---|---|---|
revert | NFC | Double-check the token ID you want to unlock. |
AlreadyUnlocked(string code, uint256 tokenId)
The "AlreadyUnlocked" error is raised when attempting to unlock a token that is already in an unlocked state. This error indicates that the specified token with the given ID has already been unlocked and is accessible for further operations.
| Type | Code | Solution |
|---|---|---|
revert | AUL | Validate Token Status: Double-check the status of the token to ensure it is indeed in a locked state. |
InoperativeSignature(string code)
The "InoperativeSignature" error is raised when the provided signature is not operative. This error indicates that the signature provided for a certain operation is invalid or already used.
| Type | Code | Solution |
|---|---|---|
revert | IOS | Follow the steps below. |
Validate Signature: Verify that the signature provided is in the correct format and matches the expected signature format for the specific operation. Ensure that all required parameters and data are included in the signature generation process.
Check Signature Validity: Perform signature verification using the appropriate cryptographic algorithms and methods. This may involve using public key cryptography, digital signature libraries, or other security mechanisms to validate the signature's authenticity.
Ensure Correct Signature Usage: Confirm that the signature is being used correctly in the context of the operation. Check that the signature is applied to the intended data and that the verification process is correctly implemented according to the specific requirements and protocols.
InsufficientBalance(string code)
The "InsufficientBalance" error is raised when the caller does not have a sufficient balance to perform a specific operation. This error indicates that the caller's account or wallet lacks the required funds or tokens needed to complete the requested action.
| Type | Code | Solution |
|---|---|---|
revert | IB | Check Account Balance: Verify the caller's account balance to confirm if it meets the minimum balance requirements or has enough funds or tokens for the operation. |
NotOwner(string code, uint256 tokenId)
The "NotOwner" error is raised when the caller of a function is not the owner of the specified token. This error indicates that the current user does not have the necessary ownership rights to perform the requested operation on the token.
| Type | Code | Solution |
|---|---|---|
revert | NO | Verify Token Ownership: Check the ownership status of the token in question. Ensure that the caller is the rightful owner of the token and has the necessary ownership rights. |
UnauthorizedToTransfer(string code)
The "UnauthorizedToTransfer" error is raised when the caller is not authorized to transfer the subscription metadata.
| Type | Code | Solution |
|---|---|---|
revert | UTT | Caller is not the buyer address. Double-check the caller or the provided parameter. |
PriceMismatch(string code)
The "PriceMismatch" error is raised when the seller and the buyer do not agree on the price.
| Type | Code | Solution |
|---|---|---|
revert | PM | Double-check the selller's sellPrice and buyer's buyPrice parameters. |
InvalidSentAmount(string code)
The "InvalidSentAmount" error is raised when the sent amount is not equal to the price.
| Type | Code | Solution |
|---|---|---|
revert | ISA | Double-check the sent amount requested buy the seller. |
TokenMismatch(string code)
The "TokenMismatch" error is raised when the seller and the buyer do not agree on the token.
| Type | Code | Solution |
|---|---|---|
revert | TM | Double-check the selller and buyer fromTokenId parameters. |
GivenEntityIdMismatch(string code)
The "GivenEntityIdMismatch" error is raised when the seller and the buyer do not agree on the entity ID.
| Type | Code | Solution |
|---|---|---|
revert | GEIM | Double-check the selller and buyer entityId parameters. |
SellerAddressMismatch(string code)
The "SellerAddressMismatch" error is raised when the seller and the buyer do not agree on the seller address.
| Type | Code | Solution |
|---|---|---|
revert | SAM | Double-check the selller and buyer seller parameters. |
UriMismatch(string code)
The "SellerAddressMismatch" error is raised when the seller and the buyer do not agree on the listed URI.
| Type | Code | Solution |
|---|---|---|
revert | UM | Double-check the selller and buyer slotUri parameters. |
SellerIsNotTheSigner(string code)
The "SellerAddressMismatch" error is raised when the seller is not the signer of the order.
| Type | Code | Solution |
|---|---|---|
revert | SNS | Check the provided order or the signature. |
BuyerIsNotTheSigner(string code)
The "SellerAddressMismatch" error is raised when the buyer is not the signer of the order.
| Type | Code | Solution |
|---|---|---|
revert | BNS | Check the parameters. |
FailedToSent(string code)
The "FailedToSent" error is raised during the transfer of the amount to the seller.
| Type | Code | Solution |
|---|---|---|
revert | FTS | Try to execute the function again. |
InvalidCollection(string code, address tokenContract)
The "InvalidCollection" error is raised when the provided collection ID is invalid. This means that the collection ID does not correspond to a valid or existing collection.
| Type | Code | Solution |
|---|---|---|
revert | IC | Follow the steps below. |
Verify Collection ID: Double-check the collection ID you provided and ensure its accuracy. Cross-reference it with the available collections to confirm that the ID matches an existing collection. It's possible that there was a typographical error or a misunderstanding of the correct collection ID.
Retrieve Valid Collection IDs: If you are unsure about the valid collection IDs or want to ensure their correctness, consult the documentation or the system that provides the collection IDs. Retrieve a list of valid collection IDs and verify that the ID you provided is included in that list.
RoyaltyIsTooHigh(string code)
The "RoyaltyIsTooHigh" error is raised when the provided royalty percentage is considered too high. This error typically occurs when you attempt to set a royalty percentage that exceeds the allowed limit or violates the rules and regulations of the system.
Royalty should be between 0 - 3000
| Type | Code | Solution |
|---|---|---|
revert | RTH | Adjust Royalty Percentage: Update the royalty percentage to ensure it falls within the acceptable range. If the provided royalty percentage is too high, consider lowering it to a value that complies with the system's guidelines. Modify the code or configuration responsible for setting the royalty percentage to reflect the adjusted value. |
mQuark Template.sol
ExceedsLimit(string code)
Throws if a specified batch limit has been exceeded.
| Type | Code | Solution |
|---|---|---|
revert | EL | The maximum limit is 255, reduce the number of given URIs. |
ArrayLengthMismatch(string code)
Throws if there is a mismatch in the length of arrays.
| Type | Code | Solution |
|---|---|---|
revert | ALM | Check the length of the given arrays. They should have the same length in order to execute the code . |
UnexistingCategory(string code)
Throws if the specified category does not exist while setting the template category.
| Type | Code | Solution |
|---|---|---|
revert | UEC | Check the spelling of the category name and be sure the category is created. |
UnexistingTemplate(string code)
Throws if the specified template does not exist while setting the template category.
| Type | Code | Solution |
|---|---|---|
revert | UET | Check the given template ID and be sure the template is exist. |