What Is CBLT? The Obligation Token Explained

Start here: the simplest version

When you work within this platform and earn CBLT, you have not been paid. You have been given a record — a precise, traceable record — that the productive economy around you owes you something back.

When you commit CBLT to a new contract, you are making the same kind of promise in the other direction: you owe a future performance. The CBLT sits in escrow until you deliver.

Nothing is settled. Nothing is taxed. Nothing is consumed. The system is working.

Settlement — the moment where value is actually realised — happens once: when you burn your CBLT to access something real. A property lease. An expert service. A hotel room built by the same network you contributed to. At that point, an invoice is generated, VAT is applied, and revenue is recognised. For the first time in the whole chain, a consumption event has occurred.

Everything before that burn was production. And in production, the same rules apply as they do inside any company: people work toward a shared outcome, obligations are passed down the chain, and no tax event occurs at each internal handoff.

What CBLT is not

Before going further, let's clear the most common misconceptions:

• Not a cryptocurrency. CBLT does not exist to appreciate in price. There is no speculation, no mining, no open market where you can sell it to a stranger for profit.
• Not a stablecoin. CBLT is not pegged to any currency and makes no price stability promise.
• Not equity. CBLT carries no ownership of the platform, no governance votes over the company, and no share of its profits.
• Not a gift card. A gift card is bought with cash by the person who wants to receive services. CBLT is earned by the person who delivers services. The direction is opposite.
• Not wages. Wages are settled at the time of work. CBLT is a deferred claim — it only becomes realisable when it is burned for something real.
• Not money. CBLT cannot be redeemed for cash from the platform. Its value lives only within the network of obligations it represents.

The hotel construction analogy

Imagine a hotel is being built. The project involves a wood cutter, a woodworker, a contractor, and a developer. None of them is billing the next person in the chain. They are all contributing toward the same thing: a finished hotel.

When the hotel opens, guests pay to stay. That is when revenue is recognised. That is when VAT is collected. That is the consumption event.

Now imagine those same four people will be entitled to stay in the hotel themselves once it opens — their contribution earns them access to the output they helped create. The wood cutter cuts trees. The woodworker shapes them. The contractor assembles. Each passes the obligation forward. Each holds a record of their contribution. None of them has been "paid" in the moment. None of them has consumed anything.

That is exactly how CBLT works.

The burn event — redeeming CBLT for a hotel stay, a lease, an expert service — is the moment the wood cutter finally stays in the room they helped build. Revenue is recognised at that moment. An invoice is generated. Tax applies. Everything before it was internal to the productive chain.

The legal precedent: this is not a new idea

This model is not novel. It has been operating legally in multiple jurisdictions for nearly a century.

The WIR Bank (Switzerland, 1934 — present) — a deliberate contrast, not a precedent

WIR is sometimes raised as a comparison, and it's worth addressing directly rather than citing it as supporting precedent, because it isn't one. The Swiss WIR Bank issues WIR Francs — a complementary currency circulating among roughly 60,000 Swiss businesses, used interchangeably with Swiss Francs to pay for arbitrary goods and services across a large member network. Checked against Swiss tax guidance on barter and WIR-denominated transactions: income from WIR-denominated business is taxed exactly like income in ordinary Swiss Francs, and VAT is due on WIR transactions the same way it's due on cash transactions, valued at the settled amount. There is no tax deferral in how Switzerland treats WIR.

That's not a problem for CBLT's position — it's the reason CBLT is structured differently. WIR is taxed like cash because it functions like cash: a general-purpose currency substitute. CBLT is deliberately not that. CBLT is a voucher — a conditional right to a specific future category of use (a lease, a stay, an expert service), not a medium of exchange for arbitrary goods and services — which is why it falls under the Voucher Directive's MPV rules (Argument 2, below) rather than under ordinary currency or barter treatment. The distinction is the whole point: CBLT was designed to avoid becoming the thing WIR is. If CBLT ever did become freely exchangeable for arbitrary goods and services the way WIR is, it would likely lose MPV treatment and pick up WIR's tax treatment along with it — which is exactly why the structural features later in this article (no cash redemption, no passive yield, traceable origin) are treated as non-negotiable, not incidental.

Time banking (US, UK, EU)

