dosong

This week’s crypto market macro backdrop | 8.17

Every Monday I’ll go over a few key macro numbers—only the ones that matter for crypto prices.

The most important one: U.S. 10-year real yield (TIPS) at 2.39%, basically sitting at the highest zone in the past five years. Real yields are the hardest-core gravitational pull for risk assets—when they don’t loosen, it’s hard for BTC to push higher every time.

But there’s a sign worth watching: the Fed’s total assets at $6.76T have been quietly rising since the lows in May. After more than three years of balance-sheet reduction, if this is truly the end, it could be the starting point of the next liquidity story. That said, right now it’s still just a hint, not confirmation.

China-side is a bit cold: the manufacturing PMI is 49.2, still in contraction territory; M2 growth at 7.7% is also near recent lows. The commodities market hasn’t really warmed up either—copper-to-gold is stuck at a low level.

One-sentence summary: real rates haven’t eased, liquidity hasn’t turned—but the first hint of a turn may be showing. The backdrop is like this; how to play it is up to each of you.

I’ll update these numbers every Monday. If you want to keep tracking, give it a follow.

$BTC #macro

Cardano's Dijkstra upgrade was split into two phases

The roadmap has just been released: Phase 1 uses nested transactions plus Linear Leios. The node team’s goal is to have it on the mainnet by the end of 2026; Phase 2 has Peras slated for Q2 2027, activated via a hard fork without changing the era.

Two things, explained in one sentence each: Leios targets the consensus layer, boosting throughput; Peras is a vote-driven fast finality mechanism, aiming for faster settlement. Both are the fruits of years of R&D along the Ouroboros research line.

One wording is worth clarifying: the original says the node team’s “current goal,” not a fixed launch date. If you see headlines about “must go live within the year,” take them with a grain of salt—there are several quarters between this roadmap and actual delivery, and veteran users know it.

By the way, Cardano eras are always named after computer scientists; this round is Dijkstra, the guy behind the shortest path algorithm.

Do you think this time they can deliver on schedule?

$ADA #Cardano将Dijkstra升级分两阶段

What profit opportunities does Binance have today | 8/17

There isn’t any new profit opportunity today, but a bunch of ongoing events are all about to expire—so if you want to go for it, make a move in the next two or three days.

The PLUME Spot Trading Tournament ends on 8/20. The 500U threshold isn’t high—if you already trade regularly, it’s just convenient to do.

The ALLO Spot Tournament closes on 8/19. If you’ve already been doing it, hurry up and push for the leaderboard. There’s also Alpha’s POWER Trading Competition: the top 2,000 users share the prize pool, and the early-bird multiplier is already decreasing. Still, it’s not too late to join now—applications close on 8/20.

Coming to a close soon: Wallet-chain Trade & Win S5 ends today. If you’ve participated, try to push for the top 300. If you haven’t entered, don’t join now. The GRVT Trading Competition ends tomorrow, 8/18—new entries don’t offer great value.

Risk reminder: ACX, HFT, PIVX, PYR, VANRY, and VIC have already been delisted. If you still hold any of them, deal with them ASAP. Also, SOPH deposits/withdrawals via the BSC network will be closed at 8:00 AM UTC on 8/21—if you have positions on-chain there, transfer them out as soon as possible.

These event windows are almost gone. If you’re afraid of missing the next wave, follow along—I update every day.

$PLUME #撸毛攻略

What opportunities are there to earn on Binance today | 8/16

Every morning I’ll go through Binance’s official announcements, the Launchpool page, and the Alpha event page, and pick out what’s worth watching. Today: no new campaigns, just one major update.

Most convenient to do: the latest round of flexible (U) savings with interest rate increases, up to 8% APY, from 8/16 to 9/14. No minimum deposit, zero risk—just subscribe if you have idle U. The downside is that larger funds are capped.

Major update: the XRP airdrop for RLUSD holders has restarted. The reward pool has expanded to 1,000,000 XRP, ending on 9/11. Note: it’s not “easy money.” It requires margin or a contract average daily trading volume of 500U. If you already have trading habits, then it’s worth considering.

Hurry—deadline soon: the ALLO spot contest closes on 8/19. If you’ve already joined, make sure to push the leaderboard. New entry at this point has poor value for money.

Risk reminder: the SOPH deposits/withdrawals via BSC will be closed at 8:00 (UTC) on 8/21. If you’re holding it, remember to handle it. Also, there have been many DM scams impersonating “free money” harvesting—Binance/official accounts won’t DM you.

If you want to see more, I’ll post one every day. Which one are you doing today? Chat in the comments.

$XRP #撸毛攻略

The SEC starts approving a 3x leveraged Bitcoin ETF

On Friday, the SEC posted for public comment six 3x daily leveraged ETF proposals submitted by Cboe BZX, under filing number SR-CboeBZX-2026-065. There is one each for Bitcoin, Ethereum, gold, silver, crude oil, and natural gas, issued by Volatility Shares.

I read through the SEC’s original text, and two details are worth noting.

First, it doesn’t touch spot holdings. All six hold front-month and next-month futures. Bitcoin and Ethereum trade on the CME, gold and silver on COMEX, and oil and gas on NYMEX; the remaining allocation is placed in cash-like collateral.

