cosmos-sdk VS gaia

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.

Cosmos Hub Validators can get up to speed with the upgrade process : HERE

Follow the development: HERE

https://github.com/cosmos/gaia/branches/active

You for example go to the official source repository of cosmos, which is https://github.com/cosmos/gaia/releases, and get the official CLI client. You can use that to create a AUTHZ transaction which you sign on your ledger. It’s the same transaction you can sign with yieldmos or RestakeApp and Keplr as soon as the UI is updated. It’s just a limitation in the UI that we need to use the CLI for now. You never enter your seed in the CLI if you use a ledger.

If you’re talking specifically about the “Composable Parachain”, the Cosmos equivalent is Interchain Security which is set to launch imminently https://github.com/cosmos/gaia/blob/main/docs/interchain-security.md

Cosmos is actually one of the harder chains to validate because of its heavier system requirements (https://github.com/cosmos/gaia/issues/704), and since it doesn't enforce any minimum commission rates, so validators are pushed to offer lower (even negative!) rates to attract delegations to stand out in this relatively large 175 active set.

for over six months I have been reporting that there are issues with interchain foundation delegations on the cosmos hub. Trying to report this has led to retaliation-- the first person I reported this to was Billy, and he attempted to use the contributors covenant (contributorcovenant.org) to remove me from cosmos during proposal 69. He said I tweeted too much. To the best of my knowledge I'm the sole validator trying (https://github.com/cosmos/gaia/pulls) to make code contributions to the hub.

I recommend reading the Interchain Security Litepaper for more info on V1-3, and the rationale behind some design decisions.

Cosmos Hub Bloat: Fat Gaia by Jacob Gadikian, Notional Validator The main bloat here comes from future dapps that have been approved by governance. The extra load on the Hub would increase the RAM usage, upkeep cost, and system requirements for validators Could possibly increase barrier to entry for new/independent validators

I learned about what I said in #3 from a short discussion with one of the devs. More generally, here's the interchain security litepaper.