Time banking systems — operated by hOurworld, TimeBanks USA, Timebanking UK, and hundreds of local networks — exchange time credits between members: one hour of service earns one credit, redeemable for one hour of another member's time.

In the UK, HMRC has confirmed that where time banking operates through a not-for-profit intermediary and credits are not used commercially, VAT does not apply to the exchanges. In the US, the IRS has generally treated community time banking as outside normal tax reporting, though commercial platforms attract higher scrutiny.

The key precedent from both models: when an instrument circulates within a defined community toward a shared productive purpose, regulators have consistently distinguished it from commercial cash-equivalent transactions.

This precedent is strongest for small-scale, genuinely reciprocal, non-commercial exchange — hour-for-hour, no large sums, typically run through a registered charity or community interest company. It should not be relied on, by itself, to support a large commercial project like the €100M property development case study — that's a different fact pattern, and a tax authority is likely to scrutinise a commercial-scale construction project differently than a community time bank. Time banking is cited here as supporting context for community-scale platform use, not as precedent covering every scale of CBLT activity.

Why VAT does not apply to intermediate CBLT transfers

This is the part most accountants will want to understand. The short version: VAT applies once — at the burn event. Not at every transfer in between. Here is why, with the legal basis for each argument.

The frame that ties the arguments below together: CBLT is a right of use, not a sale. At no point — when it's earned, when it moves between participants, when it sits in escrow — does CBLT transfer ownership of anything. It records a conditional obligation that, when exercised, grants a right to use something specific: a lease, a stay, a service. It is never a sale or purchase of that thing, and it is never money changing hands for it. EU VAT law already has a well-established, separate regime for a right of use granted now and exercisable later — that's exactly the voucher category (Argument 2), and it's also why leases and rights of use are timed differently from outright sales of goods more generally. Each argument below is really the same underlying point, examined from a different angle: no sale has occurred, so no VAT is due, until the right is actually exercised at burn.

Argument 1: CBLT is not consideration in the VAT sense

This argument supports Argument 2 below; it is not, on its own, the primary basis for the "no VAT on intermediate transfer" position — see the closing note in this section.

An earlier framing of this argument rested on there being no direct link between the work and the CBLT transfer, citing Tolsma v Inspecteur der Omzetbelasting (Case C-16/93, 1994) and Mohr v Finanzamt Bad Segeberg (Case C-215/94, 1996) — cases about a street musician's unsolicited donations and a one-way compensation payment with no reciprocal service. That framing doesn't survive close reading: when a general contractor passes CBLT to a subcontractor for the subcontractor's labour, there plainly is a direct, bilateral relationship with clear reciprocal performance — structurally closer to the fact pattern where Tolsma and Mohr find a direct link does exist than to the fact pattern where it doesn't. Leaning on those cases as the primary basis risks citing precedent that supports the opposite conclusion once a specialist reads it closely.

The more defensible claim doesn't require denying that a direct link exists. EU VAT law requires consideration to be capable of being expressed in monetary terms for a supply to be taxable — a direct link between work and reward is necessary but not sufficient; what changes hands also has to function as ascertainable payment. CBLT, prior to burn, is not money or a money-equivalent: it is a conditional, non-negotiable obligation record whose ultimate redemption value is not fixed or known at the point of transfer (see Argument 2 — this is the same fact that makes CBLT an MPV rather than an SPV). So even granting that a direct link exists between the subcontractor's labour and the CBLT they receive for it, no ascertainable consideration has changed hands yet — that only happens once the obligation is actually settled for a real good or service at burn.

Tolsma and Mohr remain useful as general supporting citations on the direct-link doctrine, and are kept in the "For your accountant" summary below for that reason. But the primary basis for "no VAT on intermediate transfer" should be Argument 2, which is purpose-built for exactly this fact pattern.

Argument 2: CBLT is a Multi-Purpose Voucher under EU Directive 2016/1065

The EU Voucher Directive, which came into force across all member states from 2019, introduced a specific VAT framework for instruments accepted as consideration for a future supply. It distinguishes two types:

• A Single-Purpose Voucher (SPV): the goods or services and the VAT rate are known at the time of issue. VAT is charged on issue.
• A Multi-Purpose Voucher (MPV): what will be supplied — and therefore the VAT rate and place of supply — is not known at the time of issue. VAT is charged only at the point of redemption, not at any earlier transfer.

