FloraChain settlement architecture & regulator-readable provenance.

BloomBridge’s technology and ledger vertical is built around a deliberately narrow framing: provenance for licensed product, audit-ready transaction records, and settlement support for the commodity-trade vertical. Speculative-token language, yield-product marketing, and Web3-disruption framing are explicitly avoided. The infrastructure is built to be auditable — by counterparties, by counterparty banks, and by the regulators whose frameworks the operating brands sit inside.

Three platforms. One settlement spine.

BloomBridge Ledger (BLT) is the Group’s operating-ledger platform. It records licence-aware transactions, intra-group activity, counterparty-facing documentation, provenance records, and compliance-sensitive operating data in a single audit-ready environment. It is practical infrastructure, not a token launch.

FloraChain is BLT’s immutable settlement layer — a sovereign Layer-1 blockchain, fully IBC and EVM compatible, designed to connect with the broader multi-chain economy while operating on independent infrastructure. Both permissionless and permissioned environments are supported. The chain is positioned as digital banking infrastructure and financial settlement rails for compliant real-world finance and assets at scale.

MetaFlora is the cannabis-sector and real-world asset platform layer for genetics provenance, licensed-product authentication, supply-chain visibility, product verification, and real-world asset organization. It provides regulator-grade visibility into cultivar lineage, batch movement, genetic verification, product authenticity, and counterparty integrity.

A worked example: BR-2026-04-K12.

The clearest way to describe what regulator-readable provenance actually means is to walk through a query. The example below is taken from the FloraChain console.

Read as documentation, the response is unambiguous. The batch originated under a named BoMRA licence number in Botswana, was processed under a named DCC licence in California, carries a cultivar lineage that can be cross-checked against MetaFlora’s genetic registry, and travelled a seventeen-step chain of custody with zero anomalies. Settlement closed against a verified counterparty. A regulator reading this record sees what they need to see: who, where, under what licence, and with what break in the chain (none).

“The audit, provenance, authentication, settlement, and real-world asset use cases above are the framing the Group is willing to stand behind to counterparties.”

Institutional use cases the Group will stand behind.

The Group is explicit about the use cases it characterises its infrastructure around: provenance tracking for licensed cannabis products, audit-ready transaction records, genetic and product authentication, supply-chain visibility, counterparty documentation, permissioned institutional data environments, settlement support for commodity-trade flows, and real-world finance and asset recordkeeping.

The framing is restrained on purpose. Cannabis is a regulated industry. Commodity trade runs through banks. Both terminate in compliance functions whose tolerance for speculative framing is zero. The Group’s ledger infrastructure is built to live inside those functions, not outside them.

Why a sovereign chain.

FloraChain is sovereign — its own validator set, its own consensus, its own governance — while remaining IBC and EVM compatible. The architectural choice follows from the use case. Settlement for licensed cannabis movement and physical commodity trade requires the operator to be able to commit to chain governance, validator policy, and data residency on its own terms. A general-purpose chain cannot make those commitments. A sovereign Layer-1 can.

The IBC and EVM compatibility preserves connectivity. Counterparties operating on Cosmos-ecosystem or Ethereum-ecosystem rails can interoperate without forcing the Group to compromise on the chain’s independent posture.

This whitepaper is issued by BB Digital. Technical documentation, validator policy, and counterparty onboarding for permissioned environments are issued upon request under NDA. Document ID: BB-GROUP-PROFILE-2026-V6.