Blobpedia

Keyword/full-text search over the Celestia knowledge base (CIPs, Celestia/rollup/node docs, forum, whitepapers, blog, YouTube transcripts, celestiaorg GitHub issues/PRs, releases and Discussions). Celestia-specific — do NOT use for other blockchains (use the Ethereum or other-chain docs tool), the general web (use the web-search tool), other knowledge bases (use the dedicated RAG tool), or local files. Use this for exact-term or name lookups; use semantic_search for conceptual how-does-X-work questions, and get_doc to read a full page once you have its id.

Read the full text of one Celestia Improvement Proposal (CIP) by its id. Celestia governance docs only — not GitHub issues or arbitrary proposals (use a GitHub tool for those). Get the id from search or list_cips first.

Browse or filter Celestia Improvement Proposals (CIPs) by status (Draft, Review, Final) or type. Celestia governance proposals only — do NOT use this to list GitHub issues, pull requests, or proposals from other chains (use the GitHub MCP or that chains tool for those). Use get_cip to read one in full, get_cip_history for its status timeline, and get_cip_mentions for where it is discussed.

Read one Celestia community forum thread (forum.celestia.org) with its posts, by topic id. This is the CELESTIA FORUM channel — not GitHub Discussions (use get_github_discussion). The topic id is the number at the end of the thread link that search, get_recent_changes and the list tools print (https://blobpedia.org/discussions/2314 is topic 2314); that link is accepted as well.

Read the full text of one Celestia whitepaper or research PDF by slug. Celestia papers only — not arbitrary web PDFs (use a web-search tool for those). Call list_whitepapers first to get a valid slug.

List the Celestia whitepapers and research PDFs indexed here (slug plus title). Celestia-specific — not arbitrary web PDFs (use a web-search tool for those). Use get_whitepaper to read one by slug.

無需輸入參數。

Show which CELESTIA content is trending on blobpedia this week (most-viewed CIPs, forum threads, docs, etc.). This is a Celestia content-engagement signal only. It is NOT token price or market trends (for trending coins, gainers, or TIA price movement defer to the price/market MCP such as CoinGecko) and NOT general web or crypto-wide trends (defer to a web-search MCP). Only fire when the user is asking what is popular within Celestia content. Zero arguments.

無需輸入參數。

Read the FULL text of one indexed Celestia documentation page by id (Celestia node and developer docs plus partner docs) — exact commands, flags, and whole sections a search snippet truncates. Best for Celestia operational/how-to questions. Celestia docs only — not docs of other projects (use that projects docs tool) and not the web (use a web-search tool). Get the id from search or semantic_search first.

Show the status-change timeline of one Celestia Improvement Proposal (CIP) — when it moved Draft to Review to Final, etc. Celestia governance only. Needs a CIP id (from search or list_cips).

List file/PDF attachments of one Celestia Improvement Proposal (CIP) — e.g. signed vote records, supporting docs — by CIP id. Celestia governance only. Get the id from search or list_cips.

Find where a given Celestia Improvement Proposal (CIP) is referenced across blobpedia: forum threads, blog posts, celestiaorg GitHub issues and pull requests, and sibling CIPs. Celestia-specific cross-reference — use to see who is discussing a CIP and where. Needs a CIP id (from search or list_cips).

Timeline of what changed on Celestia recently across blobpedia (new/changed CIPs, forum threads, blog posts, GitHub releases, radar alerts), newest first. Celestia activity only — not a GitHub commit feed (use a GitHub tool) and not general crypto news (use a web-search tool). Use get_trending for what is popular rather than what is new.

Counts of CELESTIA CONTENT indexed by blobpedia (how many CIPs, forum threads, docs, videos, etc.). This is INDEX/catalog coverage of what blobpedia has cataloged, NOT live chain state. For LIVE on-chain metrics (block height, TIA supply, validators, cumulative blob data) or TIA price/market, use get_network_state on THIS server instead. Zero arguments.

無需輸入參數。

Live Celestia ON-CHAIN state + TIA market, fetched in real time (source: Celenium indexer + CoinGecko): mainnet block height, total TIA supply, validator count, cumulative blob data posted, total txs/accounts/namespaces, plus TIA price, market cap and 24h change. Celestia mainnet only — this is the LIVE on-chain/price layer, distinct from get_network_stats (which counts indexed CONTENT, not chain state). Use this for current/live chain questions or TIA price right now. Zero arguments.

無需輸入參數。

Browse the Celestia ecosystem catalog (rollups, DeFi, wallets, infrastructure, etc.), optionally filtered by category or keyword. Celestia ecosystem only — not a general crypto-project directory (use a web-search tool for that). Returns catalog entries, not live project data.

Browse rentable bare-metal servers for Celestia nodes (validator, bridge or Fibre) from the Unity Nodes Pulse datacenter catalog: 23 hosting providers, price and stock, location, CPU, RAM, NVMe, uplink and traffic terms, and Pulse's own compatibility verdict per node role (Compatible, Needs benchmark, Check caveats, Not compatible) with the reason. Filter by role, verdict, region, country, provider, price and hardware; cheapest first. Celestia node hosting only, not a general server search and not a quote: prices, stock and verdicts are a snapshot refreshed every 15 minutes. Servers that miss a role hardware or price floor are not listed for it, as on the Pulse page. mode real = what Unity Nodes recommends from its own measurements, docs = the larger official Celestia envelope. Fibre verdicts assume the launch-minimum stake: use size_fibre_node for yours. FDP = Celestia Foundation Delegation Program hosting rules. Use get_datacenter_offer for one server and list_datacenter_providers for the provider overview.

Full detail of one rentable server from the Pulse Celestia datacenter catalog, by the id that list_datacenter_offers prints: hardware, price and setup fee, upgrade options (storage, RAM, bandwidth tiers with prices), traffic terms, provider notes, the Pulse compatibility verdict with every reason for each node role in both the real and the docs envelope, the FDP hosting-rule verdict per role, how many Celestia validators already run on the same provider, and the provider status page incidents. Celestia node hosting only. A snapshot, not a quote: confirm price and stock on the provider order page. The id changes when a provider changes the configuration, so an id from an old answer may be gone.

Overview of the hosting providers in the Pulse Celestia datacenter catalog: how many servers each lists, how many Pulse lists for each node role and how many of those are Compatible, regions, price range for validator servers, bandwidth billing, the FDP hosting rule, how many Celestia validators already run there and whether the provider status page shows open incidents. Use it to choose a provider before browsing servers with list_datacenter_offers. Celestia node hosting only. Provider data is a snapshot refreshed every 15 minutes from Pulse.

Size the extra hardware a Celestia Fibre node needs on top of a validator, from the validator's share of voting power: storage rows, disk, sustained ingress, monthly inbound traffic, RAM and the uplink to order. A port of the Celestia Foundation's public Fibre calculator as Pulse implements it, calibrated to Mocha. The november_preview throughput is an UNCONFIRMED estimate, not an official Celestia figure. A sizing calculator, not live network data; the output links to the Pulse page that lists the servers for this plan.

List Celestia validators with their current numbers from Unity Nodes Pulse: status (active set, inactive, jailed), voting power, stake, commission, missed block proposals over 24 hours, 7 and 30 days, and the 30-day change of voting power. Mainnet or the Mocha testnet. Filter by status or name; sort by voting power, commission, missed proposals or voting-power change. Celestia validators only, from a snapshot refreshed every 15 minutes. Missed proposals are the health signal Pulse uses; Celestia commits blocks at two thirds of voting power, so a validator missing a signature is not necessarily down. Monikers are typed by the validators and marked untrusted. Use get_celestia_validator for one validator.

Everything Unity Nodes Pulse knows about one Celestia validator: status, voting power and stake, commission, missed block proposals over 24 hours, 7 and 30 days, signature participation over 7 days, voting-power change over 24 hours, 7 and 30 days, where it is hosted when Pulse could place it, and whether it has signalled for the pending network upgrade. Look it up by operator address (celestiavaloper...) or by name; a partial name that matches several validators returns the candidates. Mainnet or the Mocha testnet. Celestia only, from a snapshot refreshed every 15 minutes. Names are typed by the validators and marked untrusted.

Operator view of how the Celestia network is doing right now, from Unity Nodes Pulse: latest block and the measured block time, throughput, staking, the validator set (active, inactive, jailed, online voting power), how full recent blocks are and which validators produced them, which rollups posted the most data, the DA light-node measurements Unity Nodes takes (network and local head, sampling lag, header arrival lag) and the official status page. Mainnet or the Mocha testnet (block fullness, rollups and the status page are mainnet only). Celestia only, a snapshot refreshed every 15 minutes. For live on-chain totals and the TIA price use get_network_state.

Where the next Celestia network upgrade stands, from Unity Nodes Pulse: the app version being signalled and the current one, how much voting power has signalled against the threshold, whether the threshold is reached and the block the upgrade activates at with the date estimate Pulse gives and the block time it rests on, the latest stable release Pulse recommends, the largest validators that have not signalled, governance proposals (active and recent, with vote tallies) and the history of hard forks. Mainnet or the Mocha testnet (hard-fork history is mainnet only). Celestia only, a snapshot refreshed every 15 minutes. For release notes and the version to install use get_latest_release and get_breaking_changes.

Celestia staking economics and what it costs to run a validator, from Unity Nodes Pulse: staking APR, inflation, the share of supply that is staked, annual provisions, Pulse's reference monthly server costs per hosting provider (minimum, recommended and archive tiers), the stake at which a validator on each provider breaks even at an assumed 20% commission, and the estimated monthly operator earnings of the largest validators. Mainnet only, a snapshot refreshed every 15 minutes. The reference hardware prices are curated by Unity Nodes and can lag the market: for live server prices use list_datacenter_offers. For the TIA price use get_network_state.

無需輸入參數。

What the Celestia nodes that Unity Nodes runs actually use, measured on its own servers and shown beside Celestia's recommended hardware, from Unity Nodes Pulse: CPU cores, RAM of the processes, page cache, data size and its change per day, free disk and network for each node role (validator, consensus node, bridge, Fibre, light node), as median, 95th percentile and maximum over 1, 7 or 30 days. Measured values, with two clearly labelled estimates kept apart from them (a straight-line projection of each node's data size and the Celestia Foundation's Fibre calculator for Unity Nodes' voting power): a role Unity Nodes does not run is said to have no measurements (there is no Fibre on mainnet yet), the chain's own load in the same window (block data per second) with a correlation r of each node's CPU, network and disk load with it (a link in how they moved, not a cause; shown once four hours overlap), and the answer says how much of the window the samples fill, so early figures are provisional. For what Celestia's documentation requires, use search or get_doc ("Hardware requirements"); for servers that meet it, list_datacenter_offers; for an estimate of Fibre load, size_fibre_node. Celestia only.

