ethdo VS consensus-specs

You can check the parameters you are sending to the Abyss contract and makes sure the withdrawal_credentials field contains your withdrawal address(es). Pick one of the successful transactions on the Abyss contract on etherscan and then click show more details. Then press the "Decode Input Data" button and you can see withdrawal_credentials details. So you can check these fields in Meta Mask (or your hardware signing wallet) to make sure this field is set with your correct withdrawal address(es). If you want to check the entire message is correct, then you can use a tool like ETHDo.

You should contact staked.us support. You cannot configure the derivation path with Wagyu Key Gen. It uses the default and most common derivation path. ethdo is a tool that can be used to use a custom derivation path. See https://github.com/wealdtech/ethdo/blob/master/docs/usage.md

ethdo still works fine for creating wallets.

No. ethdo can. See https://github.com/wealdtech/ethdo/blob/master/docs/usage.md

https://github.com/wealdtech/ethdo/blob/master/docs/changingwithdrawalcredentials.md here you go, ethdo is perfectly legit, but also very powerful tool, be careful and godspeed

It looks like the the 'Advanced Operation' of ethdo lets you change your validators' withdrawal credentials individually.

I think its 1 million: https://github.com/ethereum/consensus-specs/issues/2137

how "radically decentralized" the development of the Ethereum core is. In the past half a decade only 133 devs have contributed to Ethereum source code. 2 devs have written 25% of the code. The first 10 developers have written 70% of the Ethereum code. Consensus specifications the ones that all the clients implement. Half are Consensys employees https://github.com/ethereum/consensus-specs

I think this will be defined here: https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/fork-choice.md

Clients dependent on Consensys core and ETH management repo. A client is just the implementation directed by Consensys written in a different language. Fact is about 10 developers are the only reason those clients will update with staking. https://github.com/ethereum/consensus-specs

Exits are processed at 7 per epoch (currently). There is no queue for withdrawals. See https://github.com/ethereum/consensus-specs/pull/3068

https://github.com/ethereum/consensus-specs/blob/dev/specs/p...

For that, we have to take the vanilla deposit contract from the consensus specs: deposit_contract.sol, get the Solidity compiler version 0.6.11, compile the binary of the runtime part, and create an empty deposit tree.

The PoS consensus specification