Stellar DeFi

Templar Vaults on Stellar: Deposits, Withdrawals and Payouts

How Templar vaults on Stellar take deposits, queue withdrawals and pay them out, with on-chain payout times, keys and allocations as of 10 November 2026.

How Templar curated vaults on Stellar take deposits and pay out queued withdrawals

Updated 10 November 2026: vault, governance, adapter and Blend pool state read on-chain through Soroban RPC; account history and signers from Horizon; vault rules from Templar's vault documentation and Bizantine Labs' vault page; TVL from DefiLlama.

A Templar vault on Stellar is a set of Soroban contracts that takes one asset, such as USDC, issues transferable shares and lets a curator lend the money into markets. Deposits settle at once. Withdrawals settle at once only up to the vault's idle cash; anything larger becomes a request that the vault's allocator pays later. In the one live Templar vault we found, Bizantine Labs' tBizUSDC-CORE, the two queued requests on record took 38 and 52 days to pay.

This page covers the vaults. Templar's lending markets, which run on NEAR and lend Stellar USDC to borrowers, are explained in Templar Protocol on Stellar.

tBizUSDC-CORE at a glance

MeasureOn-chain, 10 November 2026
CuratorBizantine Labs, on Templar's Soroban vault framework
Total assets3,930.44 USDC
Idle cash (instant withdrawals)504.02 USDC, 12.8%
In Blend's Fixed pool2,924.65 USDC, 74.4% (pool On Ice)
In Templar markets, via a custodian501.84 USDC, 12.8% (XLM and BTC routes)
Largest holderOne address, 99.9% of shares
Fees15% performance, 0% management
Queued payouts observed38 and 52 days
Admin, curator and adapter adminOne account, one signer
Timelocks24 h; 48 h for upgrades; none for adapter upgrades
Code version1.3.0-rc.1, upgraded 7 November 2026
AuditHalborn audit of Templar's vault framework; no attestation of this deployment

For scale, DefiLlama put Templar's lending markets at $11.46M of Stellar deposits on 10 November, up from $11.27M on 7 November. The vault is a small, separate product at about $3,900.

How a Templar vault is built

A Templar vault is several contracts. The vault holds the money and the books, a share token records who owns what, an ERC-4626-style proxy gives wallets the standard deposit and withdraw calls, a governance contract holds the rules and timelocks, and one adapter per market moves money in and out of that market.

The accounting is one line: total_assets = idle_assets + external_assets. Idle assets are USDC sitting in the vault contract. External assets are what the adapters report the vault's market positions are worth, and Templar's documentation notes that operators refresh those values rather than reading them live. In the week to 10 November the allocator account refreshed them several times a day.

ContractAddress
VaultCBH7TK…4XAA
Share token (tBizUSDC-CORE)CCZF6E…Q2GW
ERC-4626 proxyCB6XEP…TGX5
Governance (since 7 Nov 2026)CA4SFI…YYQT
Blend adapterCDWB5P…QQZO

The proxy follows the ERC-4626 shape that SEP-56 brings to Stellar, so a wallet can call deposit, redeem, max_withdraw and the preview functions without knowing Templar's internals. Each call is forwarded to the vault, which runs it.

How deposits work

Depositing is one transaction. You call deposit on the proxy, the vault takes your USDC into idle cash and mints shares at the current share price. The curator moves that cash into markets in later transactions, so a new deposit first adds to the vault's instant-withdrawal buffer.

There is no deposit cap in the contracts: max_deposit returned an effectively unlimited number on 10 November. Bizantine's page calls its $1M pilot cap "advisory only". Deposits are open to any address, though governance or the Sentinel can switch on a whitelist or blacklist later.

Fees are paid by minting new shares to the fee recipient, which dilutes holders instead of moving tokens. The 15% performance fee is measured from the last fee checkpoint, not from a high-water mark, so Templar's documentation warns that recovering a loss can be charged a fee. By our calculation the share price rose 0.49% between the first deposit on 11 September and 10 November, roughly 3% a year after fees. Bizantine's page modelled 6.4% gross and 5.4% net, and labels that "illustrative only".

Two ways out: instant and queued

