Yuuki Trading

That night I stopped looking at 2.9 seconds, I watched the MacBook Pro fan roar as Browser Wallet generated a Private Transfer Proof for a Phoenix transaction...

first time 11s, second time 3.8s, third time 2.9s.

beautiful!

but going from 11 to 2.9 is a 73.6% reduction, meaning Warm Start is nearly 3.8 times faster than Cold Start.

I only paid attention to the gap between the two states.

real users aren’t going to keep Browser Client open all day just so Parameter Caching is always ready, are they?

close the tab, switch networks, battery drops, open it again... WASM Module loads, Initialization Parameters initialize, Local Proof Generation runs again.

Peak Memory Usage 1.2GB isn’t that alarming on Mac.

move to a Smartphone with 4GB RAM, and that alone already takes up 30% of total RAM.

honestly, this is the Client-side Performance I actually want to examine in Hedger.

I like Dusk pushing Privacy down to the client with Lightweight Circuit.

a Private Transaction where the Proof stays on the user’s device feels right to I.

but being right doesn’t mean it’s easy to live with.

30 Cold Starts at 11s is 330s.

30 times at 2.9s is only 87s.

a difference of 243s... more than 4 minutes.

I want Browser Benchmark to run under Poor Network, unstable 4G, CPU throttling and Older Android Device, not just powerful machines with Cached Parameters.

if Batch Aggregation or Multi-transfer Aggregation can bundle multiple transfers into a Single Proof, I prefer that over forcing Proof Generation down by another few tenths of a second.

reducing time sounds good.

reducing the number of times you have to wait is what actually matters.

Testnet gives I the right to be patient.

Mainnet lets technology in without making I notice it.

for I, the best Privacy is the kind that turns cryptography into background noise... it runs, but no one has to think about it.

if you had to choose, would you rather Dusk show off faster Proofs, or prove that even the worst Cold Start is still light enough for real-world use?

#dusk $DUSK @Dusk

Yesterday, I sat down and sketched the Range Order AMM of @TermMax on paper, pulled the Multi-Kink Curve around, and only then realized this is not a game of “choosing APR” just to make it look good...

I tried placing 820,000 U at 15%, pushing notional up to 4,600,000 U and then raising the quote to 23%: maker is putting cost of capital on the line against taker.

each segment runs on vXt × vFt = L², while Instantaneous APR = (vFt/vXt) × (365/remaining days).

remaining days = 90, Virtual Reserve Ratio = 0.05 gives APR ~20.28%; increase the ratio to 0.055 and APR becomes ~22.31%... Virtual Reserves move only slightly, yet the rate already reacts quite noticeably, pulling the risk profile of maker along with it.

honestly, this was the part that kept me sitting there the longest.

before, I used to look at TVL, but with the Maker-Taker Model I look closely at Quote Depth and Filled Volume.

no matter how beautifully Curator draws the Segmented Interest Rate Curve, if Slippage Bounds are too tight, Binary Execution keeps reverting, and Market Maker does not refresh the quote, then even a thick Order Book can still be hard to fill.

looking good is one thing.

usable liquidity is another!

Cross-Segment Continuity connects the curve smoothly, but code does not stand there watching the market.

Passive LP can deploy capital; active market making has to watch Interest Rate Slippage, Capital Efficiency and Continuous Quoting.

Atomic Orders move Idle Capital to Aave to Earn Yield, but that does not automatically create quoting discipline.

that is what I am cautious about with Cold Start.

TGE is 25.08.2026, so I will look at @TermMax through Market Depth before TVL: does Curator compete on rate, can taker fill large sizes without hitting the Slippage Bound?

if yes, Interest Rate Discovery starts to smell like money.

if not... Range Order AMM is still just a glowing price board with an empty trading counter.

will everyone be watching TVL, Quoted Liquidity, Filled Volume or the staying power of maker after TGE?

#TermMax @TermMax

Last night I opened @TermMax again close to midnight... planned to look for 5 minutes and then sleep, but ended up getting stuck on a division.

31.25M USD TVL, 27.22M USD Active Loans.

27.22 / 31.25 = nearly 87%.

that number woke me up more than coffee.

with a Fixed-rate Market, I don't like capital sitting pretty on a dashboard; when nearly 87% of TVL becomes Active Loans, Capital Efficiency gives us something to talk about.

but the more I looked, the more something kept bothering me...

98.3% of TVL is still on Ethereum, around 30.72M USD.

Morpho, Aave, Venus, Pendle already have Protocol Integration, Keyrock has Institutional Participation... so is the Multi-chain Ecosystem actually creating Capital Inflow, or has it only added more routes?