Second, the “3x” is a daily reset. Every day at the close it resets back to zero and starts over. In a choppy market, holding for a month may mean you’re losing first even if the underlying hasn’t fallen—compounding drag isn’t a small issue.

If this gets approved, it would be the first batch of 3x crypto ETFs in the U.S. For mainstream brokerage accounts, it would be a one-click way to go 3x long Bitcoin, and intraday volatility would likely jump up another level.

But right now this is only an initiation of the review process—still far from approval. Don’t let clickbait headlines lead you astray.

Would any of you be willing to trade a 3x product? I can barely hold a 2x one.

$BTC #SEC审查6只3倍杠杆商品ETF

Has the DuskEVM mainnet really gone live?

While scrolling through the square, I saw several posts saying that the DuskEVM mainnet launched at the beginning of the year. I’m a bit skeptical— in the reference materials the Dusk team provides to creators, it says: “DuskEVM mainnet is coming”. Does “is coming” mean it hasn’t come yet?

No point guessing—just connect directly.

The documentation clearly lists three networks: mainnet Chain ID 744, testnet 745, and devnet 310.

The mainnet rpc is rpc.evm.dusk.network. DNS resolves to 91.98.4.132, pointing to lb.h2.dusk.network. The domain exists, and load balancing is set up too. I sent requests—but no one replied.

The testnet rpc.testnet.evm.dusk.network, on the other hand, works fine. eth_chainId returns 0x2e9, which converts to 745, matching the documentation.

So the mainnet truly hasn’t been opened yet. The official sources didn’t lie—those articles are the ones adding the drama.

I also took a quick look at the testnet and noticed two numbers I couldn’t stop staring at.

One is the timestamp of block 1: 2026-07-27 18:27:05 UTC. This test chain was just restarted from genesis 19 days ago.

The other is more interesting: in the most recent 10 blocks, there are 10 transactions total—exactly 1 transaction per block. I checked the type; it’s 0x7e. The from is 0xdead...dead0001, and the to is 0x4200...0015—the system deposit transaction that every OP Stack block must include. In other words, during that time there were zero real user transactions.

Yes. DuskEVM is an OP Stack rollup, and the documentation also says it currently uses a centralized sequencer.

I’m not saying this project isn’t any good. A quiet testnet is completely normal. Every testnet is quiet.

What I’m saying is this: when something like “the mainnet hasn’t launched” turns out to be true, you can tell by just calling the RPC for 30 seconds—you don’t need to wait for someone to tell you.

$DUSK #dusk @Dusk

Has anyone actually deployed a contract on 745? I’d love to hear your real experience.

Everyone on the scoreboard has been talking about Phoenix’s anonymous set under the mask—yet it was shut down on the mainnet three months ago.

Over the past couple of days, I’ve gone through dozens of posts on the DUSK leaderboard. Several are genuinely discussing Phoenix’s privacy UTXOs and anonymous sets, and one even cites the USENIX paper from Kappos 2018 about breaking Zcash. It’s written really well.

But when I checked on-chain: Phoenix has already been disabled on the mainnet.

Block height 4,414,095, 2026-06-06 18:17:13 UTC. That hard fork was called Boreas.

All three places line up, and they’re all the same as the original text:

1. The official node info at nodes.dusk.network, /on/node/info. In the VM feature table, DISABLE_PHOENIX is 4414095, the same height as HARDFORK_BOREAS.

2. On GitHub, dusk-network/rusk’s CHANGELOG v1.7.0: “Activate Boreas and Phoenix disablement on mainnet at block 4_414_095.”

3. vm/CHANGELOG.md is more direct: “Add execution gating to disable Phoenix payments and settlement calls.”

The awkward part is that docs.dusk.network’s overview still says that Phoenix is responsible for confidential shielded transfers. The docs and the chain don’t match.

More coincidentally, Dusk open-sourced a tool called Pituitary just this March. Its job is precisely to detect contradictions between specification documents and code.

Why it was turned off—there’s been no official explanation. The blog stopped updating after April 22. I won’t invent reasons for them; I’ll just present one potentially relevant fact: the March AEGIS hard fork fixed 39 issues, including 7 critical ones. Four of them were concentrated on Phoenix’s fee and refund chains—silent inflation, arithmetic overflow that halts the chain, and refund theft. That’s what the official wrote in their own security analysis on March 11. Pretty straightforward.

Could it be only transitioning to an intermediate state of Hedger? Possibly—but that’s speculation, and I won’t state it as a conclusion.

What I really want to say is something else: before discussing a blockchain’s privacy model, first make sure that model is currently actually enabled.

$DUSK #dusk @Dusk

Has anyone found an official statement formally explaining this disablement? I honestly couldn’t find one.

I forgot to brush for a day, can I still catch up?

Fake Authorization

Beef

Is it a non-custodial wallet?

Top up opBNB?

You are not gray, you must have rushed to opBNB.

Unless you enable the setting to show risk tokens, they are hidden by default

How about trying pancake?

The big boss has a lot of BNB

You need to top up some TRX as a fee.

no price，no

you already got the token，just because your network issue，you can not see the picture