Staking Defense League

We engage in dialogue and take action to counter staking’s trend toward centralization. #KeepStakeDecentralized 💪 Begun by @cfl0ws @ChainflowPOS

[Staking Defense League @StakingDefense]

SDL has not and will NOT EVER LAUNCH A TOKEN.

It has come to our attention someone is impersonating the Staking Defense League and has created a domain to promote a token.

Again, to be 100% clear, Staking Defense League has not, and will not ever launch a token.

We are looking into the origins of this effort and vigorously pursuing takedown requests.

End of Tweet.

[Staking Defense League @StakingDefense]

@Namecheap @_SEAL_Org We were not given a report ID. Emailed [email protected] and received confirmation of receipt our report—no ID, thus far. Please reach out via DM and we’re happy to coordinate directly!

[Staking Defense League @StakingDefense]

Thanks to @_SEAL_Org for their attention to this matter. We have also submitted an abuse request to the registrar @Namecheap and will work to get the domain suspended asap. https://t.co/KKW6dD0tdJ

[Chainflow 🌞 ⚒️ @ChainflowPOS]

Thanks to the quick response from @_SEAL_ORG 🙏
The fraudulent Staking Defence League token sale domain has been added to their blacklist:

https://t.co/EtqX7tt9SC

[Staking Defense League @StakingDefense]

Further, Staking Defense League (SDL) will never contact or dm you about any token or financial opportunity, nor would we ever solicit for personal information. Stay safe out there friends! End of Tweet.

[Staking Defense League @StakingDefense]

SDL has not and will NOT EVER LAUNCH A TOKEN.

It has come to our attention someone is impersonating the Staking Defense League and has created a domain to promote a token.

Again, to be 100% clear, Staking Defense League has not, and will not ever launch a token.

We are looking into the origins of this effort and vigorously pursuing takedown requests.

End of Tweet.

[Staking Defense League @StakingDefense]

RE the #cetushack on @SuiNetwork

Speaking on behalf of #SDL -- We have voted yes on the proposal.

After careful consideration of the discussion both in the validator community and online there appears to be consensus amongst both validators and protocol users on fund recovery and we want to honor that, especially in a time of crisis.

While the Slippery Slope Fallacy is named as such for a reason, we do believe there needs to be swift and decisive action to create an objective framework for potential "black swan" events in the future. We are committed to being a part of this process and will share more thoughts in the coming weeks.

Without such a framework, we will not be inclined to support any future vote that challenges the immutability of the Sui protocol.

Our largest concerns--which are shared by many--are moral hazard both for users and developers, as well as any decision that places unsustainable governance power in the hands of validators or any other small group of entities.

At time of publishing, the Cetus hack ranks near the top 10 largest hacks in crypto history, passing any objective measure of an outlier event. It should be noted, however, that only in the case of the Ethereum's DAO hack did those events result in protocol level action. If this is to be Sui's DAO Hack Moment, which was so controversial it led to the creation of ETC, then it must be treated with the same level of severity.

At SDL, we believe the strongest networks are built on governance minimization with a well-codified, transparent set of rules for participants that cannot be easily changed. That does not mean the network cannot respond to crisis or adapt in the face of existential threats, quite the contrary. It simply means that there must be a set of transparent, well-codified rules network participants agree upon that inform how the network responds to crisis.

We have been a part of many networks that have faced hacks and existential network issues, these are often necessary moments in a network's progression to maturity and help shape the participants collective values. How the network responds is always more important than the event itself.

As the Cetus Hack fades into the rearview mirror we can no longer claim ignorance as a community--if we are unable to respond in a way that repairs the sacrifice in trust resulting from this decision and are not prepared if/when the next event happens, the fault will be solely ours.

Excited to keep building with you all.

[Chainflow 🌞 ⚒️ @ChainflowPOS]

This week’s Nakamoto Coefficient decentralization board of PoS networks at https://t.co/tkeJUdrIQZ:

@Cardano $ADA 24 (24)
@Algorand $ALGO 11 (11)
@Aptos $APT 18 (18)
@cosmos $ATOM 6 (6)
@AvailProject $AVAIL 35 (35)
@avax $AVAX 25 (25)
@agoric $BLD 5 (5)
@BNBCHAIN $BNB 7 (7)
@Polkadot $DOT 171 (171)
@MultiversX $EGLD 9 (9)
@hedera $HBAR 10 (10)
@JunoNetwork $JUNO 7 (7)
@0xPolygon $MATIC 4 (4)
@NEARProtocol $NEAR 12 (12)
@osmosiszone $OSMO 10 (10)
@PulsechainCom $PLS 12 (12)
@THORChain $RUNE 31 (31)
@SeiNetwork $SEI 8 (8)
@solana $SOL 20 (20)
@StargazeZone $STARS 9 (9)
@SuiNetwork $SUI 18 (18)
@CelestiaOrg $TIA 6 (6)
@Nano $XNO 12 (12)

The higher the Nakamoto Coefficient, the more resilient the network is.

How to read the chart:
$x: y (z)
x = network's native currency
y = curent Nakamoto Coefficient
z = previous Nakamoto Coefficient (snapshot taken every 6 hours)

#NakamotoCoefficient #KeepStakeDecentralized

[Staking Defense League @StakingDefense]

the social layer always undervalued -- as is the diversity that makes it valuable

[zak.eth @0xzak]

On August 15, 2010, Bitcoin broke.

A bug in Block 74638 created 184 billion BTC out of thin air. That’s not a typo. Two outputs of 92 billion BTC each slipped through because the code didn’t check for integer overflow. The system just accepted it. Bitcoin’s sacred 21 million cap? Completely ignored.

This wasn’t a theoretical flaw. It actually happened. And it proved something most people still don’t understand.

Bitcoin’s scarcity is not protected by code. It’s protected by people.

The only reason Bitcoin didn’t die that day is because someone noticed. A fix was pushed. A patched client was released. Nodes upgraded. Within five hours, the invalid block was erased from consensus. Bitcoin’s monetary policy was rescued, not by the protocol, but by the humans running it.

That’s the truth behind the “trustless” narrative. Code did not save Bitcoin. The community did.

Scarcity was never a guarantee. It was a fight. And it still is.

[Staking Defense League @StakingDefense]

📣

[vitalik.eth @VitalikButerin]

We should talk less about public goods funding and more about open source funding

https://t.co/49yzI429C6

[Staking Defense League @StakingDefense]

🐋 Day 11: Myth-Busting Decentralized Storage!

Let’s dive into common myths about decentralized storage—and set the record straight with specifics:

Myth: "Decentralized storage is too slow for practical use."
Reality: Walrus Protocol leverages advanced erasure coding (aka "Red Stuff"), which divides data into encoded fragments across multiple nodes. This means data retrieval can match—and often outperform—traditional cloud services by fetching fragments simultaneously from multiple nodes, optimizing speed and reliability.

Myth: "It’s not secure enough for sensitive data."
Reality: Walrus ensures robust security by encrypting and splitting your data into multiple encoded shards, distributed across decentralized storage nodes. No single node stores the entire data set, significantly reducing attack vectors compared to centralized servers—where a single breach can expose everything.

Myth: "Only blockchain experts and developers can use it."
Reality: While Walrus is built on advanced tech (integrating smoothly with the Sui blockchain), it prioritizes usability with intuitive tools, clear documentation, and straightforward APIs. Whether you're a seasoned dev or exploring decentralized storage for the first time, you’ll find easy entry points to start building immediately.
Heard other myths or misconceptions? Drop them below, and let’s debunk together! 🛠️🔎

#WalrusCountdown #DecentralizedStorage #SDL

[Staking Defense League @StakingDefense]

@0xTPT @WalrusProtocol @ChainflowPOS @atalma_io @0xTuDudes Legends all

[Staking Defense League @StakingDefense]

yield for me, not for thee

[toly 🇺🇸 @toly]

The yield prohibition is lame af

[Staking Defense League @StakingDefense]

Day 12: WE ARE LIVE