honestly, this is where I got stuck.

1.5M Registered Wallets and 90K DAU sound big, but Activity can swell and then shrink once Incentive gets thinner.

so I don't want to count wallets.

I want to see whether Borrowing Demand comes back, whether Lender continues Liquidity Provision, whether Market Depth gets deeper, whether Liquidity moves away from Ethereum.

30-day Protocol Revenue is around 19.9K USD.

19.9K / 27.22M Active Loans is only around 0.073% over 30 days... Real Usage is leaving traces, while the path from Usage to Revenue is still thin.

this is what makes @TermMax worth watching ahead of TGE 25.08.2026.

if after TGE, User Retention holds, Borrower comes back because of Fixed-rate Demand rather than Campaign Rewards, while Ecosystem Partnerships pull Assets across EVM Chains, the story will be different.

for me, the strongest protocol isn't the place that gets the most visitors.

it's the place people choose to return to for a second time, a third time... when the rewards get smaller.

that's when TVL starts to carry weight, Protocol Revenue becomes worth watching, and Multi-chain finally stops looking like a colorful map.

after 25.08.2026, will you look at Capital Efficiency, Market Depth or User Retention to know whether TermMax is actually growing?

#TermMax @TermMax

That night I was planning to bridge a little DUSK from Dusk Mainnet to BSC, just a light test first to be safe... but looking at the numbers made me realize that “sending as little as possible” can sometimes be a bad test.

I entered 10 DUSK into Dusk Official Bridge. the 1 DUSK Bridge Fee alone was already 10%, not even counting Dusk Network Transaction Fee.

25 DUSK means 4%; 50 DUSK is 2%; 100 DUSK is only 1%.

Net amount received = Amount sent - 1 DUSK - Network transaction fee.

sending 1 DUSK or less means BSC-side Payment = 0; minimum useful amount is 1.000000001 DUSK, Destination Address receives only 0.000000001 DUSK after bridge fee.

truthfully, by this point I changed my mind.

because I wasn’t only testing the money.

I was testing the Cross-chain Process: Mainnet Transaction goes into Official Bridge Account, Memo carries the 0x Address for Routing to the BSC Address, then BEP20 DUSK finally reaches the Final Destination.

sounds simple... only when I cross-checked everything myself did I realize how mentally taxing it was.

Official Web Wallet has Address Format Validation, but Final Address Verification is still my responsibility. Missing Memo, Incorrect Memo, Routing Error or using the wrong BEP20 Deposit Address can all block Automatic Processing; that’s when Asset Recovery becomes the real concern.

BTC Transfer got me used to a direct Receiving Address. but this flow separates Sending Responsibility and Routing Responsibility; being correct on Mainnet doesn’t necessarily mean I can feel at ease on the BSC side.

if the Exchange hasn’t confirmed Support for BEP20 Deposit Address, I won’t send.

Self-custody Wallet first... once I see BEP20 DUSK arrive in the right place, then I’ll move forward.

for me, 1 DUSK may not be the most expensive part; the most expensive moment is when the interface feels so familiar that I assume I already understand the entire flow.

when testing a bridge, would you choose the smallest amount, a reasonable fee ratio, or the ability to control every Routing point?

#dusk $DUSK @Dusk

One evening I opened Dusk Wallet and retraced Asset Migration like handling a sum of money where mistakes were not allowed...

what made I uncomfortable was not the Bridge Fee.

but the status.

ERC20/BEP20 to Dusk Mainnet requires Approve then Execute Migration; a successful Transaction Confirmation does not mean Mainnet Migration has already run.

two signatures, one wrong step and the Transaction Flow goes off track.

Processing Time can be close to 1 hour.

I do not need a better-looking Wallet Experience; I need Transaction Status to clearly show Pending, Processing, Completed or Failed, along with the Transaction Hash and an Asset Recovery path if there is an error.

Dusk Mainnet Bridge to BSC is even more stressful.

Memo must contain the Destination BSC Address, Bridge Fee is 1 DUSK; an incorrect Memo can cause Automated Processing to go off flow.

User Error Protection, Risk Control and Asset Security!

on 16/1, 8,068,000 DUSK left the Signing Wallet; a Bridge Attempt of 8,910,000 DUSK was stopped by Emergency Shutdown.

a difference of 842,000 DUSK, about 10.4%.

Bridge Security is not just the Consensus Layer.

it is also Signing Architecture, Bridge Isolation, Permission Management, Wallet Connection, Wallet Permissions, Transaction Signing and Access Control.

Financial-grade Infrastructure serving Regulated Onchain Finance cannot have “don’t click the wrong thing” as its primary protection mechanism.

Transaction Flow has to explain itself.