CBLT is an MPV. When CBLT is minted, it is not known whether it will be redeemed for a hotel stay, a legal consultation, an expert adjudication service, a property lease, or another category of service — each of which may attract a different VAT rate in a different jurisdiction.

The consequence under EU law is unambiguous: every intermediate transfer of an MPV is outside VAT scope. The wood cutter passing CBLT to the woodworker — not a VAT event. The woodworker passing it to the contractor — not a VAT event. The contractor redeeming it for a hotel stay — VAT event, applied at the rate applicable to that service on the date of redemption.

This is not a workaround. It is the explicit design of the Voucher Directive, applying precisely as intended.

A standing constraint this depends on. MPV status specifically requires that at the moment of issue, what CBLT will ultimately be redeemed for — and therefore the applicable VAT rate and place of supply — is genuinely unknown. If a future platform feature ever made a specific CBLT issuance's eventual redemption determinable at mint time (for example, a CBLT unit contractually pre-committed to one specific redemption type from creation), that class of CBLT would look more like a Single-Purpose Voucher — taxed at issue, not at redemption, a materially worse outcome. This is recorded as a standing engineering constraint in the platform's governing architecture spec (docs/architecture/ltu_cblt_master_spec.md), not just a legal aside: any product decision that would make redemption determinable at mint needs to be checked against this before it ships.

A supporting analogy, not a pillar: the single enterprise principle

This is offered as one additional way to think about the "no supply between participants" position, not as an independent, load-bearing argument. It is a bigger analogical stretch than Argument 2, and it is the point most likely to be picked apart first by anyone with real EU VAT group experience.

Polysar Investments Netherlands BV v Inspecteur der Invoerrechten en Accijnzen (Case C-60/90, 1991) concerns when a holding company is or isn't treated as conducting independent economic activity for VAT purposes — a question about corporate group structures, not about networks of legally independent contractors passing obligations between themselves on a construction site. Article 11 of the VAT Directive's VAT-group mechanism is a real, related concept: member states may allow closely bound legally-independent persons to be treated as a single taxable person, making transactions between them VAT-transparent — but that status has to be formally elected and approved per jurisdiction; it is not something a construction consortium acquires automatically by working toward a shared output.

Read narrowly, this is a useful directional analogy: a group of contractors on a shared build does resemble a single economic unit in some ways. Read broadly, as a direct legal holding that applies to CBLT transfers, it overstates what Polysar actually decided. It is kept here as one input among several, not removed — but it should not be asked to carry weight the case cannot support on its own. Argument 2 remains the primary basis; this section is context, not a co-equal pillar.

Argument 3: VAT is a tax on consumption, not on production

The fundamental policy purpose of VAT, established in the First VAT Directive and confirmed across decades of ECJ jurisprudence, is to tax consumption — the final use of a good or service by an end user — not the intermediate stages of production.

Applying VAT to every CBLT transfer during production would create exactly the cascading tax effect that VAT was designed to eliminate. A wood cutter passing obligations to a woodworker, both of whom are working toward the same hotel, has not consumed anything. No consumption event has occurred. Taxing that transfer would mean the same underlying value is taxed multiple times before it reaches the end consumer — precisely what the input tax credit mechanism of VAT was built to prevent.

The correct and legally sound position: VAT applies at the burn event, once, on the value of the service or access redeemed. The invoice generated at burn is the VAT document. It is the record that consumption occurred, who consumed it, what was received, and what tax is due.

The tax picture — clearly stated

The difference between earning CBLT and earning Euros

If a contractor pays you €100 for a day's work, you have received money. It is income on the day you receive it. Income tax applies. If you are VAT-registered, a supply has occurred.

If the same contractor acknowledges your day's work with CBLT within this platform, no settlement has occurred. The CBLT records an obligation. You have not received anything realisable yet. The tax event occurs when you burn that CBLT — when you redeem it for something real: a hotel stay, a service, a lease. At that point, an invoice is generated and the appropriate tax applies.

This is not a tax avoidance structure. It is a timing alignment: the tax event matches the consumption event, because no consumption occurs until burn. This is how every sound accounting framework — from EU VAT rules to US revenue recognition standards — is designed to work when applied correctly to deferred obligation instruments.

