Yuuki Trading

There was a time I opened a Position, went to brush my teeth for 5 minutes, and when I came back I was still checking the Health Factor before even looking at the BTC price...

that was when it started to feel funny.

we say we're managing capital, but capital is managing us instead!

on the Public Testnet of @BabylonLabs_io I tried using 0.08 BTC worth 8,000 USDT as Collateral.

BTC Collateral Factor of 78% brings the Risk-Adjusted Collateral Value down to 6,240 USDT.

if Debt is 4,000 USDT, Health Factor = 6,240 / 4,000 = 1.56.

sounds pretty comfortable.

but I no longer look at Maximum Borrowing Capacity... I look at Liquidation Price, Safety Margin and ask myself: if BTC takes a Drawdown at 3 a.m., what would happen to me?

BTC drops 25%, Collateral Value falls to 6,000 USDT.

after the Collateral Factor, only 4,680 USDT is counted, with the Health Factor at around 1.17.

still above the Liquidation Boundary of 1.0.

still some Volatility Buffer left.

then I increased Debt to 5,500 USDT to see what “better” Capital Efficiency feels like.

the initial Health Factor is around 1.13.

BTC only needs to drop 15%, and it is already around 0.96.

before accounting for Interest Accrual.

before accounting for Oracle Update.

before accounting for Liquidation Bonus.

three things that sound highly technical, but when Position Health drops fast, they stop being theory...

TBV gives me what I like: Native BTC stays on Bitcoin, Self-Custody still preserves Asset Control.

but Application-Side Parameters are still running, Lending Risk is still running, and Liquidation Risk has not gone anywhere either.

to be fair, I am starting to dislike Positions with Capital Efficiency that looks too beautiful.

for me, the largest Borrowing Capacity is not necessarily an advantage.

a good Position should be able to withstand Market Volatility... without turning every Price Decline into an alarm.

would you choose more Yield, more Leverage... or keep a Safety Margin large enough that you do not even need to remember you have a Position?

#baby $BABY @BabylonLabs_io

I have a pretty bad habit when testing protocols: the moment I see true, my brain automatically stamps it as “done”... and that exact reflex once made I misread an entire State Machine.

that day, looking at ack_complete=true, I almost ignored vault_active=false.

good thing I stopped.

Pre-PegIn passing 12 Signet Block Confirmations only means the Confirmation Count has reached the Trigger Condition for ACK Collection to begin, not that Vault Activation has happened.

one state label changes, and the control rights change with it.

Signing Participants completing the Collaborative Setup within an ACK Window of roughly 24 hours gives ack_complete=true; but User Authorization still does not exist if the User has not performed the Secret Reveal within the Activation Window of roughly 48 hours.

24/48 = 50%.

in other words, the ACK Window occupies only about half of the Activation Window's time space... yet I used to unconsciously treat ACK Completion as the Final State.

honestly, this is where I find the design of @BabylonLabs_io pretty uncompromising.

the protocol does not care how impatient we are.

it only cares whether the State Dependency is correct.

if there are not enough ACKs before Expiration, the Vault may expire and Peg-in Fee Refund becomes a valid branch.

if enough ACKs already exist but Secret Reveal has not happened, continuing to suspect ACK Data Loss or spamming ACK Retry only sends us in circles.

I started reading logs in three layers: Block Confirmation first, Collaborative Setup second, User Activation last.

no skipping steps.

no interpreting the protocol on its behalf.

and from that point on, I also noticed something rather painful: Testnet Parameters such as 12 blocks, ~24h, or ~48h may be Mutable Parameters, but the most reliable thing is actually the State Transition between Pre-PegIn, ACK Completion, Active State, and Final State.

in your view, should a good Bitcoin Vault try to make the experience feel “fast”, or should it force users to respect each layer of authority like this?

#baby $BABY @BabylonLabs_io

