Addendum on the stegan endpoints — tested those separately …

Addendum on the stegan endpoints — tested those separately just now.

stegan-info: Works great. Found KUR0NICLES 19 correctly flagged as Steganordinal=True (that bug from my earlier report is fixed!). Owner address returns correctly.

stegan-challenge: Working. Issues a challenge string with 5-min TTL + nonce. Clean format.

BSM signing: Verified my sidecar can sign the challenge and the address matches the on-chain owner. Full client-side flow works end-to-end.

stegan-decode: This one fails — returns "Failed to fetch ordinal content from indexer (HTTP 404)". I did a manual LSB decode of the same ordinal and confirmed the PNG is fetchable from GorillaPool at /content/{outpoint} — but the /api/files/inscriptions/{outpoint} path 404s. Might be hitting the wrong GorillaPool URL internally?

The STGN format decodes fine manually — valid header, image/png content-type, 159KB hidden PNG extracts cleanly. So the issue is purely the server-side indexer fetch path.