BQ Labs

Internal linkages

  • Company / operator boundary around BQ Chain packaging, consortium framing, and claims-governance workflow: bq-labs.
  • Strongest shared-mutual baseline: nexus-mutual.
  • Segmented-pool insurance contrast: insuredao.

Protocol / company boundary

  • Keep this note focused on the protocol surface: sponsor-defined pools, LIT liquidity, parametric versus governance-routed claims, and the way underwriting capital is segmented.
  • Keep bq-labs focused on the named entity boundary that frames the governance topology, BQ Chain operating shell, and the broader claims / business workflow around the protocol.
  • That split matters because the mechanism question is how does this insurance market work?, while the company question is who is still shaping the market’s governance and operating structure?

Control surface

  • At the protocol layer, authority sits in sponsor pool design, parametric-trigger definition, liquidity admission, and the governance bodies that decide non-automatic claims.

  • For the current named operator shell around that machinery, use bq-labs.

  • Read BQ Labs as a BTCFi-specific underwriting-market experiment, not as a general insurance anchor.

  • Last reviewed: 2026-08-06 UTC