EntryOnly

フォローする前に必ず読んでおくべきこと

1. すべてのトレードが勝ちになるわけではありません。この世界で誰もがそれを保証できるわけではなく、私も例外ではありません。

2. 私がシェアするすべてのトレードには、明確なエントリー、TP、SLが付いています。それらを適切に守る必要があります。特にストップロス。

3. 常に私のトレードアップデートを注意深くフォローしてください。価格が数時間動いた後にエントリーレベルに戻ったときにトレードに入らないでください。

例: もし私が午前8時にトレードを呼び出し、価格がすでに動いている場合、あなたが午後5時にエントリーに戻ったときにそれを見たなら、そのトレードはもう受けないでください。

4. 1日あたりのトレード数は決して固定されていません。ある日は多く、ある日は非常に少ない場合があります。それは常に市場の状況とセットアップの質によります。

5. 最も重要なことは、どのトレードにも入る前に慎重に考えることです。それはあなたのお金であり、あなたの決断です。常にDYOR。

$ESPORTS $BTC $ETH

Cross-checked the "leading fixed-rate protocol" language against an actual lending leaderboard this morning.

Press coverage keeps calling @TermMax Fi "the leading fixed-rate protocol for decentralized finance," and the Cumberland-led raise ($4.25M seed, alongside HashKey, Decima, Longling, MZ Web3) gets cited as validation. Fair enough on the backing.

But pulled up DeFiLlama's lending category just to see where TermMax actually sits: #36 by TVL out of 467 tracked protocols, 0.1% of the category's $41.7B. Aave alone is $14.3B. Morpho's $8.08B. Even mid-tier names like Venus Core Pool ($1.08B) or Maple ($2.4B) dwarf it.

Meanwhile the actual capital-allocation decisions, which markets get liquidity, what risk parameters apply, who curates a vault, are already made by a small named list (Keyrock, Edge Capital, AlphaPing, Origami Crypto, others), fully operating before a single TMX vote has ever happened. TMX's governance utility includes curator whitelisting, but whitelisting arrives after the curator relationships and vault strategies already exist.

TGE is set for Aug 25. Governance rights technically start there too, just on top of a curator lineup and market structure token holders had no vote in building.

"Leading" and "#36 in a niche corner of lending" aren't contradictory exactly, early-stage categories work like that. But makes me wonder what's actually left for governance to decide, versus what's just ratifying choices already locked in before launch.

#termmax @TermMax $BTW $HEMI $VELVET

I went back through Dusk's core components page last night, trying to map out where Dusk Trade actually sits relative to everything underneath it, because I'd been treating it as just another app without thinking about what it's built on.

At the bottom is DuskDS, handling consensus, settlement, data availability, and finality, running on Rusk as the node implementation, Succinct Attestation as the consensus mechanism, and Kadcast for peer to peer networking. Above that sit the two execution paths, DuskEVM for Solidity and standard EVM tooling, DuskVM for native Rust and WASM contracts, both settling back down to DuskDS. Then there's Citadel handling identity, credentials, and selective disclosure, and Dusk Connect handling wallet discovery and account connection. Dusk Trade sits at the very top, the actual product layer, turning all of that into something a user experiences as onboarding, buying, selling, and settlement.

What struck me is how much has to be coordinated correctly just for Dusk Trade to function as one clean workflow. Identity from Citadel, wallet state from Dusk Connect, execution from EVM or VM, and finality from DuskDS all have to line up behind a single trade action.

Is that tight coordination actually the hard engineering problem here, harder than any single layer on its own?

#dusk $DUSK @Dusk $BTW $HEMI

I catch myself doing this every time I read "privacy" in a blockchain context, mentally treating it as one dial, fully open on one end, fully closed and unverifiable on the other. Going through Dusk's own breakdown of what it actually provides made me stop doing that.

Privacy, transparency, and selective disclosure show up as three separate rows in how Dusk describes its capabilities, not one sliding scale. Privacy covers shielded transfers and zero-knowledge proofs. Transparency covers public accounts and public chain data. Selective disclosure is its own distinct thing, controlled visibility specifically for issuers, venues, auditors, or supervisors. Hiding something from the general public and losing the ability to verify it turn out to be two completely different properties, not one.

