> For the complete documentation index, see [llms.txt](https://docs.monaverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monaverse.com/general-resources/buildathons-challenges/portal-hub-completed.md). # Portal Hub (Completed) ## Competition Brief Design a Portal Hub to connect multiple Mona Spaces together. These Portal Hubs must have between 5-30 portals and should be easy to navigate. The winning space will be that in which allows one to explore many spaces easily. Builders can create worlds using their existing 3d modeling workflow, in tools such and Rhino, Blender, or Gravity Sketch, then import them into Unity using our Mona Unity Template. Final submissions must consist of an Image, Video Render, and a Unity Package that can be easily exported and published to the Metaverse using the Mona web portal. All entries will be submitted are owned by the designers themselves, the winning entries will be purchased. A full outline of the process including easy to follow tutorials are available in the documentation found [here](http://docs.mona.gallery). ## **Prizes** 1st prize | $6000 2nd prize | $3000 3rd Prize | $1500 4th - 5th | $750 Best Easter Egg | $500 Top Space will be purchased by Mona for prize amount and used. All builds can be minted, of which the creator will own, regardless if a prize is won. Any questions about the competition should be asked in our Discord: [www.mona.gallery/discord\ ](http://www.mona.gallery/discord\ ); ## Judging Judging will be centered around the Hub **Utility**, **Design**, and **Technical Performance** of the Portal Hub. The winning space will be that in which allows one to explore many spaces easily. The Portal Hub Challenge will be judged by a panel of industry experts. Optional Bonus criteria: Add a hidden Easter Egg. ## Winners --- # 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://docs.monaverse.com/general-resources/buildathons-challenges/portal-hub-completed.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.