Mr Crypto_ 加密先生

#dusk $DUSK @Dusk I thought Dusk’s token burn was mainly a supply story until I looked at where the missing rewards actually come from.

The interesting part is that Dusk does not simply hand the full block reward to the block generator.

Its current reward design gives the generator 70%, with up to another 10% available depending on the committee credits included in the certificate. The development fund gets 10%, while the validation and ratification committees receive 5% each. Any part of that extra 10% that is not distributed is burned.

That changes how I read the burn.

It isn't a separate buyback mechanism running in the background. It is tied directly to how much eligible consensus participation gets reflected in the block certificate.

And that makes the mechanism more interesting to me than a headline like “DUSK is deflationary.”

Dusk’s Succinct Attestation system uses randomly selected provisioners across proposal, validation and ratification stages, so the reward structure is connected to actual consensus participation rather than simply paying everyone a flat amount.

But there is a limit to the story.

A higher burn does not automatically mean the network is unhealthy, just as a lower burn does not prove perfect participation. It tells us that part of the available reward was not distributed under the protocol rules.

That makes me wonder:

Should protocol-level burns be viewed mainly as tokenomics, or can they also become useful signals for understanding how efficiently a consensus system is operating?

What do you think DUSK’s burn mechanism tells us most?👀

#termmax @TermMax I went into TermMax expecting the interesting part to be the fixed maturity. I ended up paying more attention to what happens to liquidity before a deal is actually taken.

TermMax V2 changes something that sounds small but has bigger consequences: the same pool can support positions across multiple markets through Atomic Orders.

That means a curator doesn't have to permanently split $1.1M across three markets just because all three are open. The protocol can show that liquidity across them, while the same capital can only be consumed once. If one market takes $500K, the available amount is reduced across the others at the same time.

That changed how I think about the design.

The problem isn't simply finding a good lending rate. It's making larger amounts of capital usable without leaving part of it stranded in the wrong market.

TermMax is also moving toward an aggregator that can combine different liquidity sources into one execution, instead of making users piece together orders themselves.

But there is a boundary.

Showing the same liquidity in several places doesn't create more money. It only makes existing capital more flexible, with the atomic rule keeping it from being spent twice.

Even with $牛来 and $BIO getting market attention, this infrastructure detail is what I find more interesting.

Does this kind of shared liquidity become more important than the rate itself when DeFi starts handling much larger credit positions?

As DeFi scales, what matters more for large credit markets?

#termmax @TermMax Spent the afternoon digging through a few open positions on TermMax and the locked numbers are what actually made me stop.

Once you open a trade the rate and the end date just sit there. You see the full amount you’ll have to pay back right from the start. The cost side stays still while the market keeps moving.

Alpha takes it a step further. You pay one clear chunk up front to go long or short. That chunk is the most you can lose. No margin calls, no forced sales if the price swings against you. Each position lives inside its own Gearing Token NFT so nothing from one trade can spill into another.

On the other side people lock in their return by buying Fixed-Rate Tokens at a discount and cashing them for full value at maturity. The yield is set the moment they enter.

Because both sides of the deal are written down before anything starts, you can size against a fixed number instead of watching a rate that keeps shifting every few blocks.

The protocol is already live across ten chains with over ninety million locked and more than a million and a half wallets. TMX lands on August 25.

Grabbed my water and sat with it a bit longer. The clarity is real. What still feels like friction is whether people actually size more carefully when the exact cost and the max loss are sitting right in front of them, or if most still open the same kind of trades they always did, just with cleaner numbers.

Still turning that over.

#dusk $DUSK @Dusk Spent the afternoon sitting with the Zedger and Hedger docs and the split between them is what actually stuck.

Dusk is built for regulated assets that need privacy and rules at the same time. It doesn’t try to hide everything from everyone. It just keeps things private where it matters and still lets the right people check when they have to.

Zedger lives on the native side. It uses a hybrid UTXO and account setup. That mix gives stronger anonymity because each piece of value doesn’t carry the same permanent identity a normal wallet address does. It’s the one built for the full life of a regulated asset — issuing it, limiting who can hold it, paying dividends, voting, recovering lost tokens — while keeping the people’s data private.

Hedger sits inside the EVM part. Account-based systems make full anonymity much harder, so it focuses on hiding the balances and the amounts instead. It uses homomorphic encryption and zero-knowledge proofs so everything stays encrypted end-to-end but can still be verified. The upside is obvious: normal tools like Foundry, Hardhat and regular wallets just work. The downside is you lose some of the deeper anonymity Zedger can still reach.

The docs are pretty honest about it. Two different ceilings, each matched to the environment it has to live in. One doesn’t replace the other.

