Big update for @Stakingverse and LUKSO staking.
We are currently onboarding a new node operator: @DevM8B.
By taking this step, we are unlocking staking capacity on LUKSO responsibly, while strengthening decentralization, client diversity, and network resilience.
Stakingverse has grown into a major part of LUKSO staking. That is good for $LYX holders, but it also means we need to be responsible about concentration. We do not want Stakingverse-controlled infrastructure to become too large a share of the network.
By working with M8B as an additional node operator, we can increase staking capacity while improving validator and client diversity.
M8B has been active in blockchain, DeFi, and node operations for years, and has worked across multiple projects in Web3. We have also worked with M8B for years and have full confidence in their technical expertise, reliability, and operational discipline.
M8B has also been an advisor to Stakingverse since day one. They have been involved from the early stages, so this is not a random new operator relationship. It feels like a logical and trusted next step with a team that already understands Stakingverse, LUKSO, and the standards we want to maintain.
M8B will operate under the Stakingverse setup, so the liquid staking token remains the same: $sLYX. Users will not need to switch to a different liquid staking token or fragment liquidity across multiple staking derivatives.
A key part of this onboarding is client diversity. M8B will run node clients that are currently underrepresented on LUKSO, and in any case different from the clients used by the existing Stakingverse setup. This helps reduce correlated risk and contributes to a more stable network.
We believe it is important that $LYX holders have access to staking. LUKSO staking should not stay blocked for any longer, for the sake of the network.
That is why we are taking this step carefully:
• experienced node operator
• new operator infrastructure
• better client diversity
• shared $sLYX liquidity
• phased capacity increases
• safety-first onboarding
We expect to start next week by opening the first 1 Million $LYX of new staking capacity in batches.
More details will follow as we progress.
And we’re fully filled again within just a couple of minutes 🚀
Around 1 million $LYX has now been deposited into @DevM8B validators.
The network activation queue for these new validators is currently estimated at around 24 days. Before then, we’ll share an update on how we plan to proceed from there.
No worries, staking will open up again one way or another. Stay tuned 👀
My PR for the @ethPandaOps Dora explorer was merged into master today.
It adds a validator dashboard based on withdrawal address / withdrawal credentials, plus filtered validator and activity views. So you can monitor validator sets tied to one withdrawal address instead of checking them one by one.
I will make sure to get this live for LUKSO this week, so validators can track their validator setup from the explorer again.
https://t.co/qUzettOAwF
100K more $LYX was just staked at Stakingverse and flowing into validators operated by @DevM8B!
Stakingverse is now also fully integrated in the activity feed on https://t.co/1H1GEQIdAE
Did you know this repo is public and you can integrate it on your own website and contribute to it?
Check it out:
https://t.co/at2WD5guXE
We're now running validator nodes on @lukso_io as a node operator for @StakingVerse.
Advisors from day one. This is what that trust looks like in practice.
Client diversity improves. Correlated risk drops.
#LUKSO#Staking#NodeOperator
The LUKSO Network is probably the only network next to @ethereum that has such a client diversity
(See second image).
Thanks to the ethereum node developers and their support from the @ethereumfndn 🙏
With 170k validators and the size of the network, @lukso_io is quite decentralized. Making it the ideal layer for profiles, identities and culture.
(Note: Currently the @Stakingverse pool is larger, but @DevM8B will be adding more validators, so that will decrease the portion stakingverse will have)