Automated Processing has to leave a trace.

Asset Recovery has to provide a way back.

DeFi can make users learn on their own; with Onchain Finance, the system has to clearly state which step is complete, which is not, and where the error is.

because Asset Security is not the feeling that “it’s probably fine”...

it has to be the ability to verify every status, every signing permission, every step of asset movement.

if I have to open the explorer three times to reassure I that the money is still in the flow... has Dusk truly reached the Financial-grade standard yet?

#dusk $DUSK @Dusk

There are days when I open the Dusk documentation just to see how Phoenix Shielded Transfers work… and end up sitting there for almost the entire session on Selective Disclosure.

the more I read about PLONK, zk-SNARK, KZG, Audit Hooks and KYC Assertions, the more I feel Dusk is solving a problem far more frustrating than Privacy: hiding data while still having to prove that you are clean enough to step into Institutional Settlement.

honestly, this is what stays with me the longest.

Privacy Chains are everywhere.

but a Native L1 Settlement that keeps transactions private, lets regulators reveal what they need, and still wants to tie RWA Issuance into MiCA and the DLT Pilot… its ambition is not small.

then I scroll down to the stack.

DuskDS.

Piecrust/DuskVM.

DuskEVM.

Hedger with Homomorphic Encryption.

SBA PoS underneath.

5 technical layers look beautiful… but they could keep the operations team awake at night!

especially when dusk-plonk once had a selector evaluation bug related to the KZG opening check, which makes it impossible for me to take Formal Verification and Audit Coverage lightly.

as for adoption, I still haven't taken my foot off the brake.

NPEX talks about more than 200M in issuance, 21X and Quantoz make the European Compliance story sound very compelling, but confirmed issuance is not On-Chain Locked Value, partnership is not Settlement Volume, Testnet is even less so recurring Fees.

from there, I started looking at Dusk differently.

I don't ask “how strong is Privacy?”.

I ask “who will pay for the right to stay private from the market while still being transparent to the right people?”

if it's banks, brokers, exchanges and issuers… Dusk may be building Compliance Infrastructure disguised as Privacy.

but if nobody pays for that right, no matter how beautiful the cryptography is, it will simply sit still inside the architecture.

in your view, is the hardest thing for Dusk the technology… or turning Selective Disclosure into a habit that TradFi is actually willing to use?

#dusk $DUSK @Dusk

Last night I opened the Dusk wallet, sipping coffee while drawing a DeFi Protocol flow, and when I got to the part where Liquidity went through Moonlight and Phoenix I had to redo the diagram twice...

Moonlight uses Account Model, Public Transaction is clear, easy to index, easy for Auditability, Liquidity Pool or Reserves placed here give auditor fewer headaches.

Phoenix, on the other hand, is UTXO Model + Zero-Knowledge Proof, Confidential Transaction, Amount Privacy, Counterparty Privacy, Selective Disclosure... Privacy Blockchain!

that part makes I hesitate.

protocol has 10 million USD, I keep 7 million on Moonlight for Institutional Adoption, NPEX, Tokenized Securities and Compliance, while 3 million goes to Phoenix for private flow... does capital efficiency remain intact?

honestly Privacy does not make I uneasy.

fragmented liquidity is what makes I uneasy!!!

Dusk has more than 200 million tokens Staking, 36% live supply at the time of measurement.

Node Participation is solid, security also has weight.

strong Staking does not mean strong composability.

MiCA, MiFID II, Regulatory Acceptance, Auditability pull Moonlight toward institutions; Phoenix, on the other hand, pulls ecosystem toward Privacy, ZKP and Selective Disclosure.

both directions make sense...

will developer maintain one smart contract logic, or two execution assumptions?

how will Liquidity Provider rebalance?

whale wants to hide Position but protocol still needs PoR, so who bears that complexity?

I used to think the greatest advantage of Dusk was Dual-Model Architecture.

now I think the real advantage only appears when Cross-Model Interaction, Compliance Whitepaper and developer tooling make protocol builders completely forget that two model exist underneath.

if developer still has to remember it every day... no matter how beautiful architecture is, it is still charging a fee through complexity.

do you think Dusk is building an abstraction strong enough, or will ecosystem naturally lean entirely toward Moonlight or Phoenix?

#dusk $DUSK @Dusk

Last night I reopened some old code, sat watching the terminal run proof after proof and forgot about my coffee... thought of @Dusk.

when I read SBA Consensus, I was more drawn to Blind Bid, Proof-of-Blind Bid and Private Leader Election than Privacy.

Block Generator participates in Non-interactive Sortition, Confidential bid sits behind Zero-Knowledge Proof.

