Warren Buffett is sitting on nearly $400B in cash, and that’s hard to ignore.
The last time Berkshire built a cash pile this large was around the 2007–2008 period. It doesn’t guarantee a crash, but it does suggest Buffett sees more value in waiting than chasing current prices.
I went into the DuskEVM bridge guide looking for withdrawal timing.
The fee line was what made me stop.
Moving DUSK into the current DuskEVM testnet flow is fairly simple: submit the deposit on Dusk L1, then wait for the balance to appear on DuskEVM.
Coming back is different.
A withdrawal requires three separate actions:
Initiate it on DuskEVM. Prove it on Dusk L1. Finalize it on Dusk L1.
The wallet can move through “Waiting for output proposal,” “Ready to prove,” “Proof submitted” and “Waiting to finalize” before the DUSK is released.
That part makes sense. The return journey is where DuskDS verifies the state coming from the EVM layer.
But then I noticed the user also needs enough unshielded DUSK on the L1 to pay for both the proof and finalization transactions.
So someone can hold DUSK inside DuskEVM, start moving it back, and still need a separate usable L1 balance to complete the exit.
The funds are not necessarily stuck. The user may simply be missing the asset required to finish proving that they are allowed to retrieve them.
That feels like a small technical requirement until DuskEVM is used by someone who has never touched Dusk L1 directly.
A Solidity developer may understand contracts and MetaMask perfectly, while the end user only sees a withdrawal sitting at “Waiting to finalize.”
Dusk’s docs are careful here. They tell users to follow the wallet status rather than estimate readiness from elapsed time alone.
Now I am watching how much of this survives into the final production experience.
Will users still manually manage three transactions and two L1 fees, or will the wallet abstract the process without hiding which settlement stage their money has actually reached?
The bridge is not only moving DUSK between layers. It is where DuskEVM’s familiar front end meets Dusk-native settlement and where that difference becomes impossible to ignore.
I had been looking at DuskEVM and Dusk Trade as two separate parts of the roadmap.
One brings Ethereum developers. The other brings tokenized financial products to investors.
Then I realized they may be trying to solve opposite sides of the same problem.
Developers rarely stay on a new network just because deployment is easy. They need users, liquidity and assets worth building around.
Investors have the reverse problem. A platform can offer tokenized assets, but those assets become far more useful when there are wallets, exchanges, lending markets and other applications ready to support them.
DuskEVM could supply the applications.
Dusk Trade could supply the assets and users.
$DUSK sits between them as the gas token for activity on DuskEVM, while staking helps secure the wider network.
On paper, the loop makes sense. A tokenized asset reaches Dusk Trade, investors gain access to it, and developers build services around its trading, borrowing or settlement. More use then creates more transactions paid in @Dusk .
But the timing is where I paused.
If applications arrive before real assets and users, developers may find an empty market. If financial products arrive before useful applications and liquidity, investors may have little reason to do anything beyond the original purchase.
Neither side can wait forever for the other one to appear.
So I would not judge this strategy only by the number of DuskEVM deployments or the amount listed on Dusk Trade.
I would look for overlap: assets that are actually being used inside applications, investors returning for more than one transaction, and liquidity moving between the product and developer sides of the ecosystem.
#dusk is not only trying to attract builders or investors.
It needs both groups to arrive close enough together for the $DUSK utility loop to start moving.
An ECSP can help fund the original offering. That does not mean investors will have somewhere liquid to sell the asset afterward.
Dusk’s NPEX relationship matters here because NPEX also brings regulated secondary-market infrastructure through its MTF licence.
So there is a possible route:
ECSP for raising the capital.
Dusk infrastructure for issuing and settling the asset.
NPEX or Dusk Trade for later market access.
Looks complete on paper.
But tokenizing an SME security does not suddenly create buyers on both sides. A small company’s bond can settle perfectly onchain and still trade once every few weeks with a wide spread.
That is the part the “more assets and TVL” language skips over.
Bringing an asset onto Dusk creates supply.
Keeping it useful requires pricing, buyers, market makers, corporate actions and an exit route.
I would not measure this strategy only through the value of assets issued.
I would watch what happens after issuance.
Do investors hold everything until maturity?
Can they exit without taking a large discount?
Does the same asset generate real secondary turnover?
The first offering proves Dusk can originate an asset.
The first functioning secondary market proves it can support one.
TermMax calls the vault participant a Depositor, which initially made the role sound almost passive.
The V2 curator controls made me read that description differently.
A Curator can choose markets, allocate capital, create orders, configure borrowing and lending curves, manage queues and charge a performance fee. The vault contract also exposes controls around minimum APY, market whitelisting, timelocks, guardians and bad-debt handling.
That is not simple yield routing.
It is delegated fixed-income portfolio management performed through smart contracts.
The depositor avoids placing every order personally, but the underlying decisions do not disappear. Someone still decides which maturity deserves capital, which collateral is acceptable, where a curve should begin and how much liquidity should be committed.
TermMax constrains that authority in useful ways. Whitelists limit available markets, timelocks delay sensitive changes and a guardian can cancel pending actions.
But those protections govern what a Curator is allowed to change. They cannot guarantee that the chosen markets, curves or allocations will perform well.
That makes headline vault APY a weak starting point for judging a @TermMax vault.
I would rather inspect the Curator’s market selection, curve history, performance fee, timelock and response to bad debt.
The depositor is not removing strategy risk. They are choosing who is allowed to manage it.
I assumed the new Dusk Wallet was mainly a redesign of the existing web wallet.
Then I read the April developer-preview announcement and checked the repositories.
The old web wallet could interact with Dusk directly, but it was a standalone application. A dApp could not discover it, request a profile or ask it to sign a transaction through a standard connection flow.
That left a gap between Dusk contracts and actual users.
Dusk Connect fills the application side of that gap. It lets a dApp discover compatible wallets, request profile access and send user-approved actions through a shared provider interface.
The new Dusk Wallet sits on the other side.
It keeps the keys locally, shows the request and lets the user approve or reject it. Its first release includes public and Phoenix balances, shielding, private transfers, staking and DRC-20/DRC-721 asset flows.
One implementation detail stood out to me.
A dApp does not automatically receive everything after “Connect Wallet.” Public profile access, shielded receive addresses, message signing and transactions have separate request and approval flows. Permissions are also stored per origin.
That matters on Dusk because connecting to a financial application may involve more than exposing one public address.
But this is still a developer-preview story.
A connection standard becomes valuable only when real dApps adopt it and compatible wallets implement it correctly. One first-party wallet proves the interface can work; it does not yet prove a broad application ecosystem.
Dusk already had contracts, privacy and settlement.
Dusk Connect and the new wallet provide the missing interaction layer between them and the person clicking the button.
The milestone I would watch next is simple: a production DuskDS dApp where a user can connect, approve and complete a shielded or tokenized-asset action without leaving the application.
Confidentiality alone does not make a blockchain suitable for financial markets.
A private ownership transfer is still unreliable if participants cannot determine exactly when it becomes final.
This is why Dusk’s architecture matters beyond zero-knowledge proofs.
Applications can run through DuskEVM or DuskVM, while DuskDS handles consensus, data availability and settlement. Once a block is ratified through Succinct Attestation, the network reaches deterministic finality rather than leaving institutions exposed to normal user-facing reorg uncertainty.
I see the design as two connected requirements:
Protect the transaction while it is processed. Make its final state unambiguous once settled.
For regulated assets, privacy protects the parties. Finality protects the market.
One sentence in TermMax’s documentation needs careful reading.
A borrower can purchase FTs from the market and use them to repay the debt. If those FTs trade below face value, this can cost less than repaying directly with debt tokens.
Mechanically, that is correct.
But the discount is not guaranteed to remain available.
An FT can be redeemed for one debt token at maturity. My expectation is that its price should move closer to that face value as maturity approaches, unless liquidity or collateral risk changes the market.
A borrower who sold FTs at $0.80 may therefore not be able to buy them back later at the same price.
If the FT trades at $0.98 and the swap includes fees and slippage, most of the apparent repayment saving has already disappeared. Thin liquidity could make the buyback even less attractive.
TermMax’s V2 contracts confirm that the repayment flexibility is real: the GT contract includes `repay`, while the router includes `swapAndRepay`.
The overlooked variable is timing.
Buying back FT may work well while a meaningful discount and sufficient liquidity remain. Closer to maturity, direct repayment could be simpler.
TermMax gives borrowers another repayment route.
The market decides whether that route is actually cheaper.
When I look at how Gen Z approaches money, I notice one major difference: they do not want to wait until their 30s or 40s to understand investing. Many young people are entering financial markets earlier because information and financial tools are now available through their phones. Previous generations often depended on banks, brokers or financial advisers to access markets. Gen Z can learn a concept, compare assets and explore global markets from the same device. Platforms like binance have made digital assets more accessible, while Binance Academy gives beginners a place to understand the basics before participating. But easier access does not automatically lead to better decisions. Starting early can be valuable because it gives someone more time to learn, begin with smaller amounts and understand how markets behave. The problem is that social media often makes investing look easier than it is. Young people see profit screenshots, viral tokens and stories of quick wealth. They rarely see the failed trades, liquidations and emotional decisions behind them. This creates pressure to act before learning. For me, the better approach is not to ask, “Which asset can make me rich quickly?” The better questions are: What am I buying? Why does it have value? What risks am I accepting? How long can I hold it? What would make me change my decision? Gen Z is also more willing to explore different assets, including stocks, Bitcoin, stablecoins and tokenized products. This does not mean every new opportunity is safe. It means the way younger people think about investing is changing. Crypto adds another challenge because markets operate globally and around the clock. Constant access can easily become constant monitoring. Checking prices every few minutes can push someone into emotional decisions. A normal decline begins to feel like an emergency, while a sudden rally creates fear of missing out. Learning when not to act is just as important as learning how to buy. Many young people are also thinking more seriously about their financial future because they have experienced rising living costs, inflation and uncertain career paths. They do not want to depend only on a salary or savings account. But investing should not replace basic financial planning. Understanding expenses, managing debt and keeping emergency savings still come first. Money needed for education, rent or daily life should not be exposed to an asset that can lose value quickly. I believe the strongest Gen Z investors will combine modern technology with traditional financial discipline. They will use digital platforms for access without confusing access with expertise. They will learn from online content but verify information independently. They will explore new markets without putting everything in one place. Nobody can control what the market does next, but every investor can control how much they risk, whether they understand the product and how they react when prices move against them. Gen Z is not changing investing only by starting younger. This generation expects education, market access and global opportunities to be available immediately. That creates more independence, but also greater personal responsibility. Having the market in your pocket is powerful. Knowing when to participate, when to wait and when to walk away is what makes the difference. Starting early can help, but starting with knowledge matters more. How do you think Gen Z is changing investing? Educational content only. Always do your own research, understand the risks and check availability in your region. #Binance #BinanceAcademy #LearnWithBinance
One detail in TermMax’s liquidation design deserves more attention than the phrase “RWA support.”
The Gearing Token contract includes `previewDelivery`, `delivery` and `liquidate`. TermMax’s documentation explains why: if normal repayment or liquidation liquidity is insufficient, FT holders can receive a proportional share of the available underlying assets and collateral.
That is not the protocol promising every lender an effortless cash exit.
It is the protocol defining what the lender can claim when selling the collateral immediately would be difficult or destructive.
For liquid crypto collateral, an AMM can often sell assets and repay lenders. That assumption becomes weaker with private credit, tokenized property or other assets that do not trade continuously.
Physical delivery avoids pretending those markets have instant liquidity.
But it also transfers a real decision to the lender.
Receiving collateral may protect the legal or economic claim, yet the lender could still inherit valuation uncertainty, custody requirements and an asset that takes time to sell.
TermMax itself describes physical delivery as a risk mitigant, not a way to eliminate risk. That distinction matters.
This mechanism could widen the collateral that fixed-rate lending can support, particularly beyond highly liquid tokens.
Whether it works well will depend on what is delivered, how it is valued and whether lenders have a practical route to hold or exit it.
Before choosing the rate, I would ask a simpler question:
What matters most if repayment comes through physical delivery?
My first instinct was to treat all of that like one big adoption number.
But it isn’t.
The €300M+ figure is about assets institutions are bringing into the Dusk market infrastructure. The 50K+ number is reach across crypto and partners. And the 210M+ DUSK staked is doing a completely different job, it is securing the network.
None of those numbers is TVL.
That sounds obvious once you say it, but I think it matters because @Dusk is not really building around the usual DeFi dashboard logic.
If I only looked for deposits sitting inside protocols, I would miss what the project is actually trying to grow.
One signal is asset supply.
One is distribution and investor access.
One is **network security**.
And they can move independently.
That actually made the Dusk adoption story feel more useful to me because now I know what I’m looking at.
€300M of confirmed issuance does not mean €300M is already locked onchain today, and 210M DUSK staked does not mean users deposited that amount into some RWA product.
Different numbers, different parts of the machine.
I’d rather read them separately than combine everything into one impressive-looking TVL story.
TermMax says a project can put treasury tokens into a Dual Investment Vault, choose a higher strike, and collect premiums while traders take the other side. Its live Alpha interface currently describes those yields as being funded by long/short buyers.
But there is a detail worth looking at more carefully.
On actual TermMax Alpha vault pages, the risk notice explicitly says deposited tokens may be converted into USDT if the strike price is reached. That warning is visible today on multiple vaults, including the IR and NVDAon vaults.
So I don’t think the interesting question is simply:
“Can a project earn yield on idle treasury tokens?”
My interpretation is that the vault can also encode a conditional treasury sale.
Below the strike → treasury keeps collecting premium.
Strike reached → some tokens can be converted at a price selected in advance.
That is materially different from a team suddenly deciding to market-sell treasury inventory.
What I cannot verify from the public material is whether this actually reduces market impact at meaningful treasury size. That would depend on vault liquidity, demand from traders and how aggressively the project sets its strike.
Still, this changes how I look at TermMax Alpha.
For projects, the vault may be less about finding another source of APY and more about deciding in advance what price makes treasury distribution acceptable.
That is a much more interesting form of token utility.
$DUSK I was comparing the transaction models in Dusk’s Core Components documentation when one detail corrected my earlier assumption.
Phoenix is not described as a privacy application sitting above Dusk.
It sits inside DuskDS.
The documentation confirms that DuskDS supports two models: Moonlight for transparent public accounts and Phoenix for shielded transfers.
Phoenix is UTXO-based, while both models can transfer DUSK, pay gas and enter contract execution.
That placement matters more than the usual “private transactions” description.
On a standard public account model, someone does not always need your name to learn something useful. Repeated transfers, changing balances and interactions with the same contracts can build a recognizable settlement pattern.
Phoenix changes the information available underneath that activity. A zero-knowledge proof can demonstrate that a valid output is being spent, while a nullifier prevents it from being spent again.
The network can verify the transaction without reproducing the same public account trail.
I initially wanted to describe that as private settlement for every asset on Dusk. The documents do not support that broad claim.
Phoenix specifically handles shielded DUSK flows. Privacy for regulated securities still depends on the application design, DuskVM contracts, identity rules and selective disclosure.
So the narrower conclusion is probably the stronger one: Phoenix protects the base movement entering settlement and execution. It does not make the whole financial workflow disappear.