Skip to content

Media blobs

Boing stores content-addressed media blobs on L1 (NFT media and related workloads). Admission and caps are height-gated; clients should call boing_getMediaBlobParams before large puts.

From a probe of boing_getMediaBlobParams:

FieldValue
activationHeight1200
activetrue
phase7CapActivationHeight1306
phase7CapActiveAtTiptrue
effectiveMaxBytesAtTip268435456 (256 MiB)
maxBytes (baseline field)Still reports the smaller baseline; effective tip cap is what matters for admission

Operators must keep identical activation / PHASE7 env across validators; partial rolls fork admission. Fly public testnet coordinates admission at height 1200; PHASE7 cap at 1306.

MethodUse
boing_getMediaBlobParamsCaps, activation, gas / checklist knobs
boing_getBlobMeta / boing_getBlobMetadata / bytes
boing_getBlobAccessAccess / ACL-related metadata
DAS / sample / serve-challenge methodsAvailability sampling and challenges

Wallet publish sessions for PutBlob (boing_requestPutBlobSession) are an Express-side flow, not a boing-node JSON-RPC method.

Phase 34 introduces deployer-owned download ACL behavior (wallet proof for publisher / grantee; operator token override paths on explorer). Product details: monorepo docs/BOING-L1-MEDIA-BLOBS.md and docs/HANDOFF_BLOB_DOWNLOAD_ACL.md. Observer streams bytes via its own /api/blob/download path when authorized.

Several PHASE checklist items remain scaffolded (for example ReservedRealV1 verifier, optional BLS committee flip). Treat opaque DAS proofs as not full availability evidence until verify is implemented. Re-read capActivationChecklist on the live params object before ops changes.