> For the complete documentation index, see [llms.txt](https://docs.gpu.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpu.net/gvex/trading-pairs.md). # Trading Pairs #### GPU/USDT The primary trading pair for the GPUNET ecosystem. $GPU is the native utility token that powers all interactions on GPUNet, including: * Paying for compute resources (AI inference, rendering, blockchain computations) * Staking for network rewards * Governance participation * Subnet operations Trading GPU/USDT allows participants to enter and exit the GPUNET ecosystem with stablecoin liquidity. #### Nodes/USDT Provider Nodes are NFT assets that represent operational infrastructure within the GPUNET network. Node holders can: * Operate as validators or GPU providers * Earn token rewards for contributing compute capacity * Build stackable node operations businesses * Participate in network governance **NFT Trading Mechanics**: Nodes are ERC-721 compliant NFTs that trade against USDT on GVEX. * Hardware specifications (GPU models, compute capacity) * Historical earnings * Operational status * Network reputation When trading Nodes, you're exchanging these operational assets directly on-chain. Settlement occurs instantly, and the NFT transfers to the buyer's wallet upon trade execution. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.gpu.net/gvex/trading-pairs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.