Binance Square
dosong
36 Posts

dosong

前币安员工|氛围量化主理人|币圈不OG|只发核过原文的料|2倍杠杆都拿不住
9 Following
27 Followers
15 Liked
Posts
·
--
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
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升级分两阶段
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升级分两阶段
·
--
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_Foundation Has anyone actually deployed a contract on 745? I’d love to hear your real experience.
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_Foundation Has anyone found an official statement formally explaining this disablement? I honestly couldn’t find one.
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?
I forgot to brush for a day, can I still catch up?
·
--
Fake Authorization
Fake Authorization
无聊交易员
·
--
Guys, what the hell is this?
·
--
Beef
Beef
署哥
·
--
#Megadrop The current earnings are very low, I forgot to lock in the fixed investment a couple of days ago, I don't know how much profit I can get this time, I have no expectations.
·
--
Is it a non-custodial wallet?
Is it a non-custodial wallet?
Domingo_gou
·
--
@CZ @Yi He @Binance News I would like to ask everyone, what is going on here?

I received a stablecoin on the TRON (TRX) network using my Binance wallet and wanted to swap it for a stablecoin on the BNB chain. However, the system prompted me that my TRX balance was insufficient to cover the network fees. So, I went to the deposit interface and saw that I could withdraw from the Binance exchange to my wallet, so I chose to withdraw 10 USDT (because the minimum requirement is 10 USDT, and there's a 1 USDT fee), thinking I could finally deal with this asset.

But after the withdrawal, I found that my TRX balance was still insufficient; the actual fees to be paid were close to 3 USDT, and I had to give up. Not long after, Binance sent a notice saying I had "violated operational rules," and if I didn't submit for review, my account would be suspended?

This left me a bit confused; the withdrawal operation between my own wallet and the exchange would actually trigger an account suspension risk? What puzzled me even more was that I had previously seen a user on X asking about this, and the response did not clarify this situation.

I want to ask how Binance determines this kind of "violation"? How is this review algorithm specifically triggered? I feel a bit lost as an ordinary user and hope to get a clear answer. Thank you.
·
--
Top up opBNB?
Top up opBNB?
贾玲别跑
·
--
Why am I gray, my friends?
·
--
You are not gray, you must have rushed to opBNB.
You are not gray, you must have rushed to opBNB.
2026加油啊
·
--
Why does the wallet have a bnb link but no quantity input?
·
--
Unless you enable the setting to show risk tokens, they are hidden by default
Unless you enable the setting to show risk tokens, they are hidden by default
永远不卖大饼
·
--
Someone gave me twenty thousand coins, encountered a Pixiu plate #币安LaunchpoolNIL
This morning I found that my wallet inexplicably had extra act coins, the platform warned of risks but I didn't do anything, reported it to customer service, and in the afternoon it inexplicably disappeared again. Does anyone know what happened?
·
--
How about trying pancake?
How about trying pancake?
浪三
·
--
What's going on here (⸝⸝ᵕᴗᵕ⸝⸝)
Have you been hacked?
·
--
The big boss has a lot of BNB
The big boss has a lot of BNB
Meta猿
·
--
$KAITO $BNB I have a question recently.
Now, every time a new coin is listed, everyone is short. As long as you go short without thinking, you will make money. Do market makers really let retail investors make money?
If everyone has the inertial thinking of going short when a new coin is listed. Will there be a reversal? I always feel that the dog dealer will not let retail investors make money so easily.
This time, the holder airdropped very little kaito. I didn't sell it. I treated it as an experiment. Only with real warehouses can you pay attention to market changes. Let's see how it will trend later.
·
--
You need to top up some TRX as a fee.
You need to top up some TRX as a fee.
求财
·
--
How to transfer Usdt out of the Web3 wallet??
I don't know how to operate, I transferred it in without understanding, and I want to buy sol, but I can't exchange it.
I need help, how can I get it out or buy something else,
Is there customer service? Please come out.
·
--
no price,no
no price,no
Richard Teng
·
--
Your Web3 wallet is key to blockchain, but vigilance is crucial.

· Never import a seed phrase someone gives you
· Don’t rush into “urgent” fixes

Scammers exploit urgency—your best defense is knowledge and caution.

Read more 👇
https://www.binance.com/en/blog/all/web3-wallet-security-blockchain-rectification-and-seed-phrase-traps-explained-3131126202547005897
·
--
you already got the token,just because your network issue,you can not see the picture
you already got the token,just because your network issue,you can not see the picture
Sherry kk
·
--
I'm extremely disappointed with my recent experience with Binance. I ordered a BAB token, but instead received a flower icon. I reached out to @Binance Customer Support for help, and they assured me that the issue would be resolved within 2 days. However, it's now been 6 days and nothing has changed.

Frustrated, I requested a refund since I didn't receive what I ordered, and it wasn't my mistake to begin with. Shockingly, @Binance Customer Support threatened to terminate our chat. I expect more professionalism and better customer service from a reputable platform like Binance.

NOTE:
THIS TOKEN IS ISSUED BY BINANCE DIRECTLY, NO THIRD PARTY IS INVOLVED.
·
--
scam history,ignore it
scam history,ignore it
KCL maker
·
--
me found this in web 3 Wallet... Anybody know about it #story
·
--
BNB $1000,2025
BNB $1000,2025
·
--
why you use the old version?
why you use the old version?
LESLIE DOLPHIN ICEBERG
·
--
Trading meme coins daily but its risky not financial advice..invest money you willing to lose..you can use telegram and dexscreener to make profit by swapping your coins using#BinanceWeb3
·
--
it is a soul bound token,it can not be sold
it is a soul bound token,it can not be sold
Aayushsaini
·
--
Hey everyone pls help me i ascendantily buy BABT NFT of binance now does now able to sell it pls help me what to do with NFT cost 1 USDT
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number
Sitemap
Cookie Preferences
Platform T&Cs