These past few days I’ve picked up a slightly bad habit... whenever I come across a protocol talking about yield, I no longer look at the APR first, I look for the money’s exit path first.

with @BabylonLabs_io it was the same.

I sat down and traced a 0.05 BTC flow from UTXO → P2TR Output → Taproot Script → Unbonding, then got stuck right at CLTV.

301 blocks.

if we take an average of 10 minutes/block, it takes more than 50 hours.

honestly, that number bothered me even more than a low yield... but it was also exactly what made me believe this lock is not just a decorative “unstake” button.

then came EOTS.

Finality Provider uses a One-Time Schnorr Signature, nonce commitment is bound to block height; if it Double Signs two conflicting blocks, then k=(s1-s2)/(H1-H2).

sounds like a problem that only exists on paper?

Private Key can be Extracted → Slashing Transaction has a real execution path → UTXO bears the consequence.

I even pulled out the Control Block and Taproot Leaf to inspect them again, because this is where I see the biggest difference: punishment does not exist only inside a Contract State Machine.

Bitcoin Consensus stands behind the execution.

CLTV guards the exit path.

EOTS guards signing behavior.

Taproot guards the spend conditions.

I’m becoming increasingly allergic to systems that feel too “smooth”, because sometimes that smoothness merely hides the fact that users are handing Control over to a layer of Contract Custody.

for me, Mainnet Ownership is worth more than a pretty receipt.

Security Premium lies exactly there: Finality Provider can earn reward, but when it breaks the Finality of a Bitcoin Secured Network, Cryptographic Slashing does not ask what excuse it has.

if 0.1% of 0.05 BTC gets burned, that is 0.00005 BTC disappearing for real.

small in quantity... but enormous in economic meaning.

would you choose a protocol that lets you withdraw as fast as possible, or choose a protocol that makes whoever protects Finality think twice before signing?

#baby $BABY @BabylonLabs_io

There was a time i chose a Validator just because the Commission was lower... looking back now, i realize i was viewing the network like a price board.

Babylon made me change that habit.

21 Validator Nodes, 14 are on AWS US East, which is about 66.7%.

3 are on Google Cloud Europe, 2 on Alibaba Cloud Hong Kong, while Bare-Metal Nodes are only 2/21... about 9.5%.

but honestly, the thing i fear most is not AWS.

i fear Correlated Failure.

same Cloud Provider → same Geographic Region → same Availability Zone or shared Operations Team → the Blast Radius expands extremely fast.

at least 8/21 nodes are mentioned under the same Stakin, which is about 38.1%.

suppose one deployment fails, credentials run into issues, or the same monitoring system reports incorrectly... eight different names on the Validator Set could still fall in the exact same rhythm.

that is where i used to misunderstand Validator Decentralization.

Node Count does not equal Voting Power.

more servers also do not equal Infrastructure Diversity!

a network can look extremely crowded, but if Failover is weak, there is no Standby Server, Multi-Cloud Deployment is poor, Disaster Recovery is vague, RTO drags on... then when an incident arrives, that is when the true face of Network Resilience reveals itself.

i once paid extra Commission for a Validator running a Bare-Metal Server and even thought it was a waste at the time.

now i think differently... a few percentage points of Commission may actually be the price of buying Redundancy, Geographic Diversity, Fault Isolation and an SRE team that does not fall asleep at the wheel.

the bigger @BabylonLabs_io becomes, the more i want to look at Operator Concentration, uptime history, failover design and infrastructure topology before looking at APY.

Decentralization is most beautiful not in the number of logos on the screen — it lies in how many things a single failure can drag down with it.

if you had to choose, would you prioritize cheaper Commission or a Validator with a smaller Blast Radius?

#baby $BABY @BabylonLabs_io $BLESS $HOME

Last night I opened Aave v4 again, still the same vault... but this time I didn't look at USD first.

I looked at time.

0.12 BTC sits inside TBV Flow, vaultBTC shows its status, Borrowing Capacity is over 7,000 USD, while I only pull 4,800 USD.