Is CBLT a security? The US position

Under the Howey test — the US Supreme Court's 1946 framework for identifying securities, confirmed in SEC v W.J. Howey Co. — an investment contract requires: an investment of money, in a common enterprise, with an expectation of profits from the efforts of others.

CBLT fails on two counts addressed here, plus a third addressed below that earlier drafts of this analysis left open. First, CBLT is primarily earned through performance, not purchased with money. Second, CBLT promises no profit: it carries no yield, no appreciation right, and no share of the platform's revenue. The value of a CBLT is the right to have equivalent work performed in return — which is the definition of a contractual right, not an investment.

Common enterprise — the prong this analysis previously left unaddressed. Howey's second prong asks whether participants' fortunes are tied together: horizontally, where investors pool capital and share pro rata in profits or losses, or vertically, where an investor's return depends on a promoter's efforts and success. CBLT does not create horizontal commonality — each participant's CBLT reflects their own individually performed work, verified and recorded against a specific contract, not a pooled fund whose gains or losses are shared pro rata across unrelated holders. Nor does it create the strong form of vertical commonality that concerns securities regulators, where an investor's return rises and falls with a promoter's managerial efforts on undifferentiated pooled capital — a CBLT holder's ability to redeem depends on the specific contract they are party to being fulfilled, not on the platform's general managerial success. There is a weaker sense in which participants share exposure to a project's completion — if a hotel is never finished, several participants' CBLT is affected together — and that is worth stating plainly rather than glossing over, since it is the closest this analysis comes to a common-enterprise fact pattern. But it resembles the shared risk that any set of subcontractors on the same physical project already bears under ordinary contract and construction law, not the pooled-investment commonality Howey's second prong targets. On balance, CBLT does not satisfy the common enterprise prong in the sense securities case law requires — but this conclusion specifically benefits from securities counsel review, not just a general legal read (see the standing recommendation at the end of this article).

Recent SEC guidance and enforcement posture (2024–2025) have trended toward distinguishing tokens performing a practical, non-investment function from securities. This document does not rest that observation on a single named, dated SEC release — no specific statement, no-action letter, or rule proposal is cited here, and none should be assumed. Treat this as a directional read on enforcement posture, not a citable settled framework, until a specific source is identified and confirmed. CBLT is more conservatively structured than most tokens discussed in that context regardless: it has no secondary market by design.

The risk area to monitor: if CBLT were to develop a liquid open market where it could be bought and sold freely for cash, regulators would revisit the classification. The platform's structural design — no cash redemption from the platform, no open exchange listing — is what maintains this position.

The EU and MiCA position