No Signaling.

No Targeting.

No Stake-Based Surveillance.

but honestly, after debugging it myself a few times, I am no longer easily convinced by the word “private”...

I look at Prover, Verifier, Circuit Constraints, Polynomial Evaluation and dusk-plonk.

suppose 1,000 proofs go through, each proof has 4 Polynomial Evaluations that need to be checked, meaning 4,000 verification points.

what if a Verification Gap sits exactly where the most important Security Assumption is?

Malicious Prover does not need to break the entire system.

it only needs a gap small enough for a Forged Proof to slip through, then BlindBidProof, Sortition Correctness and Consensus Security start becoming a different story.

that is what I fear most about Cryptographic Implementation: Attack Surface is sometimes not broad...

MEV Resistance is genuinely strong.

Targeted-Attack Resistance is worth a lot too.

but the more a Privacy Layer hides from the user's eyes, the more I demand Battle Testing to be brutal, the tougher the Verifier has to be, Verification Correctness has to become almost obsessive.

OtterSec once hit exactly on unchecked Polynomial Evaluations, and that made me change the way I see it: a protocol is not trustworthy because it uses PLONK, but because the assumptions underneath PLONK have been hammered on for long enough and are still standing.

I still like the direction DUSK is taking... it is just that now I no longer ask “how much privacy do we get”.

I ask: how many punches has the part we cannot see already taken?

if you had to choose, would you trust a system because its design is the most beautiful, or because its Verifier has survived the worst tests?

#dusk $DUSK @Dusk

BR — Momentum is constructive on the 30m and order flow leans to buyers, while the broader structure is aligned and this remains a cleaner continuation setup.

$BR /USDT - LONG
- Entry: 0.221298 — 0.223522
- TP1: 0.23391
- TP2: 0.240658
- TP3: 0.251607

Stop Loss: 0.207812

Price is holding a 30m bullish structure with 15m bullish retest conditions, and the long side has support from +2.46% 30m momentum, 1.22x relative volume, and a 30m taker buy/sell ratio of 1.1254, showing more aggressive buy flow.

BEAT — Momentum is weak on the 30m and order flow still leans to sellers, while the broader structure is aligned bearish and this setup favors waiting for the retrace into entry.

$BEAT /USDT - SHORT
- Entry: 0.974896 — 0.984496
- TP1: 0.935
- TP2: 0.913127
- TP3: 0.856

Stop Loss: 1.033

Price is below the entry zone for now, with 30m BEARISH; 15m BEARISH structure, while the short side is backed by -2.24% 30m momentum, 1.76x relative volume, and a 30m taker buy/sell ratio of 0.6230, showing more aggressive sell flow.

APR — Momentum is modest on the 30m and order flow is still balanced to slightly soft, while the broader structure is not fully aligned and this remains a lower-confidence setup.

$APR /USDT - LONG
- Entry: 0.462277 — 0.466923
- TP1: 0.5574
- TP2: 0.6325
- TP3: 0.719754

Stop Loss: 0.337023

Price is still working inside a 30m RANGE with 15m BULLISH_RETEST structure, but the long side has support from +3.47% 30m momentum and a top-20 order-book depth imbalance of 21.35%. At the same time, the 30m taker buy/sell ratio is 0.9976, which keeps order flow close to balanced rather than strongly confirming immediate expansion.

INX — Momentum is weak on the 30m and order flow still leans to sellers, while the broader structure is aligned bearish and this setup follows that pressure.

$INX /USDT - SHORT
- Entry: 0.00799431 — 0.00806169
- TP1: 0.007751
- TP2: 0.007607
- TP3: 0.0072316571

Stop Loss: 0.0084261714

Price is trading with bearish structure on both the 30m and 15m, and the short side has support from -4.10% 30m momentum, 1.82x relative volume, and a 30m taker buy/sell ratio of 0.5866, showing more aggressive sell flow.

SKYAI — Momentum is firm on the 30m and order flow leans to buyers, while the broader structure is only partly aligned and this remains a lower-confidence setup.

$SKYAI /USDT - LONG
- Entry: 0.077794 — 0.078657
- TP1: 0.08111
- TP2: 0.08366
- TP3: 0.088415

Stop Loss: 0.073131

Price is still working inside a 30m range with 15m bullish structure, but the long side has support from +6.37% 30m momentum, 2.26x relative volume, and a 30m taker buy/sell ratio of 1.1706, showing more aggressive buy flow.

APR — Broader structure is aligned bullish, but near-term momentum has cooled and order flow still does not fully confirm, so this remains a lower-confidence setup.