That reframed something for me. I'd been assuming an encrypted balance was, by definition, unverifiable to everyone. It's actually the opposite premise, encrypted from the public by default, verifiable to whoever's authorized, on a case by case basis rather than an all-or-nothing switch.

What I haven't pinned down yet is the actual mechanism deciding who counts as authorized in a given case, and whether that determination happens at the protocol level or gets left to whichever application is built on top. That's the piece I want to understand next.

#dusk $DUSK @Dusk $BTW $TUT

I used to keep the safety rules as a mental list I'd recite before a trade, badge, completion rate, payment name, don't release on a screenshot. Recently I noticed I don't recite it anymore. I just do it, the way I don't consciously remember to check a mirror before changing lanes.

That shift happened somewhere around my ninth trade, I know the number because I still have all nine Order IDs saved, back when saving them felt like a chore instead of a reflex. The list stopped being something I ran and became something I noticed only when I skipped a piece of it, a half-second gap where something felt off before I could name what.

What's left, stripped down to what I actually still check: who I'm trading with, not just their badge but how long the badge has been true. What actually lands in my own bank app, never what someone tells me landed. And whether anything about the pace feels wrong, too fast, too convenient, too eager to leave the order chat.

Everything else, Order IDs, receipts, staying on-platform, isn't a step anymore either. It's just what happens by default when the three real checks are already running.

Self-critique: I don't think this makes me safer than someone still reciting the list step by step. Muscle memory doesn't announce itself installing; it just quietly finishes one day, and a memorized list catches things a half-formed instinct might miss on a day I'm distracted in a way habit never will.

I still don't know what happens the first time my instinct is wrong instead of my checklist. I'd like to think I'd notice. That's exactly the kind of thing instinct always assumes about itself.

#binancep2pantoan @Binance Vietnam $TUT $HEMI $SNDK

Hedgerの特徴リストの1行を何度も読み返しました。すぐには私の頭に入ってこなかったからです。「ハイブリッドなUTXO/Accountモデル」。クロスレイヤーの合成（composability）を支え、現実世界の金融システムとの統合を可能にする、と説明されています。私はしばらく考えましたが、なぜ機密トランザクションのエンジンが、1つだけ選ぶのではなく、同時に両方のモデルを必要とするのかが分からなかったのです。

そして「なるほど」と腑に落ちた詳細を見つけました。Hedger Alphaのセットアップでは、ユーザーは2つの別々のアドレスを使います。コントラクトとやり取りするための通常のEVMアドレスと、暗号化された残高を保持するために特化した、別個のHedgerアドレスです。これが実際のところ「ハイブリッド」な部分です。システムのうち、通常のEVMとして動く必要がある部分ではアカウント型のアドレスを使い、暗号化された状態を保ち、レイヤーをまたいで合成可能である必要がある部分では、その下にUTXOに近い構造を持たせています。

最初にこれがどう動くのかを思い描いたときは、2アドレスモデルになるとは予想していませんでした。1つのウォレット、1つの残高で、プライバシーはその上にただ適用されるものだと思っていたのです。DuskEVMが片側で標準のEVMツールと会話する必要がある一方で、Hedgerの機密ロジックはもう片側で動くのだ、と考えると、この分け方のほうが筋が通ってきます。ただし、それにはユーザー、あるいはウォレットのインターフェースが正しく管理しなければならない項目が少し増える、ということでもあります。

#dusk $DUSK @Dusk $AIO $PORTAL

というのも先週のP2P売買で起きたんだけどね、みんな。自分でも「そんなものがある」なんて知らなかったのに、危うく引っかかりそうになったよ。

買い手は「支払いは完了した」と言って、QRコードを送ってきて、「銀行アプリはこういう方が分かりやすいから、『確認用の領収書を見るためにスキャンして』」って言うんだ。無害に聞こえるでしょ？
俺はほぼスキャンしちゃったんだよね。癖で。たぶんVietQRコードは100個くらい、何も考えずにスキャンしてきたから、もう1個も「判断」って感じがしなかった。