MiCA (the EU's Markets in Crypto-Assets Regulation, fully in force from December 2024) defines utility tokens as crypto-assets granting "access to a good or service supplied by the issuer." CBLT does not grant access to a service supplied by the platform — it grants a claim on another participant's future performance. The issuer is not the ultimate service provider.

The honest position: CBLT does not fit neatly into any of MiCA's three regulated categories — e-money tokens, asset-referenced tokens, or utility tokens as classically defined. It may fall outside MiCA's scope entirely as a contractual rights instrument rather than a crypto-asset.

If the platform were to publicly offer CBLT or list it on an exchange, the safest compliance position would be to treat it as a utility token and publish a crypto-asset whitepaper — not because the classification is precise, but because it is the closest available framework and regulators would apply it by analogy in the absence of clearer guidance.

What CBLT definitively is not under MiCA:

• Not an e-money token. It is not pegged to fiat. The platform is not an e-money institution and no ECB licence is required.
• Not an asset-referenced token. It is not backed by a basket of assets. Reserve requirements do not apply.

The structural features that protect this classification

Three architectural decisions keep CBLT outside financial regulation and ensure its legal character remains clear:

1. No cash redemption. The platform does not redeem CBLT for fiat currency at any price. There is no exit to cash through the platform.
2. No passive yield. Holding CBLT generates nothing. Value is only realised through active participation in new contracts or redemption for real services.
3. Traceable obligation origin. Every CBLT has a recorded origin — which contract or activity created it, who earned it, who holds it. It is not an anonymous bearer instrument. This traceability is what makes the audit trail clean for accountants and for any regulatory inquiry.

None of these are accidental. They are the deliberate design decisions that give CBLT its legal character. If any of them were changed — particularly introducing cash redemption or a yield mechanism — the regulatory classification would need to be reassessed immediately.

For your accountant

When presenting CBLT transactions to your accountant or tax adviser, communicate these points:

• CBLT is a deferred obligation instrument, not cash or a cash equivalent
• Intermediate transfers during production are not supplies for VAT purposes — cite the Voucher Directive (2016/1065) MPV framework as the primary basis; Tolsma (C-16/93) and Mohr (C-215/94) support the general "no ascertainable consideration at intermediate transfer" point but should not be the primary citation
• The tax event is the burn/redemption — the invoice generated at burn is your VAT document and your income recognition document
• Keep records of CBLT balances, transfer history, and the fair market value at the time of any burn event — the platform provides exportable transaction history for this purpose
• Always obtain independent advice in your specific jurisdiction, as treatment varies across member states and outside the EU

Before this goes into marketing, a podcast, or investor-facing material

This is a stronger draft than the version that existed before this review pass, but it is still a draft, not cleared legal or tax advice. Two things need to happen before any of this is used publicly:

• EU VAT counsel should review Arguments 1–4 above as applied specifically to CBLT's actual technical mechanics — not the general legal areas, the specific application to this platform's contracts, escrow, and burn logic.
• US securities counsel should review the completed Howey analysis, including the common-enterprise prong above.

Both reviews should happen against this version, not the shorter version that preceded it — reviewing a draft with known gaps already closed is a better use of a reviewer's time than reviewing one that still has them.

In the meantime, the deferred-tax-event treatment described above is a position, not a certainty. To see exactly how much that position is worth in a real project — and how quickly it disappears if a reviewer rejects it — see the CBLT vs Traditional Finance — Development Simulator, which computes both the argued position and a worst-case floor where every CBLT-side tax argument is rejected, side by side.

Editorial changelog

2026-08-10 — Legal review pass, prompted by a truncated reconstruction of this article having stated a materially different, incorrect tax-timing position (immediate taxation at milestone release) than the fuller version restored here. Nothing below was deleted; citations that didn't hold up were replaced with the specific reason they don't apply, not silently cut.

• Argument 1 reframed, not weakened: previously leaned on Tolsma/Mohr "no direct link" case law, which arguably supports the opposite conclusion once read against CBLT's actual fact pattern (a contractor paying a subcontractor in CBLT is a direct, bilateral exchange). Reframed around CBLT not constituting ascertainable monetary consideration at intermediate transfer; Tolsma/Mohr kept as supporting citations.
• Argument 2 (MPV) confirmed as the primary basis for "no VAT on intermediate transfer," with a new standing engineering constraint documented — see docs/architecture/ltu_cblt_master_spec.md.
• Argument 3 (Polysar) demoted from a co-equal pillar to an explicitly-labelled supporting analogy — kept, not deleted, but no longer asked to carry weight the case doesn't support alone.
• WIR Bank section rewritten as a deliberate contrast rather than supporting precedent, after checking Swiss tax guidance: WIR is taxed exactly like cash, with no deferral — the opposite of what the original framing implied.
• Time banking caveated for scale: the precedent supports small, non-commercial, community-scale use; it is now explicitly flagged as not sufficient on its own to support the commercial-scale property development case study.
• Howey common-enterprise prong added — the securities analysis previously addressed three of Howey's four prongs and left this one open.
• Unnamed "SEC's 2025 framework" softened to a directional observation, since it could not be pinned to a specific, named, dated document.
• Right-of-use framing added near the top of the VAT section, tying Arguments 1, 2, and the WIR contrast together under one explicit distinction instead of leaving it implicit across four separately-argued points.
• Tax-timing position centralised: shorter articles that touch this topic now pull the same paragraph from config/docs_legal_snippets.php instead of restating it freehand, so a future edit can't silently drift out of sync the way it did before.

This article is for informational and educational purposes. It does not constitute legal or tax advice. The legal analysis presented represents the platform's interpretation of applicable frameworks. Individual circumstances vary and you should obtain independent professional advice before relying on any characterisation described here.