gaia VS gno

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.

The Portal Loop is an effort to create a continuously-deployed staging testnet to be hosted on the official gno.land website. The testnet will be reset at each commit on our repository, but it will re-play all the transactions from its previous version, dropping any that might fail following breaking changes in the code. The Portal Loop will provide a central place where you can experiment with the latest Gno.land updates, resolving the problem our existing testnets have faced (becoming stale only a few months after their launch) while also paving the way for building DAOs and on-chain Game of Realms and Proof-of-Contribution systems.

There is an ongoing issue 683 open here and we have continued to work on enhancing stack/frames development over the last month. We’re adding a new function in the standard library std.PrevRealm (previously GetRealmCaller). Currently, we only have GetOrigCaller, which returns the user calling the first realm. This is not secure and we need a way to call the previous caller. This will allow a realm to handle GRC20 treasuries. See issue 667 and issue 634 for further details.

The incentivized competition to find the best contributors to Gno.land continues in phase one, with slow but steady progress being made. Nir1218 initiated an Evaluation DAO Kickoff discussion in issue 792 to initiate testing code for the key smart contract infrastructure that will power the Gno.land platform. We are also interviewing architects for the core team with experience in governance modules and creating new economies on-chain, and a new DevRel team member will be joining us soon to create awesome tutorials and documentation to advance Game of Realms further. Gno.land must be built by the community and we will not rush to push Game of Realms to the second phase until we have found quality contributors to complete the challenge tasks and become the platform’s first founding members.

Hi Brandon, Great chat today. Your focus on challenges like upgradability aligns with our goals, although v1.0 won't support dynamic calls. We need inventive minds for new patterns. Remember, we're considering several upgradability improvements: - Unix-symlink/git-sha1 aliases (https://github.com/gnolang/gno/issues/694) - Built-in single-tx migrations - UI experiments from contracts (https://github.com/gnolang/gno/tree/master/examples/gno.land/p/demo/releases) - Webui enhancements - Restricted contract patching - Local IBC (async dynamic calls) Looking forward to improving Gnoland together. Best, Manfred

You should check out Gnoland https://gno.land/

website: https://gno.land/

Firefox detected a potential security threat and did not continue to gno.land. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.

GNO (gno.land) on Cosmos says they would tackle this issue of sending coins to a wrong address. How? no idea.

GNOLand

The Peace.md (https://github.com/gnolang/gno/blob/master/gnoland/docs/peace.md) isn't great either when it starts with: