# Facets {% embed url="" %} ## Information in louper.dev Information about facets of the AavegotchiDiamond can be seen in [louper.dev](https://louper.dev/?address=0x86935F11C86623deC8a25696E1C19a8659CbF95d\&network=polygon), a user interface for diamonds. ## AavegotchiFacet.sol Implements the ERC721 standard. Handles logic related to claiming Aavegotchis, updating traits, increasing kinship, and locking Aavegotchis for resale. ## CollateralFacet.sol Handles logic related to Aavegotchis' collateral stakes, including increasing, decreasing, and burning Aavegotchis to return all stake to the owner. ## DAOFacet.sol Handles logic and functions intended to be managed and called by the AavegotchiDAO, including adding new whitelisted collaterals, creating new Haunts (Aavegotchi generations), creating and minting new items and sets, and granting experience to Aavegotchis. ## ItemsFacet.sol Implements the ERC1155 standard. Handles all logic related to equipping, consuming, and transferring items. Items come in three types: wearables, badges, and consumables. ## ShopFacet.sol Handles all logic related to buying Portals, converting vouchers into Wearables, and purchasing items using GHST token. ## SvgFacet.sol Handles all logic related to rendering Aavegotchi SVGs using onchain metadata. ## VRFFacet.sol Implements the Chainlink VRF functionality and updates Aavegotchi state variables when completed. The function to open portals is also in this facet. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.aavegotchi.com/developers/aavegotchi-contracts/diamond-standard/facets.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.