2026-04-09 to 2026-04-15 · run 20260416T144633Z
docs.wal.app recorded 11,795 unique visitors and 18,625 pageviews for Apr 9–15, 2026, with Walrus Sites intro and getting-started pages driving the most traffic. Kapa analysis of 65 conversations reveals that blob enumeration limitations, mainnet setup friction, and blob/object ID confusion are the most pressing developer pain points. Immediate documentation improvements to onboarding, blob enumeration guidance, and access control clarity are the highest-leverage actions this sprint.
Evidence: 17 of 65 Kapa conversations (26%) concerned the absence of a public blob enumeration API and pruned RPC event history.
Interpretation: Developers are blocked or wasting time because this critical limitation is undocumented or hard to find.
Action: Publish a dedicated doc section on archive RPC requirements with a tested Python enumeration snippet.
Evidence: 13 of 65 Kapa conversations covered first-time mainnet setup, private key import, and CLI version mismatches.
Interpretation: Lack of an end-to-end mainnet onboarding guide forces developers to resolve setup issues via chatbot.
Action: Create a single mainnet quickstart page covering Sui CLI init, key import, and Walrus config sequentially.
Evidence: Combined /walrus-sites/intro variants attracted ~4,211 visitors with 100% scroll depth this week.
Interpretation: Developers are deeply engaged with Walrus Sites content, indicating high product interest and documentation demand.
Action: Add next-step navigation links and deeper component/storage guides directly from the Walrus Sites intro page.
Evidence: 10 chatgpt.com-referred visitors averaged 161 seconds per session, versus 38 seconds site-wide.
Interpretation: AI-referred users arrive with specific, complex questions and need more comprehensive documentation to self-serve.
Action: Ensure the most-asked Kapa topics have dedicated, easily discoverable doc pages for AI-assisted discovery.
Evidence: 4 Kapa conversations specifically reported retrieval failures caused by conflating NFT Object IDs with Walrus Blob IDs.
Interpretation: Without a clear visual distinction, developers will continue making this ID-mapping mistake in production.
Action: Add an annotated diagram distinguishing Blob IDs from Sui Object IDs on the blob retrieval reference page.
Why it matters: No public enumeration API exists and pruned RPC nodes silently return empty results, blocking developers.
Recommended doc action: Add a doc section on archive RPC requirements and include a tested Python enumeration snippet.
Why it matters: First-time setup failures and CLI mismatches are the leading onboarding barrier for new developers.
Recommended doc action: Create an end-to-end mainnet onboarding guide covering Sui CLI init, key import, and Walrus config.
Why it matters: Confusion over CLI vs HTTP API vs SDK prevents developers from choosing the right storage method.
Recommended doc action: Add a comparison page with code examples summarizing all storage methods and when to use each.
Why it matters: Public-by-default storage surprises developers expecting private blobs, risking unintended data exposure.
Recommended doc action: Add a prominent public-by-default warning and link to a concise Seal access-control FAQ.
Why it matters: Sui vs Walrus epoch confusion causes incorrect storage cost estimates and missed renewal windows.
Recommended doc action: Add an epoch duration reference table and live epoch status link prominently in the docs.
Why it matters: Developers cannot optimize storage costs without clear guidance on Quilt limits and savings.
Recommended doc action: Create a dedicated Quilt FAQ covering size limits, cost savings, and blob management differences.
Why it matters: ID conflation causes retrieval errors that are difficult to debug without an explicit explainer.
Recommended doc action: Add a diagram distinguishing NFT Object IDs from Walrus Blob IDs with concrete lookup examples.
Scope: New standalone page covering Sui CLI init, private key import, Walrus config, and first blob upload.
Why now: 13 Kapa conversations this week confirm setup friction is the top onboarding blocker.
Expected impact: Reduces mainnet setup support volume and improves getting-started page conversion.
Scope: New doc section explaining enumeration limitations, archive node requirement, and a tested Python snippet.
Why now: 17 conversations—26% of all Kapa traffic—were blocked by this undocumented limitation.
Expected impact: Unblocks the largest single Kapa pain point and reduces repeat chatbot queries.
Scope: Inline warning on blob storage pages plus a concise linked Seal access-control FAQ page.
Why now: 10 Kapa conversations show developers are unaware of default public visibility.
Expected impact: Prevents accidental data exposure and reduces Seal-related support questions.
Scope: Single page comparing CLI, HTTP API, and SDK storage with code examples and decision guidance.
Why now: 11 Kapa conversations reflect confusion about which storage method to use and when.
Expected impact: Reduces retrieval and storage confusion, improving developer confidence and time-to-first-blob.
Scope: Annotated diagram on the blob retrieval reference page distinguishing the two ID types with examples.
Why now: Retrieval failures from ID conflation are silent and hard to debug without visual guidance.
Expected impact: Eliminates a common retrieval error class and reduces Kapa questions on this topic.
Scope: New FAQ covering Quilt size limits, cost savings vs standard blobs, and management differences.
Why now: 7 Kapa conversations ask Quilt basics that have no consolidated reference today.
Expected impact: Enables cost-conscious developers to adopt Quilt without requiring chatbot assistance.
Scope: Prominent table on homepage or overview page showing Sui vs Walrus epoch durations with a live status link.
Why now: 7 Kapa conversations show persistent epoch confusion affecting storage cost planning.
Expected impact: Reduces epoch-related questions and improves storage duration planning accuracy.
Scope: Add contextual next-step links to component docs and storage guides directly from /walrus-sites/intro.
Why now: 4,211 visitors with 100% scroll depth reach the page bottom with no clear onward path.
Expected impact: Increases pages-per-session for the highest-traffic content page and reduces drop-off.
Plausible and Kapa raw JSON were fetched and analyzed automatically before this report was rendered.