sounds a little wasteful, right?

to be honest, I used to think Collateral Efficiency meant the more you borrowed, the better.

now I see the opposite.

the most valuable thing is not a high limit, but knowing where the collateral currently sits inside the Lock → Challenge → Redemption State Machine, how much time remains in the Challenge Window, and when the Unbonding Window could leave me stuck.

that is the real risk.

UTXO Proof goes into the Programmable BTC Collateral API, underneath are Taproot Timelock, ZK Proof, BABE Protocol handling Bitcoin ZK Verification, while on my side all I see is the Liquidation Threshold and the Stablecoin Borrowing button.

it feels very strange...

the more complex the system becomes, the fewer things the experience makes me think about.

but having fewer things to think about does not mean I am allowed to become complacent!

I deliberately leave more than 2,000 USD of Borrowing Capacity untouched like a brake.

for me, that is what makes @BabylonLabs_io keep me thinking for a long time: vaultBTC does not just turn locked assets into Collateral for EVM DeFi, it turns “locked time” into a variable that has to be managed.

wBTC solves Liquidity through Custody and adds a Trust Chain.

TBV chooses Cryptographic Verification, UTXO Proof and Challenge Period.

two completely different paths.

if vaultBTC later expands into Morpho, RWA Collateral Pool or more BTCFi markets, I will still keep this same habit: not borrowing everything.

even when the dashboard tells me I still have room left!

because when the market shakes hard, a 20% buffer can sometimes be worth more than another 20% of Stablecoin sitting in the wallet.

would you choose maximum Collateral Efficiency, or accept earning less in exchange for a truly wide breathing room?

#baby $BABY @BabylonLabs_io $IDOL $BEAT

Last night I plugged my Ledger Stax back into my Macbook Pro just to check something that seemed incredibly small: do I truly understand what I am about to sign?

An Unsigned PSBT from @BabylonLabs_io appeared on screen: 0.032 BTC, fee 7 sat/vB, one existing UTXO being spent and one new P2TR output being created.

I sat in silence...

because behind that interface were an Internal Key, Taproot Script Tree, CLTV Timelock Leaf, EOTS Slashing Path and Unbonding of 1008 blocks, approximately 7 days.

honestly, I once thought a Hardware Wallet was merely a place to store a private key.

wrong.

it is where I am forced to confront the consequences.

Is the Output address correct?

Is the Amount off?

Does the Locktime match?

is this a Key-Path Spend or a Script-Path Spend?

the moment I press confirm out of habit, every concept such as Self-Custody, Signing Authority or On-Chain Ownership immediately turns into an empty slogan.

Ledger does not know the Babylon state.

Babylon frontend cannot see the private key.

Finality Provider cannot arbitrarily touch the P2TR output either.

User Signature → Schnorr Signature → Transaction Broadcast → Block Confirmation.

clear, cold, with no one there to save me from a careless decision.

the part that kept me thinking the longest was EOTS.

Double-sign is not merely recorded as an operational mistake; Private-key Extraction can trigger slashing of 0.1% and send that portion of the assets to a burn address.

I prefer this kind of design over systems that offer nothing more than a beautiful dashboard and a support button.

because Script-Level Hard Constraints do not care whether you are a whale, validator or newcomer.

sign correctly and move forward.

sign incorrectly and bear the consequences.

in my view, the deepest value of Native BTC Staking does not lie in Yield, but in turning ownership into responsibility that can be verified through cryptography.

everyone wants absolute control... but are they truly ready to accept absolute responsibility for every single signature?

#baby $BABY @BabylonLabs_io $GRVT $KOMA

There was a time I let a script run through 47 epochs just to reconcile reward accounting with the canonical state.

by morning, the coffee was still untouched... while the numbers looked far too perfect to be trusted.

one Finality Provider had already left the active set, the stake had unlocked, yet ActiveSatoshis remained there as though no state transition had ever occurred.