What kept nagging after I closed the tabs is how often both get flattened into one vague “privacy on Dusk” line. The difference is real. Still wondering how many people actually choose the lane that fits what they’re building, instead of treating privacy like it’s the same feature everywhere.

Spent the afternoon looking at how Dusk distributes its block rewards and one small detail kept bothering me: part of the generator reward can simply disappear.

The plan is still the same. 500 million DUSK will be emitted over 36 years. It starts around 19.86 DUSK per block and halves every four years.

Each block reward splits clearly. Seventy percent plus up to an extra ten percent goes to the block generator. Ten percent goes to the development fund. Five percent each goes to the validation and ratification committees. The variable ten percent for the generator depends on how many votes are included. Whatever part of that slice is not earned gets burned on the spot.

The live market numbers sit right beside that design. Price is around 0.0655. Market cap is roughly 32.5 million dollars. Fully diluted value sits near 65 million. Circulating supply is about 499 million out of the 1 billion maximum. Daily volume is around 4.1 million.

The emission curve tells you how much new DUSK is still planned. The burn line removes a slice before it reaches circulating supply. The market is currently valuing the circulating supply at roughly half of the fully diluted value.

Still chewing on whether the daily burn and the long halving schedule are enough to keep the supply story tight, or whether the gap between circulating value and fully diluted value stays the louder signal for now.

@Dusk #dusk $DUSK

#termmax @TermMax Spent late at night digging into how liquidations actually work on TermMax and noticing the rules are tighter than a typical open-ended pool.

A position becomes liquidatable when its loan-to-value hits or crosses the LLTV line. That can happen if the collateral price drops or the debt token rises. There is also a second trigger: if the borrower does not repay by the fixed maturity date, the loan opens for liquidation during a two-hour window.

When liquidation starts, the system does not always take everything at once. If the outstanding debt is above 10,000 dollars, a liquidator can only clear up to 50 percent of it in one go. That partial step is meant to reduce the hit on the borrower while still bringing the position back toward safer levels.

A 10 percent penalty is applied to the liquidated debt amount. Half of that goes to the liquidator as a reward, and the other half goes to the protocol reserve. If a position is fully cleared, any leftover collateral is returned to the borrower.

In some markets there is also a physical delivery path if the normal liquidation process does not fully resolve the debt.

Still chewing on whether the dual LTV buffer plus the partial-liquidation rule actually keeps most positions from reaching the edge, or whether the two-hour maturity window ends up doing more of the quiet work once real price swings arrive.

What matters most in liquidation design?

#termmax @TermMax
Everyone talks about DeFi lending like the main challenge is finding liquidity. Looking at TermMax, I started wondering whether the harder problem is knowing what that liquidity will actually cost.

I spent some time going through TermMax’s fixed-rate design, and the structure is surprisingly straightforward.

Most DeFi money markets use floating rates, so borrowing costs can change while a position is open. TermMax takes a different approach. Borrowers lock in the cost for a defined maturity, while lenders can buy a Fixed-rate Token, or FT, below its face value.

At maturity, that FT can be redeemed for the debt token’s full face value. The difference between the purchase price and the final value becomes the lender’s fixed return.

Every market is built around a debt token, collateral token, and maturity date. Underneath that are XT, market-specific collateral, LLTV limits, and order curves that adjust pricing as liquidity changes.

The interesting part is what this structure does to DeFi lending. Instead of leaving the future value of a debt position uncertain, TermMax turns it into something participants can price today.

The mechanism makes sense.

The bigger question is adoption. Floating-rate markets already have the liquidity and user habits. Will knowing the borrowing cost upfront be valuable enough to move liquidity into fixed-term markets?

That may be TermMax’s real test.

Everyone talks about Dusk’s fast finality. I found the interesting part in what happens when the first block fails.@Dusk

Spent the afternoon digging through Dusk’s finality rules in the whitepaper and current docs, and the n=0 path is what actually stopped me.

Blocks move through four states: Accepted, Attested, Confirmed, then Final. The key number is n, how many earlier iterations in the same round already failed.

When n equals zero, the block is marked Attested right away. Once it has a single successor that is itself Attested or Confirmed, it becomes Confirmed. That is the fast path the docs describe.

When n is greater than zero, the rules change. The block only starts as Accepted. It then needs 2n consecutive Attested or Confirmed blocks after it before it can reach Confirmed. An iteration-5 block with two earlier failures, for example, needs four more good blocks. Only after it is Confirmed and its parent is already Final does it become irreversible.

The design deliberately gives the first successful generator stronger finality. Later ones earn the same strength only after the network has seen more evidence that earlier attempts really failed.

That part checks out.

