Upload multiple items sequentially.
Array of items to upload, each with data and a label.
Optionalsigner: PolkadotSignerOptional signer. When omitted, auto-resolved.
Optionaloptions: Omit<BatchUploadOptions, "gateway">Batch upload options (timeout, progress callback).
Check whether an account is authorized to store data on the Bulletin Chain.
Use as a pre-flight check before upload to provide clear UX instead of letting the transaction fail mid-execution.
SS58-encoded account address to check.
Authorization status with remaining quota.
checkAuthorization for the standalone function equivalent.
Check if a CID exists on the gateway.
Fetch raw bytes by CID.
Auto-resolves query path: host preimage lookup inside a container, direct IPFS gateway fetch standalone.
Optionaloptions: QueryOptionsFetch and parse JSON by CID.
Auto-resolves query path (same as fetchBytes).
Optionaloptions: QueryOptionsBuild the full gateway URL for a CID.
Upload data to the Bulletin Chain.
Raw bytes to store.
Optionalsigner: PolkadotSignerOptional signer. When omitted, auto-resolved (preimage in host, dev signer standalone).
Optionaloptions: Omit<UploadOptions, "gateway">Upload options (timeout, waitFor, status callback).
StaticcomputeCompute CID without uploading. Static — no instance needed.
StaticcreateCreate from an environment — resolves API via chain-client, gateway from known list.
StaticfromCreate from an explicit API and gateway (custom setups, testing).
StatichashReconstruct a CID from a 0x-prefixed hex hash. Static — no instance needed.
Useful for converting on-chain hashes back to CIDs for IPFS gateway lookups. Pass optional hash algorithm and codec to match the on-chain CID configuration.
OptionalhashCode: HashAlgorithmOptionalcodec: CidCodechashToCid for full documentation.
Ergonomic entry point for Bulletin Chain operations.
Bundles a typed Bulletin API (from chain-client) and an IPFS gateway URL so callers don't need to re-pass them on every call.
Both upload and query paths auto-resolve based on the environment:
fetchBytes/fetchJson) — inside a host container the host preimage lookup (with caching) is used; standalone falls back to direct IPFS gateway HTTP fetch.Example