honestly, I am not as afraid of numbers as I am of incorrect numbers that remain deterministic, still get recorded by the keeper, then pass through reward distribution as though everything were normal.

x/costaking → stale state → phantom stake → reward leakage.

a short chain... yet economic security can be breached through exactly one field that was never reset!

@BabylonLabs_io uses a dual staking model, BTC staking weight, BABY staked amount, epoch duration and cumulative_reward_ratio to distribute validator rewards.

it sounds highly sophisticated.

but GHSA-4rmq-mc2c-r495, CVSS 6.9, shows that an inactive FP can still retain non-zero ActiveSatoshis after leaving the validator set.

meanwhile GHSA-869w-47c6-fq8q, CVSS 8.2, follows a different path: IBC packet → token minting → DepositValidatorRewardsPool → integer overflow → panic → EndBlocker crash → x/epoching stops → chain halt.

one bug strikes accounting.

one bug strikes liveness.

two different doors, both leading to the same uncomfortable question: does the state machine truly reflect the assets that still exist?

I once simulated 500 units of phantom stake persisting for another 24 epochs.

with only a 3% deviation in reward weight, those still carrying exposure get diluted, while those who have already left the system continue receiving rewards... the dashboard stays green, blocks keep running, who would notice?

my view is rather harsh: a protocol does not lose trust because it has bugs; it loses trust when economic discrepancies still appear valid.

would you trust the dashboard... or trace every state transition yourself?

#baby $BABY @BabylonLabs_io $GRVT $KOMA

📊 $COTI Liquidation Heatmap — Short-Term Bias Leans LONG

$COTI is trading near 0.0179 after recovering from the 0.015 area. The nearest major liquidation clusters are concentrated above the current price, while lower support zones remain well defined below.

🔹 Immediate upside zone: 0.0188–0.0192
🔹 Next liquidity zone: 0.0200–0.0204
🔹 Key support: 0.0168–0.0162
🔹 Major downside liquidity: 0.0142–0.0138

Main scenario:
• Holding above 0.0168 keeps the bullish structure intact
• A clean break above 0.0192 could extend the move toward 0.0200–0.0204
• Losing 0.0162 would weaken the setup and increase the risk of a move toward 0.0142–0.0138

Disclaimer: Trading always involves risk, do your own research (DYOR)

It seems stronger than I initially thought. The more I research, the more I see the team has accomplished some impressive things. However, the crash from $0.22 to $0.08 within minutes still keeps me from fully trusting it.

I'm not planning to buy for now, but I won't rule out its potential either.
This is just my personal opinion.

For now, I'm staying on the sidelines and watching.

In the next few hours or days, we'll see whether it heads back to $0.07 or $0.20.

#45NgayTuDoTaiChinh $BEAT $ON

There was a time close to 2 a.m. when I deliberately killed the local node and restarted it just to watch the logs run line by line.

cold noodles, the laptop fan screaming, block height frozen for nearly 40 seconds... at that point I had no interest left in hearing about security inheritance.

I only asked: after a panic-induced crash, can state synchronization really bring the node back to the correct canonical chain?

I built a small scenario: 12 minutes of downtime — 3 competing block headers — 1 staking transaction slipping into the wrong fork.

Bitcoin light client still verifies block headers and UTXO script validation very efficiently, but it cannot detect every chain reorganization, orphan block or deep rollback.

efficient does not mean reliable!

@BabylonLabs_io has a highly ambitious architecture: Bitcoin-secured PoS, Finality Provider, Cross-chain Slashing and EOTS.

but the more I tested it, the more I realized that the most dangerous attack surface does not lie in the whitepaper.

it lies in restart state, return value, signature domain and a few lines of code that seem insignificant.

2 EOTS Signatures at the same Block Height → Double-signing → Private-key Extraction.

