The `RMRKTokenHolder` contract allows ERC-20 tokens to be held and managed by specific token IDs. It supports transferring ERC-20 tokens to and from these token IDs, ensuring proper validation and balance checks. The contract includes hooks for custom logic before and after transfers and maintains a nonce for each token ID to track outgoing transfers. It implements the `IERC7590` interface for compatibility.

The `RMRKNestableAutoIndex` contract extends the `RMRKNestable` contract to manage nested NFTs with automatic indexing of child tokens. It maintains mappings to track the indices of pending and active child tokens for each parent token. The contract includes functions to add, accept, and transfer child tokens, updating indices accordingly. It also supports interface detection and overrides the `ownerOf` function.

The `RMRKSoulbound` contract is an abstract implementation of the IERC6454 interface, designed to manage soulbound tokens, which cannot be transferred once minted. It includes a hook `_beforeTokenTransfer` that reverts any transfer attempts unless the token is being minted or burned. The `isTransferable` function checks if a token can be transferred, and `supportsInterface` verifies support for the IERC6454 interface.

The `IRMRKMultiAssetAutoIndex` contract is an interface for managing multi-asset tokens. It allows token owners or approved managers to accept or reject pending assets for a given token. Accepted assets are moved to the token's active asset array and cannot be removed, only replaced. The contract emits events (`AssetAccepted` and `AssetRejected`) when assets are accepted or rejected.

This Solidity code defines three mock smart contracts that extend the functionality of the RMRK (Remarkable) protocol with soulbound (non-transferable) token features. Each contract has specific conditions for when tokens become soulbound: after a certain block number (`RMRKSoulboundAfterBlockNumberMock`), after a set number of transfers (`RMRKSoulboundAfterTransactionsMock`), or per individual token (`RMRKSoulboundPerTokenMock`). They also support multi-asset functionality and interface compatibility checks.

The `RMRKSoulboundAfterBlockNumber` contract extends the `RMRKSoulbound` module to restrict token transfers after a specified block number. It initializes with a `lastBlockToTransfer` parameter, which sets the final block number where transfers are allowed. The `getLastBlockToTransfer` function returns this block number, and the `isTransferable` function checks if the current block number is within the allowed transfer period.

The `RMRKMinifiedEquippable` contract is a comprehensive NFT management system that integrates ERC721, ERC7401 (nestable), ERC6220 (equippable), and ERC5773 (multi-asset) standards. It supports token transfers, minting, burning, and nested ownership. Additionally, it allows for equipping assets to tokens, managing child tokens, and handling asset approvals and priorities. The contract also includes hooks for various token and asset operations.

The `RMRKReclaimableChild` contract extends `RMRKNestable` to allow reclaiming abandoned child tokens. It maintains a mapping to track pending child tokens, preventing their reclamation. The contract includes hooks to update this mapping before adding, accepting, or transferring child tokens. It also implements the `reclaimChild` function to transfer ownership of abandoned child tokens back to the caller.

The `RMRKEquippable` contract is a module for managing equippable assets in a nested NFT system. It allows for the acceptance, rejection, and prioritization of assets for tokens. The contract supports equipping and unequipping child NFTs into parent NFTs, ensuring compatibility through catalog checks. It includes asset approval mechanisms and maintains mappings for asset metadata, equippable groups, and equipment states.

The `RMRKTokenAttributesRepository` contract is a repository for managing on-chain attributes of NFTs. It allows setting and retrieving various attribute types (address, bool, bytes, int, string, uint) for tokens within a collection. The contract includes access control mechanisms, supports batch operations, and allows presigned messages for attribute updates. It ensures only authorized users can manage attributes based on predefined access types.

The `RMRKMultiAssetAutoIndex` contract extends the `RMRKMultiAsset` contract to manage assets associated with tokens, providing automatic indexing for pending assets. It allows accepting or rejecting assets for a token, updates the index of pending assets accordingly, and ensures proper interface support. The contract maintains a mapping to track the index of each asset in the pending list for efficient management.

The `RMRKCore` contract is a passthrough contract for the RMRK core module, allowing for granular editing of base-level ERC721 functions. It provides two public functions: `VERSION()`, which returns the version of the RMRK EVM contracts package ("2.5.3"), and `RMRK_INTERFACE()`, which returns the interface identifier for the RMRK package (0x524D524B).

steven2308

ThunderDeliverer

CicadaNCR

stevyhacker

Yuripetusko

dependabot[bot]

ed-iv

omahs

dev-andreavendrame

Ayuilos

BoynChan

Swader

1337-ishaan

martinloesethjensen

hadrysmateusz

RMRK is a set of NFT standards that compose several NFT module primitives. Putting these modules together allows a user to create NFT systems of arbitrary complexity.