There is no foolproof security, but there are very few chains that go this far to protecting your privacy.
Most "decentralized" applications have admin based backdoors.
With @secretnetwork you know your code will run on a platform that is designed against surprise backdoors.
The key is switching from MRSIGNER to MRENCLAVE.
MRENCLAVE prevents anyone, even with full access to the Secret Network source code, from running a backdoor version of the network.
Enhancing security always has the risk of "locking yourself out" making the chain impossible to restart after a bug.
Secret Network developed features to allow recovery, but only in a decentralized manner with validator agreement.
Congratulations to @SecretNetwork for completing a very technically challenging upgrade without trouble.
Chill Validation has awaited this security upgrade for years.
This upgrade makes the chain harder to "debug" for everyone, especially bad actors.
forum.scrt.network/t/secret-…
Chill Validation looks forward to @union_build on @babylonlabs_io
Diversify your delegation by staking part of your holdings with Chill Validation on Babylon
Cosmos Hub ⚛️ @cosmoshub 5 Mar 2025 Article The Vision for the Cosmos Hub in the Post-Interop World On the Cosmos Hub, IBC v2, and IBC Eureka. Bridges are everywhere. They were physical first, but now we generally talk about them within a digital context. The Ottomans built the Galata Bridge to
Jackal Radio #02 - The Jackal Outpost, Web3 Storage & The Future of Data Monetization
(00:09) Jackal Quick Connect Explained
(00:50) The Jackal Outpost
(01:57) How does The Jackal Outpost work? – A breakdown.
(05:06) The Jackal Outpost, a distribution advantage (06:32) Base Outpost Launch & Future Outpost Launches
(07:40) Why EVM First? – Understanding the strategy behind targeting EVM chains.
(10:09) Elastic Storage Payments – How Web3 storage plans can integrate with smart contracts.
(12:43) DAOs & Community-Powered Storage – How decentralized groups can fund data storage.
(14:34) Data Storage for AI Agents – Can AI pay for its own memory? Let’s talk automation.
(15:12) Jackal Pin: A Decentralized IPFS Pinning Service – A new app from Jackal Labs.
(17:26) Who Uses Jackal Pin vs Quick Connect? – What's the difference?
(19:36) Who will use Jackal Pin? – Who do we think will be the initial users of Jackal Pin?
(23:55) Plans for Jackal in 2025, and beyond.
(26:27) Digital Twin – Aggregating your personal data for real-time AI insights.
(28:08) Data Pools: The Next Economy – How you can opt-in to sell your data on your terms.
(33:20) Scaling Jackal Beyond Storage – Jackal’s path to becoming something greater.
(34:54) Jackal's Data Monetization Possibilities – How Web3 users can generate revenue from their own data.
(42:28) Cleaning the Data? Warehousing the Data? (48:06) Why would people choose Jackal for their data?
(55:46) How will the chain scale? – Expanding Jackal as more data storage is needed.
(01:16:00) Jackal Labs' Goals
(01:18:15) Who made it to the end? – If you made it this far, we salute you.
The top validator does not work 700x harder than the bottom honest validator yet gets 700x the rewards.
Why should we starve honest validators if they deliver the same results?
Eliminating good teams does not improve the Cosmos.
We see the @cosmos_sdk team working hard to improve p2p.
Improve network technologies instead of cutting honest validators. We value smaller teams who know what they are doing.
There is too much inflation going to the top and not enough going to the bottom. Inflation to the top should be reduced and given to the bottom.
Validators who "assume" the identity of another validator or sybil should be excluded.
Perfection unnecessary. Improvements first.
Chill Validation votes against reducing validator set size for @osmosis.
Taking a bad reward structure resulting from poor delegation incentives to punish lower validators makes no sense.
Osmosis should innovate better and smarter rewards.
Users who want privacy are willing to learn how to achieve it.
Using a different cointype or different seed phrase will get you a new address.
But only cointype 60 aligning with EVM will accomplish ease of use.
Most degen users want ease of use. Many Dapps expect wallets to give the same address on multiple blockchains.
Chill Validation has helped numerous users recover funds sent to wrong addresses and standardizing on 118 prevented most new problems.
But what about privacy?
Different cointypes for each network means different addresses for each chain. This gives users privacy.
However, in general usage, users want bridging and airdrops to the "same" address (not private).
Give users ease of use by default and privacy by choice. Why?
Make cointype 60 the new default and allow OG users to select cointype 118. Migration as a service is not necessary. Long term, support smart wallets with mutable signers (authtx but not for nerds).
Why do validators wait around making no blocks? It's because we wait for validators with large delegations to get ready. There is no technical need for this stall.
Spread out your delegations and increase your chain uptime.
Recent Neutron Halt Details.
hadron.notion.site/Post-mort…
I’m incredibly excited to join Interchain Inc. and to work with the talented team from Skip!
I’m humbled to have the opportunity to contribute even more to #Cosmos ⚛️
$ATOM is the heart of the open decentralized internet!