How concentrated Celestia validation and data availability are, from Unity Nodes Pulse: the hosting providers and countries that carry the most validator voting power, how much voting power has no known host, and the public bridge nodes (status, version, uptime, host). Mainnet or the Mocha testnet (bridge nodes are mainnet only). Celestia only, a snapshot refreshed every 15 minutes. Host names come from a network crawl and can be wrong for validators that sit behind sentries. To choose where to run a node use list_datacenter_providers.

The Unity Nodes validator guide for Celestia (moved here from runcelestia.xyz): the path to an active validator in three phases, the ten setup steps, operator gotchas, and the FAQ and common errors with their fixes. Every item names the Celestia docs page it was checked against, says whether the docs or the chain confirm it (verified) or it is operator experience (partial), and records where the docs or the chain disagree with the guide: those win over the guide. For exact commands and requirements use the official docs (search or get_doc); for the live state of the network get_celestia_network_health and get_celestia_upgrade_status; for choosing a server list_datacenter_offers; for what Unity Nodes' own nodes measure get_celestia_hardware_usage.

Resources curated by Unity Nodes validators (moved here from unityhub.dev/celestia): endpoints, explorers, monitoring, services, tools, faucets, articles, videos and learning material for node operators (page validator), builders (developers), the community and people learning about Celestia (education). Called with no arguments it lists every page and section with its size; pass page and section to read one, network to keep one network, query to find words in labels, titles, descriptions and URLs. What a linked page says about itself is third-party text and is fenced. For peers, seeds and snapshots of the live network use get_celestia_operator_toolkit.