[Walrus 🦭/acc @WalrusProtocol]

The time is now: Walrus Mainnet is officially LIVE.

We’re here to fundamentally transform how apps use and engage with data — empowering you to do more with your data, blob by blob.

Ready to build? Go 👇
https://t.co/h2zJNbAL1T

[Staking Defense League @StakingDefense]

🐋 Day 13: Walrus Countdown – How the Sui Blockchain Enhances Walrus Protocol 🐋

Today we're exploring the unique role that the Sui blockchain plays in powering the Walrus Protocol, specifically highlighting technical aspects that set it apart from traditional decentralized storage networks.

🛠️ Sui Highlights for Walrus:

Object-centric Storage: Lightning-fast data retrieval and updates.

Scalable Throughput: Seamless growth to support heavy workloads and increasing user demand.

Secure Transactions: Move programming language for rigorous security against common exploits.

This marks the first decentralized storage protocol built on the latest version of high throughput blockchains, we're excited to see how it addresses the issues that have plagued decentralized storage over the years!

#30DaysofWalrus #SuiBlockchain #WalrusProtocol

[Staking Defense League @StakingDefense]

topical

[Matthew Green @matthew_d_green]

You should use Signal. Seriously. There are other encrypted messaging apps out there, but I don’t have as much faith in their longevity. In particular I have major concerns about the sustainability of for-profit apps in our new “AI” world.

[Staking Defense League @StakingDefense]

🐋 Day 14: Archival Storage – Protecting Our Digital Heritage

Archival storage is about securely preserving data over extended periods—often decades or generations. But traditional digital storage systems have repeatedly failed, leading to permanent loss of cultural and historical data.

Why decentralize archival storage?

Built-in redundancy:
-Decentralized storage splits files across multiple independent nodes, eliminating single points of failure.

Cryptographic integrity:
-Data authenticity is ensured through cryptographic verification, protecting archives from unauthorized changes.

Future-proof access:
No risk of vendor lock-in, sudden shutdowns, or pricing hikes, preserving long-term access to your data.

Real-world cautionary tales:

Myspace Data Loss (2019):
A botched server migration erased over 50 million songs uploaded from 2003–2015, permanently wiping out countless original works from emerging artists.

Google+ Shutdown (2019):
Google's sudden closure deleted years of user-generated content, posts, and discussions—erasing a vast snapshot of digital culture and personal history.

Vine Closure (2017):
Twitter abruptly discontinued Vine, and while some popular videos were preserved elsewhere, millions of creator's videos vanished permanently, taking a unique moment of internet history with them.

Decentralized archival storage isn’t just technical innovation—it’s a safeguard against the digital extinction events of our past.
#30DaysOfWalrus #ArchivalStorage #DecentralizedStorage #StakingDefenseLeague

[Staking Defense League @StakingDefense]

Glad to see good news for @TornadoCash. However you feel, Crypto is and always will be a forcing function for our social contract and the debate around freedom, privacy, and security.
https://t.co/ZiIeN5HFq2

[Staking Defense League @StakingDefense]

🐋 Day 15: Quick Recap – WAL Tokenomics Explained 🐋

Missed the WAL tokenomics announcement? Here's your 30-second breakdown:

Supply: 5 Billion WAL total; 1.25 Billion at initial circulation.

A 10% subsidy pool will be used to help incentivize and maintain pricing, but Walrus' burn token mechanic will be interesting to see tested in the wild.

Learn more here: https://t.co/mipJr9Zkhs

As projects like Chainlink have learned, pricing data in tokens creates natural volatility--a responsive validator set kept honest by an engaged community will help maintain equilibrium.

Very excited for launch next week!

[Staking Defense League @StakingDefense]

More governance discussion plz

[Chorus One @ChorusOne]

https://t.co/a34fWkspVt

[Georgios Konstantopoulos @gakonst]

hiring one Reth Core Dev -- this is a unique opportunity to work with me & under direct mentorship from @r_krasiuk on upgrading Ethereum. responsibilities would be 100% time spent on core protocol development. cash/equity.