osmosis VS ibc

For more details about the v16 upgrade, including new modules, features, and improvements, check out the changelog https://github.com/osmosis-labs/osmosis/blob/v16.0.0/CHANGELOG.md

Osmosis has something similar: IBC rate limiting

Was looking through the documentation for https://github.com/osmosis-labs/osmosis/tree/main/cosmwasm/contracts/crosschain-swaps and saw that the proposal on Osmosis has already passed: https://www.mintscan.io/osmosis/proposals/454

This proposal proposes that the chain elect to do a software upgrade to the v5.0.0 software tag of the Osmosis codebase on block height 2383300. The timing of this upgrade is crucial to properly execute the Proposal 32 airdrop clawback. This clawback should happen right at the Airdrop end date of December 15th 5PM UTC, thus this upgrade must execute before it.

See more in the changelog

PR in the tweet: https://github.com/osmosis-labs/osmosis/pull/2334

If you ever want to check a project is not just image then head to their github activity https://github.com/osmosis-labs/osmosis/commits/main

There's really no unauthorized access to the code, as the Osmosis chain source code is open source: https://github.com/osmosis-labs/osmosis

Curious to dig more into the Cross-Chain Validation concept?Feel free to explore the docs.

Additional Tasks that were not tied to any specific phase included testing various misbehavior scenarios (getting slashed for downtime or double-signing), auditing ICS validator set replication (Find a consumer chain validator set that has not existed in the provider chain or has been received in the wrong order) or trying to break the correct behavior assumptions of the ICS-28 spec

Upgrade IAVL proof verification to ICS23 spec.

Syncronous IBC sounds like request-response similar to IBC Query proposal (https://github.com/cosmos/ibc/pull/735 ) Is it that one? But it still on draft proposal status to protocol, it is far away from implementation

Some old threads: https://github.com/cosmos/ibc/issues/411

I believe this is also why there are developments going underway to help incentivize IBC relayers. https://github.com/cosmos/ibc/tree/master/spec/app/ics-029-fee-payment to help pay relayers with fees, Evmos intentionally cutting the gas needed for certain IBC operations in half, the IBC packet forwarding middleware can offload TXs to more well-funded validators on Cosmos ... etc etc.

Sending NFTs cross-chain (https://github.com/cosmos/ibc/pull/615)

Both generic smart contracts, DeFi, and NFTs can be built on a platform like that, specifically for DOGE, or fully interoperable through Cosmos IBC on a generic chain that a Dogecoin peg zone would then connect to.