Plan a future strkBTC-to-USDC loan through Vesu on Starknet, with clear checks for LTV, liquidation, variable rates, fees, quotes, and risk controls.
Arkadii Kaminskyi
Arkadii Kaminskyi
Head of Operations at Sats Terminal
Head of Operations at Sats Terminal with 5 years of experience in crypto. Specializes in DeFi, yield farming, and borrowing — has reviewed 50+ crypto products.
Availability notice, August 17, 2026: This Starknet/Vesu route is not currently available in the public Sats Terminal Borrow interface. Sats Terminal has a real integration for using strkBTC to borrow USDC from Vesu's Re7 USDC Prime pool, but Starknet is excluded from the public browser loan profile, and the current staging quote route rejects Starknet requests. This is a held draft that explains the intended eligible workflow for a future launch. It is not an instruction to execute the route today.
The short answer to how the route is designed to work is straightforward. Bitcoin would be converted or bridged into strkBTC on Starknet, that strkBTC would be supplied as collateral to the Vesu Re7 USDC Prime pool, and the position would borrow native USDC. The borrower would then manage a variable-rate, overcollateralized loan whose safety changes with the BTC price, accrued interest, the pool's live risk parameters, and available liquidity.
The difficult part is not the sequence of clicks. It is verifying that the exact route is enabled, that the quote is fresh, and that the starting loan-to-value ratio leaves enough room for Bitcoin volatility. Readers new to the basic model may want to start with how Bitcoin lending works. This guide focuses on the Starknet and Vesu details that matter before a transaction is signed.
| Route element | Intended configuration | What must be verified |
|---|---|---|
| Current Sats Terminal status | Held and unavailable in the public Borrow interface | An explicit availability update and a successful fresh quote |
| Network | Starknet mainnet | Correct network, wallet, recipient, and transaction fee handling |
| Collateral | strkBTC | Exact token address, amount received after conversion, and bridge assumptions |
| Debt asset | Native USDC on Starknet | Exact token address, gross debt, and payout destination |
| Protocol and pool | Vesu V2, Re7 USDC Prime | Pool identity, pair status, debt capacity, liquidity, and live parameters |
| Borrow rate | Variable | Current APR, utilization, and the effect of future rate changes |
| Risk boundary | Pair-specific maximum LTV used by the integration as the liquidation boundary | Current max LTV, health factor, liquidation price, and chosen buffer |
| Sats Terminal fee | Current default platform or disbursement fee is 1% | Fee amount, any disclosed override, bridge costs, network costs, and estimated net receipt |
The Sats Terminal Vesu availability page reflects the important current limitation: an integration can exist in the product stack without being available as a browser route. External Vesu market availability is also not enough by itself. The Sats Terminal quote service, browser profile, transaction orchestration, and supported payout path all have to agree before the route is executable.
Native BTC does not run inside a Starknet lending contract. The configured Vesu route therefore uses strkBTC, an eight-decimal BTC representation on Starknet, as collateral. Economically, the borrower is seeking to preserve Bitcoin price exposure while unlocking stablecoin liquidity. Technically, the position holds a token on Starknet, not native bitcoin on the Bitcoin network.
That distinction adds a separate risk layer. A borrower must understand how native BTC becomes strkBTC, which contracts and bridge providers are involved, whether the quoted output can change, and how the token is redeemed when the loan is closed. A BTC representation can follow the BTC price while still carrying contract, bridge, issuer, liquidity, and operational risks that native BTC does not have. The broader guide to Bitcoin loan collateral explains why the representation matters as much as the ticker.
The configured pair borrows native USDC on Starknet. It is not a Vesu USDT route, and it should not be confused with legacy USDC.e. Opening the position creates USDC debt that grows as interest accrues. Closing it requires enough supported USDC to cover the then-current principal and interest, plus any transaction or routing costs outside the debt itself.
The gross amount borrowed and the amount delivered to the borrower are not necessarily the same. Under Sats Terminal's current default pricing, a 1% platform or disbursement fee is deducted from the principal payout. A cross-chain payout can also have a bridge cost. The quote must distinguish gross debt, fee, estimated routing cost, and expected amount received.
Vesu is built around isolated pools and lending pairs. Its official pool documentation explains that a pair combines a specific collateral asset with a specific debt asset and assigns parameters such as loan-to-value, liquidation bonus, and debt cap. Liquidity can be shared among pairs inside one pool, but it is not shared across separate pools.
Sats Terminal's pinned configuration targets the Re7 USDC Prime pool and only the strkBTC-to-USDC pair. The pool name is not a substitute for the contract address, and the asset symbols are not a substitute for token addresses. A future eligible quote should resolve all three before execution. It should also confirm that the pair is active, not deprecated, sufficiently liquid, and below its debt cap.
Isolation limits how risk spreads between pools, but it does not remove risk inside the selected pool. Pool liquidity, oracle behavior, parameter changes, curator decisions, and the performance of other pairs that share liquidity can still affect the market a borrower uses.
The following sequence describes the integration contract, not a live path available today. The exact screens, transaction count, providers, and sponsorship model can change before launch. A borrower should treat the enabled interface and its fresh review screen as authoritative.
The first check is binary: does the public Sats Terminal Borrow composer return a Starknet quote whose protocol is Vesu, whose pool is Re7 USDC Prime, whose collateral is strkBTC, and whose loan asset is USDC? A marketing page, a protocol listing, or a previously saved screenshot does not establish eligibility. The quote endpoint must accept Starknet and return the route for the specific amounts requested.
Do not send BTC to an old deposit address or attempt to reconstruct the transaction manually from this article. Wait for the public interface to show the route as enabled. The dedicated Vesu USDC route status page can explain availability, but the final proof is still a fresh composer quote.
The borrower would enter the amount of BTC to use and the desired USDC principal. The quote converts collateral into a current dollar value and calculates the requested LTV:
LTV = USDC debt divided by the current dollar value of strkBTC collateral.
Borrowing more USDC raises LTV. Adding more collateral lowers it. The maximum shown by the market is a hard risk boundary, not a recommended target. A sensible starting point depends on expected BTC volatility, how quickly the borrower can react, whether additional collateral or USDC is held in reserve, and how long the loan may remain open.
The route would fetch live Vesu pair data rather than rely on a published static rate. The review should include the variable borrow APR, maximum LTV, collateral amount, liquidation price, debt capacity, gross USDC borrowed, the current default 1% Sats Terminal fee, estimated bridge or payout cost, and estimated amount received.
Any material change should trigger a refresh. That includes changing the BTC amount, USDC amount, LTV, payout chain, payout asset, or destination address. It also includes leaving the screen open while market conditions move. A quote is a time-sensitive snapshot, not a promise that the same rate, liquidity, or conversion output will be available later.
Once the route is genuinely live and the borrower confirms a current review, the intended orchestration begins with BTC on the Bitcoin network and produces strkBTC on Starknet. The amount that actually arrives on Starknet matters. Bridge fees, conversion behavior, minimums, confirmation timing, and slippage can make the received collateral differ from an early estimate.
The lending step should use the confirmed destination amount, not blindly reuse the amount initially typed. If the conversion output is lower, the same USDC principal would create a higher LTV. The workflow must either recalculate and revalidate the position or stop instead of opening a loan outside the approved risk limit.
For the configured integration, supplying collateral and borrowing are designed to be executed together against the Vesu pool. The position is identified by the pool, collateral token, debt token, and Starknet account. A successful transaction should produce an onchain receipt that can be matched to the intended pool and asset addresses.
The borrowed USDC may remain on Starknet or be routed to a supported destination, depending on the final product configuration. A cross-chain payout is a second route with its own provider, cost, minimum, recipient, and failure modes. The borrower should verify the final chain and token, not assume that a USDC label means the funds will land on a preferred network.
A completed interface state is useful, but independent transaction evidence is stronger. Confirm the Starknet transaction status, the strkBTC collateral amount, the USDC debt amount, the pool contract, the account that owns the position, and the payout transaction if funds left Starknet. Then record the opening LTV, liquidation price, variable rate, net amount received, and any fees.
If the loan transaction succeeds but the payout route fails, the debt can still exist. That is why the lending transaction and the disbursement transaction must be checked separately. Never repeat a borrow merely because the expected USDC has not appeared at the destination.
LTV rises when the USDC debt grows or the value of strkBTC falls. It falls when debt is repaid, more collateral is added, or BTC appreciates. Because interest accrues over time, a position can slowly become riskier even if the BTC price stays flat.
For this Sats Terminal integration, the intended health-factor view can be understood as the pair's maximum LTV ratio divided by the position's current LTV ratio:
Health factor = maximum LTV ratio divided by current LTV ratio.
A health factor of 1 means the position has reached the pair boundary. A value above 1 represents some buffer, but it is not a guarantee of time to react. Prices, oracle updates, accrued interest, and competing liquidators can move faster than a borrower can bridge funds or submit a repayment.
Assume 1 strkBTC is worth $100,000, the borrower takes 35,000 USDC, and the pair boundary is 70%. These numbers are illustrative, not current Vesu terms.
The same hypothetical 70% boundary produces very different buffers at different starting LTVs:
| Starting LTV | Opening health factor | Approximate BTC decline to boundary | Interpretation |
|---|---|---|---|
| 30% | 2.33 | 57.1% | Wider mathematical buffer, with all other risks still present |
| 40% | 1.75 | 42.9% | Less room for a deep drawdown |
| 50% | 1.40 | 28.6% | A normal BTC correction could consume much of the buffer |
| 60% | 1.17 | 14.3% | Little room for volatility, delays, or accrued interest |
These percentages ignore fees, oracle differences, bridge timing, and interest. They are not recommendations. Use the live pair parameter and quote math when the route becomes available.
Vesu's official documentation describes a full-liquidation model: once a position exceeds the pair's liquidation LTV, a liquidator can repay all debt and receive eligible collateral at a discount. This differs from protocols where a liquidation may repay only part of the debt. The integration also treats Vesu's liquidation factor as the liquidator discount, not as a second LTV threshold. That makes a conservative opening buffer particularly important.
Vesu borrowing is variable-rate borrowing. According to the protocol's pool model, the interest-rate curve responds to utilization and can also adjust over time as sustained demand changes. A rate visible at origination can rise or fall while the loan remains open. There is no fixed monthly payment that freezes the cost.
A complete cost estimate should separate five components:
Consider a hypothetical quote for 20,000 USDC at an 8% variable annual rate held for 90 days. A simple, non-compounding estimate of interest would be about 394.52 USDC. The current default 1% Sats Terminal fee would be 200 USDC, so the borrower would receive 19,800 USDC before any payout routing cost while still owing a gross 20,000 USDC principal. The 90-day cost would already be about 594.52 USDC before bridge, network, or payout costs. Actual accrual mechanics and the live rate control the final amount.
Collateral supply yield or incentive rewards may offset part of the economic cost, but neither should be subtracted as if guaranteed. Supply yield, reward eligibility, token price, allocation, and claim timing can all change. Compare cost without rewards first, then treat any incentive as a separate variable scenario.
When the route is eventually enabled, a borrower should satisfy every prerequisite before sending funds:
Starknet accounts are smart-contract accounts, so account deployment and transaction authorization can differ from an EVM wallet flow. A user should never copy an address from a test environment into a mainnet action. Network, account, token, and recipient must all match the final signed request.
The highest-value habit is to read the quote as a transaction specification. Before signing, check every field below and stop if one is missing or inconsistent.
| Quote field | Verification question | Why it matters |
|---|---|---|
| Availability | Is Starknet accepted by the public quote route right now? | A configured integration is not automatically a live product route. |
| Market identity | Does it say Vesu, Re7 USDC Prime, strkBTC, and native USDC? | Another pool or token can have different risk and liquidity. |
| Collateral output | How much strkBTC is expected to arrive after the BTC conversion? | Less collateral means a higher realized LTV. |
| Debt and capacity | Is the gross USDC debt within live liquidity and the pair's debt cap? | Capacity can disappear between an old estimate and execution. |
| Risk parameters | What are current LTV, maximum LTV, health factor, and liquidation price? | These define the usable volatility buffer. |
| Variable rate | What is the current borrow APR, and is it clearly labeled variable? | The cost can change after the loan opens. |
| Fees | Does the quote show the 1% current default fee plus network and routing estimates? | Gross principal can be materially higher than net proceeds. |
| Payout | Which chain, token, and address receive the USDC, and how much? | A cross-chain payout adds a separate execution path. |
| Freshness | Was the quote refreshed after the last input, destination, or market change? | Stale parameters can make the review inaccurate. |
If any field changes after refresh, reassess the whole position rather than checking only the rate. The current USDC borrowing page is useful for comparing routes that are actually eligible in the public composer, but it should not be read as proof that Vesu is enabled.
Opening the loan is the beginning of the risk-management work. The intended dashboard would read the onchain Vesu position and normalize collateral value, debt, current LTV, maximum LTV, health factor, variable rate, and liquidation price. Those figures should be monitored together.
A falling BTC price, rising debt, or tighter market parameter can reduce the buffer. The normal responses are to add strkBTC collateral, repay part of the USDC debt, or close the position. Each response requires time, available assets, and a working transaction path. A plan that depends on buying or bridging assets after a crash may fail when networks and markets are busiest.
Use independent price alerts and review the Bitcoin collateral volatility checklist before deciding on a starting LTV. Monitoring is not a promise that liquidation will be prevented. Alerts can be delayed, data sources can fail, and prices can move through a threshold between checks.
A partial repayment lowers debt and usually improves health. Adding collateral improves health without reducing principal, but increases the amount exposed to the same contracts and bridge assumptions. Full closure requires enough USDC to cover all current debt and releases collateral only after repayment succeeds.
The pinned integration also recognizes a current $10 Vesu floor for nonzero residual debt or collateral in this pool. A tiny remainder can fail as a dusty balance, so a future interface should validate the result of partial repayment or withdrawal before submitting it. This value can change and must be checked against the live market implementation.
Keep transaction hashes and verify onchain state after every management action. A wallet notification or an interface toast is not a substitute for confirming that debt and collateral changed as intended. For a broader operating routine, see how to monitor loan health.
Borrowing USDC against strkBTC combines several systems. Risk should be evaluated end to end, not only at the Vesu pool layer.
| Risk | How it can affect the borrower | Practical control |
|---|---|---|
| BTC market and liquidation risk | A BTC decline raises LTV and can trigger full liquidation. | Start below the limit, hold a reserve, and monitor continuously. |
| Variable-rate risk | Higher utilization can raise interest and grow debt faster. | Model higher-rate scenarios and reassess the position regularly. |
| Smart-contract risk | A defect or exploit in Vesu, tokens, wallets, or routing contracts can cause loss. | Review official audits and limit exposure to an amount you can afford to risk. |
| Oracle risk | A stale, incorrect, or manipulated price can distort collateral valuation. | Understand the pool's oracle configuration and avoid a narrow buffer. |
| strkBTC representation risk | The token can face bridge, redemption, liquidity, or contract problems separate from BTC. | Verify the exact asset and understand its conversion and exit path. |
| USDC risk | Stablecoin depegging, freezing, or chain-specific liquidity issues can affect payout and repayment. | Verify native USDC and keep a supported repayment reserve. |
| Pool and curator risk | Liquidity, debt caps, or risk parameters can change. | Check live pool data before opening and before adding debt. |
| Bridge and payout risk | Conversion or cross-chain disbursement can be delayed, fail, or deliver less than estimated. | Verify each transaction leg and never repeat the borrow without checking debt. |
| Interface and availability risk | A route may be disabled while a position still requires management. | Understand fallback access and keep records of pool, assets, account, and transactions. |
Vesu's official risk guide highlights smart-contract, oracle, collateral, curator, utilization, and liquidation risks. Audits, monitoring, and isolation can reduce some exposures, but they cannot eliminate borrowing risk.
Some Vesu BTCFi activity may be associated with STRK incentives, but reward economics should not drive the core borrowing decision. Eligibility, allocation, APR, token price, and distribution timing are variable. A quote should never present a reward rate as fixed, and a borrower should be comfortable with the loan's cost and liquidation risk even if rewards are zero.
For the incentive mechanics, see how Starknet BTCFi rewards work. For the separate operations layer, see how Sats Terminal tracks and claims Vesu STRK rewards. Both are future cross-links and should remain secondary to collateral safety, rate, and total cost.
If the route is enabled later, it may fit a borrower who wants USDC liquidity without selling BTC exposure, understands tokenized BTC and Starknet, can tolerate a variable rate, chooses a meaningful liquidation buffer, and has both collateral and USDC reserves for position management.
It may not fit someone who needs to borrow today, requires a fixed rate or guaranteed net proceeds, cannot actively monitor an overcollateralized loan, does not accept bridge and smart-contract risk, or would be forced to sell assets during a rapid BTC drawdown. It is also unsuitable if the quote is incomplete, the payout route is unsupported, or the requested amount is too close to the pair's debt capacity.
There is no universal safe LTV. The right decision depends on the live market boundary, the borrower's time horizon, the size and accessibility of reserves, and the drawdown the borrower can survive without relying on perfect execution. The expected outcome of a conservative structure is more room to respond, not immunity from loss.
Final availability notice, August 17, 2026: The strkBTC-to-USDC Vesu route is not currently available in the public Sats Terminal Borrow interface, and the current staging quote route rejects Starknet. This article is planning guidance for a future eligible route, not a live call to borrow.
Use the checklist now to decide what evidence you would require from a future quote. Wait for an explicit Sats Terminal availability update, then recheck the route, pool, assets, LTV, rate, capacity, 1% default fee, network costs, payout, and quote freshness from the beginning. Until that status changes, compare only routes that the public composer actually returns and do not attempt to initiate this Starknet/Vesu flow.
Common Questions
No. As of August 17, 2026, Starknet is excluded from the public Sats Terminal Borrow loan profile, and the current staging quote route rejects Starknet. The Vesu integration exists, but the browser route is not available. Do not send funds or try to execute it from this guide.