A Templar vault has two exits. An atomic withdrawal pays at once, but only from idle cash, and never pulls money back from a market. A queued withdrawal escrows your shares with a fixed claim at today's share price and waits for the allocator to pay it, after a cooldown of one hour on this vault.

  • Atomic (atomic_withdraw, atomic_redeem): settles in one transaction from idle assets. max_withdraw shows the limit. For the largest holder it was 504.02 USDC on 10 November, so 12.8% of their position could leave at once. On 6 November one address deposited 1 USDC and took it back out in two atomic withdrawals within a minute.
  • Queued (request_withdraw): your shares move into escrow and the claim is fixed. The allocator recalls money from markets if needed and calls execute_withdraw. Requests are paid in order, in full or not at all, and the owner cannot cancel one. Templar's documentation adds that the queue does not hold idle cash aside, so an atomic withdrawal can use the cash a queued request is waiting for.

Bizantine's page says that "in the normal case a queued request is paid within about 5 minutes of its cooldown ending", that the vault recalls money from Blend hourly, and that bringing money back from Templar's markets is a manual bridge that "can take several days". The record shows longer waits. The allocator account has called execute_withdraw twice since it began operating in early September, both on 2 November:

Request filed (UTC)AmountPaid (UTC)Wait
11 Sep 2026, 19:092.00 USDC2 Nov 2026, 14:0451.8 days
25 Sep 2026, 20:01100.00 USDC2 Nov 2026, 14:0437.8 days

We read both from Horizon: the request transactions on the owners' accounts and the payouts from the allocator's. Both amounts were small next to the vault's assets and Blend's free cash, so the wait points to when the allocator acted rather than to a market that could not pay. We could not find a stated reason. A payout policy written on a web page is a promise; the queue itself has no deadline.

What happens if a payout fails

Payouts are all or nothing. If idle cash cannot cover the request at the head of the queue, execute_withdraw fails and the request stays queued with its shares in escrow. If a payout gets stuck part-way, the allocator, curator or Sentinel can abort it, and the vault returns the escrowed shares to the owner.

The abort path is in Templar's Soroban vault README: it restores any collected amount to idle, refunds the escrowed shares, drops the request and returns the vault to normal. Two consequences follow. Returned shares are worth whatever the share price is then, not the fixed claim you filed. And because requests are paid in order, one large request that cannot be funded holds up every request behind it until it is paid or aborted.

Who controls the vault

On 10 November 2026 one Stellar account with a single signer held the admin, curator and adapter-admin roles. Bizantine says the key is custodied at Fordefi and that the allocator key sits in the same Fordefi vault. A separate single-key Sentinel can pause the vault and tighten rules, but cannot loosen them.

RoleAccountSigners (Horizon)
Admin, curator, adapter adminGAXHOW…IM2P1
AllocatorGBZCCM…KTUE1
SentinelGAHJUZ…KPTW1
Custodian and NAV reporterGBCF7W…EBGK1

The setup changed in the week before this check. On 4 November the admin proposed a code upgrade and a migration; both were executed on 7 November, and the vault now reports version 1.3.0-rc.1. The same day governance moved to a new contract with a 24-hour timelock on every change and 48 hours on upgrades and migrations. One proposal was pending on 10 November: making the admin account the recipient of skimmed tokens. Templar's documentation still listed the old governance contract.

The timelocks cover the vault, not its adapters. Bizantine discloses that adapter upgrade() is gated by the admin key with no timelock. The Blend adapter held 74% of the vault, so its code could be replaced in one transaction by one key. A Fordefi-custodied key is harder to lose than a hot wallet, but it is still one key.

Where the money is deployed

About three quarters of tBizUSDC-CORE sat in Blend's Fixed pool on 10 November 2026. Around 13% was idle in the vault, and the rest was lent into Templar's XLM and bitcoin markets through a custodian whose reports set its value.

RouteUSDCShareCap on-chain
Idle in the vault504.0212.8%n/a
Blend Fixed pool (direct adapter)2,924.6574.4%400,000 USDC
Templar XLM/USDC (custodial)301.127.7%250,000 USDC
Templar BTC/USDC (custodial)200.725.1%400,000 USDC
Templar XRP and ZEC (custodial)00%Being retired

Templar's documentation lists the Blend route at "400,000 USDC and 40% of NAV", but the vault had no cap groups configured on-chain, which is where a percentage limit would live. Only the absolute caps were in force. Bizantine's page now targets 72.5% in Blend, so the 74.4% matches the curator's plan.

Blend's Fixed pool (CAJJZS…BXBD) was On Ice on 10 November: suppliers can deposit and withdraw, but nobody can open new loans. Its USDC reserve had 45.96M supplied, 34.44M borrowed (74.9% utilised) and 11.68M of free cash. Its backstop reported a token price of zero, so a bad-debt loss would fall on USDC lenders, this vault included. DefiLlama showed the pool's USDC rate at 5.38%. More in Blend pools on Stellar and the Blend backstop explained.

