英鸿³³₇
618 Publications
英鸿³³₇
Compte Square Vérifié+2016年进入币圈⭕｜近我者富｜x推特@yinghong7613 英鸿337
Trade fréquemment
4 an(s)
1.6K+ Suivis
56.2K+ Abonnés
43.4K+ J’aime
Publications
Tous
Citations
Direct
PINNED
Uxuy与subb 专场|币安广场AMA专场重磅来袭8月28日晚，锁定青蛙王子-BNB直播间
时间:20:00~22: 00
我们将围绕UXUY与SUBB生态展开深度交流，开启实时问答互动。
和行业伙伴一起聊聊Web3的新机遇，现场多多互动福利
#SUBB #UXUY#币安广场AMA
时间:20:00~22: 00
我们将围绕UXUY与SUBB生态展开深度交流，开启实时问答互动。
和行业伙伴一起聊聊Web3的新机遇，现场多多互动福利
#SUBB #UXUY#币安广场AMA
灼见
·
--
🔥 BTC站上 $80K之后，今天真正值得关注的不是价格，而是资金。
$BTC 在突破 $80K后，目前仍围绕这一关键位置反复争夺。
但价格背后，一个更重要的信号正在出现：
机构资金正在持续回来。
美国现货BTC ETF已经连续 8个交易日净流入，这一轮累计流入约 $2.8B。
与此同时，ETH ETF同样保持连续8日流入，累计资金已经超过 $1B。
这意味着当前市场正在发生一个值得关注的变化：
前期行情更多由突破、Short Squeeze和情绪修复推动。
而现在，真正的ETF资金开始成为行情的重要变量。
今天还有另一个关键事件：
约 $6.09B BTC期权 + $920M ETH期权到期。
所以接下来的市场可能不会平静。
我现在更关注三个信号：
🔹 BTC能否真正站稳 $80K
🔹 ETF资金连续流入能否延续
🔹 BTC稳定后，资金会不会进一步扩散到ETH和BNB
突破可以制造热度。
持续的资金流入，才能决定行情的质量。
接下来真正值得问的已经不是：
“BTC还能涨多少？”
而是：
“资金下一站会去哪里？”
👇 BTC / ETH / BNB？
#BTC #ETH #BNB
$BTC 在突破 $80K后，目前仍围绕这一关键位置反复争夺。
但价格背后，一个更重要的信号正在出现：
机构资金正在持续回来。
美国现货BTC ETF已经连续 8个交易日净流入，这一轮累计流入约 $2.8B。
与此同时，ETH ETF同样保持连续8日流入，累计资金已经超过 $1B。
这意味着当前市场正在发生一个值得关注的变化：
前期行情更多由突破、Short Squeeze和情绪修复推动。
而现在，真正的ETF资金开始成为行情的重要变量。
今天还有另一个关键事件：
约 $6.09B BTC期权 + $920M ETH期权到期。
所以接下来的市场可能不会平静。
我现在更关注三个信号：
🔹 BTC能否真正站稳 $80K
🔹 ETF资金连续流入能否延续
🔹 BTC稳定后，资金会不会进一步扩散到ETH和BNB
突破可以制造热度。
持续的资金流入，才能决定行情的质量。
接下来真正值得问的已经不是：
“BTC还能涨多少？”
而是：
“资金下一站会去哪里？”
👇 BTC / ETH / BNB？
#BTC #ETH #BNB
做常人不敢做的事，是需要资本的，完美演绎了加密圈的魅力，就是看不顺但无法干掉
Nice
Eman098
·
--
#dusk $DUSK @Dusk
What caught my attention while going through Dusk's docs: only two contracts exist At genesis the stake contract and the transfer contract. Everything else including DuskVM and DuskEVM sits on top of them.
That's a strange amount of concentration for a chain built to settle regulated assets. So I wanted to check what these two actually do and whether they can be changed later.
The stake contract tracks provisioners who is staked how much when rewards mature when slashing applies. The transfer contract handles both public (Moonlight) and shielded (Phoenix) balances and it's the only place contract to contract fund movement actually happens. Every execution environment routes through it for settlement and data availability per current docs.
Why that matters: if you are building on DuskEVM or issuing assets through Dusk Trade, you are not just trusting your own contract logic. You are trusting that these two genesis contracts behave correctly indefinitely since they are the settlement substrate underneath everything else.
Here is what I couldn't pin down. Docs describe these contracts being refactored over time the staking contract was rebuilt to fix a storage issue and later engineering updates changed its Event structure. So they clearly aren't frozen in the immutable at genesis sense.
What's unclear to me is the actual upgrade path: is it discretionary (protocol team ships a network upgrade) or is there a formal on chain governance step that provisioners vote on before genesis contract logic changes? The docs I found describe what the contracts do, not how modifications to them get authorized.
For a chain positioning itself for institutional settlement that distinction team authorized upgrade vs. provisioner ratified upgrade seems like it should be documented explicitly somewhere.
Has anyone seen where @Dusk specifies the actual Authorization process for genesis contract changes?
$DUSK #dusk
What caught my attention while going through Dusk's docs: only two contracts exist At genesis the stake contract and the transfer contract. Everything else including DuskVM and DuskEVM sits on top of them.
That's a strange amount of concentration for a chain built to settle regulated assets. So I wanted to check what these two actually do and whether they can be changed later.
The stake contract tracks provisioners who is staked how much when rewards mature when slashing applies. The transfer contract handles both public (Moonlight) and shielded (Phoenix) balances and it's the only place contract to contract fund movement actually happens. Every execution environment routes through it for settlement and data availability per current docs.
Why that matters: if you are building on DuskEVM or issuing assets through Dusk Trade, you are not just trusting your own contract logic. You are trusting that these two genesis contracts behave correctly indefinitely since they are the settlement substrate underneath everything else.
Here is what I couldn't pin down. Docs describe these contracts being refactored over time the staking contract was rebuilt to fix a storage issue and later engineering updates changed its Event structure. So they clearly aren't frozen in the immutable at genesis sense.
What's unclear to me is the actual upgrade path: is it discretionary (protocol team ships a network upgrade) or is there a formal on chain governance step that provisioners vote on before genesis contract logic changes? The docs I found describe what the contracts do, not how modifications to them get authorized.
For a chain positioning itself for institutional settlement that distinction team authorized upgrade vs. provisioner ratified upgrade seems like it should be documented explicitly somewhere.
Has anyone seen where @Dusk specifies the actual Authorization process for genesis contract changes?
$DUSK #dusk
幸运雨Rain
·
--
🌤️周三午后，允许自己暂时跳出盘面的喧嚣🍂。
投资不是时刻盯盘的博弈，懂得留白同样重要📊。
市场的涨跌轮番上演，不必被每一根K线牵动心绪🕊️。
放下浮躁的执念，守住自己的投资节奏与认知边界⚖️。
很多机会，都是在冷静观望之中慢慢浮现⏳。
沉淀自我，保持松弛，时间终会回馈有耐心的人✨。
愿我们于起伏之中，寻得属于自己的从容力量💫。
投资不是时刻盯盘的博弈，懂得留白同样重要📊。
市场的涨跌轮番上演，不必被每一根K线牵动心绪🕊️。
放下浮躁的执念，守住自己的投资节奏与认知边界⚖️。
很多机会，都是在冷静观望之中慢慢浮现⏳。
沉淀自我，保持松弛，时间终会回馈有耐心的人✨。
愿我们于起伏之中，寻得属于自己的从容力量💫。
Connectez-vous pour découvrir plus de contenu