CRC-721 vs CRC-1155#
CRC-721 represents individually identifiable assets, while CRC-1155 can represent many token types in one contract. On CenturionDEX, a v3 liquidity position is a CRC-721 NFT because each position can have its own pool, fee tier, price range, and accrued fees.
How the standards differ#
Both standards run as smart contracts on the EVM-compatible CVM, but they organize ownership differently:
- CRC-721: each token has a distinct token ID and one current owner. Two tokens from the same contract can carry different rights, metadata, or values.
- CRC-1155: one contract can track multiple token IDs, and each ID can have a supply greater than one. Transfers can also move several IDs in a single transaction.
A CRC-721 balance tells you how many unique tokens an address owns. To identify the assets, an interface also reads their token IDs. A CRC-1155 balance is queried for a particular owner and token ID, because the same address may hold different quantities of many IDs from one contract.
How approvals work#
The approval models are broader than CRC-20 allowances:
- A CRC-721 owner can approve one token ID or authorize an operator for every token in that collection.
- A CRC-1155 owner normally authorizes an operator for all of the owner's assets in that contract.
- An operator approval can transfer covered assets without another signature until the approval is removed.
This is why an NFT approval deserves the same scrutiny as a fungible-token approval. Disconnecting a website does not remove an onchain operator permission.
CenturionDEX liquidity positions#
CenturionDEX v2 positions are represented by fungible CRC-20 LP tokens because every share in the same v2 pool follows the same full-range model. CenturionDEX v3 positions are CRC-721 NFTs because each position can be configured differently.
For example, two users may both provide liquidity to the same CTN/token v3 pool. One chooses the 0.05% fee tier and a narrow range, while the other chooses the 0.30% tier and a wider range. Their positions are not interchangeable, so each is represented by its own token ID.
Common issues#
- A position is missing: confirm that your wallet is connected to Centurion and that you selected the address that owns the NFT.
- A transfer fails: the recipient may be a contract that cannot safely receive the token standard, or the operator approval may be missing.
- A wallet shows no image: metadata display can fail even when ownership is correctly recorded onchain.
- You approved the wrong operator: remove the approval through a trusted Centurion-compatible approval manager or wallet interface.
Stay safe#
Never sign an operator approval from an unsolicited link. Verify the contract, token ID, operator, and requested action in your wallet. Never share a recovery phrase, private key, or password with anyone claiming they need it to display or recover an NFT.