Network · Heartwood

Ownership recorded on-chain, with eligibility checked on every transfer.

Recording who holds what is the easy part; keeping every holder eligible and every transfer within the rules is what has kept institutions at arm's length. Heartwood is built for exactly that. It keeps the ownership record for the assets the platform issues, lets only vetted, eligible parties hold them, and checks eligibility and jurisdiction on every transfer before it can settle.

What It Is

Ownership on the ledger, compliant by construction

Institutions want the transparency of ownership kept on a shared ledger, but not at the cost of holding an asset that could pass to an ineligible or unvetted party.

Heartwood keeps that record on-chain. Each holding carries its terms and its ownership register, every change of hands is written to the ledger, and every transfer is bound by the platform's rules.

It is distinct from the native coin, the unit the network settles and governs in. Heartwood governs who may hold what, enforced at the moment of transfer rather than reconciled after it.

Capabilities

What the ownership layer delivers

Eligibility-Gated Transfers

Every transfer confirms both parties are vetted and eligible for the asset's jurisdiction before it settles, enforced by the platform, not convention.

The Ownership Register

Every asset the platform issues carries its terms and a register of who holds it, kept on the ledger and current to the last transfer.

Auditable to the Underlying

Each holding links to the verified provenance behind it, so what a party holds can be audited from the record down to the evidence beneath it.

Jurisdiction Aware

Eligibility is checked against the jurisdiction each asset is issued for, so a transfer permitted in one place cannot slip through in another.

Shared Compliance Rails

The same transfer rules are reused by Bloom for credit transfers, so eligibility is proven once and applied consistently across the platform.

Audit-Ready Reporting

Disclosure and audit exports come straight from the record that governs transfers, so answering an auditor is a query, not a project.

How It Works

From issued asset to compliant transfer

1

Recorded

An asset is issued on-chain with its terms and its ownership register.

2

Verified

Each party's eligibility and due-diligence status is established and anchored.

3

Checked

Every transfer confirms both parties are eligible for that jurisdiction.

4

Settled

Only compliant transfers settle on-chain; the rest are simply refused.

Enforced, Not Assumed

Compliance as a property of the asset

Checked at Every Transfer

Rather than trust parties to comply, Heartwood checks eligibility and jurisdiction at transfer. A transaction that would breach the rules cannot settle, so compliance is a property of the asset, not a promise about it.

Audit-Ready by Design

Disclosure and audit exports come from the same record that governs transfers. Oversight becomes a matter of reading the record, not assembling one after the fact, and an auditor's question is answered from the ledger itself.

In the Pipeline

Where Heartwood sits

Sigil

Performs the due-diligence work off-chain that establishes whether a party is eligible to hold or receive an asset Heartwood records.

Torc

Anchors each party's eligibility status on-chain, the very status Heartwood reads to allow or deny a transfer at settlement.

Canopy

The portal where eligible, vetted parties see what they hold and move it under the same rules Heartwood enforces at settlement.

Thanks, you are subscribed. We will be in touch with what matters, and nothing that does not.

Ownership on the ledger, with compliance built into every transfer.

Speak with the team about keeping ownership on-chain with eligibility enforced by the platform.