walrus-sites-portal

What problem does it solve?

Running Walrus Sites locally for testnet requires a correctly configured portal, and common issues like 404s, port conflicts, and misunderstanding original_package_id can block you from viewing your sites.

Core Features & Use Cases

• Testnet portal setup: Clone the Walrus Sites repo, install dependencies, copy the testnet config, and start the portal to view testnet sites locally.
• 404 and misconfiguration troubleshooting: Diagnose Page not found errors by checking blob expiration, verifying original_package_id, and confirming the correct site object URL/subdomain.
• Portal architecture and routing understanding: Explain how base36 subdomains map to Sui site objects and how dynamic fields lead to Walrus blob retrieval and serving content.
• Operational guardrails: Provide specific rules like keeping original_package_id unchanged and running the start command from the correct directory.
• Use case: You have a testnet site and visit a base36 subdomain expecting content, but you see 404; use this skill to verify config correctness, confirm the site object type, and fix the workflow.

Quick Start

Ask the AI: how do I run the local Walrus Sites portal for testnet and troubleshoot a Page not found error on my base36 site URL?