> For the complete documentation index, see [llms.txt](https://docs.peeplet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peeplet.com/platform.md). # The Platform ## Ownership Peeplets are ERC-721 tokens on Ethereum under the collection name Peeplet (PEEP). * **Eggs.** Every Peeplet begins as an egg, minted through OpenSea SeaDrop or in the app. * **The hatch.** Hatching is a real on chain event. The owner submits the hatch transaction, and a signed authorization commits the outcome to the token forever. What your egg became is part of the token, not a database row. * **Traits.** Each Peeplet carries its look (body, eyes, headgear, gadgets, and more) as token traits, rendered consistently on marketplaces and in the world. * **Royalties and metadata** follow the ERC-2981 and standard collection metadata conventions, so Peeplets behave well everywhere NFTs are traded. ## One Shared World The valley is a single networked multiplayer world. There is no offline mode and no private copy: every visitor sees the same Peeplets living the same lives. * **The world server** runs the authoritative simulation: creature movement, farming, weather, day and night, and every Peeplet mind. * **The web app** at peeplet.com is the front door: wallet connection, your roster, and the game itself, playable in the browser with nothing to install. * **Owners join, everyone watches.** Connecting a wallet that holds a Peeplet lets you enter the world alongside it. Visitors without one can still watch the valley live. ## Fair by Construction Because Peeplets act for themselves, there is nothing to bot and no grind to automate. Progress belongs to the world, not to whoever clicks fastest. Ownership gates identity (which Peeplet is yours), never power. --- # 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.peeplet.com/platform.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.