阿尔法灰

edge capital's running vaults that span both sides of termmax's $10,000 partial-liquidation threshold right now, and that number ends up mattering more than i expected. under it, a liquidator can wipe your whole position in one shot. over it, they're capped at 50%. so the real damage from getting liquidated isn't purely about how bad your collateral dropped — it's, well, it's mostly about which side of that line your loan happens to sit on.
the penalty itself doesn't move either way though. flat 10% on the liquidated debt value, split 5% to whoever calls it and 5% to the protocol reserve, borrower eats it regardless of position size. physical delivery is there to protect the lender if things go really wrong, but nothing softens it for the borrower on the small end.
not calling it broken, liquidators need an incentive to show up fast either way. just curious if that $10k line came from actual borrower-size data or just landed there because it's a clean number 🤔

#termmax @TermMax

i went back to why moonlight even exists, since it's usually described as giving institutions a transparent option alongside phoenix's privacy. dusk's own updated whitepaper says something more specific though — actually, i had to reread the line twice because i assumed it'd say something about institutional demand, but no, it says moonlight was added because integrating with exchanges was getting complicated, and the exact phrase is that it "removes any risk of being delisted."
that's a different story than "we built optionality for institutions." this reads like exchanges needed visibility dusk's shielded model couldn't give them, and moonlight got built to keep listings intact, not because users were asking for a public account model.
i don't think that's a bad reason, exchange delisting risk is a real threat and dusk was upfront about it in their own writeup. but it does complicate the "privacy-first, compliance-by-design" pitch a little — if exchanges are effectively the ones dictating that a transparent mode has to exist, how much of dusk's dual-model architecture is protocol philosophy versus a response to listing pressure.
does anyone know how much actual transaction volume runs through moonlight versus phoenix right now, or is that split not published anywhere? 🧐

#dusk $DUSK @Dusk

i went to compare dusk against polymesh since they both target regulated securities, and the actual architectural difference is bigger than i expected. polymesh is built as a permissioned l1 — it gives up open participation specifically to get compliance guarantees. dusk goes the other way, staying a permissionless pos chain and trying to get the same regulatory comfort through zk-based selective disclosure instead of restricting who can run a node.
that's not a small design choice, it's basically two different bets on the same problem, and this next part is my own read, not something i've seen a regulator confirm either way — permissioned systems seem easier for regulators to reason about since there's a known, fixed validator set, so polymesh's approach reads as the safer bet on paper. dusk's is harder to verify from the outside: it's claiming you can keep permissionless consensus and still satisfy the same institutional trust requirements, but i haven't seen anyone actually test whether regulators treat that as equivalent.
to be fair, permissionless is a real decentralization advantage dusk has that polymesh doesn't — actually, i almost left that part out, but it matters just as much as the risk side does.
has any regulator actually weighed in on whether dusk's model satisfies the same bar polymesh's permissioned structure does? 🧐

#dusk $DUSK @Dusk

280,000,000 tmx tokens go to investors with a documented 12-month cliff and 24-month vesting after that, down to the exact monthly release frequency. that level of disclosure is sitting in the whitepaper right now. what's not in there is the one date all of that math actually depends on — tge is still listed as "to be announced."
i get why teams hold the exact date close until listings and liquidity are actually lined up, that's normal practice. but termmax's own roadmap puts v2 at q2 2026 and tge right after at q3 2026, and my read is the tge date is the one actually waiting on v2, not the other way around — you don't launch a token event before the product it's supposed to be governing has shipped its next version.
could be wrong on the ordering, but that's where i'd put my money 💭

#termmax @TermMax

🔥🔥🔥

i went looking for dusk's own announcement of duskevm's mainnet launch, since i kept seeing conflicting dates in aggregator coverage — some saying january 2026, one calling it "second week of january," another in may still describing testnet work meant to "advance readiness for the upcoming duskevm mainnet." i couldn't find a primary dusk.network post confirming an actual duskevm go-live date anywhere, only secondary sources repeating each other with different years and confidence levels.
that's different from a slipped launch — this is a case where i can't even confirm one happened, and honestly i went back through their news page a second time assuming i'd just missed the post, i hadn't. the core mainnet, duskds, launched january 7, 2025, that part's solid and dusk's own site confirms it. but duskevm specifically, the evm-compatible layer everyone's citing as live, i just can't trace back to dusk's own words.
to be fair, the architecture itself — duskvm for native rust contracts, duskevm for solidity — is genuinely documented and real, this isn't a fabricated feature. it's specifically the "is it live yet" question nobody's own source seems to answer clearly.
has dusk actually confirmed duskevm mainnet is live anywhere on their own channels, or is this still aggregator noise? 🧐

#dusk $DUSK @Dusk

was digging through the vault docs on termmax last night and noticed something curators literally can't do that a solo range order setter can — in a two-way order, a vault can only borrow by selling ft it already earned from lending first. no direct collateralization, not even once. i almost skipped past it as boilerplate but it's actually a pretty firm structural wall.
makes sense why, honestly — a vault's holding pooled depositor usdc, so letting a curator post that as collateral to lever up would be a completely different risk profile than an individual doing it with their own funds. keyrock and edge capital are both running live vaults right now, and i genuinely can't tell if this rule has ever actually forced either of them to leave yield on the table, or if it's just a rail nobody's bumped into yet 🤔
#termmax @TermMax

i went to check messari's summary of the january bridge incident against dusk's own notice, and they don't match at all. messari describes it as a confirmed exploit — a compromised signing wallet, millions of dusk stolen, funds moved to bsc before the bridge got shut down. dusk's own january 17 notice reads completely differently: monitoring flagged suspicious activity on a team-managed wallet, they paused things as a precaution, and — actually i had to go back and reread that line because i assumed "no losses expected" meant something closer to messari's version, it doesn't — they state directly that no user funds were impacted.
so which one do you believe, the primary source or the aggregator? normally i'd default to the project's own statement, but "no losses expected" from a team writing about its own incident isn't exactly a neutral read either.
either dusk under-described what happened, or messari over-described it. i genuinely don't know which, and i think that gap matters more than the incident itself at this point.
has the bridge actually reopened yet, and did any final numbers ever get published anywhere neutral? 🧐
#dusk $DUSK @Dusk

i went to see whether dusk itself holds the mtf license everyone keeps citing, and it doesn't — npex does. dusk's own regulatory-edge post is actually careful about this, it says compliance is "embedded" through npex's mtf, broker and ecsp licenses, not that dusk applied for and holds anything directly. the dlt-tss piece is still listed as forthcoming, not in hand.
but scroll through aggregator write-ups and you'll see phrasing like "dusk is pursuing an mtf license," which quietly turns a partnership into something that sounds like dusk's own regulatory status. that's not a small wording slip, it's the difference between "we built infrastructure a licensed entity uses" and "we are licensed."
to be fair, this is still real regulatory coverage, npex's licenses genuinely do apply across the stack according to dusk's own post. i just think the messaging drifts further from the actual structure the further it gets from dusk's own site.
anyone know if dusk plans to hold any license itself eventually, or is npex's coverage meant to be permanent? 🧐

#dusk $DUSK @Dusk