Oracle Integration

This guide covers oracle integration for Lombard’s Bitcoin-backed assets, including Proof of Reserve feeds for LBTC and BTC.b.

Key Changes

• LBTC is yield-bearing (since July 22), accumulating price based on Bitcoin yield
• BTC.b is a yieldless, risk-free Bitcoin wrapper maintaining 1:1 parity
• Both tokens use burn-and-mint bridging mechanisms requiring dual Proof of Reserve feeds

API Endpoints

Step 1: BTC.b Solvency Ratio

Calculate reserves backing the protocol versus BTC represented on the ledger.

Reserve Address (Base): 0xe7Ebc588F4EC9297d9867aD75a9b5D86848c8018

Important:

• Any ratio value greater than 1.0 should be clipped to 1.0
• Values below 1.0 require secondary verification and incident response procedures (potential DeFi liquidation impacts)

Step 2: LBTC Ratio

Two approaches:

1. Calculate supply ratio — query LBTC supply and backing Bitcoin through dedicated API endpoints
2. Direct ratio endpoint — query the ledger’s ratio endpoint directly

Interpretation:

• Values above 1.0 indicate LBTC has gained value (appreciation)
• Values below 1.0 suggest depreciation, requiring additional monitoring and alerts

Step 3: BTC.b Ratio

Calculate from either:

1. Lombard Ledger and destination chain data
2. Bitcoin network data combined with ledger information

Block Height Queries

Query specific block heights using the x-cosmos-block-height header:

GET /endpoint
x-cosmos-block-height: 12345

Timestamp Resolution

For historical data, resolve timestamps via binary search on the Tendermint RPC:

Production RPC: https://mainnet-rpc.lombard-fi.com