then GenerateRandomness, SetByteSlice, Secp256k1 Group Order, Nonce Bias and HNP Attack connect into another path: weak Randomness → EOTS Private-key Recovery.

and that is not all...

missing domain separation can turn a PoP Signature into a Signature Replay for MsgCommitPubRandList, leading to message-type confusion and an invalid public-randomness commitment.

honestly, I do not evaluate a protocol by how well it performs under ideal conditions.

I look at it when RPC lags, the Process dies, Headers arrive out of order and the Operator is half asleep.

Cryptographic Elegance is a promise.

Operational Resilience is where the real money is.

with Babylon, do you place your trust in the security model... or in the system’s ability to survive the chaotic minutes no one ever puts in a demo?

#baby $BABY @BabylonLabs_io $BEAT $BANK

📊 $BANK Liquidation Heatmap — Short-Term Rebound Bias Leans LONG

$BANK is trading near 0.188 after a steep decline from above 0.35. The broader structure remains bearish, but the strongest nearby liquidation clusters are positioned above the current price.

🔹 Immediate upside zone: 0.200–0.210
🔹 Next liquidity zone: 0.220–0.230
🔹 Major upside liquidity: 0.255–0.262
🔹 Key support: 0.175–0.165

Main scenario:
• Holding above 0.175 keeps a rebound toward 0.200–0.210 possible
• A clean break above 0.210 could extend the move toward 0.220–0.230
• Losing 0.165 would weaken the rebound setup and expose 0.150–0.135

Disclaimer: Trading always involves risk, do your own research (DYOR)

In April 2026, I opened a testnet Vault, locked 0.6 BTC, minted 0.4 vaultBTC, then borrowed 3,250.7 USDC; 43 minutes later, the collateral ratio was green but the oracle was 2 blocks behind...

that was when I understood, assets sitting in Taproot UTXOs do not necessarily sleep soundly.

the problem is not just custody risk.

but once liquidation begins, what are we allowed to do?

@BabylonLabs_io built a resilient bridge-free architecture: host-chain state travels with a Groth16 proof, BABE reduces verification cost, BitVM3 moves off-chain computation into a garbled circuit, then uses a fraud proof to handle invalid spends.

permissionless challenge sounds great

but how long is the challenge window when the mempool is congested?

how does a whitelisted liquidator respond if oracle lag coincides with a 15.7% price wick?

Oracle lag → Liquidation latency → Bad debt... the market does not need to break cryptography, it only needs to move faster than the system.

Aave V4 Spoke uses vaultBTC as a 1:1 restricted ERC-20, repays USDC, then unlocks the mainnet UTXO; elegant, easy to understand.

but I once spent 8 hours exiting a Vault because liquidity dried up; self-custody does not mean self-rescue.

this is where I look closely — the self-rescue path, collateral ratio buffer, emergency repayment, liquidity depth, and execution risk.

a protocol can be cryptographically secure yet still operate poorly.

a Vault may not be stolen from but can still be liquidated according to the rule, block, oracle!

alpha testnet is only a technical test; mainnet deployment, BTC mainnet congestion, and a full market cycle are the real test of character.

as for governance, staking-gated access, fee auctions, or the August unlock... to me, they come after vault security.

I do not need the promise of “trustless”.

I need proof that when everything goes wrong, there is still a way out.

do you judge a Vault by its cryptographic proof, or by the number of minutes it gives you to save yourself before liquidation?

#baby $BABY @BabylonLabs_io $BANK $AKE

At 2:17 on 18/11/2025, I opened a Vault: 0.7 BTC collateral, 18,400.5 USDC debt, health factor 1.6.

there was no cinematic scene; only the sound of the laptop fan, a cup of coffee, and the liquidation price sitting 19.3% away from the market price.

I thought yield was money sitting still and reproducing on its own.

wrong!

yield is a living position: collateral ratio → borrow rate → oracle update → liquidation engine.

