cosmos-sdk VS rust-libp2p

This is a old known issue called "clipping" in the Cosmos SDK that happens when a validator was previously jailed and slashed: https://github.com/cosmos/cosmos-sdk/issues/5282

💡 GasMultiplier Instead of specifying the gas price, you may use the "gas": "auto” so that the blockchain application automatically estimates gas for you before submitting the transaction into the network for consensus with the estimate. This is why we include the gasMultiplier. By providing the gas multiplier you are specifying that the gas estimate should be multiplied by this number to account for possible changes in the gas fee estimate and the eventual gas fee. See The estimate is not always the exact gas required for the transaction execution.

Shido is now listed on cosmos.network. Shido Chain is interoperable with all chains and dApps in the Cosmos for value sharing and joint liquidity through the IBC Protocol.

We have pinned this post to bring information front and center on the Cosmos Network Project and its evolution into the Internet of Blockchains. A new Interchain Era is here, bringing interoperability, scalability, and mass adoption to the Cosmos Ecosystem!

Cosmos (ATOM) is a dPoS blockchain. Often it is named in the list of 3rd generation blockchains like ADA, DOT, ALGO, etc. As one can already see it has a lot of competition. To be able to get a better view of ATOM it is to not describe what it is in itself but how it compares to its competitors.

The cosmos.network website is not indexed by Bing. Someone noticed this and created a scam website my-cosmos[.]network which is ranking very high for the search term "cosmos network"

Upgrade Cosmos-SDK to SDK v0.44 from SDK v0.42 For a full list of updates in Cosmos-SDK v0.44.3 please see its changelog. Noteable highlights include:\n - Authz - Allows granting arbitrary privileges from one account (the granter) to another account (the grantee). \n- New modules:\n - Bech32IBC - Allows auto-routing of send msgs to addresses on other chains, once configured by governance. Allows you to do a bank send on Osmosis to a cosmos1... address, and it is automatically sent to the corresponding Cosmos Hub address over IBC. This is a big step in enabling more seemless IBC UX.\n - TxFees - Enables validators to easily accept txfees in multiple assets, whitelisted by governance, by declaring minimum fees in OSMO. Alternative fee assets are converted to their OSMO value, using the spot price on their primary OSMO base pair pool. This upgrade pre-whitelists all the assets currently supported on the Osmosis frontend with an OSMO basepair pool.\n- Implements Proposal 32 - Clawback of unclaimed Osmo and Ion on airdrop end date. (December 15th, 5PM UTC)\n- Upgrade IBC from a standalone module in the SDK to IBC v2. This improves the utility of Ethereum Bridges and Cosmwasm bridges.\n- Blocking OFAC banned ETH addresses \n- Numerous minor bug fixes, gas fixes, and significant speedups.

Instead of just imagining, Cosmos created a system that enables blockchains to connect. That system thrives on a hub - Cosmos Hub.

Substrate and Lighthouse use libp2p as a networking stack for communication between nodes. The libp2p framework is a versatile modular peer-to-peer networking stack. It provides a collections of abstractions, mechanisms, and protocols for facilitating communication in P2P systems. In particular, libp2p supports multiple transport mechanisms (TCP, QUIC, WebSocket, WebTransport, etc.), encryption schemes (TLS and Noise), and stream multiplexing. Higher-level protocols in libp2p are implemented on top of reliable, ordered, bidirectional binary streams, which are transparently encrypted and multiplexed by the framework.

It's a peer-to-peer "engine" with switchable components. Seems to run on different platforms (browsers, mobile, desktop, server).

At a glance, it looks pretty much like libp2p (https://libp2p.io/) but seems to integrate with libp2p as well (meaning you should be able to use Bifrost on one end, and libp2p on the other), so I'm guessing there is at least some fundamental difference, but I cannot spot it. Seems to use slightly different terminology compared to libp2p.

ComposeDB is a graph database created by 3BoxLabs, a company well-known in the Web3 ecosystem for their work on decentralized identifiers (DIDs) and their main product the Ceramic network. Ceramic is a network of nodes that store and share composable data streams on top of libp2p, the network stack that also powers IPFS.

Yes, there is already a Rust version (https://github.com/libp2p/rust-libp2p) that behaves well at this level but I think we can reach a higher level of performance on this point with Zig. Also, if you look at the long term roadmap of libp2p (https://github.com/libp2p/specs/blob/master/ROADMAP.md), the mobile devices and IoT integrations for example are part of the considerations.

libp2p

At Filecoin Foundation, we see the technologies in the Filecoin ecosystem offering rock-steady stepping stones to this better future. Libp2p lets individual users find and talk to each other, without needing central servers. IPFS gives new services a way to find data, wherever it is stored — freeing them from dependence on one social media company over another and letting users move from one service to another. The Filecoin network itself, with incentivized storage, not only provides a provably stable basis for hosting content, but also shines a light on the kind of incentive systems that will enable independent social media to sustain and provide for itself for the long run, without relying on the largesse of the current tech giants.

Maybe https://libp2p.io

So, after rolling my eyes and saying to myself 'not another web3 protocol', I began to understand the need for something new that not only takes advantage of the cutting edge in peer to peer networking but also acknowledges the fact that the client-server architecture is also not going away (which is incredibly important in a world full of low-powered, embedded devices).