protocol VS consensus-specs

🏀 Enzyme Finance - actively managed crypto funds (or ‘vaults’) with open track records and strategies for different risk tolerances

Enzyme is what you're looking for: https://enzyme.finance/

Cross-chain-compatible Vaults / Asset Management - Enzyme (https://enzyme.finance/) runs on Ethereum / Polygon, so this niche is a bit taken, but cross-chain vaults can be implemented with a non-tradeable vault-intrinsic token (or tokens). That is, the vault can still run on one chain and implement tokenized versions of strategies that any PM is taking. Enzyme is fairly limited due to only covering Ethereum DeFi.

Check out Enzyme (formerly known as Melon). They've been working on this for years.

If you are holding long term you can potentially earn more by staking it (it allows others to leverage it and pay you interest). It what exchanges do when you leave your crypto with them. There are still RISKS and I personal I don't do any of that. One place to start learning about it is https://enzyme.finance, I have a friend that runs a fund on their platform. There are others out there, this just happens to be the one I know about.

Thanks for information. I really don't know much about Mai. The system I propose doesn't transfer token to user wallet but it transfer to a secure fund where user can do anything he wants: like enzyme.finance. It will be really combination of aave protocol and enzyme without interest but profit sharing.

You could invest in one of the funds at enzyme.finance. You delegate your funds into a vault (smart-contract) managed by someone else but everything remains very much transparent and you can exit at any time.

Enzyme (MLN #332 CoinGecko 164M$ Mcap) - https://enzyme.finance/ - Enzyme is a decentralized asset management infrastructure built on Ethereum. Using Enzyme Smart Vaults, individuals and communities can build, scale and monetize investment strategies. - Enzyme empowers you to build and scale vaults based on the investment strategies of your choice like ETFs and markets. - Main product: https://app.enzyme.finance/depositor/leaderboard

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