$APR /USDT - LONG
- Entry: 0.380637 — 0.384583
- TP1: 0.424113
- TP2: 0.451782
- TP3: 0.493284

Stop Loss: 0.327273

Price is still holding within a bullish intraday structure with 30m BULLISH; 15m BULLISH, but the long side is tempered by -5.26% 30m momentum and a 30m taker buy/sell ratio of 0.9623, showing aggressive flow is not fully tilted to buyers.

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

$ZEC is trading near 488 after being rejected from the 493–495 area. The heatmap shows substantial long-liquidation liquidity below the current price, with several strong clusters that could attract price if selling pressure continues.

🔹 Immediate downside zone: 483–480
🔹 Next liquidity zone: 473–470
🔹 Major downside liquidity: 462–460
🔹 Key resistance: 492–495

Main scenario:
• Staying below 492–495 keeps short-term downside pressure active
• Losing 480 could accelerate the move toward 473–470
• A deeper liquidation sweep could bring the major 462–460 cluster into focus
• Reclaiming 495 would weaken the bearish setup and reopen the path toward 499–502

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

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

$PROM is trading near 3.27 after a strong rally from the 1.80 area. Price remains elevated, while the nearest significant short-liquidation clusters are concentrated just above the current level.

🔹 Immediate upside zone: 3.32–3.36
🔹 Next liquidity zone: 3.40–3.46
🔹 Key support: 3.10–3.05
🔹 Major downside liquidity: 2.95–2.88

Main scenario:
• Holding above 3.10 keeps the bullish structure intact
• A clean break above 3.36 could trigger a squeeze toward 3.40–3.46
• Losing 3.05 would weaken the bullish setup and increase the risk of a move toward 2.95–2.88
• A deeper breakdown below 2.88 could shift momentum decisively back to the bears

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

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

$APR is trading near 0.388 after an explosive rally from the 0.20 area. Price is now close to the upper liquidation zone, while substantially larger long-liquidation liquidity remains below the current price.

🔹 Immediate resistance: 0.395–0.400
🔹 Immediate downside zone: 0.350–0.340
🔹 Next liquidity zone: 0.320–0.305
🔹 Major downside liquidity: 0.270–0.245

Main scenario:
• Staying below 0.395–0.400 keeps the risk of a short-term pullback elevated
• Losing 0.350 could accelerate the move toward 0.320–0.305
• A deeper liquidation sweep could bring 0.270–0.245 into focus
• A sustained break above 0.400 would weaken the bearish setup and signal continued price discovery

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

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

$VELVET is trading near 0.531 after a sustained decline from the 0.90 area. Although the broader price structure remains bearish, the heatmap shows significantly larger short-liquidation liquidity above the current price.

🔹 Immediate upside zone: 0.56–0.60
🔹 Next liquidity zone: 0.64–0.69
🔹 Major upside liquidity: 0.74–0.76
🔹 Key support: 0.52–0.50

Main scenario:
• Holding above 0.52 keeps a short-term rebound setup alive
• Reclaiming 0.60 could open the path toward 0.64–0.69
• A clean break above 0.69 could trigger a stronger squeeze toward 0.74–0.76
• Losing 0.50 would weaken the rebound setup and increase downside risk toward 0.47–0.44

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

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

$CYS is trading near 1.11 after a sharp decline from the 1.70+ area. While the broader price structure remains bearish, the heatmap shows substantially larger short-liquidation liquidity above the current price.

🔹 Immediate upside zone: 1.16–1.20
🔹 Next liquidity zone: 1.25–1.30
🔹 Major upside liquidity: 1.34–1.36
🔹 Key support: 1.05–1.00

Main scenario:
• Holding above 1.05 keeps a short-term rebound setup alive
• Reclaiming 1.20 could open the path toward 1.25–1.30
• A clean break above 1.30 could trigger a stronger squeeze toward 1.34–1.36
• Losing 1.00 would weaken the rebound setup and increase downside risk toward 0.95–0.90

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

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

$TUT is trading near 0.1026 after a sustained pullback from the 0.13–0.14 area. Despite the bearish price structure, the heatmap shows significantly larger short-liquidation clusters above the current price.

🔹 Immediate upside zone: 0.109–0.112
🔹 Main liquidity zone: 0.119–0.124
🔹 Major upside liquidity: 0.143–0.146
🔹 Key support: 0.095–0.091

Main scenario:
• Holding above 0.100 keeps a short-term rebound setup alive
• Reclaiming 0.110 could open the path toward 0.119–0.124
• A strong squeeze above 0.124 could bring the 0.143–0.146 liquidity cluster into focus
• Losing 0.095 would weaken the rebound setup and increase the risk of a move toward 0.091–0.088

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