What a Celestia node operator needs to bootstrap and keep a node healthy, from Unity Nodes Pulse: persistent peers and seeds, snapshot and address-book mirrors, state-sync servers with the current trust height and hash, the auto-upgrade script, the Unity Nodes pruned snapshot with its restore and verify procedure, and the health of public RPC, REST and gRPC endpoints (status, latency, app version). Mainnet or the Mocha testnet. Celestia only, curated lists plus a probe refreshed every 15 minutes. The restore procedure deletes the node data directory: read it before running anything. Endpoint status is what Pulse measured from its own server.

Is Celestia Fibre ready? Status of the Celestia Fibre network (CIP-51, validator-operated blob publishing) from Cumulo's open Fibre Network Monitor: whether enough stake has a ready Fibre host to reach the 2/3 threshold, how many validators registered a host and are ready, how fast each probe region reaches 2/3, how many validators, hosting providers or countries could fail before ready stake drops below 2/3, validators still missing a host, fee and escrow parameters, whether validators keep the data they signed, the network history, and Cumulo's weekly and monthly reports. Cumulo monitors the Mocha testnet (mocha-5) today. Figures are measured and computed by Cumulo from probes in several regions and relayed unchanged, with Cumulo credited. Pick a view: overview, quorum, liveness, concentration, missing, payments, retention, method, history or report. Validator names are typed by the validators and marked untrusted. For one validator use get_fibre_validator; for blobs and fees use get_fibre_blob_market. For the hardware a Fibre node needs use size_fibre_node.

