How many of you got liquidated using heavy leverage during a volatile move?
I got liquidated on $BTC and $HYPE before, so TermMax immediately caught my attention.
I had mentally put fixed-rate + fixed-term in the same box as predictable risk.
Then I looked at what actually happens when the collateral moves.
The rate stays fixed. The maturity stays fixed.
The position doesn't.
Once a TermMax loan breaches its LLTV threshold, liquidation becomes possible. And if maturity arrives without repayment, the position enters a liquidation window.
Then I found one detail that made me look at the risk differently.
For debt above $10,000, liquidators can liquidate up to 50% of the debt, with a 10% penalty on the liquidated amount.
So liquidation doesn't necessarily mean the whole position disappears.
Half can go while the other half remains.
That got me thinking about liquidation differently.
I used to ask: “Can my position get liquidated?”
Now I'd rather know: “What does my position look like after liquidation starts?”
Because the fixed rate tells me what the debt costs.
It doesn't tell me what survives when the collateral gets hit.
1H structure is still bullish after the strong breakout from ~0.18. Price is now consolidating around 0.22–0.24, rather than immediately giving back the move.
I would wait for a pullback, not chase at 0.2285.
$ACE Long entry: 0.220–0.224 Stop-loss: 0.211 TP1: 0.242 TP2: 0.252
Invalidation: 1H close below 0.211.
Key resistance is 0.2522. A clean breakout above that level could open the way for further continuation.
$HEMI — Trade Plan Bias: LONG The 1H chart still looks bullish. After the breakout, HEMI pulled back sharply but buyers defended the 0.0075–0.0081 area and pushed price back toward the high.
I would not chase at 0.00886.
$HEMI Long entry: 0.00835–0.00855 on a successful retest Stop-loss: 0.00795 TP1: 0.00920 TP2: 0.00970
Invalidation: 1H close below 0.00795.
Key level: 0.009245. A clean 1H breakout above it would strengthen the continuation setup.
$BTW — Trade Plan Bias: SHORT The chart shows a massive 1H breakout, followed by rejection from 0.7789 and three consecutive red candles. Momentum is cooling, so I would not chase the short at 0.648.
$BTW Short entry: 0.675–0.700 on a failed retest Stop-loss: 0.725 TP1: 0.610 TP2: 0.555
Invalidation: 1H close above 0.725.
The key is the retest. After a +75% move, chasing either direction is risky.
I thought fixed-rate borrowing gave me the easiest answer in DeFi: “Tell me the rate, and I'll know what this borrow costs.”
Then I looked at TermMax’s borrowing curve.
One documented example starts around 17% APR for the first 1.5M, moves toward 15%, then another 0.2M moves toward 10%, while the final 0.17M moves toward roughly 7.5%.
That's when “fixed rate” started sounding different to me.
Say I need 500K. I might interact with one part of the curve. Now say I need 2M.
I'm not simply borrowing four times as much at the same fixed rate. A larger borrow can push my order into a different part of the curve.
So the question isn't simply: “What's TermMax's fixed rate?”
It's: “What rate does my size actually reach?”
And that's the part I hadn't considered. The rate can be fixed once my portion is matched.
But before that, my order still has to find its place on the curve.
So if I were putting a large amount through TermMax, I'd want to know one thing before looking at the headline rate:
I was looking at Dusk’s prover requirements like I was shopping for a gaming PC. 16 cores?
I thought that meant a proof could throw all 16 at the problem.
Then I found the awkward part. Proof generation is single-threaded. So a 16-core machine doesn't make one proof a 16-core job.
Then I noticed the other part of Dusk's requirements: prover performance is tied to how many workers the server can run simultaneously, with one CPU core specified per worker. That made the 16-core number feel very different.
The cores aren't simply making one proof faster. They're giving the prover more room to handle multiple proving jobs at the same time.
And suddenly I realized I'd been reading the hardware requirement as one number: How fast is this prover?
But there are two very different questions hiding underneath it.
How quickly can one proof get through its work? And: How much proving work can the machine handle concurrently?
I thought 16 cores answered the first question. It doesn't, at least not by itself.
Bias: SHORT — the 1H chart shows a sharp rejection from 0.1515 followed by consecutive lower highs and strong selling. The bounce around 0.122 is weak so far.
I wouldn’t short directly into 0.122. Wait for a relief bounce toward 0.124–0.127 and rejection.
Bias: LONG — the 1H chart shows a clear breakout from the 0.088 area with a massive expansion candle. The current red candle is a pullback from the spike, but it hasn't broken the breakout structure yet.
I would wait for a retest around 0.1025–0.1050, rather than chase at 0.1073.
Bias: $VELVET SHORT — the 1H structure is clearly bearish, with consecutive lower highs and lower lows. Price is sitting near 0.511 support, so I would not short at 0.5187 after the dump. Wait for a bounce into the entry zone and rejection.
I was looking at Dusk Trade and made a connection that felt almost too easy.
More tokenized securities on Dusk. More trading. More DUSK demand. Makes sense.
Then I looked at what was actually being traded.
The security isn't DUSK. ...wait.
Dusk Trade can handle the financial asset while DUSK sits underneath as the network asset. So I started wondering if I had quietly merged two different things in my head.
Dusk activity. DUSK activity.
They sound like the same thing until they aren't.
A security can change hands without that whole financial flow becoming demand for DUSK. And now I can't really look at “more assets on Dusk” the same way.
The part I'd want to understand isn't just how much gets traded. It's how much of that activity actually reaches DUSK.
@Dusk $DUSK #dusk What matters more for DUSK if Dusk Trade scales?