でも、何か引っかかって動けなくなった。なんで“自分の口座に入金されたことを確認するために”何かをスキャンする必要があるんだ？逆だろ。VietQRコードって、片方向に作られてる。スキャンする人からの送金内容を、スキャン先に入っている口座へ送るためのものなんだ。

その規格に「スキャンすると、すでに到着したお金が表示される」バージョンなんて存在しない。もしそれが“領収書”だというなら、領収書が果たす役割をしていない。

結局、スキャンしなかった。自分の銀行アプリを開いたら、何も入金されていなかった。

今後覚えておくことがいくつかある：

🔴 他人が送ってきた「支払いを確認するため」と称するQRコードは決してスキャンしない。確認するのは自分のOWNアプリ、それだけ。

🟡 依頼がどこかおかしいと感じたら（例えば“すでに自分のものになっているお金を見るのに、なぜ俺が何かをする必要があるの？”というように）、それ自体が危険信号。

🟢 本当の残高は、自分の銀行アプリで直接確認する。近道なし、リンクなし、誰かから送られてきたコードなし。

みんなもこのQRトリック、前に遭遇したことある？どれくらい一般的なのか、純粋に気になってる😳
#binancep2pantoan @Binance Vietnam $BTW $ACE $VELVET

Once I saw DuskEVM was OP Stack based, I wanted to trace an actual transaction through it instead of just accepting the label. So I went through the flow step by step last night.

A transaction gets submitted to the DuskEVM sequencer first. That's standard OP Stack behavior, the sequencer orders it and includes it in an L2 block almost immediately. That's the part that feels fast and familiar to anyone who's used a rollup before. But the sequencer isn't the end of the story here, a batcher takes that transaction data and publishes it to DuskDS, Dusk's settlement and data-availability layer underneath.

That's the adapter piece I was trying to understand. OP Stack normally hands that job to Ethereum. Here it's swapped out for DuskDS instead, which means the same rollup architecture developers already know is being redirected toward a settlement layer built specifically around deterministic finality for regulated assets, not toward general-purpose L1 security.

Following it through like that made something click that reading the summary hadn't. The sequencer step and the DuskDS step are doing genuinely different jobs, one gets your transaction moving, the other is what actually anchors it. I hadn't separated those two moments before, I'd just been picturing "transaction happens" as one single event.

#dusk $DUSK @Dusk $AIO $HEMI

He suggested a video call to "make this easier," screen-shared his banking app live so I could watch the transfer happen in real time. A balance ticked upward on his shared screen, an amount that matched the order almost to the dong.

Except I'd never once seen my own account update because of something happening on someone else's screen.

That's the strange geometry of a screen-share: I was watching pixels rendered on his device, encoded, sent to mine, displayed back, a recording of an interface, not an interface connected to my bank in any way. A number changing on a screen he controlled told me exactly as much about my own balance as a photo would have. Less, actually, I couldn't even freeze the frame to look closer.

I said thanks, ended the call, opened my own banking app on my own device, using nothing he'd shown me. Nothing had landed.

He'd apparently been very convincing to watch. He just hadn't been connected to my account at any point, and no amount of watching changes that.

What actually unsettled me afterward wasn't the trick, it was how much more convincing "watching" felt than reading. I know a screenshot can be edited. Somehow "live" bypassed that instinct completely, like watching made it real in a way a still image never could.

I still don't have a clean answer for why. I just check my own screen now, regardless of what I'm shown on someone else's.

#binancep2pantoan @Binance Vietnam $Q $SPORTFUN $BASED

Every time I look at a new privacy-focused L1, I brace myself for a familiar catch, whatever tooling I already know from Ethereum gets thrown out and I have to learn a completely new stack just to build anything. Reading into DuskEVM, that wasn't really the case here.

DuskEVM is built to let developers keep using Solidity and existing Ethereum tooling, with something called Hedger sitting alongside it as part of that layer. DUSK itself is used to pay gas and execution fees on that side, and it can move between the Dusk L1 and DuskEVM through a bridge. On the surface, that means a developer coming from an EVM background isn't starting from zero.

