How Does Templar Protocol Work?
Templar Protocol enables borrowing stablecoins against native Bitcoin, Ethereum, Stellar, and other chain assets without bridges or wrapped tokens, using multi-party computation (MPC) for cross-chain collateral management. With ~$17M TVL and $4M in pre-seed funding, it is an early-stage protocol pursuing a technically ambitious cross-chain lending approach.
TVL
$26M
Sector
Lending
Risk Grade
C+
Value Grade
D-
Core Mechanisms
6.1.1
Over-collateralized lending where users deposit BTC, ETH, XLM, or other native chain assets to borrow stablecoins
Standard over-collateralization model but applied across multiple chains natively
6.4.3
NovelCustom oracle infrastructure for pricing cross-chain native assets (BTC, XLM, etc.) without bridged representations
Must price native assets across different chains — no standard oracle covers all chains natively
8.1.3
NovelMPC-based cross-chain message passing for collateral management without bridges or wrapped tokens
Uses NEAR Chain Signatures and MPC networks to control collateral on external chains — novel approach
6.2.2
Interest rate model for stablecoin borrowing against volatile cross-chain collateral
Standard kinked utilization curve adapted for multi-chain context
6.3.2
Liquidation mechanism that must coordinate across chains to seize native collateral
Cross-chain liquidation adds latency and complexity vs single-chain liquidation
5.4.1
Multisig-controlled protocol parameters during early stage
Early-stage team control typical for new protocols
How the Pieces Interact
Cross-chain collateral requires cross-chain price feeds — if the oracle lags or fails on one chain, liquidations may be delayed while collateral value drops on another
Cross-chain liquidation requires MPC network coordination — if MPC nodes are slow or unavailable, underwater positions cannot be liquidated promptly
Collateral ratio depends on accurate cross-chain pricing — any oracle manipulation could allow undercollateralized borrows or premature liquidations
Utilization-based rates may not reflect true liquidity availability when collateral is locked across multiple chains with varying settlement times
Team-controlled parameters combined with novel MPC infrastructure create centralization risk — team could modify collateral requirements or MPC configurations
What Could Go Wrong
- Multi-party computation (MPC) key management for cross-chain collateral introduces novel trust assumptions not yet battle-tested
- Cross-chain collateral management without bridges relies on Chain Signatures and NEAR Intents — highly experimental infrastructure
- Custom oracle approach for multi-chain asset pricing creates broader attack surface than standard Chainlink feeds
- Very early-stage protocol with limited track record — mainnet launched recently with $4M pre-seed funding
MPC Network Failure Freezing Cross-Chain Collateral
ModerateTrigger: MPC signing nodes become unavailable or fail to reach threshold consensus during a market downturn requiring mass liquidations
- 1.Market downturn causes multiple positions to become undercollateralized across BTC, ETH, and XLM chains — Liquidation engine needs to seize collateral on multiple external chains simultaneously
- 2.MPC network becomes congested or nodes go offline under high signing demand — Cross-chain collateral seizure transactions cannot be signed and broadcast
- 3.Liquidations stall while collateral values continue to drop — Bad debt accumulates beyond what the liquidation spread can cover
- 4.Stablecoin lenders realize their funds are backed by declining, unliquidatable collateral — Lenders rush to withdraw, creating a bank run on available stablecoin liquidity
- 5.Protocol becomes insolvent as bad debt exceeds remaining collateral value — Total loss for remaining depositors; protocol reputation destroyed
Risk Profile at a Glance
Overall: C+ (38/100)
Lower score = safer