List the validators of the Celestia Fibre network with Cumulo's measurements: whether each registered a Fibre host and is ready, stake rank and share, typical round trip, uptime over 24 hours, 7 and 30 days, and where the host runs (country, hosting provider). Mocha testnet (mocha-5). Filter by registered or not, status, name, country or provider; sort by stake, latency, uptime or name. From a snapshot refreshed every 15 minutes of an open API by Cumulo, credited in each answer. Validator names and hosts are typed by the validators and marked untrusted. Use get_fibre_validator for one validator with its signing record, data retention, probes and diagnosis.

Everything Cumulo's Fibre Network Monitor measures for one Celestia validator on the Mocha testnet (mocha-5): whether its Fibre host is registered and ready, where it runs, round trip from each probe region, uptime, how often it signed blobs, whether it keeps the data it signed, certificate identity, flags and, when something is wrong, Cumulo's diagnosis. Look it up by name, operator address (celestiavaloper...) or consensus address (celestiavalcons...). Optionally add live sections from Cumulo: status (ready right now), history (hourly uptime and round trip), blobs (which blobs it signed, did not need to sign, or could not), checks (latest download checks). Not signing a blob is not a failure when the publisher already had 2/3; only "not ready" is. Names, hosts and certificate names are typed by the validators and marked untrusted. Use list_fibre_validators to find validators.

Who pays for Celestia Fibre blockspace and how much: blobs settled, bytes, fees in TIA, blob size distribution, the on-chain fee formula and Cumulo's check of every charge against it, the publishers (accounts that pay) with their share of bytes and fees, price per MiB, escrow balances and withdrawals, the namespaces posting data, and blob activity over time. From Cumulo's open Fibre Network Monitor on the Mocha testnet (mocha-5); testnet TIA, not a mainnet price. Choose the period: 24h, 7d, 30d or all. Give an account (celestia1...) to see one publisher live: its blobs, namespaces, escrow deposits and withdrawals. Namespace names are bytes chosen by the publisher and marked untrusted. For individual blobs use list_fibre_blobs; for validators use get_fibre_validator.

List the latest blobs published through Celestia Fibre with who signed them: time, namespace, size, fee in TIA, signatures against the validator set, share of stake that signed and whether it reached 2/3, best probe region, and whether Cumulo could prove the data is available by sampling rows. Mocha testnet (mocha-5), newest first. Without filters this is a snapshot refreshed every 15 minutes; with a namespace, payer or validator filter, or more than 25 blobs, it is fetched live from Cumulo. Namespace names are chosen by the publisher and marked untrusted. Use get_fibre_blob for one blob with its signers.

One Celestia Fibre blob settled on the Mocha testnet (mocha-5), live from Cumulo: when and at what height it settled, who paid and how much, namespace, size, how many validators signed and the share of stake, whether it reached 2/3 (exact integer check by Cumulo), how many validators signed, were not needed or were not eligible, the payment promise and the retention deadline, and Cumulo's availability check by sampling rows. Look it up by the id from list_fibre_blobs ("<txhash>:<message index>"), by transaction hash or by blob id. Namespace names are chosen by the publisher and marked untrusted.

