> For the complete documentation index, see [llms.txt](https://planetary-defense-guide.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://planetary-defense-guide.gitbook.io/guide/wax-blokchain/readme.md). # What is the WAX Blockchain A quick introduction to the WAX blockchain, the network Planetary Defense and its NFTs run on. WAX (short for Worldwide Asset eXchange) is a blockchain built specifically for NFTs, gaming, and digital collectibles, rather than being a general-purpose chain adapted for that use. Every NFT in Planetary Defense lives on WAX, so understanding it will help you get the most out of the game.
### Built for NFTs, not adapted for them Most NFT projects run on general-purpose blockchains like Ethereum, which were designed for smart contracts in general and have gas fees and network congestion as a result. WAX was designed from the ground up around a single use case: letting people create, own, and trade digital assets. It has its own native NFT standard built for tradeable, on-chain collectibles, plus tools like AtomicHub that make minting and trading straightforward without needing to write any code. That's why so many games build their NFTs on WAX rather than a general-purpose chain, Planetary Defense included. ### Fast, and free to use WAX runs on Delegated Proof of Stake (DPoS): instead of miners competing to solve puzzles, a set of elected block producers called WAX Guilds take turns confirming transactions, with a new block roughly every half second. This means confirmations are near-instant, and — unlike most NFT blockchains — regular transactions on WAX don't cost gas fees for players. For a game like Planetary Defense, that means trading, crafting, and moving NFTs around doesn't cost you anything beyond the in-game resources involved. ### Why WAX over other blockchains Compared to general-purpose smart contract chains, WAX offers a few concrete advantages for NFT-based games: * No gas fees: you don't pay to trade, craft, or move NFTs, unlike most Ethereum-based games * Fast confirmations: blocks land roughly every half second, instead of waiting minutes for a transaction to confirm * Purpose-built NFT tooling: an on-chain standard designed for tradeable collectibles, plus marketplaces and wallets built specifically around it * Energy efficient: WAX's consensus model uses a small set of validators rather than mass computation, so it's far more energy efficient than proof-of-work chains like Bitcoin, and the network is certified carbon neutral * Low barrier to entry: wallets are free to create and don't require you to already hold cryptocurrency to get started This is why Planetary Defense is built on WAX: it lets you truly own your NFTs as on-chain assets, and trade or use them without fees getting in the way. Next, let's set up the wallet you'll need to hold them. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://planetary-defense-guide.gitbook.io/guide/wax-blokchain/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.