anchor VS eos

here is the link: https://greymass.com/anchor/

Just import Your Private Key on Anchor Wallet (https://github.com/greymass/anchor/releases) and than You can move token or unstake them without problem

I did not pay any money, first I created the account on https://wallet.telos.net/ (Saved my private key information) then downloaded Anchor https://greymass.com/anchor/ and imported my private key. All without paying anything.

4 - import the backup of Scatter on Anchor Wallet (use the same password of Scatter to access Your wallet on Anchor wallet) (https://github.com/greymass/anchor/releases)

Just download Anchor Wallet https://greymass.com/anchor/, insert your private key and you will have access...

Best to use https://github.com/greymass/anchor/ instead of Scatter.

Now that I'm getting started, I see that the [eos github repo](https://github.com/EOSIO/eos) is labeled as a public archive. What is the meaning behind this? Is the project no longer maintained? Is the codebase now somewhere else? This doesn't exactly inspire confidence as a new developer.

First up, you need to use more than just the master branch, which is appears is what you're doing. Developers use repositories in different ways (unfortunately) and this makes it hard to benchmark. You said there was 0% retention of developers and no activity, and as an example of how that number is inaccurate I'd point you to heifner's profile on github. You can see within the last few days he's both created code, issues, and been managing pull requests. Scroll back to 2019 and you'll find him contributing to the core codebase. If you continue to look through the top contributors on the eosio/eos repo you'll continue to find more of the top developers are actually active and developing on the project.

You're not interpreting the commit history correctly because you're not looking at all of it. See here: https://github.com/EOSIO/eos/branches

Compare that to EOS. They havent had much updates for the past 2 months here.

B1 left the (token = mainnet) community, and there probably never was a big developer community beside B1 and the block producers which tried to push the mainnet repo forward. Development happens at EOSIO but this is not the mainnet and not the token!

Having the same issue, any luck fixing? Otherwise talking to devs or waiting for a fix seems to be the only ways to get it working. It's clearly a server error, most likely coming from EOS VM engine, most likely somewhere from these lines (or their equivalent in a custom implementation): https://github.com/EOSIO/eos/blob/master/libraries/chain/apply_context.cpp#L134

EOSIO IBC code is completed by block.one devs and open sourced: https://twitter.com/bytemaster7/status/1366580996389404672 Simply put, allows a fully validating node to sign the action merkle root of a block it fully validated and then publish that signature over AMQP for other components to consume and act upon https://github.com/EOSIO/eos/pull/9122#event-3380150510