List what happened on the Celestia Fibre network (Mocha testnet, mocha-5), newest first: blob payments, validators registering or leaving their Fibre host, status changes, host reconfirmations and escrow deposits, as recorded by Cumulo's Fibre Network Monitor. Without filters this is a snapshot refreshed every 15 minutes; with a type or validator filter, or more than 50 events, it is fetched live from Cumulo. Event titles quote names typed by validators and publishers and are marked untrusted. For one validator's whole record use get_fibre_validator.

Search the Celestia Fibre history kept by Cumulo (Mocha testnet, mocha-5), live: give a transaction hash, blob id or commitment, a block height, an account (celestia1...), a namespace, a validator (name, celestiavalcons1... or celestiavaloper1...) or a UTC day (YYYY-MM-DD) and get the blobs, events, validators or the daily totals that match, with the archive files of a day. Use it when you hold an identifier and do not know what it is. For the latest blobs or events without an identifier use list_fibre_blobs or list_fibre_events. Names in results are typed by validators and publishers and marked untrusted.

List the GitHub repositories that blobpedia has INDEXED for Celestia, with item counts. Read-only view of the Celestia index on this server — does NOT browse your GitHub account or arbitrary repos (use a dedicated GitHub tool for that). Zero arguments.

無需輸入參數。

List GitHub Discussions from Celestia repos (e.g. celestiaorg/docs) cached on this server, ranked by upvotes then recency. Celestia repos only, from the local cache — not arbitrary GitHub Discussions (use a dedicated GitHub tool for those). Use get_github_discussion for the full body plus comments of one thread; this is GitHub Discussions, not the community forum (use get_discussion).

Read one Celestia GitHub Discussion (celestiaorg/docs and other Celestia repos) cached on THIS server — full body plus comments — by an id you got from list_github_discussions on this server. Celestia cache only: if the id was not returned by this servers list_github_discussions, or the request is just a raw GitHub node id (e.g. D_kw...) with no Celestia context, this is NOT the tool — use a dedicated GitHub tool for arbitrary GitHub Discussions. This is GitHub Discussions, not the community forum (use get_discussion). Pair it with list_github_discussions, which supplies the valid ids.

Get one Celestia-related YouTube video cached on this server (metadata plus transcript), by video id. Celestia-only cache — does NOT fetch arbitrary YouTube videos or search YouTube at large (use a dedicated YouTube tool for that). Find ids via list_videos or search.

Browse Celestia-related YouTube videos cached on this server, filtered by channel/date/transcript availability. Celestia-only cache — does NOT search YouTube at large (use a dedicated YouTube tool for that). Metadata only; use get_video for the transcript of one video by id.

Who runs Celestia: leadership and team members of the Celestia Foundation and Celestia Labs — names, roles and background — plus the headline figures from the official celestia.org About page. Use for "who is the CEO/CTO", "who works on Celestia", or team-background questions. People and org facts only — this is NOT Celestia documentation (use search or get_doc), NOT CIPs or their discussion (use list_cips/get_cip and get_cip_mentions), and it holds no grant-programme, board-seat or membership records.

Semantic (meaning-based) search over the Celestia knowledge base (CIPs, Celestia/rollup/node docs, forum, whitepapers, blog, releases, ecosystem, YouTube transcripts, celestiaorg GitHub issues/PRs). Celestia-specific — do NOT use for other blockchains (use the Ethereum or other-chain docs tool), the general web (use the web-search tool), other knowledge bases (use the dedicated RAG tool), or local files. Use this for conceptual how-does-X-work questions; use search for exact-term or name lookups, and get_doc to read a full page once you have its id.

Personalized onboarding for building ON CELESTIA — running a node, posting a blob, or deploying a rollup that uses Celestia for data availability. ALWAYS use this when a developer asks how to get started or build ON CELESTIA (prefer it over the Celestia search tool for those questions). ASK the user about their background FIRST (rollup_dev, node_operator, app_dev, researcher, new_to_celestia), then return a path with docs.celestia.org links. Celestia-only — NOT for getting started with non-Celestia frameworks, languages, or dev tools (React, Node.js, generic blockchain onboarding, etc.); for those defer to a general docs or web-search tool.

Full-text search across blobpedia's indexed GitHub issues across Celestia repos. Celestia ecosystem only. Use to find prior reports, open bugs, or requested features. For a broader cross-corpus search use the `search` tool with type="github".

Search blobpedia's indexed Celestia talks/videos (YouTube transcripts). Celestia-specific. Returns matches across title + transcript with a short snippet around the hit.

