# Lombard details Bitcoin Smart Account controls for BTC.b

> The primary diligence record now identifies the pre-signed Bitcoin spending paths, Ethereum Smart Account Registry, Token Operator, TEE-based Arbitration Oracles, unilateral exit route, and liquidation-driven reserve rebalancing used by this BTC.b issuance model.

- URL: https://riadefi.com/on-chain/2026-04-15-lombard-btc-b-bitcoin-smart-accounts-architecture/
- Type: Control change
- Stage: Confirmed
- Evidence: developing
- Materiality: material
- Event date: 2026-04-15
- Version: 1, published 2026-08-22 (first published 2026-08-22)
- Follow-up: 2026-04-30
- Advisor-relevant: yes
- Affects: Lombard BTC.b (asset)

Developing. Some claims here are not yet confirmed; they are listed apart from the confirmed facts. A new version replaces this one when the primary evidence changes.

## What happened

Lombard published a technical architecture guide describing how Bitcoin Smart Accounts retain BTC under depositor control while issuing BTC.b on Ethereum for use as on-chain collateral.

## What changed

The primary diligence record now identifies the pre-signed Bitcoin spending paths, Ethereum Smart Account Registry, Token Operator, TEE-based Arbitration Oracles, unilateral exit route, and liquidation-driven reserve rebalancing used by this BTC.b issuance model.

## What did not change

The guide does not establish that every BTC.b unit uses this architecture, provide all deployed contract addresses or named independent Arbitration Oracle operators, prove public availability, or demonstrate safety under stress.

## Confirmed

- The architecture pre-signs the allowed PSBT spending paths before BTC is deposited and uses Taproot addresses to constrain future states.
- A unilateral path from the vault to an unbond timelock address is designed to permit exit if the Token Operator is unavailable.
- Lombard states that a Smart Account Registry deployed on Ethereum records BSA instances, deposited UTXOs, pre-signed PSBTs, and position state.
- The Token Operator mints BTC.b on Ethereum after a Bitcoin deposit is finalized.
- Arbitration Oracles monitor Bitcoin and Ethereum, run in AWS Nitro Enclaves, and use AWS KMS policy restrictions for signing keys.
- The described liquidation process moves one or more vault UTXOs to Lombard reserves after a liquidator acquires and exits BTC.b collateral.

## Still open

- The exact registry and related contract addresses, production code hashes, attestation policy, and independent Arbitration Oracle set were not supplied in the cached article.
- It remains unclear which existing BTC.b supply uses Bitcoin Smart Accounts versus Lombard's other custody and issuance routes and how fungibility and reserve reporting distinguish them.
- Public eligibility, legal title, custodian terms, fees, dispute-operation history, and observed unilateral-exit timing remain unverified.
- No stress evidence establishes the behavior of partial liquidations, Token Operator outages, Arbitration Oracle outages, or conflicting Bitcoin and Ethereum state.

## What it means for an advisor

- Review the Lombard BTC.b memo so its custody, control, redemption, reserve, and liquidation analysis distinguishes the Bitcoin Smart Account issuance route from other BTC.b routes.
- Require deployed-address, attestation, operator, reserve-accounting, legal-title, and exit evidence before treating Smart Account-issued BTC.b as equivalent to previously reviewed BTC.b.
- Do not infer that a 1-of-k arbitration claim, TEE isolation, or pre-signed spending paths eliminate hardware, cloud, Token Operator, oracle-availability, liquidation, or implementation risk.

## Sources

1. [Bitcoin Smart Accounts: architecture, explained](https://www.lombard.finance/blog/bitcoin-smart-accounts-architecture-explained/) · Lombard Finance · 2026-04-15


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.