isidorosp

> I think this cuts to the heart of the issue. Any attempt to socialize block production rewards by anyone other than the block producer can be pretty easily worked...

@LefterisJP bumping this after our convo in Paris, also to note that Lido currently supports the following networks: Ethereum, Polygon, Solana, Polkadot (via Moonbeam), Kusama (via Moonriver). I'm sure that...

> > @LefterisJP bumping this after our convo in Paris, also to note that Lido currently supports the following networks: Ethereum, Polygon, Solana, Polkadot (via Moonbeam), Kusama (via Moonriver). I'm...

@Jstar101 Does the stakewise DAO control the validator exit signatures? I thought it was a committee. Can the DAO (i.e. an onchain vote of token holders) trigger a validator exit,...

Cross-posting my thoughts here from the discord thread: --------- In my personal opinion there is no strictly trustless on-chain staking protocol currently (my view may be a bit unorthodox, but...

> Ensuring a committee, acting under instruction from a DAO, can force close validators and regain access to pool funds is a clear winner here in my opinion. Granted, the...

> Service does not require trusting any humans to custody your keys or distribute rewards. Contract upgrades or forced validator exits may be handled by a DAO, but cannot rely...

@LefterisJP bumping this as it's something LEGO is still interesting in supporting!

Other things that could be tracked via an activity feed: * Internal rotki events (adding / editing / deleting master data e.g. blockchain accounts) (in general a full log of...