Search across release-notes bodies of all indexed Celestia repos for a feature/keyword. Celestia-specific. Use to find which release first mentioned X.

What a Celestia node operator has to know and do for each consensus app version, from the official release notes: required OS and glibc, binary and multiplexer changes, config changes, KMS and signer changes, pruning, Fibre setup. Official text relayed as published, not a summary; for a version the official page does not cover yet (the newest), the Upgrade Notice of the latest stable celestia-app release. Give from_version (the version you run now) and to_version to get every version in between, only to_version for one version, or nothing for the newest. Celestia only. Which version mainnet runs now and where the upgrade signal stands: get_celestia_upgrade_status.

Surface release notes likely to contain security or CVE fixes. Celestia-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords.

Surface forum posts authored by top-volume Celestia forum contributors (likely maintainers/core team) on a topic. Celestia-specific. Use when you want to weight expert voices over the general forum.

Look up one GitHub issue or PR by repo + number. Celestia repos only.

Find Celestia code snippets in forum posts on a topic. Filters forum_posts where the rendered HTML contains `<pre>` or `<code>` blocks AND matches the topic keyword. Celestia-specific.

Rank likely Celestia experts on a topic across blobpedia: forum activity matching the topic, plus overall forum volume of that author. Celestia-specific.

Map ecosystem_projects matching a topic to the GitHub repos that mention them, building a quick "who references these projects" picture. Celestia-specific. Useful for "who else is building around X?".

Given one Celestia ecosystem project, find others with complementary tags/category that could plug in. Celestia-specific. Lightweight heuristic: overlap of tags + adjacent categories.

Paste a Celestia ERROR MESSAGE, stack trace, or error code and get the most likely resolved fixes from blobpedia history: forum threads where the same error was discussed, and related GitHub issues (each with its own date). Needs a literal error string or code; do NOT use it for symptom descriptions with no error text (e.g. "my node won't sync"), use semantic_search for those. Celestia-specific. Returns top matches from forum and github.

Compare two versions of one Celestia repo and return the release notes between them, plus any forum threads near the release window. Celestia-specific. Use when a developer is planning an upgrade and asks "what breaks moving from X to Y?". Pass version strings as they appear in github_releases tags (with or without the leading "v").

Walk the CIP `requires:` graph from a starting CIP or PR draft. Returns the full chain of prerequisites that must reach a settled status before the starting proposal becomes implementable, with each prerequisite's current status. Accepts both merged CIPs ("CIP-0005", "5") and open-PR drafts ("PR-203"). Celestia governance only. Use when planning around a CIP that hasn't shipped yet.

Fetch the release-notes body for one version across celestia-app / celestia-node / celestia-core / rollkit / celestia-openrpc. Celestia-specific. Returns the rendered release body with a link to the GitHub release.

Surface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, plus open GitHub issues. Answers "is anyone else hitting this?". Celestia-specific. Does NOT return fixes, solutions, config, or how-to steps, and returns nothing when no open issue matches; for "how do I fix / configure / why does X happen" use semantic_search (then get_doc) instead.

Given a Celestia feature or capability description, find the matching CIP(s) by searching titles and bodies. Celestia-specific. Use to answer "is there a CIP for X?".

Get the single latest release (version tag, publish date, and GitHub release-notes link) for ONE NAMED Celestia repo: app, node, core, rollkit, or openrpc. Celestia-specific. Requires a package name as input.

Get the Celestia Radar, blobpedia's curated feed of time-sensitive ecosystem alerts: breaking changes, upgrade deadlines, protocol changes and required node-operator/rollup actions, each with deadline, affected components and source link. Filter by level (critical/important/ecosystem/all). Celestia-only. Use when a user asks what's changing, what's about to break, or what deadlines are approaching on Celestia.

Find Celestia ecosystem projects most similar to a free-text description by matching across title + category + description + tags. Celestia-specific. Useful before proposing a project to check overlap with what already exists.

Find contradictions between docs, forum and GitHub on a topic. Returns counts of how each surface talks about it plus the most recent doc-page and forum statement so the caller can spot mismatches.

Construct a structured Celestia onboarding sequence for a stated goal: whitepaper → relevant docs → CIPs to know → forum starter threads → talks. Celestia-specific. Topic-driven (distinct from get_started_guide, which is background-driven).