What kept nagging is how rarely the slower path shows up in everyday conversation. Under normal conditions most blocks take the n=0 route and reach strong finality quickly. The extra requirements only appear when the network is already under stress.

Still wondering how many people quoting “instant finality” have actually sat with the difference between the two paths.
#dusk $DUSK

Spent the afternoon looking at how settlement actually works on Dusk Trade and ended up in a different place than I planned..... @Dusk
Most chains treat ownership as a wallet balance that can move freely. Here the ownership has to stay legally clear. Money market funds, government bond ETFs, equity trackers and bonds come on-chain with the same title requirements they already carry in traditional markets. Instant settlement still happens, but only inside that legal frame.
The platform runs as a regulated Multilateral Trading Facility under EU rules. It is closer to a neobroker than to an open liquidity pool. No one spins up a random trading pair. Authorized participants and KYC sit at the front door because the assets themselves demand it.
That creates a quiet trade-off. The useful DeFi pieces — same-block settlement and the ability to use the assets in other contracts — stay available. The permissionless listing culture does not. The open part is verification and settlement speed, not free entry for every token.
Grabbed my chai and sat with the difference. One side sees the guardrails as necessary for real assets. The other side still reads them as friction. Both can be true at the same time.
Still chewing on whether the institutions who already hold these instruments will treat the faster rails as an upgrade, or whether the compliance layer will keep the two worlds further apart than the technology alone suggests.
#dusk $DUSK

Spent the afternoon digging around Dusk’s live numbers and kept landing on the same quiet stretch.@Dusk
Price sitting at 0.0649. Market cap around 32.68 million. Circulating supply just under 500 million against a 1 billion max. Volume at 3.52 million on the day. Still roughly 94 percent below the 2021 high of 1.1657.
The story has stayed consistent for years: a privacy-focused chain built for regulated finance, zero-knowledge tools, and the XSC standard so institutions can move tokenized assets under European rules without everything sitting in the open. Modular design, plus the newer DuskEVM testnet so Solidity developers can actually deploy.
That part is clear on paper.
What kept circling is the distance between the pitch and the chain itself. Most activity still looks like staking. A few hundred transactions on a typical day. Real confidential contracts or live securities remain scarce. Early vesting finished years ago, so no big unlock cliffs are coming. Staking emissions just keep releasing steadily.
The token mainly covers gas and staking. Nothing more layered than that. Holders absorb the ongoing inflation while waiting. The teams that might actually need the privacy features may not need to hold much of the token at all.
Still chewing on whether the tech is simply ahead of its users, or if the timeline for real institutional volume is longer than most people watching the chart are prepared to sit through.
#dusk $DUSK

Kept coming back to the Rusk repo this evening, and the quiet consistency of the v1.7 work is what actually landed.@Dusk

Rusk is the main reference client for Dusk, written in Rust. It sits at around 204 stars right now. The public 1.7.0 and 1.7.1 releases from June tightened archive storage, improved consensus handling, and strengthened Phoenix support.

The codebase includes the core modules: consensus, DuskVM, the prover service, recovery tools, and wallet-core. Regular commits are still landing, and multi-node testing infrastructure continues to expand.

That part is real and practical. The node work is moving forward without much noise.

What kept nagging after I closed the tab is the gap between the steady engineering and the wider conversation. The reference client keeps receiving focused updates. Yet most of the attention still sits on the higher-level products and announcements built on top of it.

The people actually running nodes, checking the archive improvements, or testing the multi-node setups remain a smaller group than the overall narrative suggests.

Still wondering how long that split stays in place — solid client work continuing quietly while the louder discussion stays fixed on the layers above it.
#dusk $DUSK

Spent the afternoon poking around the current DuskEVM testnet, and the tooling familiarity is what actually stopped me.

Solidity developers can now deploy with the same Hardhat or Foundry setup they already know. Contracts settle back to Dusk’s native layer instead of sitting on a generic rollup. Hedger, the privacy add-on for confidential EVM flows, is also available for testing. Balances and transfer amounts can stay hidden when the application needs it. That combination is real on the testnet right now.

The path looks straightforward on paper. Use everyday Ethereum tools, get settlement on Dusk, and turn on privacy where it matters.

What kept circling after I closed the tabs is the gap between the open door and who is walking through it. The testnet is live. The docs and RPCs are public. Yet most of the early activity still looks like explorers checking that deployments work. The teams that actually need confidential regulated flows — the ones this stack is aimed at — have not shown up in volume yet.

Still wondering whether familiar tooling alone is enough to pull serious builders over, or if the harder part remains proving that the privacy layer and settlement path hold up once real applications start leaning on them.

#dusk $DUSK @Dusk