Aave v4 displays gross yield of 4.7%, but utilization rate edges up from 71.4% to 86.2%, variable interest rate drags net yield down to 3.3%.

add cross-chain gas costs, liquidation buffer, slippage, and redemption latency... the beautiful number starts falling apart piece by piece.

TBV still has what I like: native Taproot UTXO, BitVM3, fraud proof, challenge window, vaultBTC collateral, no bridging, no wrapped asset.

where the asset sits, what the debt is denominated in, who has the right to touch the collateral... at least the trail can still be traced.

while @BabylonLabs_io offers nominal BTC yield around 0.5%, BABY staking APY once stood at 13%–20%.

does that gap sound strange yet?

8% annual inflation, monthly token unlocks from 5/2026 through 2029, more than 90% drawdown, thin secondary-market depth... paper APR can be high, realized yield still shrinks.

if a finality provider loses liveness, there is slashing.

if the market loses liquidity, the exit price becomes distorted.

if the oracle lags by one beat, the health factor does not ask whether I read the whitepaper carefully!

honestly, after several times thinking I was earning passive income only to end up watching the position at midnight, I understood one thing: the highest yield usually charges in attention before it charges in money.

I fear volatility less than not knowing whether the risk lies in the contract, token dilution, or my own habit of chasing another 1.4%.

do you choose higher yield and constantly manage the position, or lower yield in exchange for the right to forget about it?

#baby $BABY @BabylonLabs_io $DEXE $BANK

Three months ago, at 2:17 a.m., I locked 0.6 BTC, borrowed 27,400.5 USD, set the liquidation threshold at 122.5%, then went to make instant noodles.

23 minutes later, the price dropped 18.7%.

the bowl of noodles was still hot... the position was nearly wiped out.

the contract wasn't broken.

the price oracle was still running.

the liquidator was only doing its job.

I was the one at fault.

self-custody protects assets from other people, but it does not protect us from our own decisions.

that is why, when reading section 6 of @BabylonLabs_io , I did not focus on the “no need to trust anyone” narrative first.

I looked at the exit path.

USDB is created through cross-chain minting while collateral remains inside a self-custodial vault on the Bitcoin chain; during redemption, the user burns the stablecoin → generates a zero-knowledge proof → proof verification → unlocks the vault.

no custodian.

no approval committee.

minting authority is locked within protocol rules.

that is real trust minimization, clearly reducing counterparty risk and custodial risk.

but honestly... has smart contract risk disappeared?

no.

has liquidity risk disappeared?

no, either.

a vault worth 40,000.5 USD, debt of 24,000.5 USD, collateral ratio of 166.7%; if the price drops 25.7%, the ratio falls to only around 123.8%.

just one bout of slippage, and a liquidation cascade could turn depeg risk into systemic risk.

the market does not care how permissionless you are!

section 10 was what made me sit with it longer: protocol fees → automatic auction → token burn.

as usage increases, supply contraction becomes stronger, and value capture becomes clearer.

sounds good.

but tokenomics is only worth something after a stress test, not after a few beautiful diagrams.

a good protocol does not just return the right to hold assets; it must make users see the cost of leverage before the market comes to collect.

so is USDB expanding financial freedom, or forcing users to become more mature about their own risks?

#baby $BABY @BabylonLabs_io $RIF $BANK

📊 $ESPORTS Liquidation Heatmap — Short-Term Bias Leans Bearish

$ESPORTS is trading near 0.0286 after being rejected from the 0.0305–0.0310 area. Price remains under short-term resistance, while nearby liquidity is concentrated below the current level.

🔹 Immediate downside zone: 0.0272–0.0267
🔹 Next liquidity zone: 0.0240–0.0235
🔹 Key resistance: 0.0295–0.0305
🔹 Major upside liquidity: 0.0310–0.0328

Main scenario:
• Staying below 0.0295–0.0305 keeps downside pressure active
• Losing 0.0267 could extend the decline toward 0.0240–0.0235
• Reclaiming 0.0305 would weaken the bearish setup and bring 0.0310–0.0328 back into focus

