# Contract Architecture ### How Data Flows Players may take positions by selecting a number of variables and depositing ERC-20 collateral. New positions are represented as ERC-721 tokens (Mimes). ![Mimicry data flow diagram](/files/lgTmmRhSVb07boJ3cvwJ) ### Mimics as NFTs Each minted Mimic will contain specialized metadata written to the blockchain. When rendered within a wallet, that data, along with real-time performance information, will be visible in the NFT itself. Some of the data recorded may include: * The NFT collection to peg value against * The direction of the collection's price prediction (long or short) * The USD liquidation value of the position, after fees * The amount of profit, expressed as a percentage * The amount of rewards earned | ![](/files/6MunsdguA2cLgkzw5H43) | ![](/files/9EmKD0yuMXEM1qOtvVlH) | | -------------------------------- | -------------------------------- | --- # 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.mimicry.org/whitepaper/protocol-architecture.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.