{
  "version": 1,
  "reviewed": "2026-10-29",
  "scope": "Curated research notes, not an exhaustive network registry. Historical announcements retain their dates.",
  "records": [
    {
      "id": "lazy",
      "title": "The LazyLedger origin",
      "category": "History",
      "text": "Mustafa Al-Bassam published LazyLedger in May 2019. The design separates data ordering and availability from application-specific transaction execution.",
      "url": "https://arxiv.org/abs/1905.09274",
      "date": "2019-05-22",
      "kind": "Research paper",
      "reviewed": "2026-10-29",
      "related": []
    },
    {
      "id": "mainnet",
      "title": "Mainnet Beta launches",
      "category": "History",
      "text": "Celestia Mainnet Beta launched on 31 October 2023 at 14:00 UTC under the codename Lemon Mint. This date records launch, not the start of every ecosystem service.",
      "url": "https://blog.celestia.org/celestia-mainnet-is-live/",
      "date": "2023-10-31",
      "kind": "Launch announcement",
      "reviewed": "2026-10-29",
      "related": []
    },
    {
      "id": "orbit-history",
      "title": "Arbitrum Orbit integration announced",
      "category": "History",
      "text": "The Celestia and Arbitrum foundations announced an Orbit and Nitro integration in October 2023. The announcement establishes a historical integration, not the current operating state of every Orbit chain.",
      "url": "https://blog.celestia.org/celestia-is-first-modular-data-availability-network-to-integrate-with-arbitrum-orbit/",
      "date": "2023-10-25",
      "kind": "Integration announcement",
      "reviewed": "2026-10-29",
      "related": [
        "nitro"
      ]
    },
    {
      "id": "shwap",
      "title": "Shwap changes DA networking",
      "category": "History",
      "text": "Shwap introduced a new DA messaging protocol and storage system. Its October 2024 announcement reported faster sampling and reduced storage in tests; those reported gains are not measurements by StakeUs.",
      "url": "https://blog.celestia.org/shwap/",
      "date": "2024-10-15",
      "kind": "Upgrade announcement",
      "reviewed": "2026-10-29",
      "related": [
        "das"
      ]
    },
    {
      "id": "ginger",
      "title": "Ginger targets faster blocks",
      "category": "History",
      "text": "The Ginger announcement described celestia-app v3 reducing the then-current 12-second block target to six seconds and preparing support for larger blocks. This is historical upgrade context, not today\u2019s measured cadence.",
      "url": "https://blog.celestia.org/ginger/",
      "date": "2024-10-24",
      "kind": "Upgrade announcement",
      "reviewed": "2026-10-29",
      "related": []
    },
    {
      "id": "lotus",
      "title": "Lotus adds native interoperability",
      "category": "History",
      "text": "Lotus was announced as the v4 upgrade with Hyperlane integration and changes to issuance and staking rewards. The announcement date is distinct from network activation.",
      "url": "https://blog.celestia.org/lotus/",
      "date": "2025-05-19",
      "kind": "Upgrade announcement",
      "reviewed": "2026-10-29",
      "related": [
        "hyperlane"
      ]
    },
    {
      "id": "fibre-history",
      "title": "Fibre is introduced",
      "category": "History",
      "text": "The January 2026 Fibre announcement described a separate high-throughput DA protocol operated by Celestia validators. Its 1 Tb/s headline is an announced protocol performance claim, not live traffic measured here.",
      "url": "https://blog.celestia.org/introducing-fibre-1tb-s-of-blockspace/",
      "date": "2026-01-13",
      "kind": "Protocol announcement",
      "reviewed": "2026-10-29",
      "related": [
        "fibre"
      ]
    },
    {
      "id": "das",
      "title": "How data availability sampling works",
      "category": "Network",
      "text": "Light nodes sample shares of erasure-coded block data and check proofs. Successful samples provide probabilistic evidence of availability without downloading the full block. This does not validate an application\u2019s execution.",
      "url": "https://docs.celestia.org/learn/celestia-101/data-availability/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "namespace",
        "bridge"
      ]
    },
    {
      "id": "namespace",
      "title": "Namespaced Merkle trees",
      "category": "Network",
      "text": "Namespaces let applications retrieve relevant data and its proofs instead of all applications\u2019 transaction data. Namespaces organize data; they do not by themselves identify a company or establish ownership.",
      "url": "https://docs.celestia.org/learn/celestia-101/data-availability/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "das"
      ]
    },
    {
      "id": "bridge",
      "title": "What a DA bridge node does",
      "category": "Network",
      "text": "A Celestia DA bridge connects consensus data to the data-availability network. It is different from a token bridge. StakeUs Atlas maps only explicitly inventoried DA bridge identities, not every libp2p peer.",
      "url": "https://docs.celestia.org/operate/data-availability/bridge-node/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "ibc",
        "das"
      ]
    },
    {
      "id": "fibre",
      "title": "Fibre and ordinary L1 blobspace",
      "category": "Network",
      "text": "Fibre sends encoded shards directly to validator-operated servers and settles a commitment on chain. It suits larger, short-lived data; L1 blobspace supports the existing sampling path. They have different retrieval and retention properties.",
      "url": "https://docs.celestia.org/build/post-retrieve-blob/fibre/when-to-use/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "retention",
        "buffers"
      ]
    },
    {
      "id": "retention",
      "title": "Fibre is not permanent storage",
      "category": "Operations",
      "text": "Fibre retention ends after the later of the configured retention interval from promise creation or the promise expiry. The documented default is four hours. Applications needing longer availability must preserve their own data.",
      "url": "https://docs.celestia.org/build/post-retrieve-blob/fibre/when-to-use/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "fibre"
      ]
    },
    {
      "id": "buffers",
      "title": "Budget Fibre receive-buffer memory",
      "category": "Operations",
      "text": "Worst-case receive buffers are connections \u00d7 concurrent streams \u00d7 about 132 MiB. The documented defaults of 16 and 13 imply about 26.8 GiB before other processes. Increasing connection limits increases the memory requirement.",
      "url": "https://docs.celestia.org/operate/consensus-validators/fibre/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "disks",
        "slots"
      ]
    },
    {
      "id": "disks",
      "title": "Separate Fibre data from consensus data",
      "category": "Operations",
      "text": "Celestia\u2019s operator guide requires separate data disks for Fibre and celestia-app. An unmounted disk may be a raw device used by another workload and must not be counted as free capacity.",
      "url": "https://docs.celestia.org/operate/consensus-validators/fibre/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "buffers"
      ]
    },
    {
      "id": "slots",
      "title": "Leave room for downloads",
      "category": "Operations",
      "text": "The guide warns an upload can occupy all 16 default connections. Raising max_connections can leave download slots, but operators must recompute the memory budget and validate the workload.",
      "url": "https://docs.celestia.org/operate/consensus-validators/fibre/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "buffers"
      ]
    },
    {
      "id": "object",
      "title": "Object storage has version requirements",
      "category": "Operations",
      "text": "The current guide supports S3-compatible shard storage in v10.4.0 and v10.4.0-mocha. Persistent local metadata is still needed. Existing retained shards must remain readable when switching backends.",
      "url": "https://docs.celestia.org/operate/consensus-validators/fibre/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "disks"
      ]
    },
    {
      "id": "nitro",
      "title": "Arbitrum Nitro / Orbit",
      "category": "Ecosystem",
      "text": "The documented Nitro integration uses a Celestia DAS sidecar. Its dispute verification needs a working Blobstream path. The docs warn Succinct-operated SP1 Blobstream deployments stopped receiving new commitments in September 2026.",
      "url": "https://docs.celestia.org/build/stacks/nitro-das-server/",
      "date": "",
      "kind": "Documented integration \u00b7 dependency warning",
      "reviewed": "2026-10-29",
      "related": [
        "orbit-history",
        "blobstream"
      ]
    },
    {
      "id": "op-stack",
      "title": "OP Stack alt-DA",
      "category": "Ecosystem",
      "text": "Celestia\u2019s OP Stack integration sends batch data to Celestia and records a commitment on Ethereum. A documented integration is not evidence that every OP chain uses Celestia.",
      "url": "https://docs.celestia.org/build/stacks/op-alt-da/introduction/",
      "date": "",
      "kind": "Documented integration",
      "reviewed": "2026-10-29",
      "related": [
        "namespace"
      ]
    },
    {
      "id": "hyperlane",
      "title": "Hyperlane",
      "category": "Ecosystem",
      "text": "Lotus integrates Hyperlane modules for cross-chain interoperability. The announcement describes a multisig security module for bootstrapping; applications must assess the actual deployed route and trust assumptions.",
      "url": "https://blog.celestia.org/lotus/",
      "date": "",
      "kind": "Protocol integration",
      "reviewed": "2026-10-29",
      "related": [
        "ibc",
        "lotus"
      ]
    },
    {
      "id": "ibc",
      "title": "IBC relayers and channels",
      "category": "Ecosystem",
      "text": "Celestia uses IBC for authenticated cross-chain messages and asset transfers. Relayers forward packets and proofs. A DA bridge node is not an IBC relayer, and active channels should be checked separately.",
      "url": "https://docs.celestia.org/learn/features/bridging/ibc/",
      "date": "",
      "kind": "Protocol integration",
      "reviewed": "2026-10-29",
      "related": [
        "bridge",
        "hyperlane"
      ]
    },
    {
      "id": "blobstream",
      "title": "SP1 Blobstream deployment caution",
      "category": "Ecosystem",
      "text": "Celestia\u2019s current Nitro guide warns that Succinct-operated SP1 Blobstream deployments are no longer maintained as of September 2026. Historical integration announcements must not be read as current availability guarantees.",
      "url": "https://docs.celestia.org/build/stacks/nitro-das-server/",
      "date": "",
      "kind": "Service limitation",
      "reviewed": "2026-10-29",
      "related": [
        "nitro"
      ]
    },
    {
      "id": "hibachi",
      "title": "Hibachi",
      "category": "Ecosystem",
      "text": "A trading application highlighted in Celestia\u2019s ecosystem directory. Directory inclusion is not a formal partnership claim or a live usage attestation.",
      "url": "https://celestia.org/ecosystem/",
      "date": "",
      "kind": "Ecosystem directory listing",
      "reviewed": "2026-10-29",
      "related": []
    },
    {
      "id": "plume",
      "title": "Plume",
      "category": "Ecosystem",
      "text": "A real-world-asset focused project highlighted in the ecosystem directory. Directory inclusion is not a formal partnership claim or a live usage attestation.",
      "url": "https://celestia.org/ecosystem/",
      "date": "",
      "kind": "Ecosystem directory listing",
      "reviewed": "2026-10-29",
      "related": []
    },
    {
      "id": "towns",
      "title": "Towns",
      "category": "Ecosystem",
      "text": "A group-chat application highlighted in the ecosystem directory. Directory inclusion is not a formal partnership claim or a live usage attestation.",
      "url": "https://celestia.org/ecosystem/",
      "date": "",
      "kind": "Ecosystem directory listing",
      "reviewed": "2026-10-29",
      "related": []
    },
    {
      "id": "kamigotchi",
      "title": "Kamigotchi",
      "category": "Ecosystem",
      "text": "An onchain game highlighted in the ecosystem directory. Directory inclusion is not a formal partnership claim or a live usage attestation.",
      "url": "https://celestia.org/ecosystem/",
      "date": "",
      "kind": "Ecosystem directory listing",
      "reviewed": "2026-10-29",
      "related": []
    },
    {
      "id": "mainnet-network",
      "title": "Mainnet network and releases",
      "category": "Network",
      "text": "Mainnet uses chain ID celestia. The network page lists release versions and public endpoints. Installed software, activated app version, and actual endpoint health are separate facts.",
      "url": "https://docs.celestia.org/operate/networks/mainnet-beta/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "mocha-network"
      ]
    },
    {
      "id": "mocha-network",
      "title": "Mocha testnet",
      "category": "Network",
      "text": "StakeUs tooling targets the Mocha-5 chain and keeps its measurements separate from Mainnet. Testnet observations should not be presented as Mainnet performance evidence.",
      "url": "https://docs.celestia.org/operate/networks/mocha-testnet/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "mainnet-network"
      ]
    },
    {
      "id": "cohort",
      "title": "Foundation delegation evaluation",
      "category": "Operations",
      "text": "Cohort 9 applications close on 1 November 2026 and delegation begins on 1 December 2026. The program evaluates operations and contributions; a sophisticated dashboard does not establish validator eligibility or uptime.",
      "url": "https://docs.celestia.org/operate/consensus-validators/foundation-delegation-program/",
      "date": "",
      "kind": "Documentation",
      "reviewed": "2026-10-29",
      "related": [
        "evidence"
      ]
    },
    {
      "id": "evidence",
      "title": "What Atlas observations can establish",
      "category": "Methodology",
      "text": "Atlas combines source-reported validator sets, registered Fibre hosts and explicitly inventoried bridges. IP country estimates describe endpoints, not validator signing machines. Unknown locations remain in coverage denominators.",
      "url": "https://mocha.stakeus.xyz/atlas/#methods",
      "date": "",
      "kind": "StakeUs methodology",
      "reviewed": "2026-10-29",
      "related": [
        "map",
        "ai"
      ]
    },
    {
      "id": "map",
      "title": "Reading the decentralization map",
      "category": "Methodology",
      "text": "Country shading groups approximate public endpoint locations. Validator-associated Fibre endpoint power is not geographic signing-power distribution. ASN is a routing-network identifier, not proof of shared ownership or datacenter.",
      "url": "https://mocha.stakeus.xyz/atlas/#methods",
      "date": "",
      "kind": "StakeUs methodology",
      "reviewed": "2026-10-29",
      "related": [
        "evidence"
      ]
    },
    {
      "id": "ai",
      "title": "How the evidence assistant works",
      "category": "Methodology",
      "text": "A locally hosted Model2Vec embedding model retrieves relevant curated research notes. Responses present existing notes and citations, not generated facts. Match scores indicate relevance, not confidence or truth. Questions are not sent to a third-party AI service.",
      "url": "https://mocha.stakeus.xyz/atlas/#methods",
      "date": "",
      "kind": "StakeUs methodology",
      "reviewed": "2026-10-29",
      "related": [
        "evidence"
      ]
    },
    {
      "id": "commit",
      "title": "Signature inclusion is not uptime",
      "category": "Methodology",
      "text": "Commit Radar counts included, absent and nil signatures at observed eligible heights. Commits can omit late valid signatures. Missing samples break absence streaks; the display cannot prove slashing history or downtime.",
      "url": "https://mocha.stakeus.xyz/lab/",
      "date": "",
      "kind": "StakeUs methodology",
      "reviewed": "2026-10-29",
      "related": [
        "evidence"
      ]
    },
    {
      "id": "launch-kit",
      "title": "Launch a light, bridge or consensus node",
      "category": "Operations",
      "text": "The StakeUs launch workbench generates a reviewable Python setup kit for a fresh Linux x86_64 server. It checks prerequisites, verifies release checksums and isolates its service. New binary releases are downloaded into staging; activation requires operator review.",
      "url": "https://mocha.stakeus.xyz/atlas/#deploy",
      "date": "",
      "kind": "StakeUs deployment tool",
      "reviewed": "2026-10-29",
      "related": [
        "buffers",
        "disks"
      ]
    },
    {
      "id": "hardware",
      "title": "Hardware is a starting point, not a guarantee",
      "category": "Operations",
      "text": "The current Mainnet hardware guide lists 64 GB RAM, 32 cores and 2 TB NVMe for a pruned bridge, and 32 GB RAM, 32 cores and 2 TB NVMe for pruned consensus. Mocha needs its own workload sizing.",
      "url": "https://docs.celestia.org/operate/getting-started/hardware-requirements/",
      "date": "",
      "kind": "Documented starting guidance",
      "reviewed": "2026-10-29",
      "related": [
        "launch-kit"
      ]
    }
  ]
}