The custodial routes send USDC to a custodian account, which places it in Templar's markets on NEAR. The vault does not see those positions; the custodian signs a report of their value, last filed on 10 November at 07:05 and 08:40 UTC. Templar's documentation says the custodial adapter was outside the scope of Halborn's vault audit, and Bizantine says no third party has attested to this deployment.

Idle cash versus total assets

Idle cash is the only money an atomic withdrawal can touch. On 10 November tBizUSDC-CORE had 504.02 USDC idle against 3,930.44 USDC of total assets, so 12.8% of the vault could leave at once. Bizantine targets 15% idle.

Everything above that depends on the allocator. Money in Blend can come back in an hour if the pool has free cash, and 11.68M USDC was free on 10 November. Money in Templar's markets needs the custodian to bridge it back. One address held 99.9% of the shares, so in practice the vault's liquidity is that holder's liquidity, and a second depositor would share the same 504 USDC buffer.

Risks

  • Payout timing. Queued requests have no on-chain deadline. The observed waits were 38 and 52 days.
  • Key risk. One single-signer account controls governance proposals, allocation and adapter code. Adapter upgrades have no delay.
  • Concentration. Three quarters of the vault is in one Blend pool that is On Ice and has no working backstop.
  • Custody and reporting. The Templar routes are valued by a custodian's signed report, not by on-chain reads.
  • New code. The vault runs a release candidate installed on 7 November 2026.
  • Fees. The performance fee resets at each checkpoint, so recovered losses can be charged.
  • Access. Governance or the Sentinel can switch on deposit restrictions later.

The framework's choices are sensible: timelocks that only slow down risk-increasing changes, a Sentinel that can only tighten, a published audit. The live vault's operating setup is where the risk sits. For how other vault designs handle the same questions, see curated lending vaults explained and DeFindex vaults compared.

Who it suits

A depositor who can wait weeks for anything above the idle buffer, and who is comfortable with one key and a custodian in the path, gets Blend Fixed exposure plus a slice of Templar's lending, minus a 15% performance fee. Anyone who needs to exit on demand is better served by lending on Blend directly, where withdrawals depend only on the pool's free cash. Check max_withdraw and the governance timelocks yourself before depositing; Templar's documentation shows the Stellar CLI commands.

Frequently asked questions

How do I withdraw from a Templar vault on Stellar?

Use the instant withdrawal if the vault's idle cash covers your amount; it settles in one transaction. If it does not, file a withdrawal request. Your shares go into escrow with a fixed claim, and the vault's allocator pays it later. You cannot cancel a request yourself.

How long does a Templar vault withdrawal take?

Instant up to the idle cash, which was 504 USDC in tBizUSDC-CORE on 10 November 2026. Queued requests depend on the allocator. Bizantine says they are normally paid about five minutes after a one-hour cooldown, but the two queued requests on record waited 38 and 52 days.

What happens if a Templar payout fails?

Nothing is paid partly. If idle cash cannot cover the request at the head of the queue, the payout transaction fails and the request stays queued. If a payout gets stuck, the allocator, curator or Sentinel can abort it, and the vault returns your escrowed shares.

Who controls tBizUSDC-CORE?

On 10 November 2026 one Stellar account with a single signer held the admin, curator and adapter-admin roles; Bizantine says the key is custodied at Fordefi. Governance changes wait 24 hours, upgrades 48 hours, and adapter upgrades have no timelock.

Is a Templar vault the same as Templar lending?

No. Templar's lending markets run on NEAR and lend Stellar USDC to borrowers. Its vaults are Soroban contracts on Stellar that a curator allocates, partly to Blend and partly, through a custodian, to those Templar markets.

WhaleHub Research
WhaleHub Research
Protocol research & education · WhaleHub

WhaleHub is a yield-optimization protocol on Stellar. We stake AQUA, aggregate ICE voting power, and auto-compound Aquarius rewards for stakers. This series explains the Stellar DeFi stack — and the wider market around it — in plain English.

Yield on Stellar, with the risks written down

WhaleHub stakes AQUA, pools ICE voting power on Aquarius and pays staker rewards in AQUA. No borrowing, so no health factor to watch.

Launch the app

This article is for education only and is not financial advice. Figures are taken from the sources linked in the text as of the date shown and change constantly. Verify them before acting. WhaleHub is not affiliated with Templar, Bizantine, DeFindex or the apps named here.