What I keep thinking about is what's actually happening underneath that familiar surface. The privacy and compliance logic that makes Dusk different from a standard EVM chain still has to live somewhere, and Hedger seems tied to that, though I haven't found a clear breakdown yet of exactly what role it plays or how much of the underlying complexity it's handling for the developer versus just exposing in a different form.

That's the part that makes this interesting to me rather than just convenient. Familiar tooling lowers the barrier to build, but it doesn't necessarily mean the underlying assumptions are the same as a plain EVM deployment, especially once privacy and regulated-asset logic get involved.

If anyone here has actually built on DuskEVM, I'd like to know how much of that difference you end up having to reason about versus how much stays invisible.

#dusk $DUSK @Dusk $ACE $CYS

「リリース」を押した10秒後に本当に何が起きるのか

何も起きません。これが、誰もあなたに事前に警告してくれない部分です。

自分の下した決断の大きさに見合う、何かしらの実感——確認の感触、音、アニメーション——そんなものを期待していました。ところがボタンの色が変わっただけで、画面はそのまま無難に固まり、つい30秒前とまったく同じように見えます。

その間に、何かがこっそり失敗したのではないかと半ば疑いながら、アプリを2回更新しました。

何もありませんでした。暗号資産は「リリース」をタップした瞬間にすでにエスクローから出ていて、「confirmed（確認済み）」のステータスが追いつくのに少しだけ時間がかかるだけです。私は、更新し終わる前にすでに決着していることについて、インターフェースが安心させてくれるのを待っていたのです。

その後に気づいたのは、P2Pの不安の多くが、その仕組み（即座に起きるもの）ではなく、「それを確認する」ためのその沈黙のところに住んでいるということでした。エスクローは安心を提供しません。静かに処理を済ませるだけで、感覚ではなく、証拠が欲しければ注文履歴を確認してほしい——そう期待しています。

自己批評：これは欠陥というほどではないと思いますが、それでもミスマッチです。システムはログを信じる人たちによって作られました。多くの新規ユーザーはまず感覚を信じ、ログは何かがすでに取り返しのつかないところまで進んだ後にのみ信じるのです。

それでも私は、リリースのたびに今でも2回更新します。2回目を見ても何も変わらないと分かっていながら。

#binancep2pantoan @Binance Vietnam $ACE $CYS $HEMI

Asset rules, eligibility, privacy, transfer, audit, one continuous flow

I used to think of on-chain compliance as a series of separate checkpoints bolted onto a transaction, a KYC gate here, a permission check there, mostly disconnected from each other. Looking at how Dusk frames it, it reads more like one continuous flow instead of a set of isolated steps, asset rules define what's allowed, eligibility determines who qualifies, privacy governs what stays shielded, transfer executes the movement, and audit closes the loop by keeping everything verifiable after the fact.

What stood out to me is that each stage feeds into the next rather than existing on its own. Rules aren't just static conditions checked once, they shape who's even eligible to hold the asset, which in turn shapes how privacy gets applied, since not every party in a transaction needs to see the same information. Then the transfer itself carries that logic through, and the ability to audit afterward isn't an afterthought bolted on for regulators, it's built into the same structure from the start.

It's a different mental model than the "transaction first, compliance later" approach a lot of chains default to. Here it looks more like compliance and privacy are threaded through the entire lifecycle of the asset, not just checked once at the entry point. For anything meant to serve regulated markets, that continuity seems less like a nice-to-have and more like the actual foundation the rest of the system depends on.

#dusk $DUSK @Dusk $AKE $SNXX

二重スクリーンショット、バレてしまった二枚目

最初のスクリーンショットは、口座末尾が4471のアカウントからの送金を示していました。でも私の銀行の表示には何も出ていなかったんです。

「変だな、確認してみる」そう書いてから、彼は次に二枚目のスクリーンショットを送ってきました。金額も時間も同じで、ただ口座が別。末尾は8823。

スクリーンショットが二枚。取引は一つ。それが、私がどうしても飲み込めなかった部分です。

