-
ETH-Staking-Service-22Cap-Signaling
List of Staking Providers Who Have Publicly Signaled to Cap Validator Control at 22%
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Quick update since last night. What started with just Stakewise now has Rockepool and Swell Network publicly committing to keep their Validator share under 22% of the network! Progress can be tracked here - https://github.com/BobRossiETH/ETH-Staking-Service-22Cap-Signaling
u/superphiz made a post 'yesterday' (yup, that time of night where it's technically yesterday but I didn't sleep and it's way past my bedtime) about asking staking entities to limit validator control to 22% of the network. I decided to make a GitHub list inspired by https://github.com/ethereum-cat-herders/1559-outreach/blob/main/README.md to track entities that have committed to the 22% limit.
https://iancoleman.io/bip39/ (always use offline, obvs)
In theory it's all sound and legit. But in reality there's the usual question of how it actually gets implemented in practice. Just like any other smart contract, there's the possibility of bugs/exploits, or sneaky devs upgrading the L1 contracts to disable the escape hatch before L2 sequencers turn evil, etc. In their current beta form a lot of rollups today lack this option but are working towards it (see the risks of individual rollups when it comes to withdrawing funds or how one could be censored on l2beat)