Disclaimer: Trading always involves risk, do your own research (DYOR)

📊 $ERA Liquidation Heatmap — Short-Term Rebound Bias Leans LONG

$ERA is trading near 0.0856 after maintaining a clear intraday downtrend. Although the broader structure remains bearish, larger liquidation clusters are concentrated above the current price.

🔹 Immediate upside zone: 0.089–0.091
🔹 Next liquidity zone: 0.094–0.097
🔹 Major upside liquidity: 0.104–0.110
🔹 Key support: 0.083–0.081

Main scenario:
• Holding above 0.083 keeps a rebound toward 0.089–0.091 possible
• A clean break above 0.091 could extend the move toward 0.094–0.097
• Losing 0.081 would weaken the rebound setup and expose 0.079–0.078

Disclaimer: Trading always involves risk, do your own research (DYOR)

📊 $NEAR Liquidation Heatmap — Short-Term Bias Leans Bearish

$NEAR is trading near 1.898 after maintaining a clear intraday downtrend. The closest long-liquidation clusters remain below the current price.

🔹 Immediate downside zone: 1.890–1.880
🔹 Next liquidity zone: 1.860–1.850
🔹 Key resistance: 1.925–1.950
🔹 Major upside liquidity: 1.970–2.030

Main scenario:
• Staying below 1.925–1.950 keeps downside pressure active
• Losing 1.880 could extend the decline toward 1.860–1.850
• Reclaiming 1.950 would weaken the bearish setup and bring 1.970–2.030 back into focus

Disclaimer: Trading always involves risk, do your own research (DYOR)

📊 $ZEC Liquidation Heatmap — Short-Term Bias Leans Bearish

$ZEC is trading near 517 after maintaining a clear intraday downtrend. The nearest meaningful liquidation clusters are located below the current price.

🔹 Immediate downside zone: 514–510
🔹 Next liquidity zone: 505–500
🔹 Key resistance: 526–530
🔹 Major upside liquidity: 539–550

Main scenario:
• Staying below 526–530 keeps downside pressure active
• Losing 510 could extend the decline toward 505–500
• Reclaiming 530 would weaken the bearish setup and bring 539–550 back into focus

Disclaimer: Trading always involves risk, do your own research (DYOR)

📊 $LAB Liquidation Heatmap — Short-Term Bias Leans Bearish

$LAB is trading near 0.1765 after being rejected from the 0.195–0.200 area. The nearest major long-liquidation clusters are positioned below the current price.

🔹 Immediate downside zone: 0.173–0.170
🔹 Next liquidity zone: 0.165–0.160
🔹 Key resistance: 0.183–0.188
🔹 Major upside liquidity: 0.195–0.205

Main scenario:
• Staying below 0.183–0.188 keeps downside pressure active
• Losing 0.170 could extend the decline toward 0.165–0.160
• Reclaiming 0.188 would weaken the bearish setup and bring 0.195–0.205 back into focus

Disclaimer: Trading always involves risk, do your own research (DYOR)

📊 $DEXE Liquidation Heatmap — Short-Term Rebound Bias Leans LONG

$DEXE is trading near 5.38 after a severe decline from above 40. The broader structure remains bearish, but the nearest liquidation clusters are concentrated above the current price.

🔹 Immediate upside zone: 5.60–6.20
🔹 Next liquidity zone: 7.00–8.50
🔹 Major upside liquidity: 9.50–12.00
🔹 Key support: 5.00–4.50

Main scenario:
• Holding above 5.00 keeps a short-term rebound toward 5.60–6.20 possible
• A clean break above 6.20 could extend the squeeze toward 7.00–8.50
• Losing 4.50 would weaken the rebound setup and expose 4.00–3.70

Disclaimer: Trading always involves risk, do your own research (DYOR)