本物の送金は、必ずちょうど一つの口座から行われます。もし最初のスクリーンショットが本物なら、二枚目が存在する理由はありません。待つか、もう一度確認するよう私に頼むだけでしょう。別口座の二枚目が筋として成立するのは、そもそも最初のものが最初から本物ではなかった場合だけです。

どんな本物の送金にも、その取引に紐づいた銀行発行の参照コードが必ず付随します。使い回しや編集しただけのスクリーンショットを偽造する際に、ふつうはそこまで気にしないことが多いからです。ほとんどの人は、参照コードを確かめようと思わないから。ですが、彼の二枚のスクリーンショットには、私の銀行が照会できるものと一致する参照コードが一つもありませんでした。

私は「実際にどの口座を使ったのか」を尋ねました。彼は答えず、その代わりに三枚目のスクリーンショットを送ってきたんです。今度は金額が別で、まるで量の違いが一貫性の代わりになるかのように。

私は画像への返信をやめて、自分の銀行アプリを見ているだけにしました。二つの口座のどちらからも、どんな金額でも、あの間ずっと何も着金はありませんでした。

私が予想していなかったのは、写真ではなくパターンに気づくまでにどれだけ時間がかかったか、ということです。スクリーンショットは、それぞれ単体では十分に説得力がありました。けれど並べて比べてみると――口座は一つ、次は別口座、さらに別の数字――その積み重ねで、「証拠」が三つあるのに矛盾へと変わってしまったんです。

本物の支払いは、本物のスクリーンショットが一枚あれば十分です。二枚目なんて要りません。

#binancep2pantoan @Binance Vietnam $AKE $SNXX $ACE

For a while I assumed privacy on-chain basically meant anonymity, transactions and balances disappearing from view entirely, nobody able to check anything. Reading through how Dusk actually approaches this made me realize that's not quite right, and honestly not what regulated finance would even want. A system where nobody can verify anything isn't compliant, it's just opaque, and opacity is the opposite of what financial oversight is built on.

What Dusk seems to be doing instead is closer to selective disclosure. Balances and transaction details can stay encrypted from the general public, but the underlying structure still allows authorized parties to verify what they need to verify, when they have the right to do so. That distinction matters a lot once you think about it from an institutional angle. A bank doesn't publish customer balances to the world, but it absolutely can produce records for a regulator or an auditor on request. That's the model this reminds me of, privacy as a default state with verification still fully possible, not privacy as a way to make everything untraceable.

It's a subtle difference on paper but a significant one in practice. Full anonymity and financial compliance don't really coexist, one tends to cancel out the other. What actually makes on-chain finance viable for regulated players isn't hiding data from everyone, it's controlling exactly who gets to see it and under what conditions, which is a much harder problem to solve than plain encryption.

#dusk $DUSK @Dusk $AKE $AVAAI

Why Binance Doesn't Ask You to Trust the Other Person, The Question I Was Asking Wrong

I noticed most P2P safety advice, including plenty I've written myself, is framed as a question: how do you know you can trust this person? I don't think that's actually the question Binance P2P is built to answer.

Escrow doesn't assess character. It doesn't score kindness, and it doesn't need to, because it isn't asking anyone to be trusted at all, it's holding the asset so no one has to be. The chat log doesn't verify honesty either. It just makes sure whatever was said can be checked later by someone other than the two people who said it.

The redesign, once I looked at it that way, is quieter than I expected: Binance didn't build a better way to know who to trust. It built a system where the answer to "can I trust this person" stops mattering as much, because the process holds regardless of what the person turns out to be.

Self-critique: this only holds as long as the process is actually followed. The moment a trade moves off-platform, or a screenshot replaces an actual bank check, the whole design collapses back into the original question, trusting a person, unverified, exactly the situation the platform was built to avoid. The system doesn't protect anyone from choosing to leave it.

I'm waiting to see whether that framing, trust the process, not the person, ever fully replaces the instinct to size someone up first. Mine hasn't, not completely. I still glance at a profile picture before I check a completion rate, even knowing which one actually tells me something.

#binancep2pantoan @Binance Vietnam $BR $CYS $APR