Linearprotocol debt repayment and staked token release
Linearprotocol tied the release of staked tokens to repayment of outstanding Builder debt through Linear USD (LUSD) burns. During its 2025 wind-down, converting synthetic assets into LUSD and selling LUSD served different purposes from clearing that debt. A first review of an old position therefore needed to distinguish collateral, token holdings and repayment obligations before committing funds. The shutdown plan preserved a Burn and Unstake Portal, but it didn't specify how long that access would last.
Key takeaway: Accelerated vesting put remaining rewards into staked balances during the wind-down, without clearing the Builder debt that still constrained withdrawal.
Builder debt linked LUSD burns to token release
Builder recorded staked collateral and debt, while the Synthetic Exchange changed a holder's synthetic exposure. LINA was the base collateral token; Linear USD connected borrowing, synthetic exposure and repayment. Building LUSD created a liability for the staker. Converting a Liquid, the protocol's term for a synthetic asset, into LUSD changed the holding without itself clearing Builder debt. These relationships explained why someone could hold LUSD and still have locked collateral.
Wallet-held LUSD and staked LINA reflected different roles within the system. The wallet balance was a token holding. The staked amount backed the Builder position and remained subject to its obligations. Choosing different collateral didn't remove that repayment relationship.
How much LUSD did full repayment require?
Full repayment required enough LUSD to cover the outstanding Builder liability, which could differ from the amount that the position originally created. In the original debt-pool model, account debt changed with the portfolio of Liquids across the protocol. A holder's own asset balance and share of pool debt therefore described different quantities. Changes elsewhere in the pool could affect the obligation even when that holder hadn't exchanged their Liquids. Returning to the original mint amount alone wouldn't establish that all debt had gone.
A partial burn reduced debt. Full repayment cleared the liability that stood between a Builder position and complete collateral withdrawal.
The pledge ratio expressed the relationship between collateral value and debt. In the original design, a higher collateral valuation could improve that ratio while leaving debt outstanding. Additional staked collateral supplied more backing for the liability. Burning LUSD acted on the liability itself. For the closure exit, collateral value and debt clearance therefore answered different questions.
The pool's changing portfolio also explained why a synthetic holding's conversion value wasn't a reliable proxy for an account's liability. Asset conversion valued the holding being exchanged. Debt accounting tracked the account's obligation within the shared pool.
The 2025 repayment path from review to unstaking
An initial review of an old Builder position separated the debt obligation from the assets available to meet it. Reading existing records left the position unchanged, providing a stop point before conversion or burning. In the 2025 wind-down, only conversions into LUSD remained supported on the Synthetic Exchange.
| Stage | Role in repayment | Condition affecting release |
|---|---|---|
| Review the position records | Separate staked collateral, LUSD and Liquids. | A visible stake wasn't proof of cleared debt. |
| Identify outstanding debt | Establish the liability that repayment had to clear. | Debt could differ from the original amount built. |
| Convert Liquids where needed | The wind-down exchange converted remaining Liquids only into LUSD. | Conversion alone didn't repay Builder debt. |
| Retain LUSD needed for repayment | LUSD needed for debt clearance had to remain available for burning. | Selling that LUSD left the liability unpaid. |
| Burn LUSD against debt | Burning reduced or cleared the Builder liability. | A partial reduction didn't establish a full exit. |
| Unstake eligible collateral | Debt clearance enabled withdrawal of staked LINA or other collateral. | Withdrawal remained subject to the debt position. |
A position already holding enough LUSD didn't need to convert Liquids for debt repayment. That stage mattered when synthetic exposure still needed to become LUSD. The review and preparation stages established what the position needed; they didn't themselves reduce debt or withdraw collateral.
Did selling LUSD unlock staked collateral?
Selling LUSD transferred or exchanged a token holding; it didn't perform the debt burn that the Builder exit required to release staked collateral. The shutdown instructions described conversion of remaining Liquids into LUSD, followed by selling LUSD on PancakeSwap. They separately directed Builder users to repay outstanding debt and unstake their collateral. An account holding Liquids could also owe Builder debt.
A sale could reduce an LUSD balance and produce proceeds without clearing the debt that the collateral supported. The wallet change alone therefore didn't demonstrate repayment. Full repayment meant that no Builder debt remained after the burn. Completed withdrawal added another outcome: collateral had actually left the stake.
Released rewards stayed subject to the debt position
Reward release removed the remaining vesting wait, while outstanding Builder debt continued to determine whether the resulting staked tokens could be withdrawn. The 2025 wind-down moved all remaining rewards scheduled to vest over the following 12 months into staked balances. A larger recorded stake could therefore include rewards that hadn't previously been withdrawable.
In the original 2021 model, inflationary staking rewards had a one-year lock and were automatically staked during that period. Fee distributions and inflationary rewards had separate rules, so that lock didn't describe every reward payment. The closure instruction concerned remaining locked and vesting rewards at wind-down. Reading the earlier lock rule as a fresh one-year delay would have missed the later acceleration.
What did the shutdown plan leave available for repayment?
The shutdown plan reserved a Burn and Unstake Portal for debt clearance and eligible withdrawals when the wider dApp suite was scheduled to go offline. Closure was scheduled for 2 April 2025 at 12:00 PM UTC. The retained portal's purpose covered LUSD burning where necessary and unstaking tokens. Its announced remit was limited to exit functions. Synthetic conversion belonged to the separate exchange, which the shutdown plan covered with the wider suite.
The 2025 plan didn't confirm how long the retained portal would remain accessible. Its present availability remains unconfirmed. Possessing LUSD therefore didn't by itself demonstrate a working repayment route for an old stake.
Ordinary token trading dealt with a tradable balance. The retained portal's announced purpose addressed the debt that kept collateral staked.
What readers ask about Linearprotocol
Could a partial LUSD burn restore staking-reward eligibility?
A partial burn could restore reward eligibility under the original design if it brought the pledge ratio back to the required threshold. That threshold concerned collateral value relative to debt. Meeting it wasn't equivalent to clearing all debt for a full exit. The 2025 repayment requirement concerned the outstanding liability before collateral withdrawal.
What fee did the original design apply when Liquids were converted for repayment?
The design dated 12 January 2021 specified an initial 0.25% exchange fee for synthetic conversions. That fee concerned the exchange step, distinct from an LUSD burn against debt. The historical figure didn't establish the fee at wind-down or the cost of an external LUSD sale. For a first review under that design, compare the LUSD proceeds after the exchange fee with the outstanding Builder debt.
Could the project bridge supply missing repayment LUSD after shutdown?
The closure plan scheduled both LUSD bridge directions to close permanently at the shutdown deadline. Under those terms, a post-shutdown bridge transfer wasn't an available way to move LUSD for debt repayment. The affected routes connected Ethereum and BNB Smart Chain. Bridge movement and burning against debt remained different operations.
Was liquidation a substitute for an LUSD repayment burn during wind-down?
The Liquidator had already been switched off when the closure operations update appeared. The exit instructions directed Builder users to repay outstanding debt and unstake collateral. Older plans for liquidation mechanisms didn't make that disabled module a working debt-clearance option. Voluntary repayment remained the method named for resolving Builder obligations in the wind-down instructions.
Did terminal prices guarantee the external sale value of repayment LUSD?
Terminal prices governed the conversion of Liquids into LUSD, not a guaranteed external sale price for that LUSD. Selling LUSD involved a separate market transaction, and the closure notice warned that liquidity would become increasingly limited.
How long did unstaking take after Builder debt repayment?
The wind-down terms linked unstaking to debt clearance without promising a fixed burn-to-withdrawal duration. A stated closure deadline also wasn't an execution-time estimate for an individual withdrawal. The announced portal function covered debt burning and unstaking; its existence didn't guarantee immediate processing or later availability.
Would repaying Builder debt also close a PerpDEX position?
Builder debt repayment concerned staked collateral, while PerpDEX positions required their own exits and fund withdrawals. The operations plan required PerpDEX users to complete those actions before its shutdown. Burning LUSD against a Builder liability didn't establish that a separate perpetual position had closed or that its funds had been withdrawn.