@EtherWizz_ @CYZhang01 @_RichardTeng @heyibinance @karin_veri @FullTiltFrancis @vianebinance 133K speaks volume
English
Bellamy ⚡
5K posts
Bellamy ⚡
@Bellamy_Jake1
Profit Maxi. Flying high with #BTC & #ETH
United States Katılım Haziran 2024
55 Takip Edilen2.3K Takipçiler
I’ve been active on Binance Square for 3+ years, built 133K+ followers, and stayed consistent with content, signals, and insights.
But something doesn’t make sense 👇
@CYZhang01 @_RichardTeng @heyibinance @karin_veri @FullTiltFrancis @vianebinance
English
English
$XAUH getting real attention → tokenized gold is becoming practical
Just watched this AMA 👇
youtube.com/watch?v=gomHwT…
→ Real gold + on-chain proof
→ Telegram access + yield potential
Still early… but narrative is building @BiconomyCom @HerculisCoin
YouTube
English
@mominsaqib The market doesn’t predict the future it just shows what people believe right now.
English
Haha man!
This wasn’t a trust model misunderstanding
RPCs got compromised and DVN was fed poisoned data - once the verifier layer itself is deceived, it’s not just about how many DVNs you picked
@KelpDAO trusted the system, but the system failed
Easy!
Trinh Tung | LZ@tungtrinhdinh
This case is not a failure of LayerZero, but a failure to properly understand the trust model. - @LayerZero_Labs allows each application to define who and how many DVNs they trust - @KelpDAO chose the lowest trust diversity with the highest risk: relying on a single source ➡️ When all trust is concentrated in one point, the system is no longer truly decentralized, but effectively centralized with a decentralized facade.
English
I’ve been in crypto for a while, but most projects never really aligned with my values.
Then I came across $MECCACOIN built with guidance from a Sharia board at Al-Azhar and even backed by a Fatwa.
No riba, no gambling, and a portion goes to zakat.
Joined early because it actually feels meaningful, not just hype.
@meccacoin_meme
English
@LordOfAlts @LayerZero_Core If the base layer isn’t resilient, nothing built on top can truly be secure.
English
FRAGILITY AT SCALE this is exactly what happens when one system controls the rails and everyone is pushed onto it
@LayerZero_Core calls it modular but most teams don’t build their own security from scratch they follow what’s given, what’s easy, what works
That is how you end up with a huge part of the ecosystem moving through the same path including @KelpDao
And suddenly it’s apps chose wrong
but if the system you run, the routing you control, the layer everything depends on gets compromised… that’s not on the apps using it
@KelpDao didn’t create that risk, they were operating inside it
you can’t sell flexibility and then disappear when the foundation breaks
because when the base fails, everything on top goes with it
donnoh.eth 💗@donnoh_eth
layerzero is fragility at scale. go visit sekuba.github.io/dvnstats/ by @sekubalias to understand why we need to fight this interoperability model
English
@Draxen_Web3 @LayerZero_Core @KelpDAO Defaults matter more than people admit they quietly shape the whole ecosystem.
English
Remember when keys were shared and contracts had to be reissued
The decentralized verifier network built on defaults pushed by @LayerZero_Core that most great projects including @KelpDao simply followed
1/1 didn’t come from nowhere it’s in their docs, their examples, and ~40% of the ecosystem ends up there
then a full infra-level attack hits RPCs compromised, failover forced, the whole path owned and somehow it’s framed as “config”
even though no DVN setup really saves you when the layer you operate gets taken over
and if all of this was visible across the network the whole time, it raises bigger questions than just apps chose wrong
freedom to configure sounds great until the defaults lead everyone into the same risk
good times indeed!
English
@HolaItsAk47 @LayerZero_Core @KelpDAO @KelpDAO was just a user of that stack; accountability also lies with the core layer.
English
This is the real question!
Fair point on projects choosing configs, but that’s only one part of it. The bigger issue is what sits underneath the infra, the routing, the layer everything depends on
@LayerZero_Core putting this completely on @KelpDao doesn’t feel right when that base layer is part of what they run
Kelp didn’t control that, they just used the system like everyone else
That modular security idea only works if the foundation is strong. if that layer fails, blaming the apps using it doesn’t really hold
you can’t push responsibility down when the problem sits deeper in the stack
Wu Blockchain@WuBlockchain
OneKey Founder Yishi on Handling the KelpDAO Hack 1, Best case: negotiate with the hacker and offer a 10-15% bounty. 2, If talks fail, let the LayerZero ecosystem fund cover most of the loss. 3, KelpDAO is the weakest; compensate with tokens + future revenue, or sell the whole project to L0 or BMNR. 4, Aave’s Umbrella and stkAAVE serve as the final backstop, but WETH depositors must not take any haircut — otherwise it would trigger repricing across Morpho, Spark, Fluid, Euler, blacklist the LRT sector, and set DeFi back by years. 5, He believes Aave can survive this. x.com/ohyishi/status…
English
ngl the config convo feels a bit surface level here
what actually happened sits deeper and that’s where this gets uncomfortable for @LayerZero_Core
you can’t run the infra, push docs that default to 1/1, see a huge chunk of the ecosystem including @KelpDao follow that path and then act surprised when it shows up as risk at scale
so framing it as they chose 1/1 misses above thing the design that led people there… and the infra layer that actually failed
@KelpDao didn’t invent this setup, they operated inside it
and if that setup was visible across the network the whole time, it raises a bigger question why was it allowed to become the norm in the first place
modular security sounds great until everyone ends up on the same path
and when that path breaks, pushing it back on builders doesn’t really hold
©️Jamisky@_Jamisky
over the weekend I removed a good chunk of my funds onchain after reading this post-mortem from layerzero i am going to withdraw more it's that bad layerzero is basically saying yeah we know it’s our DVN, but we warned them against using a 1/1 DVN set up 💀
English
@Cirus_Org @LayerZero_Core Defaults guide teams you cant just ignore them.
English
It is too bad to reduce this to bad config thing and this lets @LayerZero_Core off way too easy
yes, they now say 1/1 shouldn’t be used for production but that’s exactly the problem. their docs, examples, and actual ecosystem behavior helped make that setup common in the first place, and teams like @KelpDao were operating inside the path that was already there
Then when the whole thing blows up, the blame gets pushed back onto the app layer like that closes the case
it doesn’t
if a huge part of the network ends up configured the same way, that was visible. if the infra underneath gets compromised, that’s deeper than devs chose wrong. and if your whole defense is “modular security,” that only works when the base you’re asking everyone to trust is actually solid
@KelpDao didn’t invent the defaults, didn’t control the infra, and didn’t create the conditions that made this risk spread across the ecosystem
so no, calling this just a config failure really doesn’t cover what actually went wrong
Haseeb ＞|＜@hosseeb
TL:DR: * LayerZero says it was Kelp's fault for running 1/1 DVN setup, their docs warn against that (although LZ operated the actual DVN) * Yep, North Korea again * LayerZero had solid opsec but still got pwned (they're not disclosing the original compromise path it seems) * Crazy sophisticated attack. North Korea didn't actually fully compromise the LZ machine. But once they got in, they grabbed the set of RPCs the LZ machine used, and then hacked 2 of the RPC servers it was pulling from, installing fake versions of op-geth on those RPC servers. They then DDOSed the main RPC to cause failover to one of the hacked RPCs, and then the hacked RPCs reported the malicious transaction (hiding their tracks by giving different RPC responses to observability infra). Then once the attack was done, the malicious binary self-destructed, deleting the logs on the compromised RPCs. Very, very complex attack. * Boy, LZ really are not doing themselves favors with lines like these: "We want to be unambiguous on this point: the LayerZero protocol itself functioned exactly as intended throughout this event. [...] The entire attack was isolated to a single application – zero contagion risk throughout the system, zero other OFTs or OApps impacted." 😬
English
Fair point on modular security and flexibility that’s how it’s supposed to work on paper but when you zoom out and look at actual usage across the network, a different picture shows up
a large part of the ecosystem ends up on the same paths, relying on the same setups, and trusting infra that’s closely tied to @LayerZero_Core
that’s where the gap is
They putting everything on @KelpDAO doesn’t really hold. They didn’t invent the setup, they used what the system made normal
And once the infra layer itself gets hit, calling it a “config issue” starts to feel like deflection because this isn’t just one app making a mistake
If defaults shape behavior, if that behavior spreads across the network, and if the underlying layer becomes the failure point then responsibility doesn’t just sit with the apps using it
You can’t sell flexibility and then push all the risk downstream when things break
Zach Rynes | CLG@ChainLinkGod
.@LayerZero_Core’s marketing is so incredibly misleading at times, it’s absurd Take their “Decentralized Verifier Networks (DVNs)” for example DVNs are the infrastructure responsible for validating cross-chain transactions in the LayerZero ecosystem By the name, you would assume a DVN by definition is a decentralized network of node operators, right? Well no, in most instances the term “DVN” actually refers to a centralized company (a single node operator) Take their most popular DVN for example, which by default is used by most projects and therefore their associated volume in the LayerZero ecosystem It’s the “LayerZero DVN”, a centralized node run by the LayerZero Labs team themselves Not decentralized, but still called a decentralized network anyways, pretty continent security theater marketing Imagine you’re a user and you’re told a dApp’s cross-chain interactions are secured by the “LayerZero Decentralized Verifier Network” What impression is the user supposed to get from that other than thinking it’s a decentralized network and not a single centralized node? Now some may try to explain away this terminology by saying that a DVN could theoretically be decentralized in some circumstances But looking at the official list of all the DVNs in their docs, almost every single DVN is just a centralized team/company And the ones that aren’t, are often just a wrapper around another protocol that’s actually attempting to solve the cross-chain problem in a decentralized manner like CCIP or Axelar that can be used without the LayerZero framework Some may also argue that you’re supposed to compose multiple DVNs together in order to make it decentralized But (1) that doesn’t justify calling infra run by a centralized company a decentralized network and (2) the default path that most projects take is to use the centralized LayerZero Labs DVN given its chain support over other DVNs Even their flagship bridge @StargateFinance only uses a whopping 2 DVNs (one of which is the team themselves) This fantasy of projects composing networks out of DVNs just isn’t what we see in reality in the majority of situations Most devs simply do not any to deal with the massive security-sensitive problem of managing, configuring, securing, or running cross-chain infrastructure, they just want something that works Centralization runs rampant in the LayerZero ecosystem but the terminology may make you think otherwise
English
Gold has always been about trust and control 🙌
Today, most options add layers fees, intermediaries, limits
$XAUH takes a different path
Direct access from the source
Private, secure storage
No unnecessary friction
Just gold, simple and fully under
control @HerculisCoin
English
@HolaItsAk47 OKX has definitely stepped up lately, especially for active traders
English
Been thinking about where i actually want to keep my trading activity, and OKX is starting to stand out more for me.
the fee side is better, execution feels smoother, and the extra campaign/referral benefits are a solid plus. for active traders, those details matter more than people admit.
@okx @OKXmena
JOIN NOW
okx.ac/join/93952173
English
@mominsaqib The strongest narratives aren’t created, they’re lived.
English
The $ASTEROID pump this weekend was something else.
- A token sitting at a $50K market cap for months.
- A 15-year-old girl named Liv Perrotto who designed a Shiba Inu plush toy for a SpaceX mission while battling cancer.
- The toy actually flew to space. She passed away in January.
- Her final handwritten request to Elon Musk was one line: "Can you make Asteroid the SpaceX mascot?"
Her mother shared the list. It went viral. @elonmusk replied "Ok."
That sent it to 600x in 48 hours. That too a token from 2024. This was a tribute to her.
This is what the memecoins actually looks like in 2026. Not manufactured hype or random narrative or speculation.
A story that made people feel something before they had time to think about anything else.
The grift version of memecoins is dead. Retail has seen the playbook too many times. Randomly deployed tokens with no soul behind them get sold into zero within days now. The market has developed a surprisingly good filter.
What survives is genuine cultural weight. Real emotion. A moment that resonates before anyone even thinks about the chart.
Community tokens aren't going away. The one with real stories will always stay which give reason for people to actually care.
English
@CarlHaawle @HerculisCoin $XAUH bringing old value into modern finance 📈
English
Most people don’t realize the gap in gold investing
→ Physical gold = storage + extra costs
→ Digital gold apps = limited utility
→ ETFs = no real ownership
$XAUH changes that
real gold + on-chain access + liquidity
Gold but built for how people invest today
@HerculisCoin
English
@mominsaqib Most people wait for perfect timing… it never comes.
English
Nobody who built something that mattered waited until they were ready.
They moved when it was uncomfortable, when they were not sure it would work, when the timing felt wrong, when the resources were not quite there.
Certainty is a story you tell yourself after the fact.
The only honest thing you can do is start before you have it.
English
@CarlHaawle @HerculisCoin This is how real use cases look, not just hype 🚀
English
$XAUH isn’t just “gold onchain” it fits different users differently
→ DeFi users:earn yield on gold (APY + LP opportunities)
→ Digital gold buyers: no custody fees, easy access
→ TON users fast entry ecosystem
Same asset. Different use cases.
Real adoption 🤝 @HerculisCoin
English